On Wed, 02 Sep 2009 11:41:31 -0500, Karl Schmidt wrote: > Jean Delvare wrote: > > Hi Karl, > > > > On Fri, 28 Aug 2009 13:36:18 -0500, Karl Schmidt wrote: > >> I hope this isn't a stupid question -but google didn't get me there.. > >> > >> Please cc -- I'm off list.. > >> > >> I used to be able to get an alarm for fans - but now I don't. > >> > >> > >> chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*" > >> > >> # Voltage inputs > >> # Depending on the hardware setup, the ADT7463 may not have in4. > >> label in0 "V1.5" # AGP on Intel S845WD1-E > >> label in1 "VCore" > >> label in2 "V3.3" > >> label in3 "V5" > >> label in4 "V12" > >> > >> # Temperature inputs > >> label temp1 "CPU Temp" > >> label temp2 "Board Temp" > >> label temp3 "Remote Temp" > >> > >> # Fan inputs > >> label fan1 "CPU_Fan" > >> label fan2 "Fan2" > >> label fan3 "Fan3" > >> label fan4 "Fan4" > >> set fan1_min 8000 > >> > >> > >> > >> > >> lm85b-i2c-0-2e > >> Adapter: SMBus nForce2 adapter at 1c00 > >> V1.5: +1.30 V (min = +0.00 V, max = +3.32 V) > >> VCore: +1.42 V (min = +0.00 V, max = +2.99 V) > >> V3.3: +3.35 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: 7837 RPM (min = 8000 RPM) > >> Fan2: 8169 RPM (min = 0 RPM) > >> Fan3: 7964 RPM (min = 0 RPM) > >> Fan4: 7917 RPM (min = 0 RPM) > >> CPU Temp: +37.0°C (low = -127.0°C, high = +127.0°C) > >> Board Temp: +26.0°C (low = -127.0°C, high = +127.0°C) > >> Remote Temp: +23.0°C (low = -127.0°C, high = +127.0°C) > >> > >> > >> 2.6.26-2-amd64 #1 SMP > > > > This is strange. The lack of alarms for Fan2, Fan3 and Fan4 can be > > easily explained by the min being set to 0. But for CPU_Fan you should > > get one. > > > > Are you able to get _any_ other alarm flag to raise? Please try this too, for example set in0_max to 1.0V and see if in0_alarm gets raised. > > > > Which version of lm-sensors are you running? > > lm-sensors Debian release 1:3.0.2-1+b2 > #sensors -v > sensors version 3.0.2 with libsensors version 3.0.2) > > > > Can you please locate your chip under /sys/class/hwmon and list the > > name and contents of all the "*alarm*" files there? This will tell us > > whether this is a hardware/driver issue or an lm-sensors (user-space) > > issue. > /sys/class/hwmon - has two directories: hwmon0 and hwmon1 - no alarm files under hwmon0 > > > /sys/class/hwmon/hwmon1/device# ls *alarm* > alarms fan2_alarm fan4_alarm in1_alarm in3_alarm temp1_alarm temp3_alarm > fan1_alarm fan3_alarm in0_alarm in2_alarm in4_alarm temp2_alarm > > All return 0 > > /sys/class/hwmon/hwmon1# cat device/fan1_alarm > 0 > /sys/class/hwmon/hwmon1# cat device/fan3_alarm > 0 > /sys/class/hwmon/hwmon1# cat device/in0_alarm > 0 > etc.. Does "alarms" read 0 as well? -- Jean Delvare _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
