Changes between Version 12 and Version 13 of FAQ/Chapter3

Timestamp:

10/05/09 18:47:29 (4 years ago)

Author:

khali

Comment:

asus_atk0110 needs lm-sensors >= 3.1.0

FAQ/Chapter3

@@ -711 +711 @@
 With previous kernels hwmon drivers used to drive IO ranges which were potentially used by the ACPI code  in your BIOS (which is active not only during but also after boot), we now explicitly check for this and if the ACPI code claims the IO-ports used by the hwmon chip, we no longer allow the hwmon driver to load.
 
-Banging IO-ports of a chip from 2 different drivers, the Linux hwmon driver and the ACPI code is a *really* bad idea and can cause all sort of issues (including things like changing CPU / RAM voltage or clock speed). So the old behaviour was a really bad idea.
+Banging IO-ports of a chip from 2 different drivers, the Linux hwmon driver and the ACPI code is a '''really''' bad idea and can cause all sort of issues (including things like changing CPU / RAM voltage or clock speed). So the old behaviour was a really bad idea.
 
 So even though this change in behaviour makes some people unhappy as to old behaviour happened to work without problems in their case (by sheer luck really), this change is really for the best!
 
 If you have an Asus motherboard, chances are good there is an ACPI interface to read your sensors, which is safe, and no more sensors.conf tweaking needed for
-conversion formulas! Make sure you have the asus_atk0110 driver enabled in your kernel configuration to use this.
+conversion formulas! Make sure you have the asus_atk0110 driver enabled in your kernel configuration to use this. You will also need lm-sensors version 3.1.0 or later.
 
 If you want to restore the old behaviour (which might be dangerous) add: "acpi_enforce_resources=lax" to the kernel cmdline when booting (or add it in grub.conf to make this permanent).