On Tue, Nov 20, 2012 at 2:42 PM, Luca Tettamanti <kronos.it@xxxxxxxxx> wrote: > On Sat, Nov 17, 2012 at 5:13 PM, Leslie Rhorer <lrhorer@xxxxxxxxxxxx> wrote: >>> >> You can try loading the module forcing the use of a different ACPI >>> >> interface: >>> >> rmmod asus_atk0110 >>> >> modprobe asus_atk0110 new_if=1 >>> > >>> > No, that didn't work. Loading the module with the new_if=1 parm issues >>> an >>> > error: >>> > >>> > FATAL: Error inserting asus_atk0110 >>> > (/lib/modules/2.6.32-5-amd64/kernel/drivers/hwmon/asus_atk0110.ko): >>> Unknown >>> > symbol in module, or unknown parameter (see dmesg) >>> > >>> > And from dmesg: >>> > >>> > [25982.929792] asus_atk0110: Unknown parameter `new_if' >>> >>> What kernel are you using? >> >> 2.6.32-5-amd64 > > Ah, it's too old, it does not support the override. Can you send me a > copy of this file: > /sys/firmware/acpi/tables/DSDT (or /proc/acpi/dsdt if you don't have > the sysfs file). > I'll see if there might be a problem with the detection heuristic. Nope, there's only one interface (GITM), the BIOS probably has hard-coded labels and does not read the ACPI table. Luca _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
