http://bugzilla.novell.com/show_bug.cgi?id=544867 User frankebay99@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=544867#c3 Francis Lamonde <frankebay99@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |UPSTREAM --- Comment #3 from Francis Lamonde <frankebay99@gmail.com> 2009-10-07 20:20:06 MDT --- Ok got it. So yes, since 2.6.31 (2.6.30, but there was a bug so it hit only in 2.6.31 (and 2.6.29 for Fedora)) there is a new way to talk with sensors which does not conflict with acpi on the ports. This is mostly for recent MB models to prevent 2 processes to talk to the ports and potentially freeze the machine.. Mine is 2yo, so it's older and I should not have that problem. I ran 2 years without issues so I take the risk to continue the legacy way. For those people (legacy), or for the risky ones, you can edit your 'menu.lst' (grub.conf for some other distros) in /boot/grub and make sure you have the option 'acpi_enforce_resources=lax'. Something like this: --- kernel /boot/vmlinuz-2.6.31-10-desktop root=/dev/sdb1 resume=/dev/disk/by-id/ata-ST3500320AS_5QM0PP7M-part5 splash=silent quiet showopts acpi_enforce_resources=lax vga=0x317 initrd /boot/initrd-2.6.31-10-desktop --- Of course, reboot. If you run 'sensors', you'll notice it show a lot more sensors than before. Good news. Then run pwmconfig. It will not display the error anymore, but it might still fail to control/test the fans. Continue the test up to the point it creates the FANCONTROL file. Then quit and either run 'sudo fancontrol' to see if it works, or edit the file to ensure driver 'atk01100' is associated with 'hwmon0' and that the sensors are associated with another number. In my case it was 'hwmon5'. Not superclean, but for older MB it's risk free and it works. Closing. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.