Hi Guenter,
--------------------------------------------------
From: "Guenter Roeck" <guenter.roeck@xxxxxxxxxxxx>
Sent: Thursday, March 10, 2011 6:06 AM
To: "Robert Kaiser" <kairo@xxxxxxxx>
Cc: <lm-sensors@xxxxxxxxxxxxxx>
Subject: Re: RFC: nct6776f support in the w83627ehf and fan
RPMsignal de-bounce
Hi again,
On Wed, Mar 09, 2011 at 10:45:30PM -0500, Guenter Roeck wrote:
[ ... ]
> fan1: 0 RPM (min = 0 RPM, div = 64)
> fan2: 1110 RPM (min = 0 RPM, div = 32) ALARM
> fan3: 0 RPM (min = 0 RPM, div = 64)
> fan4: 0 RPM (div = 64)
>
[ ... ]
Looks reasonable. There is one problem which I had wondered about - the
ALARM
which tends to show up for running fans.
I finally tracked that down. Turns out the chip has a "maximum RPM"
register.
Apparently that register is not set, which causes the alarm.
Actually, I am not sure if I got that right. Can you set the minimum speed
of fan2
to something larger than 1110 rpm and check if that causes ALARM to go off
?
I suspect I might have misinterpreted the meaning of "Fan Count Limit". I
thought
it is the low limit, but it might well be the high limit.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Are you sure, on my nct6776f the fan alarming appears to work correctly:-
HD: 532 RPM (min = 200 RPM)
CPU: 1043 RPM (min = 500 RPM)
Case Back: 990 RPM (min = 500 RPM)
Case Front: 765 RPM (min = 500 RPM)
fan5: 0 RPM (min = 0 RPM) ALARM
note those are exactly the minimum values I've entered into sensors3.conf
and when the fan speed drops below these values I see an alarm.
Regards
Ian Dobson
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
