Red Hat Bugzilla – Bug 207209
LM_SENSORS doesn't work with Asus P4PE
Last modified: 2008-02-05 08:34:59 EST
Description of problem:
lm_sensors 2.9.2-1 fails to find any sensors on boot. The exact same config
worked properly under 2.6.16-1.2111_FC5.
Version-Release number of selected component (if applicable):
Always happens when booting 2.6.17-1.2187_FC5 on an ASUS P4PE.
Steps to Reproduce:
1. configure lm_sensors under a previous kernel.
2. install/upgrade kernel 2.6.17-1.2187_FC5.
lm_sensors fails to find any sensors
lm_sensors should find all the same sensors as the previous kernel
See bug #112740 for more info regarding a possible quirk patch that may have
been left out of the latest build. It references this URL:
This was also reported in bug #197507.
These patches may warrant a second look: (from
Author: Jean Delvare <email@example.com>
Date: Sat Apr 1 16:46:35 2006 +0200
[PATCH] PCI: Add PCI quirk for SMBus on the Asus A6VA notebook
The Asus A6VA notebook was reported to need a PCI quirk to unhide
Signed-off-by: Jean Delvare <firstname.lastname@example.org>
Signed-off-by: Greg Kroah-Hartman <email@example.com>
Author: Carl-Daniel Hailfinger <firstname.lastname@example.org>
Date: Mon May 15 09:44:33 2006 -0700
[PATCH] smbus unhiding kills thermal management
Do not enable the SMBus device on Asus boards if suspend is used. We do
not reenable the device on resume, leading to all sorts of undesirable
effects, the worst being a total fan failure after resume on Samsung P35
Signed-off-by: Carl-Daniel Hailfinger <email@example.com>
Signed-off-by: Pavel Machek <firstname.lastname@example.org>
Signed-off-by: Andrew Morton <email@example.com>
Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Cause pinned to second patch listed above. See
http://lkml.org/lkml/2006/7/26/249 This seems to apply to P4B boards, not P4PE
boards. Can it differentiate?
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.
I am still having this problem with my ASUS p4pe mobo.
Everything worked fine up through kernel:
Any kernel after that (up to 2.6.18-1.2257.fc5) has given me the following
errors on boot up (after "Uncompressing Linux..OK booting kernel"):
ACPI: Invalid PBLK length 
ACPI: Getting cpuindex for acpiid 0x1
Red Hat Nash.....
Then lm_sensors fails. I believe this to be a fairly serious problem. When I
login after all of these errors, my cpu temperture goes through the roof. I
have seen get to as high as 70 C before I shut down, whereas it normally
operates around 55 C.
100% reproducible.....just login to any kernel after 2.6.15-1.2054_FC5.
Everything noted above works fine in that kernel.
thanks for any help!
Closing since there was an error in previous mass-close and they remained in