sensors problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ryan,

On Mon, 9 Jul 2007 11:07:06 -0500, Ryan Underwood wrote:
> 
> I have a MSI BXMaster, and lm-sensors 2.10.3 from Debian and kernel
> 2.6.21.1.  Why am I having the following issues in the sensors output:
> 
> $ sensors
> w83782d-i2c-0-2d
> Adapter: SMBus PIIX4 adapter at 5000
> VCore 1:   +1.47 V  (min =  +0.00 V, max =  +4.08 V)
> VCore 2:   +1.50 V  (min =  +0.00 V, max =  +4.08 V)
> +3.3V:     +3.41 V  (min =  +2.82 V, max =  +3.79 V)
> +5V:       +5.05 V  (min =  +5.75 V, max =  +4.27 V)       ALARM
> +12V:     +12.34 V  (min = +15.50 V, max =  +7.72 V)       ALARM
> -12V:     -12.11 V  (min =  -9.40 V, max =  +3.10 V)       ALARM
> -5V:       -5.15 V  (min =  +5.10 V, max =  +1.89 V)       ALARM
> V5SB:      +5.05 V  (min =  +4.87 V, max =  +1.69 V)       ALARM
> VBat:      +2.90 V  (min =  +0.85 V, max =  +3.57 V)
> fan1:     3443 RPM  (min = 1670 RPM, div = 8)
> fan2:        0 RPM  (min =  669 RPM, div = 8)              ALARM
> fan3:     5232 RPM  (min = 2922 RPM, div = 2)
> temp1:       +42?C  (high =  +124?C, hyst =   -28?C)   sensor = thermistor      
> temp2:     +39.0?C  (high =   +80?C, hyst =   +75?C)   sensor = thermistor      
> temp3:     +40.5?C  (high =   +80?C, hyst =   +75?C)   sensor = thermistor      
> vid:      +1.500 V  (VRM Version 8.5)
> alarms:
> beep_enable:
>           Sound alarm enabled
> 
> It appears the sensors themselves are correct, but the ranges are all wrong...
> in fact the range slope is reversed.  I am using the default sensors.conf
> packaged with lm-sensors and ensured that it was active with sensors -s.

If you are using the stock 2.10.3 sensors.conf, set statements are
commented out by default. We did this because they were causing trouble
(beeps, reboot etc.) on some systems. It seems that your BIOS leaves
most limits uninitialized. Uncomment the set statements in the
w83782d-* section, run "sensors -s" again and it should be better.

For some features (e.g. fan2) you will have to add your own set
statement (set fan2_min 0) or even better ignore this fan if you don't
have it (ignore fan2).

> Not sure when this started, I had my monitoring script disabled for a while.
> At one point (year ago?) it worked fine.

Until 2.10.0, set statements were enabled by default.

-- 
Jean Delvare




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux