Ticket #1058 (closed task)
Opened 7 years ago
Multiple sensor readings. (Examined/Solved - lm_sensors 2.6.5 Linux 2.4.19)
| Reported by: | contact | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | hardware | Version: | |
| Keywords: | Cc: |
Description
GigaByte? GA-7VRXP motherboard.
I'm intrigued - here is my sensors output:
max1617-i2c-0-4c
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
Board: +50C (min = +20C, max = +60C)
CPU: +79C (min = +20C, max = +60C)
eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
SDRAM Size (MB): 512
eeprom-i2c-0-51
Adapter: SMBus Via Pro adapter at 0400
Algorithm: Non-I2C SMBus adapter
Memory type: DDR SDRAM DIMM SPD
SDRAM Size (MB): 256
it87-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.79 V (min = +1.53 V, max = +1.87 V)
VCore 2: +1.23 V (min = +2.25 V, max = +2.75 V) ALARM
+3.3V: +3.21 V (min = +1.48 V, max = +1.80 V) ALARM
+5V: +4.77 V (min = +4.50 V, max = +5.48 V)
+12V: +12.52 V (min = +11.36 V, max = +13.80 V)
-12V: -10.95 V (min = -15.86 V, max = -13.40 V) ALARM
-5V: -4.63 V (min = -10.13 V, max = -9.44 V) ALARM
Stdby: +4.86 V (min = +4.50 V, max = +5.48 V)
VBat: +0.00 V
fan1: 5443 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM
Temp1/MB: +42C (min = +20C, max = +60C)
Temp2/CPU: +87C (min = +20C, max = +60C)
Temp3: -55C (min = +20C, max = +60C)
OK, the dodgy voltages don't bother me so much - I'm interested in the
temperatures (AthlonXP 2200+ things get pretty toasty). My question is this -
the max1617 chip gives MB:50, CPU:79, the it87 gives MB:42, CPU:87. I've noticed
the max1617 readings fluctuate much more with system load, which seems
consistent with reliable readings. I'm just not sure which chip gives the more
'correct' readings. Any tips? --- doubtful that multiple chips are connected to the same sensor.
more likely that you have 4 sensors or that some are invalid.
You can use 'cpuburn' (link on our links page) to identify CPU sensor.
You could ask board mfr. for locations of the sensors.
