Jump to content
bonienl

Dynamix - System Temp

227 posts in this topic Last Reply

Recommended Posts

I can't get my Mobo Temp to show and i'm assuming it's from this

Driver `f71882fg':

  * ISA bus, address 0x480

    Chip `Fintek F71889A Super IO Sensors' (confidence: 9)

 

Is there anyway to get this working corrrectly?

 

root@Tower:~# sensors

k10temp-pci-00c3

Adapter: PCI adapter

CPU Temp:    +20.8°C  (high = +70.0°C)

                      (crit = +70.0°C, hyst = +67.0°C)

 

fam15h_power-pci-00c4

Adapter: PCI adapter

power1:      124.95 W  (crit = 124.95 W)

 

root@Tower:~#

 

Sensor-detect output

root@Tower:/tmp# perl sensors-detect
# sensors-detect revision $Revision$
# System: MSI MS-7693 [2.0]
# Board: MSI 970A-G46 (MS-7693)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             Success!
    (driver `fam15h_power')
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Fintek F71889A Super IO Sensors'                     Success!
    (address 0x480, driver `f71882fg')

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `fam15h_power' (autoloaded):
  * Chip `AMD Family 15h power sensors' (confidence: 9)

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 15h thermal sensors' (confidence: 9)

Driver `f71882fg':
  * ISA bus, address 0x480
    Chip `Fintek F71889A Super IO Sensors' (confidence: 9)

Warning: the required module f71882fg is not currently installed
on your system. Check http://www.lm-sensors.org/wiki/Devices for
driver availability.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

root@Tower:/tmp#

Share this post


Link to post

There is an issue with the CPU and MB temperatures.  This line in the SystemTemps.php sorts the temperatures and the lowest one always shows first (left position) on the webpage.

 

exec("sensors -A|awk '/^CPU Temp/ {print $3*1}; /^M\/?B Temp/ {print $3*1}'",$temp);

 

No matter which temperature is associated with the CPU and MB, the lowest temperature will always show first on the left.  In my case the MB temp is lower so it shows in the CPU temperature position.

 

Really a minor issue, but may cause some consternation when trying to get the temperatures to show in the correct positions.

Share this post


Link to post

There is an issue with the CPU and MB temperatures.  This line in the SystemTemps.php sorts the temperatures and the lowest one always shows first (left position) on the webpage.

 

exec("sensors -A|awk '/^CPU Temp/ {print $3*1}; /^M\/?B Temp/ {print $3*1}'",$temp);

 

No matter which temperature is associated with the CPU and MB, the lowest temperature will always show first on the left.  In my case the MB temp is lower so it shows in the CPU temperature position.

 

Really a minor issue, but may cause some consternation when trying to get the temperatures to show in the correct positions.

 

Well that is good to know but I can't even read my mobo temp, I think from what I have gathered is that the linux kernel doesn't support the driver needed for my mobo so I cannot get the temps

Share this post


Link to post

Well that is good to know but I can't even read my mobo temp, I think from what I have gathered is that the linux kernel doesn't support the driver needed for my mobo so I cannot get the temps

DToX, he wasn't actually responding to you, he was announcing an issue he had found, one that should be straight forward to fix.

 

I can't get my Mobo Temp to show and i'm assuming it's from this

Driver `f71882fg':

  * ISA bus, address 0x480

    Chip `Fintek F71889A Super IO Sensors' (confidence: 9)

 

Is there anyway to get this working corrrectly?

 

root@Tower:~# sensors

k10temp-pci-00c3

Adapter: PCI adapter

CPU Temp:    +20.8°C  (high = +70.0°C)

                      (crit = +70.0°C, hyst = +67.0°C)

I'm actually happy that you have the same issue I have, needing the Fintek f71882fg driver.  I suspect you haven't read my post above (found here).  Now that I know someone else needs 'f71882fg', I'll ask Tom if he can add it to UnRAID (didn't want to before if I was the only one).

 

Since yours is very similar except your board uses the k10temp chipset instead of the k8temp chipset, I think you can probably use the sensors.conf file I posted, except change "k8temp-*" to "k10temp-*".  Make sure you use an editor that keeps the linux line endings.  That should at least give you 2 CPU temps for now, until f71882fg support is added.  Be aware though that many users have reported that the k8temp and k10temp chipsets are notoriously unreliable for true temps.  Works fine for me though.

Share this post


Link to post

Well that is good to know but I can't even read my mobo temp, I think from what I have gathered is that the linux kernel doesn't support the driver needed for my mobo so I cannot get the temps

DToX, he wasn't actually responding to you, he was announcing an issue he had found, one that should be straight forward to fix.

 

I can't get my Mobo Temp to show and i'm assuming it's from this

Driver `f71882fg':

  * ISA bus, address 0x480

    Chip `Fintek F71889A Super IO Sensors' (confidence: 9)

 

Is there anyway to get this working corrrectly?

 

root@Tower:~# sensors

k10temp-pci-00c3

Adapter: PCI adapter

CPU Temp:    +20.8°C  (high = +70.0°C)

                      (crit = +70.0°C, hyst = +67.0°C)

I'm actually happy that you have the same issue I have, needing the Fintek f71882fg driver.  I suspect you haven't read my post above (found here).  Now that I know someone else needs 'f71882fg', I'll ask Tom if he can add it to UnRAID (didn't want to before if I was the only one).

 

Since yours is very similar except your board uses the k10temp chipset instead of the k8temp chipset, I think you can probably use the sensors.conf file I posted, except change "k8temp-*" to "k10temp-*".  Make sure you use an editor that keeps the linux line endings.  That should at least give you 2 CPU temps for now, until f71882fg support is added.  Be aware though that many users have reported that the k8temp and k10temp chipsets are notoriously unreliable for true temps.  Works fine for me though.

 

Thank you that was helpful, anyway fingers crossed on a future update  :)

Share this post


Link to post

I'm running a Gigabyte F2A88XM-D3H mobo with an AMD A6 5400K CPU.

 

I found this link http://ubuntuforums.org/showthread.php?t=2201555 and this one http://www.phoronix.com/forums/showthread.php?96788-Gigabyte-F2A88XM-D3H-AMD-A88X/page3 that both indicated that I needed to use modprobe it87 force_id=0x8728. Having done that, sensors now reports:

k10temp-pci-00c3
Adapter: PCI adapter
MB Temp:       +9.4 C  (high = +70.0 C)
                       (crit = +80.0 C, hyst = +79.0 C)

it8728-isa-0228
Adapter: ISA adapter
in0:          +1.00 V  (min =  +0.00 V, max =  +3.06 V)
in1:          +1.49 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +2.00 V  (min =  +0.00 V, max =  +3.06 V)
in5:          +2.22 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +2.22 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.36 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +3.02 V
fan1:        1917 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =   10 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
fan5:           0 RPM  (min =    0 RPM)
temp1:        +29.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp2:         -8.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp3:        +30.0 C  (low  =  +0.0 C, high = +60.0 C)  sensor = Intel PECI
intrusion0:  ALARM

I ended up with this in my sensors.conf:

# sensor configuration

chip "k10temp-*"
#chip "it8728-isa-0028"

label temp1 "MB Temp"
label temp3 "CPU Temp"

With the first "chip" line in effect, I get the somewhat ridiculously low reading in the single digits © as a temp being displayed in Dynamix. If I uncomment the 2nd "chip" line, instead, I get no readings showing up.

 

The values from the it8728 chip seem to be accurate, or at least reasonable, how do I get them to display instead of the values from the k10temp chip?

 

 

(As a side note, how do I get a nicely formatted word as a link, instead of displaying the full link? I know how to do <a href="url">text</a> in HTML, but how do I do it in BBCode?)

 

Share this post


Link to post

I'm running a Gigabyte F2A88XM-D3H mobo with an AMD A6 5400K CPU.

 

I found this link http://ubuntuforums.org/showthread.php?t=2201555 and this one http://www.phoronix.com/forums/showthread.php?96788-Gigabyte-F2A88XM-D3H-AMD-A88X/page3 that both indicated that I needed to use modprobe it87 force_id=0x8728. Having done that, sensors now reports:

k10temp-pci-00c3
Adapter: PCI adapter
MB Temp:       +9.4 C  (high = +70.0 C)
                       (crit = +80.0 C, hyst = +79.0 C)

it8728-isa-0228
Adapter: ISA adapter
in0:          +1.00 V  (min =  +0.00 V, max =  +3.06 V)
in1:          +1.49 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +2.00 V  (min =  +0.00 V, max =  +3.06 V)
in5:          +2.22 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +2.22 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.36 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +3.02 V
fan1:        1917 RPM  (min =   10 RPM)
fan2:           0 RPM  (min =   10 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
fan5:           0 RPM  (min =    0 RPM)
temp1:        +29.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp2:         -8.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor
temp3:        +30.0 C  (low  =  +0.0 C, high = +60.0 C)  sensor = Intel PECI
intrusion0:  ALARM

I ended up with this in my sensors.conf:

# sensor configuration

chip "k10temp-*"
#chip "it8728-isa-0028"

label temp1 "MB Temp"
label temp3 "CPU Temp"

With the first "chip" line in effect, I get the somewhat ridiculously low reading in the single digits © as a temp being displayed in Dynamix. If I uncomment the 2nd "chip" line, instead, I get no readings showing up.

 

The values from the it8728 chip seem to be accurate, or at least reasonable, how do I get them to display instead of the values from the k10temp chip?

It looks like you used "it8728-isa-0028" instead of "it8728-isa-0228".  Safer yet, try "it8728-isa-*".

 

(As a side note, how do I get a nicely formatted word as a link, instead of displaying the full link? I know how to do <a href="url">text</a> in HTML, but how do I do it in BBCode?)

Simple, click the 'Insert Hyperlink' button above your edit message box (has an earth icon, located below the Italic button).  After the initial URL, add an equal sign and the link, then the display text between the pair of bracketed 'URL's.  Like the following: 

[url=http://ubuntuforums.org/showthread.php?t=2201555]Ubuntu forum link[/url]

Displays as:  Ubuntu forum link

Share this post


Link to post

It looks like you used "it8728-isa-0028" instead of "it8728-isa-0228".  Safer yet, try "it8728-isa-*".

 

Winner, winner, chicken dinner!!! Thanks Rob, that was the ticket. Despite wearing contacts, we all need 4 eyes.  ;)

 

Displays as:  Ubuntu forum link

Thanks - don't know why I didn't think of that...  :-[

Share this post


Link to post

I've followed the guide, made the sensors.conf file but I still don't get the temps displayed.

 

When running sensors, it shows the labels have changed to "CPU temp" and "MB temp" though. Any thoughts?

Screenshot_2014-05-06_22_18_21.png.b7f9a70d826b851c93ea3d4f0ab68b57.png

Share this post


Link to post

Anyone found a way to use lm-sensors on X9SCM-F but with unRAID running under ESXi?

 

In that case modprobe w83627ehf complains 'no such device found'. Apparently such devices are not passed-through to a VM.

 

I tried with other modules, but they do not work either.

 

 

Maybe the only way is to read system temp via IPMI linux tools?

 

Edit:

I found this: http://www.thomas-krenn.com/en/wiki/Supermicro_X9SCM-F_Motherboard

 

We would require FreeIPMI package then and modified/alternative version  ;)  of System Temp plugin for IPMI.

I didn't get the X9SCM-F working under ESXi, but I did get it working on bare metal using the following steps:

 

 

My go file addition:

 

    modprobe w83627ehf

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d

    cp /boot/custom/sensors.d/sensors.conf /etc/sensors3.conf

 

My /boot/custom/sensors.d/sensors.conf file:

 

    chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

 

 

    label in0 "Vcore"

    label in2 "AVCC"

    label in3 "+3.3V"

    label in7 "3VSB"

    label in8 "Vbat"

    label temp2 "CPU Temp"

    label temp1 "MB Temp"

 

 

    set in2_min  3.3 * 0.90

    set in2_max  3.3 * 1.10

    set in3_min  3.3 * 0.90

    set in3_max  3.3 * 1.10

    set in7_min  3.3 * 0.90

    set in7_max  3.3 * 1.10

    set in8_min  3.0 * 0.90

    set in8_max  3.3 * 1.10

 

Thanks for this Ogi it was a great help to me. As Im using a later version of Dynamix WebGui all I had to do was make a sensors.conf file using a text editor and place your settings in it and just add "mod probe w83627ehf" to my go file using my text editor. The sensors.conf file is in a different place from where it used to be when using the Dynamix system temp plugin from the webGui.

 

For a new user to unRAID like me it helps so much when users post helpful things like you did, so thanks.

Im using a Supermicro X9SCM-iF Motherboard but a the temp sensors are very confusing on this board. It says Im getting 29.5 on the motherboard and 35 degree's C on the CPU using your settings in the dynamix webGui with the system temp plugin. But the IPMI says 29c system temp, 35c peripheral temp and CPU temp low. When I spoke to Supermicro Tech support last year they told me the system temp is for the motherboard sensor as correctly shown in the Dynamix WebGui but the 35c is for the peripherals like the HBA cards etc and not the CPU as the CPU just has low, med or high so Im wondering if the CPU temp of 35c showing in the Dynamix webGui is actually for the CPU or not.

Share this post


Link to post

I'm just getting started with setting up the sensors.conf file for my new rig.  I have the Gigabyte GA-X58A-UD3R_rev2 motherboard.

 

Does anyone else have this same MB and perhaps can share the config file to save me some time?

 

Update:  I was able to get this working.  I've attached my sensors.conf file, in case anyone has my same MB.  In addition, I share the output, in case I have done anything incorrectly.  That said, the temps are showing up and they look to be correct.

 

my sensors.conf:

# sensors config for Gigabyte GA-X58A-UD3R_rev2

 

chip "it8720-isa-0290"

 

  label temp1 "CPU Temp"

  label temp2 "MB Temp"

  ignore temp3

 

chip "coretemp-isa-0000"

 

My Go file:

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

# Update Sensors Config

cp /boot/custom/sensors.d/sensors.conf /etc/sensors.d/sensors.conf

modprobe coretemp

modprobe it87

/usr/bin/sensors -s

 

sensors command line output:

 

root@Tower:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +46.0 C  (high = +80.0 C, crit = +100.0 C)

Core 1:      +47.0 C  (high = +80.0 C, crit = +100.0 C)

Core 2:      +48.0 C  (high = +80.0 C, crit = +100.0 C)

Core 3:      +45.0 C  (high = +80.0 C, crit = +100.0 C)

 

it8720-isa-0290

Adapter: ISA adapter

in0:          +0.93 V  (min =  +0.00 V, max =  +4.08 V)

in1:          +1.58 V  (min =  +0.00 V, max =  +4.08 V)

in2:          +3.38 V  (min =  +0.00 V, max =  +4.08 V)

+5V:          +3.01 V  (min =  +0.00 V, max =  +4.08 V)

in4:          +0.34 V  (min =  +0.00 V, max =  +4.08 V)

in5:          +3.10 V  (min =  +0.00 V, max =  +4.08 V)

in6:          +0.08 V  (min =  +0.00 V, max =  +4.08 V)

5VSB:        +2.98 V  (min =  +0.00 V, max =  +4.08 V)

Vbat:        +3.17 V

fan1:        1885 RPM  (min =  10 RPM)

fan2:        1250 RPM  (min =    0 RPM)

fan3:        1730 RPM  (min =    0 RPM)

fan4:        1394 RPM  (min =    0 RPM)

CPU Temp:    +48.0 C  (low  = +127.0 C, high = +127.0 C)  sensor = thermistor

MB Temp:      +45.0 C  (low  = +127.0 C, high = +60.0 C)  sensor = thermal diode

intrusion0:  ALARM

 

root@Tower:~#

 

Very nice to see temps again.  :)

sensors.conf

Share this post


Link to post

As its always hard to find information about unRAID plugins etc without sometimes reading through loads of forums posts, it maybe a good idea to have a list of motherboards that forum users have already setup with the system temp plugin, sensors.confg information, with a link from each motherboard to the sensors.conf information and the go information. Just a thought but it would make it so much easier to just click a link and have the information to hand.

Share this post


Link to post

My two cents

 

Attached my simple sensors.conf for HP microserver NL36. Only CPU temp

 

Thanks marrajon!

btw: what sensor driver did you use with modprobe in the go 'file' ?

I'm hoping the N54L uses the same driver as your NL36

so I don't have to worry about installing the perl package  :)

 

(I presume the go 'file' mentioned in the directions, is the one in /boot/config/  )

 

cheers,

DM

 

Share this post


Link to post

Back in the SF thread we also ran into issues of keeping track of sensor files, I suggested that a wiki page should be added for it where people can append some of the files but no one took me up. I have the sensor file ready for my mobo if anyone wants to create the wiki/thread for it.

Share this post


Link to post

Ok, I have a few basic problems here regarding getting the temp senosors done. I have Supermicro X8SIL board, bellow is console response to "sensors".

 

root@Tower:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0:      +35.0 C  (high = +89.0 C, crit = +105.0 C)

Core 2:      +35.0 C  (high = +89.0 C, crit = +105.0 C)

 

Tried installing perl package to get "sensors-detect" output, but I stopped here as I don't know how to successfully install perl package? Where is Dynamix system Temp plugin located and what/how do I edit it as it is explained bellow;

 

- Or for Dynamix, you can modify the Dynamix System Temp plugin itself, by locating the line ending with "# perl scripting" and replacing "no-install" with "do-install". Then re-install the plugin or reboot.

 

After that do I need only sensors.conf file or do I need to edit "go" file also? Never done that before, so I feel a bit overwhelmed.  :-\

 

 

 

Share this post


Link to post

Have you read the first post in this thread, which tells you to go read the wiki?  I think step 5 talks about what directory the plugin resides.  Best if you read and follow the instructions in the wiki.

 

Not sure if the wiki says this or not, but for my Windows rig I use Notepad++ to edit.

Share this post


Link to post

Have you read the first post in this thread, which tells you to go read the wiki?  I think step 5 talks about what directory the plugin resides.  Best if you read and follow the instructions in the wiki.

 

Not sure if the wiki says this or not, but for my Windows rig I use Notepad++ to edit.

 

Sure, the step 6 which I posted above talks about installing perl package, this is where I stopped as I dont know how(and where) to edit plugin to force perl installation.

 

Step 5 in Wiki talks about where to save sensors.conf file.

 

Ok, I have notepad++ so thanks for letting me know about "go" file.

Share this post


Link to post

Ok, first run sensors-detect on the console nad see if you get anything.  if not sure what you are looking at, post the output here so we can see it.  Look at my output, about 6 posts above as a reference.  If you do get the output you are looking for, then you already have what you need to move to the next step.  The reason it tells you to try it first is because other packages may have already installed perl or one of the other packages that will allow senors ro work.

 

If you don't get the output you want, then simple locate the plugin on your boot (flash) drive and use Notepad++ to change the one line - replace don't install with do install.  Save and reboot.  Go back to step 6 and run sensors-detect again. If it now works, go to step 7.

 

you use Notepadd++ as any other TEXT file editor.  Just open Notepad++ and then open the plugin file, then scroll down until you find the line mentioned in step 6 and change it - save it and exit. Reboot and see if it works.

Share this post


Link to post

i have manged to install Perl and here is the output of "sensors-detect". I really don't know what to look for tho :(

UNRAiD login: root

Linux 3.9.11p-unRAID.

root@UNRAiD:~# sensors-detect

# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)

# System: Supermicro X8SIL [0123456789]

 

This program will help you determine which kernel modules you need

to load to use lm_sensors most effectively. It is generally safe

and recommended to accept the default answers to all questions,

unless you know what you're doing.

 

Some south bridges, CPUs or memory controllers contain embedded sensors.

Do you want to scan for them? This is totally safe. (YES/no): Yes

Silicon Integrated Systems SIS5595...                      No

VIA VT82C686 Integrated Sensors...                          No

VIA VT8231 Integrated Sensors...                            No

AMD K8 thermal sensors...                                  No

AMD Family 10h thermal sensors...                          No

AMD Family 11h thermal sensors...                          No

AMD Family 12h and 14h thermal sensors...                  No

AMD Family 15h thermal sensors...                          No

AMD Family 15h power sensors...                            No

AMD Family 16h power sensors...                            No

Intel digital thermal sensor...                            Success!

    (driver `coretemp')

Intel AMB FB-DIMM thermal sensor...                        No

VIA C7 thermal sensor...                                    No

VIA Nano thermal sensor...                                  No

 

Some Super I/O chips contain embedded sensors. We have to write to

standard I/O ports to probe them. This is usually safe.

Do you want to scan for Super I/O sensors? (YES/no): Yes

Probing for Super-I/O at 0x2e/0x2f

Trying family `National Semiconductor/ITE'...              No

Trying family `SMSC'...                                    No

Trying family `VIA/Winbond/Nuvoton/Fintek'...              Yes

Found `Winbond W83627DHG Super IO Sensors'                  Success!

    (address 0xa10, driver `w83627ehf')

Probing for Super-I/O at 0x4e/0x4f

Trying family `National Semiconductor/ITE'...              No

Trying family `SMSC'...                                    No

Trying family `VIA/Winbond/Nuvoton/Fintek'...              No

Trying family `ITE'...                                      No

 

Some systems (mainly servers) implement IPMI, a set of common interfaces

through which system health data may be retrieved, amongst other things.

We first try to get the information from SMBIOS. If we don't find it

there, we have to read from arbitrary I/O ports to probe for such

interfaces. This is normally safe. Do you want to scan for IPMI

interfaces? (YES/no): Yes

Found `IPMI BMC KCS' at 0xca2...                            Success!

    (confidence 8, driver `to-be-written')

 

Some hardware monitoring chips are accessible through the ISA I/O ports.

We have to write to arbitrary I/O ports to probe them. This is usually

safe though. Yes, you do have ISA I/O ports even if you do not have any

ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): Yes

Probing for `National Semiconductor LM78' at 0x290...      No

Probing for `National Semiconductor LM79' at 0x290...      No

Probing for `Winbond W83781D' at 0x290...                  No

Probing for `Winbond W83782D' at 0x290...                  No

 

Lastly, we can probe the I2C/SMBus adapters for connected hardware

monitoring devices. This is the most risky part, and while it works

reasonably well on most systems, it has been reported to cause trouble

on some systems.

Do you want to probe the I2C/SMBus adapters now? (YES/no): Yes

Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)

Module i2c-dev loaded successfully.

 

Next adapter: SMBus I801 adapter at 0400 (i2c-0)

Do you want to scan it? (YES/no/selectively): Yes

Client found at address 0x18

Probing for `Analog Devices ADM1021'...                    No

Probing for `Analog Devices ADM1021A/ADM1023'...            No

Probing for `Maxim MAX1617'...                              No

Probing for `Maxim MAX1617A'...                            No

Probing for `Maxim MAX1668'...                              No

Probing for `Maxim MAX1805'...                              No

Probing for `Maxim MAX1989'...                              No

Probing for `Maxim MAX6655/MAX6656'...                      No

Probing for `TI THMC10'...                                  No

Probing for `National Semiconductor LM84'...                No

Probing for `Genesys Logic GL523SM'...                      No

Probing for `Onsemi MC1066'...                              No

Probing for `Maxim MAX1618'...                              No

Probing for `Maxim MAX1619'...                              No

Probing for `National Semiconductor LM82/LM83'...          No

Probing for `Maxim MAX6654'...                              No

Probing for `Maxim MAX6690'...                              No

Probing for `Maxim MAX6680/MAX6681'...                      No

Probing for `Maxim MAX6695/MAX6696'...                      No

Probing for `Texas Instruments AMC6821'...                  No

Probing for `National Semiconductor LM95234'...            No

Probing for `National Semiconductor LM95245'...            No

Probing for `National Semiconductor LM64'...                No

Probing for `SMSC EMC1047'...                              No

Probing for `SMSC EMC1402'...                              No

Probing for `SMSC EMC1403'...                              No

Probing for `SMSC EMC1404'...                              No

Probing for `ST STTS424'...                                No

Probing for `ST STTS424E'...                                No

Probing for `ST STTS2002'...                                No

Probing for `ST STTS3000'...                                No

Probing for `NXP SE97/SE97B'...                            No

Probing for `NXP SE98'...                                  No

Probing for `Analog Devices ADT7408'...                    No

Probing for `IDT TS3000/TSE2002'...                        No

Probing for `Maxim MAX6604'...                              No

Probing for `Microchip MCP9804'...                          No

Probing for `Microchip MCP98242'...                        No

Probing for `Microchip MCP98243'...                        No

Probing for `Microchip MCP98244'...                        No

Probing for `Microchip MCP9843'...                          No

Probing for `ON CAT6095/CAT34TS02'...                      Success!

    (confidence 5, driver `jc42')

Probing for `Atmel AT30TS00'...                            No

Client found at address 0x1a

Probing for `Analog Devices ADM1021'...                    No

Probing for `Analog Devices ADM1021A/ADM1023'...            No

Probing for `Maxim MAX1617'...                              No

Probing for `Maxim MAX1617A'...                            No

Probing for `Maxim MAX1668'...                              No

Probing for `Maxim MAX1805'...                              No

Probing for `Maxim MAX1989'...                              No

Probing for `Maxim MAX6655/MAX6656'...                      No

Probing for `TI THMC10'...                                  No

Probing for `National Semiconductor LM84'...                No

Probing for `Genesys Logic GL523SM'...                      No

Probing for `Onsemi MC1066'...                              No

Probing for `Maxim MAX1618'...                              No

Probing for `Maxim MAX1619'...                              No

Probing for `National Semiconductor LM82/LM83'...          No

Probing for `Maxim MAX6654'...                              No

Probing for `Maxim MAX6690'...                              No

Probing for `Maxim MAX6680/MAX6681'...                      No

Probing for `Maxim MAX6695/MAX6696'...                      No

Probing for `Texas Instruments AMC6821'...                  No

Probing for `ST STTS424'...                                No

Probing for `ST STTS424E'...                                No

Probing for `ST STTS2002'...                                No

Probing for `ST STTS3000'...                                No

Probing for `NXP SE97/SE97B'...                            No

Probing for `NXP SE98'...                                  No

Probing for `Analog Devices ADT7408'...                    No

Probing for `IDT TS3000/TSE2002'...                        No

Probing for `Maxim MAX6604'...                              No

Probing for `Microchip MCP9804'...                          No

Probing for `Microchip MCP98242'...                        No

Probing for `Microchip MCP98243'...                        No

Probing for `Microchip MCP98244'...                        No

Probing for `Microchip MCP9843'...                          No

Probing for `ON CAT6095/CAT34TS02'...                      Success!

    (confidence 5, driver `jc42')

Probing for `Atmel AT30TS00'...                            No

Client found at address 0x48

Probing for `National Semiconductor LM75'...                No

Probing for `National Semiconductor LM75A'...              No

Probing for `Dallas Semiconductor DS75'...                  No

Probing for `National Semiconductor LM77'...                No

Probing for `Analog Devices ADT7410/ADT7420'...            No

Probing for `Analog Devices ADT7411'...                    No

Probing for `Maxim MAX6642'...                              No

Probing for `National Semiconductor LM73'...                No

Probing for `National Semiconductor LM92'...                No

Probing for `National Semiconductor LM76'...                No

Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No

Probing for `NXP/Philips SA56004'...                        No

Probing for `SMSC EMC1023'...                              No

Probing for `SMSC EMC1043'...                              No

Probing for `SMSC EMC1053'...                              No

Probing for `SMSC EMC1063'...                              No

Client found at address 0x50

Probing for `Analog Devices ADM1033'...                    No

Probing for `Analog Devices ADM1034'...                    No

Probing for `SPD EEPROM'...                                Yes

    (confidence 8, not a hardware monitoring chip)

Probing for `EDID EEPROM'...                                No

Client found at address 0x52

Probing for `Analog Devices ADM1033'...                    No

Probing for `Analog Devices ADM1034'...                    No

Probing for `SPD EEPROM'...                                Yes

    (confidence 8, not a hardware monitoring chip)

 

Now follows a summary of the probes I have just done.

Just press ENTER to continue:

 

Driver `w83627ehf':

  * ISA bus, address 0xa10

    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9 )

 

Driver `jc42':

  * Bus `SMBus I801 adapter at 0400'

    Busdriver `i2c_i801', I2C address 0x18

    Chip `ON CAT6095/CAT34TS02' (confidence: 5)

  * Bus `SMBus I801 adapter at 0400'

    Busdriver `i2c_i801', I2C address 0x1a

    Chip `ON CAT6095/CAT34TS02' (confidence: 5)

 

Driver `to-be-written':

  * ISA bus, address 0xca2

    Chip `IPMI BMC KCS' (confidence: 8)

 

Driver `coretemp':

  * Chip `Intel digital thermal sensor' (confidence: 9)

 

Warning: the required module jc42 is not currently installed

on your system. If it is built into the kernel then it's OK.

Otherwise, check http://www.lm-sensors.org/wiki/Devices for

driver availability.

 

Note: there is no driver for IPMI BMC KCS yet.

Check http://www.lm-sensors.org/wiki/Devices for updates.

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes

Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors

for initialization at boot time.

You should now start the lm_sensors service to load the required

kernel modules.

 

Unloading i2c-dev... OK

 

 

I have accidentally put YES to "Enter [NO] to automatically generate the config file (last prompt)". Is this bad or how can I undo it?

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes

 

Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors

for initialization at boot time.

You should now start the lm_sensors service to load the required

kernel modules.

 

Unloading i2c-dev... OK

Share this post


Link to post

I could be wrong and you will want Bonienl to confirm, but I would not worry about saying YES to creating the config file.  If it were me, I would just continue to step 8.  Make sure your sensors.conf file is correct, edit your GO file and  reboot.

 

 

Share this post


Link to post

Indeed no worries on that last 'yes' (this is reset upon reboot).

 

Add the following to your "go" file and reboot your system

 

# Add temperature modules

modprobe coretemp

modprobe w83627ehf

/usr/bin/sensors -s

After reboot do a "sensors" command and create your sensors.conf file as per wiki.

Share this post


Link to post

thanks to both, that did it!!!  ;) i now have both temps showing up on Dynamix!

 

 

Share this post


Link to post

;D  glad it's working.  I assume the temps look correct to you.  Some people have to switch the labels around in sensors.conf so cpu is actually the cpu, etc.  I didn't have to do that for mine.

 

What is really awesome is the announcement that Dynamix will now be included with V6!  That is so cool - this completes unraid IMO.

Share this post


Link to post

having problems getting my sensor.conf file correct - the labels are not getting changed:

 

sensors:

acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8 C  (crit = +95.0 C)
temp2:        +29.8 C  (crit = +95.0 C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +24.0 C  (high = +74.0 C, crit = +94.0 C)
Core 0:         +22.0 C  (high = +74.0 C, crit = +94.0 C)
Core 1:         +23.0 C  (high = +74.0 C, crit = +94.0 C)
Core 2:         +18.0 C  (high = +74.0 C, crit = +94.0 C)
Core 3:         +21.0 C  (high = +74.0 C, crit = +94.0 C)

nct6776-isa-0a30
Adapter: ISA adapter
Vcore:          +1.00 V  (min =  +0.60 V, max =  +1.49 V)
in1:            +1.87 V  (min =  +1.62 V, max =  +1.99 V)
AVCC:           +3.28 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.28 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +1.53 V  (min =  +1.35 V, max =  +1.65 V)
in5:            +1.27 V  (min =  +1.13 V, max =  +1.38 V)
in6:            +1.46 V  (min =  +1.42 V, max =  +1.52 V)
3VSB:           +3.34 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:           +3.17 V  (min =  +2.70 V, max =  +3.63 V)
fan1:             0 RPM  (min =  300 RPM)  ALARM
fan2:             0 RPM  (min =  300 RPM)  ALARM
fan3:             0 RPM  (min =  300 RPM)  ALARM
fan4:             0 RPM  (min =  300 RPM)  ALARM
fan5:          2042 RPM  (min =  300 RPM)
SYSTIN:         +26.0 C  (high = +75.0 C, hyst = +70.0 C)  sensor = thermistor
CPUTIN:         +19.5 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
AUXTIN:          +1.0 C  (high = +80.0 C, hyst = +75.0 C)  sensor = thermistor
PECI Agent 0:   +29.5 C  (high = +95.0 C, hyst = +92.0 C)
                         (crit = +100.0 C)
PCH_CHIP_TEMP:   +0.0 C
PCH_CPU_TEMP:    +0.0 C
PCH_MCH_TEMP:    +0.0 C
intrusion0:    ALARM
intrusion1:    OK
beep_enable:   enabled

 

sensors.conf

# lines starting with "#" are comments and ignored
# sensor configuration

chip "nct6776-isa-0a30"

label SYSTIN "MB Temp"
label CPUTIN "CPU Temp"

 

can not get the labels for SYSTIN and CPUTIN to change so we page picks it up

 

Thanks for any info

Myk

 

Share this post


Link to post

;D  glad it's working.  I assume the temps look correct to you.  Some people have to switch the labels around in sensors.conf so cpu is actually the cpu, etc.  I didn't have to do that for mine.

 

What is really awesome is the announcement that Dynamix will now be included with V6!  That is so cool - this completes unraid IMO.

 

yea, the labels are switched, not a biggie, but can't figure it out...

 

tried 3 different sensors_conf;

chip "w83627dhg-isa-0a10"

label temp2 "CPU Temp"
label temp1 "MB Temp"

and

chip "w83627dhg-isa-0a10"

label temp1 "MB Temp"
label temp2 "CPU Temp"

and

label temp1 "CPU Temp"
label temp2 "MB Temp"

 

And yes, that is awesome news indeed, cant wait for V6 final!

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.