February 28, 201610 yr Does this plugin currently have a way to offset/correct a temp value? I know my temp is off by 30 degrees. So I just have to remember to subtract that the value shown but if its possible to have an offset that would be great. Unless I'm just one of very few that is unlucky enough to have sensors that don't report correctly. I've never tried this, so can't guarantee anything. Manually edit your sensors.conf (/boot/config/plugins/dynamix.system.temp/sensors.conf), and add the line "compute temp9 (@-30),(@+30)" just below the line with the faulty temp. Replace temp9 with your raw temp name. I don't know, but you may need to reboot. For example, # sensors chip "acpitz-virtual-0" label "temp1" "CPU Temp" compute temp1 (@-30),(@+30) chip "k8temp-pci-00c3" label "temp1" "MB Temp" For more info, see the following links - http://linux.die.net/man/5/sensors.conf https://www.opennet.ru/man.shtml?topic=sensors.conf&category=5
February 28, 201610 yr I have a SuperMicro C2SEE motherboard and have followed all the steps in the wiki, but when I go to Settings > TempSettings and tap the Detect button, nothing happens. The page reloads, but there is no visible change. When logged in via SSH, running the `sensors` command accurately shows the MB and CPU temps as `temp1` and `temp2`, respectively. So as far as I can tell, everything seems to be in order. Anyone have any suggestions for how I might troubleshoot this? You are positive that Perl is installed?
February 29, 201610 yr You are positive that Perl is installed? Well, it was installed when I ran sensors-detect, but it seems Perl is no longer present after rebooting. I just ran `installpkg /boot/packages/perl-5.18.1-x86_64-1.txz` again, uninstalled and re-installed the plugin, and now the aforementioned Detect button behaves as expected. Other than putting the Perl archive at /boot/packages/perl-5.18.1-x86_64-1.txz, is there something else that I need to do to ensure Perl is always available after reboots? Side note: I wonder if this has something to do with the order of steps, specifically when the plugin is installed. Unless I'm missing something, there's no mention in these docs at which point the plugin should be installed: https://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing
February 29, 201610 yr You are positive that Perl is installed? Well, it was installed when I ran sensors-detect, but it seems Perl is no longer present after rebooting. I just ran `installpkg /boot/packages/perl-5.18.1-x86_64-1.txz` again, uninstalled and re-installed the plugin, and now the aforementioned Detect button behaves as expected. Other than putting the Perl archive at /boot/packages/perl-5.18.1-x86_64-1.txz, is there something else that I need to do to ensure Perl is always available after reboots? Side note: I wonder if this has something to do with the order of steps, specifically when the plugin is installed. Unless I'm missing something, there's no mention in these docs at which point the plugin should be installed: https://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing Perl is one of the packages you can install from the NerdPack plugin.
February 29, 201610 yr You are positive that Perl is installed? Well, it was installed when I ran sensors-detect, but it seems Perl is no longer present after rebooting. I just ran `installpkg /boot/packages/perl-5.18.1-x86_64-1.txz` again, uninstalled and re-installed the plugin, and now the aforementioned Detect button behaves as expected. Other than putting the Perl archive at /boot/packages/perl-5.18.1-x86_64-1.txz, is there something else that I need to do to ensure Perl is always available after reboots? Perl is only needed temporarily when you want to run sensors-detect or use the Detect button, not needed after that, so there's no reason to keep it installed. Besides it's big, wastes memory. Side note: I wonder if this has something to do with the order of steps, specifically when the plugin is installed. Unless I'm missing something, there's no mention in these docs at which point the plugin should be installed: https://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing Yeah, that wiki page probably needs some updating ...
March 1, 201610 yr Hey, I'm about to install System temp. And have red the wiki and forum posts. I'm wondering where i can find the latest version of PERL which is correct for unRAID. I found a link in a forum posts for v.5.18.1 but I guess this is outdated now. Any help would be nice
March 1, 201610 yr Hey, I'm about to install System temp. And have red the wiki and forum posts. I'm wondering where i can find the latest version of PERL which is correct for unRAID. I found a link in a forum posts for v.5.18.1 but I guess this is outdated now. Any help would be nice unRaid NerdPack plugin
March 1, 201610 yr Ok thanks! so I can't choose only to install PERL I get the entire packed so to speak?
March 1, 201610 yr Ok thanks! so I can't choose only to install PERL I get the entire packed so to speak? No. You first install the plugin, and then go to Settings->Nerd Pack and select which of the available options you want to install.
March 1, 201610 yr Thanks, got it up and running now. I did detect -- load drivers -- and save. Now its displaying my cpu and MB temp! Kinda found the right sensors from the description and checked the BIOS for confirmation hehe
March 5, 201610 yr Does this plugin currently have a way to offset/correct a temp value? I know my temp is off by 30 degrees. So I just have to remember to subtract that the value shown but if its possible to have an offset that would be great. Unless I'm just one of very few that is unlucky enough to have sensors that don't report correctly. I've never tried this, so can't guarantee anything. Manually edit your sensors.conf (/boot/config/plugins/dynamix.system.temp/sensors.conf), and add the line "compute temp9 (@-30),(@+30)" just below the line with the faulty temp. Replace temp9 with your raw temp name. I don't know, but you may need to reboot. For example, # sensors chip "acpitz-virtual-0" label "temp1" "CPU Temp" compute temp1 (@-30),(@+30) chip "k8temp-pci-00c3" label "temp1" "MB Temp" For more info, see the following links - http://linux.die.net/man/5/sensors.conf https://www.opennet.ru/man.shtml?topic=sensors.conf&category=5 Finally got a chance to try this out. Works perfectly! Thanks Rob!
March 5, 201610 yr Does this plugin currently have a way to offset/correct a temp value? I know my temp is off by 30 degrees. So I just have to remember to subtract that the value shown but if its possible to have an offset that would be great. Unless I'm just one of very few that is unlucky enough to have sensors that don't report correctly. I've never tried this, so can't guarantee anything. Manually edit your sensors.conf (/boot/config/plugins/dynamix.system.temp/sensors.conf), and add the line "compute temp9 (@-30),(@+30)" just below the line with the faulty temp. Replace temp9 with your raw temp name. I don't know, but you may need to reboot. For example, # sensors chip "acpitz-virtual-0" label "temp1" "CPU Temp" compute temp1 (@-30),(@+30) chip "k8temp-pci-00c3" label "temp1" "MB Temp" For more info, see the following links - http://linux.die.net/man/5/sensors.conf https://www.opennet.ru/man.shtml?topic=sensors.conf&category=5 Finally got a chance to try this out. Works perfectly! Thanks Rob! Excellent! You are precedent setting here. I'm sure others can use this too.
April 18, 201610 yr lm-sensors.org is down -- has been for a few days. Is there anywhere else I can get sensors detect?
April 18, 201610 yr lm-sensors.org is down -- has been for a few days. Is there anywhere else I can get sensors detect? http://lime-technology.com/forum/index.php?topic=36543.msg430371#msg430371
April 19, 201610 yr would love to get this working but when I run Sensors nothing shows up. I can see my CPU temp thru IPMI but that it.
April 19, 201610 yr would love to get this working but when I run Sensors nothing shows up. I can see my CPU temp thru IPMI but that it. Might need a later version of sensors-detect... See 2 posts up
April 19, 201610 yr thanks but just way to confusing for me to figure out. right click on the link and save as to your flash drive then ssh in and chmod +x whatever_the_file_name_was[code] [url=http://lime-technology.com/wiki/index.php/Setting_up_lm_sensors_to_display_CPU/motherboard_temperatures_in_add-ons_such_as_SimpleFeatures]http://lime-technology.com/wiki/index.php/Setting_up_lm_sensors_to_display_CPU/motherboard_temperatures_in_add-ons_such_as_SimpleFeatures[/url] Need to also install NerdPack GUI and Perl from it.
April 19, 201610 yr Do I copy the "sensors-detect.txt" file to the root of the flash drive or put it in the plugins folder?
April 19, 201610 yr Do I copy the "sensors-detect.txt" file to the root of the flash drive or put it in the plugins folder? Anywhere. Its a one time thing to run.
April 19, 201610 yr Thank you, got it running. It only found the CPU Temp but that really all I care about. Would be nice to have others but don't need them. Is there anyway to get it to show up under "Dynamix System Statistics" plugin? Would be great to have everything in one spot
April 21, 201610 yr I am only getting this then I type sensors from a ssh session? Can anyone help me? What I have done: 1. Install System Temp 2. Install Nerd Pack and Pearl 3. SSH into my unraid server and run sensors root@Tower:~# sensors acpitz-virtual-0 Adapter: Virtual device temp1: +27.8°C (crit = +106.0°C) temp2: +29.8°C (crit = +106.0°C)
April 26, 201610 yr Is there a way to add in a plugin to the GUI that shows temps of everything My main concern is my video card , and SAS card temp, they were hot to the touch, and recently I have added a fan to them to keep them cool, but it would be great to know that actual temps Thanks
May 27, 201610 yr Can't seem to get this to work. In the plugin under drivers all I'm getting is the 'click detect', but it doesn't seem to do anything. I went through the sensor-detect script in order to get sensors working, and it seems to be outputting temps correctly... Any ideas? root@Tower:~# sensors -u acpitz-virtual-0 Adapter: Virtual device temp1: temp1_input: 27.800 temp1_crit: 105.000 temp2: temp2_input: 29.800 temp2_crit: 105.000 coretemp-isa-0000 Adapter: ISA adapter Physical id 0: temp1_input: 46.000 temp1_max: 80.000 temp1_crit: 100.000 temp1_crit_alarm: 0.000 Core 0: temp2_input: 46.000 temp2_max: 80.000 temp2_crit: 100.000 temp2_crit_alarm: 0.000 Core 1: temp3_input: 42.000 temp3_max: 80.000 temp3_crit: 100.000 temp3_crit_alarm: 0.000 Core 2: temp4_input: 44.000 temp4_max: 80.000 temp4_crit: 100.000 temp4_crit_alarm: 0.000 Core 3: temp5_input: 45.000 temp5_max: 80.000 temp5_crit: 100.000 temp5_crit_alarm: 0.000 nct6791-isa-0290 Adapter: ISA adapter in0: in0_input: 0.904 in0_min: 0.000 in0_max: 1.744 in0_alarm: 0.000 in0_beep: 0.000 in1: in1_input: 1.016 in1_min: 0.000 in1_max: 0.000 in1_alarm: 1.000 in1_beep: 0.000 in2: in2_input: 3.344 in2_min: 0.000 in2_max: 0.000 in2_alarm: 1.000 in2_beep: 0.000 in3: in3_input: 3.328 in3_min: 0.000 in3_max: 0.000 in3_alarm: 1.000 in3_beep: 0.000 in4: in4_input: 1.016 in4_min: 0.000 in4_max: 0.000 in4_alarm: 1.000 in4_beep: 0.000 in5: in5_input: 1.992 in5_min: 0.000 in5_max: 0.000 in5_alarm: 1.000 in5_beep: 0.000 in6: in6_input: 0.112 in6_min: 0.000 in6_max: 0.000 in6_alarm: 1.000 in6_beep: 0.000 in7: in7_input: 3.472 in7_min: 0.000 in7_max: 0.000 in7_alarm: 1.000 in7_beep: 0.000 in8: in8_input: 3.392 in8_min: 0.000 in8_max: 0.000 in8_alarm: 1.000 in8_beep: 0.000 in9: in9_input: 1.120 in9_min: 0.000 in9_max: 0.000 in9_alarm: 1.000 in9_beep: 0.000 in10: in10_input: 0.000 in10_min: 0.000 in10_max: 0.000 in10_alarm: 0.000 in10_beep: 0.000 in11: in11_input: 0.848 in11_min: 0.000 in11_max: 0.000 in11_alarm: 1.000 in11_beep: 0.000 in12: in12_input: 0.000 in12_min: 0.000 in12_max: 0.000 in12_alarm: 0.000 in12_beep: 0.000 in13: in13_input: 0.064 in13_min: 0.000 in13_max: 0.000 in13_alarm: 1.000 in13_beep: 0.000 in14: in14_input: 0.016 in14_min: 0.000 in14_max: 0.000 in14_alarm: 1.000 in14_beep: 0.000 fan1: fan1_input: 2890.000 fan1_min: 0.000 fan1_alarm: 0.000 fan1_beep: 0.000 fan1_pulses: 2.000 fan2: fan2_input: 1030.000 fan2_min: 0.000 fan2_alarm: 0.000 fan2_beep: 0.000 fan2_pulses: 2.000 fan3: fan3_input: 0.000 fan3_min: 0.000 fan3_alarm: 0.000 fan3_beep: 0.000 fan3_pulses: 2.000 fan4: fan4_input: 0.000 fan4_min: 0.000 fan4_alarm: 0.000 fan4_beep: 0.000 fan4_pulses: 2.000 fan5: fan5_input: 0.000 fan5_min: 0.000 fan5_alarm: 0.000 fan5_beep: 0.000 fan5_pulses: 2.000 fan6: fan6_input: 0.000 fan6_alarm: 0.000 fan6_pulses: 2.000 SYSTIN: temp1_input: 31.000 temp1_max: 0.000 temp1_max_hyst: 0.000 temp1_alarm: 1.000 temp1_type: 4.000 temp1_offset: 0.000 temp1_beep: 0.000 CPUTIN: temp2_input: 40.000 temp2_max: 80.000 temp2_max_hyst: 75.000 temp2_alarm: 0.000 temp2_type: 4.000 temp2_offset: 0.000 temp2_beep: 0.000 AUXTIN0: temp3_input: -128.000 temp3_type: 4.000 temp3_offset: 0.000 AUXTIN1: temp4_input: -128.000 temp4_type: 4.000 temp4_offset: 0.000 AUXTIN2: temp5_input: 34.000 temp5_type: 4.000 temp5_offset: 0.000 AUXTIN3: temp6_input: 127.000 temp6_type: 4.000 temp6_offset: 0.000 PECI Agent 0: temp7_input: 40.500 PCH_CHIP_CPU_MAX_TEMP: temp8_input: 0.000 PCH_CHIP_TEMP: temp9_input: 0.000 PCH_CPU_TEMP: temp10_input: 0.000 intrusion0: intrusion0_alarm: 1.000 intrusion0_beep: 0.000 intrusion1: intrusion1_alarm: 1.000 intrusion1_beep: 0.000 beep_enable: beep_enable: 0.000 I've got this for my sensors.conf # Sensor Configuration chip "nct6791-isa-0290" label temp1 "MB Temp" label temp2 "CPU Temp"
May 27, 201610 yr Can't seem to get this to work. In the plugin under drivers all I'm getting is the 'click detect', but it doesn't seem to do anything. I went through the sensor-detect script in order to get sensors working, and it seems to be outputting temps correctly... You didn't actually say what's not working. It all looks fine, from what I can see. What temps are you seeing on the Main page?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.