Hi David, > # isadump -f 0x0680 0x80 > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: 01 00 01 00 18 ff e7 18 00 00 18 00 00 00 00 00 > 10: 02 06 67 18 c0 00 00 00 00 00 00 00 00 00 03 03 > 20: 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 > 30: 00 00 00 05 05 04 04 01 00 04 84 84 00 01 01 05 > 40: 05 05 04 05 04 05 04 01 01 00 00 00 84 13 04 57 > 50: 00 00 00 00 00 00 14 14 f0 ff ff 68 68 00 00 00 > 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Bits 6 and 7 of register 0x04 are actually cleared, so this is no driver bug. The chipset doesn't set the flags. After reading the datasheet again, I don't thing there is a way to disable them, so they have to be enabled (but not set at the moment). Could be that the chipset does only raise an alarm on slow fan, not on stopped/absent fan. Doesn't make much sense of course, but that may still be true. I'd suggest that you give a try with a working fan and make sure you get a valid speed reported. Then change the low limit above the fan speed, and see if the alarm triggers. If it does, but disappears if you then unplug the fan, then I guess it validates my theory. We may consider faking the alarm bits it this specific case, since it's odd that the chipset doesn't do it, and is contrary to what other chips such as the LM87 do, if I'm not mistaken. -- Jean Delvare http://khali.linux-fr.org/
