Hi Jeremy, On Sat, 7 Jul 2007 00:11:49 -0400, Jeremy Harmon wrote: > I'm sure these voltage values can't be correct, all of the temps seem > accurate though. > > k8temp-pci-00c3 > Adapter: PCI adapter > Core0 Temp: > +47?C > > w83627thf-isa-0290 > Adapter: ISA adapter > VCore: +1.57 V (min = +0.70 V, max = +1.87 V) > +12V: +3.65 V (min = +0.79 V, max = +0.79 V) ALARM > +3.3V: +3.39 V (min = +0.80 V, max = +0.13 V) ALARM > +5V: +4.96 V (min = +6.45 V, max = +5.33 V) ALARM > -12V: +0.39 V (min = -13.35 V, max = -14.91 V) ALARM > V5SB: +4.95 V (min = +0.91 V, max = +3.44 V) ALARM > VBat: +3.06 V (min = +1.49 V, max = +0.86 V) ALARM > fan1: 0 RPM (min = 9375 RPM, div = 8) ALARM > CPU Fan: 3183 RPM (min = 21093 RPM, div = 8) ALARM > fan3: 6553 RPM (min = 25000 RPM, div = 2) ALARM > M/B Temp: +38?C (high = +125?C, hyst = -25?C) sensor = diode > CPU Temp: +45.0?C (high = +80?C, hyst = -25?C) sensor = diode > temp3: +67.0?C (high = +125?C, hyst = -25?C) sensor = diode > vid: +0.000 V (VRM Version 2.4) > alarms: Chassis intrusion detection ALARM > beep_enable: > Sound alarm enabled > What motherboard is this? "nForce 4" motherboard really doesn't tell us anything, as the sensors are NOT in the nForce4 chip. Most of the voltages look OK to me anyway. Vcore, +3.3V, +5V, V5SB and Vbat look OK, just the limits are not (set them in /etc/sensors.conf). This only leaves +12V and -12V incorrect. Please write down what voltages your BIOS shows (labels and values, in order.) "vid" (the CPU voltage ID) is optional on the W83627THF, it seems not to be implemented on your board, so you can simply ignore it (add an "ignore vid" statement in /etc/sensors.conf.) Fans and temperatures look OK, you only have to set proper labels and limits in /etc/sensors.conf, and run "sensors -s". > > ----------------------------------- > sensors-detect > (...) > Next adapter: SMBus nForce2 adapter at 4c40 > Do you want to scan it? (YES/no/selectively): > Client found at address 0x08 > Client found at address 0x2f > Probing for `National Semiconductor LM78'... No > Probing for `National Semiconductor LM78-J'... 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 W83792D'... No > Probing for `Winbond W83793R/G'... No > Probing for `Winbond W83791SD'... No > Probing for `Winbond W83627HF'... No > Probing for `Winbond W83627EHF'... No > Probing for `Winbond W83627DHG'... No > Probing for `Asus AS99127F (rev.1)'... No > Probing for `Asus AS99127F (rev.2)'... No > Probing for `Asus ASB100 Bach'... 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 W83791D'... No Address 0x2f is typical of hardware monitoring chips, but this version of sensors-detect did not recognize what that chip was. Please try again with a more recent version of lm-sensors, either 2.10.3 or SVN. If you actually have another hardware monitoring chip on your motherboard, this can explain why some of the values reported by the W83627THG Super-I/O chip aren't valid (although it doesn't look too bad either.) -- Jean Delvare
