On Tue, Aug 21, 2012 at 04:02:32PM +0200, Luca Tettamanti wrote: > On Tue, Aug 21, 2012 at 03:43:24PM +0200, Göran Uddeborg wrote: > > Luca Tettamanti: > > > Hum, this is likely a bug in ACPI code, please send me a copy of > > > /sys/firmware/acpi/tables/DSDT > > > > Sent off list. In case anyone else also would be interested, I placed > > it at ftp://ftp.uddeborg.se/pub/DSDT too. > > Yep, broken BIOS: > > Method (FGET, 1, NotSerialized) > { > If (LEqual (Arg0, Zero)) > { > Return (^^SIOR.HWF1 ()) > } > > If (LEqual (Arg0, One)) > { > Return (^^SIOR.HWF1 ()) > } > } > > It always reads the same sensor. The other ("new") monitoring interface > seems fine though. Unload the module and try reloading it with > "new_if=1", like this: > > modprobe asus_atk0110 new_if=1 > > And see if everything looks good. > If it does, should we add the board to atk_force_new_if[] ? Guenter _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
