AMD quad socket motherboard sensor information

sfield

Weaksauce
Joined
Nov 2, 2010
Messages
74
Given the surge in popularity of quad socket AMD systems, sensor information is below. I estimated the resistor values for +5V, +12V, will confirm later. Tested with a Supermicro H8QGi-F system.

assumes w83795 module is built and loaded.

For supermicro H8QGi-F (and like variants), add the following to /etc/sensors3.conf

Code:
chip "w83795g-*"
    # supermicro H8QGi-F
    # v1.0 sensors3.conf data
    label in0 "Vcore CPU1"
    label in1 "Vcore CPU2"
    label in2 "Vcore CPU3"
    label in3 "Vcore CPU4"

    label in4 "Vdimm CPU1"
    label in5 "Vdimm CPU2"
    label in6 "Vdimm CPU3"
    label in7 "Vdimm CPU4"

    label in8 "+5V"
    label in9 "+12V"

    compute in8 @*((30/10)+1), @/((30/10)+1)	# resistor values unconfirmed.	
    compute in9 @*((56/10)+1), @/((56/10)+1)	# resistor values unconfirmed.

    ignore in11			# unknown
    label in12 "+3.3V"
    label in13 "+3.3Vsb"
    label in14 "VBAT"

    ignore temp1		# not connected diode
    ignore temp2		# not connected diode

    label temp3 "SR5690 Temp"
    label temp4 "SR5670 Temp"
    label temp5 "Sys Temp"	# thermistor in vicinity of CPU0, CPU1, exact location TBD

    label temp7 "CPU1 Temp"
    label temp8 "CPU2 Temp"
    label temp9 "CPU3 Temp"
    label temp10 "CPU4 Temp"

    label fan10 "SR5690 Fan"
    label fan11 "SR5670 Fan"

Example output from 'sensors' command, idle:
(note the min, max values are just the default programmed thresholds considered within norms -- these aren't the min/max observed. charset wasn't set to UTF-8, so degree C is garbled)
Code:
w83795g-i2c-0-2f
Adapter: SMBus PIIX4 adapter at 0b00
Vcore CPU1:  +0.88 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU2:  +0.87 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU3:  +0.86 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU4:  +0.88 V  (min =  +0.68 V, max =  +1.33 V)
Vdimm CPU1:  +1.55 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU2:  +1.55 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU3:  +1.55 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU4:  +1.54 V  (min =  +1.08 V, max =  +1.65 V)
+5V:         +5.04 V  (min =  +4.51 V, max =  +5.53 V)
+12V:       +12.18 V  (min = +10.77 V, max = +13.19 V)
+3.3V:       +3.28 V  (min =  +2.95 V, max =  +3.67 V)
+3.3Vsb:     +3.34 V  (min =  +2.95 V, max =  +3.67 V)
VBAT:        +3.22 V  (min =  +2.95 V, max =  +3.67 V)
fan1:       1291 RPM  (min =  709 RPM)
fan2:          0 RPM  (min =  709 RPM)  ALARM
fan3:          0 RPM  (min =  709 RPM)  ALARM
fan4:          0 RPM  (min =  709 RPM)  ALARM
fan5:          0 RPM  (min =  709 RPM)  ALARM
fan6:        769 RPM  (min =  709 RPM)
fan7:       1121 RPM  (min =  709 RPM)
fan8:          0 RPM  (min =  709 RPM)  ALARM
fan9:          0 RPM  (min =  709 RPM)  ALARM
SR5690 Fan: 6308 RPM  (min =  709 RPM)
SR5670 Fan: 6192 RPM  (min =  709 RPM)
SR5690 Temp: +50.5°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
SR5670 Temp: +42.8°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
Sys Temp:    +31.0°C  (high = +75.0°C, hyst = +70.0°C)
                      (crit = +75.0°C, hyst = +70.0°C)  sensor = thermistor
CPU1 Temp:   +24.2°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU2 Temp:   +24.0°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU3 Temp:   +23.5°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU4 Temp:   +24.2°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
beep_enable:disabled

Example output from 'sensors' command, folding load on watercooled system, a few degrees cooler than usual as it's not doing a -bigadv:

Code:
w83795g-i2c-0-2f
Adapter: SMBus PIIX4 adapter at 0b00
Vcore CPU1:  +1.16 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU2:  +1.15 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU3:  +1.12 V  (min =  +0.68 V, max =  +1.33 V)
Vcore CPU4:  +1.18 V  (min =  +0.68 V, max =  +1.33 V)
Vdimm CPU1:  +1.56 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU2:  +1.56 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU3:  +1.56 V  (min =  +1.08 V, max =  +1.65 V)
Vdimm CPU4:  +1.55 V  (min =  +1.08 V, max =  +1.65 V)
+5V:         +4.98 V  (min =  +4.51 V, max =  +5.53 V)
+12V:       +11.99 V  (min = +10.77 V, max = +13.19 V)
+3.3V:       +3.23 V  (min =  +2.95 V, max =  +3.67 V)
+3.3Vsb:     +3.34 V  (min =  +2.95 V, max =  +3.67 V)
VBAT:        +3.22 V  (min =  +2.95 V, max =  +3.67 V)
fan1:       1324 RPM  (min =  709 RPM)
fan2:          0 RPM  (min =  709 RPM)  ALARM
fan3:          0 RPM  (min =  709 RPM)  ALARM
fan4:          0 RPM  (min =  709 RPM)  ALARM
fan5:          0 RPM  (min =  709 RPM)  ALARM
fan6:        762 RPM  (min =  709 RPM)
fan7:       1110 RPM  (min =  709 RPM)
fan8:          0 RPM  (min =  709 RPM)  ALARM
fan9:          0 RPM  (min =  709 RPM)  ALARM
SR5690 Fan: 6250 RPM  (min =  709 RPM)
SR5670 Fan: 6221 RPM  (min =  709 RPM)
SR5690 Temp: +65.8°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
SR5670 Temp: +58.0°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
Sys Temp:    +35.5°C  (high = +75.0°C, hyst = +70.0°C)
                      (crit = +75.0°C, hyst = +70.0°C)  sensor = thermistor
CPU1 Temp:   +40.0°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU2 Temp:   +38.5°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU3 Temp:   +37.5°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
CPU4 Temp:   +37.5°C  (high = +70.0°C, hyst = +65.0°C)
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
beep_enable:disabled
 
Last edited:
Thanks sfield, although I don't know if I understand what i am reading here. Mine is a Tyan S8812WGM3NR - from /etc/modules after running sensors-detect:
Code:
# Generated by sensors-detect on Wed Apr 20 19:03:08 2011
# Adapter drivers
ipmi-si
# Chip drivers
w83627ehf


Output from sensors:
Code:
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +61.5°C  (high = +70.0°C)

k10temp-pci-00cb
Adapter: PCI adapter
temp1:       +60.5°C  (high = +70.0°C)

k10temp-pci-00d3
Adapter: PCI adapter
temp1:       +56.4°C  (high = +70.0°C)

k10temp-pci-00db
Adapter: PCI adapter
temp1:       +56.4°C  (high = +70.0°C)

k10temp-pci-00e3
Adapter: PCI adapter
temp1:       +62.1°C  (high = +70.0°C)

k10temp-pci-00eb
Adapter: PCI adapter
temp1:       +61.9°C  (high = +70.0°C)

k10temp-pci-00f3
Adapter: PCI adapter
temp1:       +57.8°C  (high = +70.0°C)

k10temp-pci-00fb
Adapter: PCI adapter
temp1:       +57.8°C  (high = +70.0°C)

w83627dhg-isa-0228
Adapter: ISA adapter
Vcore:       +0.74 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.11 V  (min =  +1.90 V, max =  +0.42 V)   ALARM
AVCC:        +3.22 V  (min =  +2.98 V, max =  +3.63 V)
VCC:         +3.22 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +1.21 V  (min =  +0.11 V, max =  +0.22 V)   ALARM
in5:         +1.14 V  (min =  +1.94 V, max =  +0.05 V)   ALARM
in6:         +1.10 V  (min =  +0.38 V, max =  +1.00 V)   ALARM
3VSB:        +3.22 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.22 V  (min =  +2.70 V, max =  +3.30 V)
fan1:          0 RPM  (min = 2109 RPM, div = 32)  ALARM
fan2:          0 RPM  (min = 8437 RPM, div = 32)  ALARM
fan3:          0 RPM  (min = 6026 RPM, div = 32)  ALARM
fan4:          0 RPM  (min =  715 RPM, div = 32)  ALARM
fan5:          0 RPM  (min = 1406 RPM, div = 32)  ALARM
temp1:       +59.0°C  (high = +103.0°C, hyst = +52.0°C)  sensor = thermistor
temp2:       +59.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
temp3:       -11.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:   +0.375 V

Is that not correct?
 
Some of this is motherboard implementation specific. The w83627dhg device output in the Tyan case doesn't look very interesting. According to the Tyan manual it also has the same chip as the Supermicro board:

"Chipset Winbond W83795G
Voltage Monitors voltage for CPU, memory, chipset & power supply
Fan Total (9) 4-pin headers
Temperature Monitors temperature for CPU & system environment
LED Fan fail LED indicator / Over temperature warning indicator / Fan & PSU
fail LED indicator
System Monitoring
Others Chassis intrusion detection / Watchdog timer support"

It's possible the sensors-detect probe didn't pick up this device -- did you also scan i2c?


Just try loading the sensor module yourself, and then run sensors again. See if you already have the sensor module:

modprobe w83795

If not, lm-sensors device support points to files here:
http://khali.linux-fr.org/devel/misc/w83795/

make
make install
modprobe w83795


Note the Tyan may be wired up to the sensor device differently than the Supermicro, so run sensors without the changes to sensors3.conf, and provide that output.
 
Last edited:
I did not have the w83795 module, so i added it. Runnin sensors-detect still didn't pick it up:
Code:
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: empty empty
# Board: TYAN S8812

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):
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627DHG Super IO Sensors'                  Success!
    (address 0x228, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0x0b00

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):
Found `IPMI BMC KCS' at 0xca8...                            Success!
    (confidence 8, driver `ipmisensors')

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):

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):
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):
Client found at address 0x19
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/MAX6690'...                      No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `National Semiconductor LM95231'...             No
Probing for `National Semiconductor LM95241'...             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/MAX6690'...                      No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Texas Instruments AMC6821'...                  No
Client found at address 0x1b
Probing for `Maxim MAX6650/MAX6651'...                      No
Client found at address 0x1f
Probing for `Maxim MAX6650/MAX6651'...                      No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

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

Driver `w83627ehf':
  * ISA bus, address 0x228
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Driver `ipmisensors':
  * ISA bus, address 0xca8
    Chip `IPMI BMC KCS' (confidence: 8)

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

Warning: the required module ipmisensors 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.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# Chip drivers
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK

Sensors output is the same as above. Adding your update to /etc/sensors3.conf did not change the sensors output.
 
thanks for posting...nice to see the interteam cooperation
 
Just another (perhaps stupid) thought... you can get a lot of info from these boards because they are typically loaded with IMPI 2.0.

Here is a Tyan example:
Tyan-IPMI-WebGUI-Server-Health-Sensor-Readings-with-Thresholds.png


Also did a piece on the standalone desktop software where you can centrally view sensor/ threshold information from one piece of software. IPMIview is a Supermicro product, but there are similar ones:
http://www.servethehome.com/supermi...er-monitoring-management-ipmi-20-kvm-over-ip/

It also does see Tyan boards.
 
Yes, those basic instructions are correct. w83795 replaces coretemp in the modprobe and other references in the SR-2 post.

BTW, the resistor values I picked and voltage display values in the sensors3.conf line up with those displayed by the supermicro superdoctor and IPMI view.

Note when I was doing early testing of the 6903 work units on the 4P AMD box, I was doing many sensor probes, and this appeared to cause some system instability. I can't say with 100% certainty whether this was the cause, but the instability went away after I stopped running the sensors during 6903 folding. Having said that, I would just use the w83795 sensors output for spot checking your system.




can anyone post a noob step by step commands to have sfield sensor info loaded and steps to install the sensors pkg. i just started up my first 4p rig and want to see how my four noctua U9's are doing

btw will these steps work for 4p boards or are they only for sr2??

http://hardforum.com/showpost.php?p=1037403943&postcount=194
 
Last edited:
I am running a Supermicro A2042G-6RF server with 4 12-core Opteron 1.9GHz micros & Ubuntu 10.04.2 LTS x64, and the front panel is indicating an overheating condition. Obviously this is a bit concerning since the system is not cheap. ;) However, when I feel the exhaust, the air seems only slightly warmer than the surrounding room temperature (~27C). So while the machine is running, I decided to use the on-board sensors to monitor temp under different operating conditions to see if I truly do have a problem.

My initial attempt to use lm-sensors was less than successful as I got all 0's for temp and fan RPM. After poking around, I found the update sensors3.conf section above. I updated my sensor3.conf, restarted the module_init_service (sudo /etc/init.d/module-init-tools restart), but still get goofy readings. :(

Here is my sensors output:
$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore CPU1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vcore CPU2: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vcore CPU3: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
Vcore CPU4: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
Vdimm CPU1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU2: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU3: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU4: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
+5V: +16.32 V (min = +16.32 V, max = +16.32 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
fan4: 0 RPM (min = 0 RPM, div = 128) ALARM
SR5690 Temp: +0.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = diode
cpu0_vid: +0.375 V

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +39.2°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00cb
Adapter: PCI adapter
temp1: +38.5°C (high = +70.0°C)

k10temp-pci-00d3
Adapter: PCI adapter
temp1: +28.5°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00db
Adapter: PCI adapter
temp1: +28.5°C (high = +70.0°C)

k10temp-pci-00e3
Adapter: PCI adapter
temp1: +26.0°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00eb
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C)

k10temp-pci-00f3
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00fb
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C)

I was presuming that the k10temp-pci-00xx temp1 values are correct because they change based on system load. However, I'm confused as to why the w83627dhg-isa-0290 values are incorrect. Additionally, why do none of the fan RPM values show up?

Finally, how would I determine which pci-00xx correlates to which temp sensor (CPU1, CPU2, CP3, CPU4, Sys Temp, etc.)? If it would help, I can also post the relevant section of my sensors3.conf file.

My only thought is that when I ran the sensors-detect, it stated that I needed ipmisensors module installed, but it appears to be deprecated. (Or maybe I'm just dumb, and couldn't find it). Does missing the ipmisensors module explain my strange results?

Any help would be greatly appreciated!

Thanks in advance.
 
Last edited:
You need the w83795 sensor device --

modprobe w83795

If not present on your system or part of included lm-sensors device support, need to pickup source here:
http://khali.linux-fr.org/devel/misc/w83795/

make
make install
modprobe w83795

Unfortunately, if you have IPMI enabled via the jumper -- which is the default -- there is a chance that the i2c accesses will conflict, which will lead to loss of i2c access until you reboot. It's generally OK to do spot readings, such as checking heavy load temperatures. If you want to collect sensor readings on a continual basis, you'll need to disable IPMI via the jumper on the motherboard. Not sure if this issue can be fixed.


The k10temp sensor readings look fine -- typical idle temperatures. The output starts with node 0 and goes to node 7. cpu1=node0,1, cpu2=node2,3, cpu3=node4,5, cpu4=node6,7

I am running a Supermicro A2042G-6RF server with 4 12-core Opteron 1.9GHz micros & Ubuntu 10.04.2 LTS x64, and the front panel is indicating an overheating condition. Obviously this is a bit concerning since the system is not cheap. ;) However, when I feel the exhaust, the air seems only slightly warmer than the surrounding room temperature (~27C). So while the machine is running, I decided to use the on-board sensors to monitor temp under different operating conditions to see if I truly do have a problem.

My initial attempt to use lm-sensors was less than successful as I got all 0's for temp and fan RPM. After poking around, I found the update sensors3.conf section above. I updated my sensor3.conf, restarted the module_init_service (sudo /etc/init.d/module-init-tools restart), but still get goofy readings. :(

Here is my sensors output:
$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore CPU1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vcore CPU2: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vcore CPU3: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
Vcore CPU4: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
Vdimm CPU1: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU2: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU3: +2.04 V (min = +2.04 V, max = +2.04 V) ALARM
Vdimm CPU4: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM
+5V: +16.32 V (min = +16.32 V, max = +16.32 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM
fan4: 0 RPM (min = 0 RPM, div = 128) ALARM
SR5690 Temp: +0.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = diode
cpu0_vid: +0.375 V

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +39.2°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00cb
Adapter: PCI adapter
temp1: +38.5°C (high = +70.0°C)

k10temp-pci-00d3
Adapter: PCI adapter
temp1: +28.5°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00db
Adapter: PCI adapter
temp1: +28.5°C (high = +70.0°C)

k10temp-pci-00e3
Adapter: PCI adapter
temp1: +26.0°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00eb
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C)

k10temp-pci-00f3
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C, crit = +70.0°C)

k10temp-pci-00fb
Adapter: PCI adapter
temp1: +25.5°C (high = +70.0°C)

I was presuming that the k10temp-pci-00xx temp1 values are correct because they change based on system load. However, I'm confused as to why the w83627dhg-isa-0290 values are incorrect. Additionally, why do none of the fan RPM values show up?

Finally, how would I determine which pci-00xx correlates to which temp sensor (CPU1, CPU2, CP3, CPU4, Sys Temp, etc.)? If it would help, I can also post the relevant section of my sensors3.conf file.

My only thought is that when I ran the sensors-detect, it stated that I needed ipmisensors module installed, but it appears to be deprecated. (Or maybe I'm just dumb, and couldn't find it). Does missing the ipmisensors module explain my strange results?

Any help would be greatly appreciated!

Thanks in advance.
 
Last edited:
sfield,

Thank you for your quick response! Luckily, I already had w83795 built and installed. However, I will be removing the jumper in a few minutes (have to kick people off the machine). I will let you know how it turns out.

Thanks again for your help!
 
One could try and use ipmi-si interface (local BMC access)
to extract sensor data that BMC collects. I've had moderate*
success with openipmish.

*) it would read sensor data but throw occasional protocol errors
 
cool... will try some of this later... thanks guys.
 
After configuring JPB1 (BMC Enable / Disable) to disabled, I no longer see the overheating condition. I then just renamed the temp1's in the Gnome Sensors app to the appropriate CPU. Unfortunately, I still don't have the fan information, but will need to revist this issue later.

Thanks again for the quick and accurate help!
 
With the w83795 device loaded, what's the output of the sensors command?

On the supermicro board, it seems that some of the sensor alarms may be set too low. At least the SR5690 chip regularly exceeds the configured critical temperature (70C). You can over-ride this with a line like this in the w83795 section of sensors3.conf:

Code:
set temp3_crit 80           # SR5690

and then run
Code:
sensors -s

If you have IPMI enabled, this will also influence the alarms generated there -- including any event log entries that are triggered. (you may want to look at your IPMI eventlog to verify the source of the alarm(s)).


After configuring JPB1 (BMC Enable / Disable) to disabled, I no longer see the overheating condition. I then just renamed the temp1's in the Gnome Sensors app to the appropriate CPU. Unfortunately, I still don't have the fan information, but will need to revist this issue later.

Thanks again for the quick and accurate help!
 
As IPMI pulls sensors periodically, its accesses (on all 4P G34 Supermicro boards) may collide with
Linux accesses (and neither is capable of proper recovery). I recommend using either IPMI or Linux'
sensors (disable IPMI) in exclusive fashion.

Linux includes support for w83795 since version 2.6.37 (thought of posting that for those who may
be interested).
 
Okay, I followed the directions here, but the new found sensors did not survive a reboot as (I deduce) the chip drivers hadn't been written to /etc/modules. Here's my complete log of what needed to be done in order to get all the sensors for my SM board working. Please note that this is after disabling IPMI using JPB1 and adding chip "w83795g-*" to /etc/sensors3.conf as referenced earlier in this thread.

Code:
rick@Server5:~$ uname -r
2.6.35-31-generic (Ubuntu 10.10)
rick@Server5:~/tweaks$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Supermicro H8QGL

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): 
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627DHG-P Super IO Sensors'                Success!
    (address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   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): 
Found `IPMI BMC KCS'...                                     Success!
    (confidence 8, driver `ipmisensors')

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): 
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): 
Client found at address 0x2d
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85'...                No
Probing for `National Semiconductor LM96000 or PC8374L'...  No
Probing for `Analog Devices ADM1027'...                     No
Probing for `Analog Devices ADT7460 or ADT7463'...          No
Probing for `SMSC EMC6D100 or EMC6D101'...                  No
Probing for `SMSC EMC6D102'...                              No
Probing for `SMSC EMC6D103'...                              No
Probing for `Winbond WPCD377I'...                           No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Analog Devices ADT7490'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `Analog Devices ADM1024'...                     No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83783S'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        Success!
    (confidence 8, driver `use-isa-instead')
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L784R/AR/G'...                      No
Probing for `Winbond W83L785R/G'...                         No
Probing for `Genesys Logic GL518SM'...                      No
Probing for `Genesys Logic GL520SM'...                      No
Probing for `Genesys Logic GL525SM'...                      No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Philips NE1619'...                             No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `VIA VT1211 (I2C)'...                           No
Probing for `ITE IT8712F'...                                No
Probing for `ALi M5879'...                                  No
Probing for `SMSC LPC47M15x/192/292/997'...                 No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Winbond W83791SD'...                           No
Client found at address 0x2f
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        Success!
    (confidence 8, driver `w83795')
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `Fintek custom power control IC'...             No
Probing for `Winbond W83791SD'...                           No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
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'...                                 No

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

Driver `w83627ehf':
  * ISA bus, address 0x290
    Chip `Winbond W83627DHG-P Super IO Sensors' (confidence: 9)

Driver `ipmisensors':
  * ISA bus
    Chip `IPMI BMC KCS' (confidence: 8)

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

Driver `w83795':
  * Bus `SMBus PIIX4 adapter at 0b00'
    Busdriver `i2c_piix4', I2C address 0x2f
    Chip `Nuvoton W83795G/ADG' (confidence: 8)

Warning: the required module ipmisensors 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.

Warning: the required module w83795 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.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# Chip drivers
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK

rick@Server5:~/tweaks$ sudo /etc/init.d/module-init-tools restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service module-init-tools restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart module-init-tools
module-init-tools stop/waiting
rick@Server5:~/tweaks$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +21.5°C  (high = +70.0°C, crit = +70.0°C)  

k10temp-pci-00cb
Adapter: PCI adapter
temp1:       +21.4°C  (high = +70.0°C)                  

w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:       +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in1:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
AVCC:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
VCC:         +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
in4:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in5:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in6:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
3VSB:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
Vbat:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
fan1:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan2:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan3:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan4:          0 RPM  (min =    0 RPM, div = 128)  ALARM
temp1:        -1.0°C  (high =  -1.0°C, hyst =  -1.0°C)  ALARM  sensor = diode
temp2:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
temp3:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
cpu0_vid:   +0.375 V

rick@Server5:~/tweaks$ modprobe w83795
FATAL: Module w83795 not found.
rick@Server5:~/tweaks$ mkdir w83795_sensor
rick@Server5:~/tweaks$ cd w83795_sensor
rick@Server5:~/tweaks/w83795_sensor$ ls
rick@Server5:~/tweaks/w83795_sensor$ wget http://khali.linux-fr.org/devel/misc/w83795/Makefile
--2012-01-05 11:18:41--  http://khali.linux-fr.org/devel/misc/w83795/Makefile
Resolving khali.linux-fr.org... 194.79.128.128, 2001:7a8:0:fe01::1
Connecting to khali.linux-fr.org|194.79.128.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1356 (1.3K) [text/plain]
Saving to: `Makefile'

100%[======================================>] 1,356       --.-K/s   in 0s      

2012-01-05 11:18:42 (15.6 MB/s) - `Makefile' saved [1356/1356]

rick@Server5:~/tweaks/w83795_sensor$ wget http://khali.linux-fr.org/devel/misc/w83795/README
--2012-01-05 11:18:54--  http://khali.linux-fr.org/devel/misc/w83795/README
Resolving khali.linux-fr.org... 194.79.128.128, 2001:7a8:0:fe01::1
Connecting to khali.linux-fr.org|194.79.128.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 304 [text/plain]
Saving to: `README'

100%[======================================>] 304         --.-K/s   in 0s      

2012-01-05 11:18:54 (54.8 MB/s) - `README' saved [304/304]

rick@Server5:~/tweaks/w83795_sensor$ wget http://khali.linux-fr.org/devel/misc/w83795/i2c-compat.h
--2012-01-05 11:19:04--  http://khali.linux-fr.org/devel/misc/w83795/i2c-compat.h
Resolving khali.linux-fr.org... 194.79.128.128, 2001:7a8:0:fe01::1
Connecting to khali.linux-fr.org|194.79.128.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1690 (1.7K) [text/x-c]
Saving to: `i2c-compat.h'

100%[======================================>] 1,690       --.-K/s   in 0s      

2012-01-05 11:19:04 (15.3 MB/s) - `i2c-compat.h' saved [1690/1690]

rick@Server5:~/tweaks/w83795_sensor$ wget http://khali.linux-fr.org/devel/misc/w83795/w83795.c
--2012-01-05 11:19:14--  http://khali.linux-fr.org/devel/misc/w83795/w83795.c
Resolving khali.linux-fr.org... 194.79.128.128, 2001:7a8:0:fe01::1
Connecting to khali.linux-fr.org|194.79.128.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 65665 (64K) [text/x-c]
Saving to: `w83795.c'

100%[======================================>] 65,665      --.-K/s   in 0.02s   

2012-01-05 11:19:15 (2.97 MB/s) - `w83795.c' saved [65665/65665]

rick@Server5:~/tweaks/w83795_sensor$ ls
i2c-compat.h  Makefile  README  w83795.c
rick@Server5:~/tweaks/w83795_sensor$ make
  CC [M]  /home/rick/tweaks/w83795_sensor/w83795.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/rick/tweaks/w83795_sensor/w83795.mod.o
  LD [M]  /home/rick/tweaks/w83795_sensor/w83795.ko
rick@Server5:~/tweaks/w83795_sensor$ sudo make install
test -d /lib/modules/2.6.35-31-generic/kernel/drivers/hwmon || mkdir /lib/modules/2.6.35-31-generic/kernel/drivers/hwmon
cp w83795.ko /lib/modules/2.6.35-31-generic/kernel/drivers/hwmon
depmod -a -F /boot/System.map-2.6.35-31-generic 2.6.35-31-generic
rick@Server5:~/tweaks/w83795_sensor$ sudo modprobe w83795
rick@Server5:~/tweaks/w83795_sensor$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +21.2°C  (high = +70.0°C, crit = +70.0°C)  

k10temp-pci-00cb
Adapter: PCI adapter
temp1:       +21.2°C  (high = +70.0°C)                  

w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:       +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in1:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
AVCC:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
VCC:         +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
in4:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in5:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
in6:         +2.04 V  (min =  +2.04 V, max =  +2.04 V)   ALARM
3VSB:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
Vbat:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
fan1:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan2:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan3:          0 RPM  (min =    0 RPM, div = 128)  ALARM
fan4:          0 RPM  (min =    0 RPM, div = 128)  ALARM
temp1:        -1.0°C  (high =  -1.0°C, hyst =  -1.0°C)  ALARM  sensor = diode
temp2:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
temp3:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = diode
cpu0_vid:   +0.375 V

w83795g-i2c-0-2f          #hurrah, new sensors found
Adapter: SMBus PIIX4 adapter at 0b00
in0:         +1.23 V  (min =  +0.68 V, max =  +1.33 V)   
in1:         +0.03 V  (min =  +0.68 V, max =  +1.33 V)   ALARM
in2:         +0.03 V  (min =  +0.68 V, max =  +1.33 V)   ALARM
in3:         +0.03 V  (min =  +0.68 V, max =  +1.33 V)   ALARM
in4:         +1.53 V  (min =  +1.08 V, max =  +1.65 V)   
in5:         +0.04 V  (min =  +1.08 V, max =  +1.65 V)   ALARM
in6:         +0.04 V  (min =  +1.08 V, max =  +1.65 V)   ALARM
in7:         +0.04 V  (min =  +1.08 V, max =  +1.65 V)   ALARM
in8:         +1.28 V  (min =  +1.13 V, max =  +1.38 V)   
in9:         +1.85 V  (min =  +1.63 V, max =  +2.00 V)   
in10:        +1.11 V  (min =  +0.98 V, max =  +1.21 V)   
in11:        +1.16 V  (min =  +1.48 V, max =  +1.82 V)   ALARM
in12:        +3.32 V  (min =  +2.95 V, max =  +3.67 V)   
in13:        +3.31 V  (min =  +2.95 V, max =  +3.67 V)   
in14:        +3.10 V  (min =  +2.95 V, max =  +3.67 V)   
fan1:          0 RPM  (min =  709 RPM)  ALARM
fan2:          0 RPM  (min =  709 RPM)  ALARM
fan3:          0 RPM  (min =  709 RPM)  ALARM
fan4:       1267 RPM  (min =  709 RPM)
fan5:          0 RPM  (min =  709 RPM)  ALARM
fan6:          0 RPM  (min =  709 RPM)  ALARM
fan7:          0 RPM  (min =  709 RPM)  ALARM
fan8:          0 RPM  (min =  709 RPM)  ALARM
fan9:          0 RPM  (min =  709 RPM)  ALARM
fan10:      5744 RPM  (min =  709 RPM)
fan11:         0 RPM  (min =  709 RPM)  ALARM
temp1:      -128.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
temp2:      -128.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
temp3:       +50.5°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
temp4:      -128.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = thermal diode
temp5:       +26.0°C  (high = +75.0°C, hyst = +70.0°C)  
                      (crit = +75.0°C, hyst = +70.0°C)  sensor = thermistor
temp7:       +24.2°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
temp8:        +0.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
temp9:        +0.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
temp10:       +0.0°C  (high = +70.0°C, hyst = +65.0°C)  
                      (crit = +70.0°C, hyst = +65.0°C)  sensor = AMD AMDSI
beep_enable:disabled

rick@Server5:~/tweaks/w83795_sensor$ 

rick@Server5:~$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Supermicro H8QGL

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): 
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627DHG-P Super IO Sensors'                Success!
    (address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   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): 
Found `IPMI BMC KCS'...                                     Success!
    (confidence 8, driver `ipmisensors')

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): 
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): 
Client found at address 0x2d
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85'...                No
Probing for `National Semiconductor LM96000 or PC8374L'...  No
Probing for `Analog Devices ADM1027'...                     No
Probing for `Analog Devices ADT7460 or ADT7463'...          No
Probing for `SMSC EMC6D100 or EMC6D101'...                  No
Probing for `SMSC EMC6D102'...                              No
Probing for `SMSC EMC6D103'...                              No
Probing for `Winbond WPCD377I'...                           No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Analog Devices ADT7490'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `Analog Devices ADM1024'...                     No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83783S'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        Success!
    (confidence 8, driver `use-isa-instead')
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L784R/AR/G'...                      No
Probing for `Winbond W83L785R/G'...                         No
Probing for `Genesys Logic GL518SM'...                      No
Probing for `Genesys Logic GL520SM'...                      No
Probing for `Genesys Logic GL525SM'...                      No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Philips NE1619'...                             No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `VIA VT1211 (I2C)'...                           No
Probing for `ITE IT8712F'...                                No
Probing for `ALi M5879'...                                  No
Probing for `SMSC LPC47M15x/192/292/997'...                 No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Winbond W83791SD'...                           No
Client found at address 0x2f
Handled by driver `w83795' (already loaded), chip type `w83795g'
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
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'...                                 No

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

Driver `w83627ehf':
  * ISA bus, address 0x290
    Chip `Winbond W83627DHG-P Super IO Sensors' (confidence: 9)

Driver `ipmisensors':
  * ISA bus
    Chip `IPMI BMC KCS' (confidence: 8)

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

Driver `w83795':
  * Bus `SMBus PIIX4 adapter at 0b00'
    Busdriver `i2c_piix4', I2C address 0x2f
    Chip `w83795g' (confidence: 6)

Warning: the required module ipmisensors 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.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# Chip drivers
w83627ehf
w83795   #ah ha, now we are going to add the new chip driver!
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

Unloading i2c-dev... OK

rick@Server5:~$

After a kernel upgrade in Ubuntu 10.10, it appears that you need to reapply the changes made. Assuming you still have the directory for the w83795 sensor, here's what needs to be done after you have installed and rebooted to the new kernel:

Code:
rick@Server5:~/tweaks/w83795_sensor$ make
  CC [M]  /home/rick/tweaks/w83795_sensor/w83795.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/rick/tweaks/w83795_sensor/w83795.mod.o
  LD [M]  /home/rick/tweaks/w83795_sensor/w83795.ko
rick@Server5:~/tweaks/w83795_sensor$ sudo make install
test -d /lib/modules/2.6.35-32-generic/kernel/drivers/hwmon || mkdir /lib/modules/2.6.35-32-generic/kernel/drivers/hwmon
cp w83795.ko /lib/modules/2.6.35-32-generic/kernel/drivers/hwmon
depmod -a -F /boot/System.map-2.6.35-32-generic 2.6.35-32-generic
rick@Server5:~/tweaks/w83795_sensor$ sudo modprobe w83795
rick@Server5:~$ sudo sensors-detect
Write the changes
Reboot
 
Last edited:
Back
Top