lm-sensors will not find it8705f with new kernel update

[C0ntract0r]

Ubuntu 9.10

I have as of today, updated to kernel 2.6.31-19. Previously, my lm-sensors would work perfectly with it8705F, I have a Soyo SY-P4VGM motherboard. Nothing else changed except the kernel update today, and upon reboot, would not find my sensors (two fan speeds, 3 temp sensors). It only shows this from sensors:

acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +75.0°C)

Before the update, it showed 3 sensors, and 2 fan speeds, and also listed my it87 hardware.

I had written a custom conky script for these options, and I only noticed it because the info did not show up.

I have re-ran sensors-detect, have made sure that the it87 module is in /etc/modules, but alas, cannot get it to work.

Would be glad to provide any info needed.

Also attached is my output from sensors-detect.

Thank you.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 5 21:12:11 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: lm-sensors 1:3.0.2-2ubuntu4
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: lm-sensors-3
Uname: Linux 2.6.31-19-generic i686
XsessionErrors:
 (gnome-settings-daemon:1626): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1626): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1715): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1722): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2067): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Daniel Letzeisen (dtl131)]

Does the it87 module load properly? Check output of lsmod command. If it's not loaded, try loading it manually and checking dmesg if it doesn't load to see why, so, to summarize:
lsmod | grep it87 #will return lines corresponding to it87 if module is loaded, returns nothing otherwise
sudo modprobe -v it87 #load it87 (with verbose option)
dmesg

I had this issue with my motherboard when moving to a recent kernel: http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

[C0ntract0r (james-4156)]

Mr Lentz,

Thank you for replying to my situation, I am a fairly new "Linux person", but I have been learning for about two years now on Ubuntu. I haven't gotten very involved with the community (but I do intend to), and this is very encouraging to me to see such a helpful response.

I figured out, just this morning how to fix this problem..

I added acpi_enforce_resources=lax to the boot line in grub.lst

Dave, could you advise me if I should leave the bug report up, or add my "solution" to it, I suppose it should still be looked at, but I want people in the same situation to know that this "fix", did in fact, "fix it", for lack of a better explanation.

Again, thank you for your reply.

James

--- On Sun, 2/7/10, Dave Lentz <email address hidden> wrote:

> From: Dave Lentz <email address hidden>
> Subject: [Bug 517897] Re: lm-sensors will not find it8705f with new kernel update
> To: <email address hidden>
> Date: Sunday, February 7, 2010, 4:46 PM
> Does the it87 module load properly?
> Check output of lsmod command. If it's not loaded, try
> loading it manually and checking dmesg if it doesn't load to
> see why, so, to summarize:
> lsmod | grep it87  #will return lines
> corresponding  to it87 if module is loaded, returns
> nothing otherwise
> sudo modprobe -v it87 #load it87 (with verbose option)
> dmesg
>
> I had this issue with my motherboard when moving to a
> recent kernel:
> http://www.lm-
> sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>
> --
> lm-sensors will not find it8705f with new kernel update
> https://bugs.launchpad.net/bugs/517897
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “lm-sensors-3” package in Ubuntu: New
>
> Bug description:
> Ubuntu 9.10
>
> I have as of today, updated to kernel
> 2.6.31-19.   Previously, my lm-sensors would
> work perfectly with it8705F, I have a Soyo SY-P4VGM
> motherboard.  Nothing else changed except the kernel
> update today, and upon reboot, would not find my sensors
> (two fan speeds, 3 temp sensors).  It only shows this
> from sensors:
>
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:       +40.0°C  (crit
> = +75.0°C)
>
> Before the update, it showed 3 sensors, and 2 fan speeds,
> and also listed my it87 hardware.
>
> I had written a custom conky script for these options, and
> I only noticed it because the info did not show up.
>
> I have re-ran sensors-detect, have made sure that the it87
> module is in /etc/modules, but alas, cannot get it to work.
>
> Would be glad to provide any info needed.
>
> Also attached is my output from sensors-detect.
>
> Thank you.
>
> ProblemType: Bug
> Architecture: i386
> Date: Fri Feb  5 21:12:11 2010
> DistroRelease: Ubuntu 9.10
> NonfreeKernelModules: nvidia
> Package: lm-sensors 1:3.0.2-2ubuntu4
> ProcEnviron:
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
> SourcePackage: lm-sensors-3
> Uname: Linux 2.6.31-19-generic i686
> XsessionErrors:
> (gnome-settings-daemon:1626): GLib-CRITICAL **:
> g_propagate_error: assertion `src != NULL' failed
> (gnome-settings-daemon:1626): GLib-CRITI...

[C0ntract0r (james-4156)]

I would like to add, that this morning I figured out a "solution" to my problem.

I added:

acpi_enforce_resources=lax

to my boot line in /boot/grub/menu.lst

I am not educated enough to know if this is a proper fix, or a workaround, but regardless, it brought my sensors back to functional status.

Dave Lentz, Thank you for your help and attention.

My apologies if I should not have reported this as a "bug", I am fairly new in the GNU/Linux world, and I was only attempting to be helpful.

[Daniel Letzeisen (dtl131)]

It's a dirty hack, and I recommend that you don't run it. It would be better to get the ACPI issue fixed with your motherboard vendor.

"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. "

[Phillip Susi (psusi)]

The problem is that virtually no motherboards actually implement ACPI properly, so it is either use the it87 driver, or go without power management and fan control. Given the choice, most people will take the latter. I suggest that if possible, Ubuntu start building its kernel with the relaxed resource enforcement on by default.