Re: Creating alarm for fans

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

 



Hi Karl,

On Wed, 02 Sep 2009 12:02:47 -0500, Karl Schmidt wrote:
> Jean Delvare wrote:
> > Please try this too, for example set in0_max to 1.0V and see if
> > in0_alarm gets raised.
> 
> no joy..
> #sensors
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:  +24.0°C
> 
> lm85b-i2c-0-2e
> Adapter: SMBus nForce2 adapter at 1c00
> V1.5:        +1.30 V  (min =  +0.00 V, max =  +1.00 V)
> VCore:       +1.42 V  (min =  +0.00 V, max =  +2.99 V)
> V3.3:        +3.33 V  (min =  +0.00 V, max =  +4.38 V)
> V5:          +5.08 V  (min =  +0.00 V, max =  +6.64 V)
> V12:        +12.06 V  (min =  +0.00 V, max = +15.94 V)
> CPU_Fan:    7826 RPM  (min = 8000 RPM)
> Fan2:       8181 RPM  (min =    0 RPM)
> Fan3:       7917 RPM  (min =    0 RPM)
> Fan4:       7929 RPM  (min =    0 RPM)
> CPU Temp:    +39.0°C  (low  = -127.0°C, high = +127.0°C)
> Board Temp:  +28.0°C  (low  = -127.0°C, high = +127.0°C)
> Remote Temp: +24.0°C  (low  = -127.0°C, high = +127.0°C)
> cpu0_vid:   +1.550 V

> > (...)
> > Does "alarms" read 0 as well?
> 
> yes - all alarms files read zero
> /sys/class/hwmon/hwmon1/device# cat alarms
> 0

OK, this rules out a user-space issue. The problem must be either at
the hardware level or in the lm85 driver.

Please unload the lm85 driver temporarily, load the i2c-dev driver, and
provide the output of the following command:

i2cdump 0 0x2e

This will dump all the device registers. I will then check against the
datasheet and see if I spot anything.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


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

  Powered by Linux