Bug 165819
Summary: | IBM ACPI extensions hosed after updating ACPI | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Frieben <jfrieben> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | byte, canfield, davidp, gc, intel-linux-acpi, liblit, mjs, noa, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-30 09:56:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 165150 |
Description
Joachim Frieben
2005-08-12 15:46:21 UTC
Sorry, I obviously meant to write: "Curiously, there is still an "ibm_acpi.ko" module present in "/lib/modules/2.6.12-1.1420_FC4/kernel/drivers/acpi" but it cannot be loaded." Can you try the errata kernel in updates-testing please ? That has an ACPI update which may fix your problem. *** Bug 167078 has been marked as a duplicate of this bug. *** To which errata kernel in updates-testing are you referring? There are a few, and all are lower release numbers than kernel-2.6.12-1.1447_FC4 (which has the same issue, as noted in Bug 167078). That comment was made before 1447 got pushed to final updates. Yes but the problem persists with 1447 (on my Thinkpad X40) [root@myrte beppe]# uname -a Linux myrte 2.6.12-1.1447_FC4 #1 Fri Aug 26 20:29:51 EDT 2005 i686 i686 i386 GNU/Linux [root@myrte beppe]# modprobe -v ibm_acpi insmod /lib/modules/2.6.12-1.1447_FC4/kernel/drivers/acpi/ibm_acpi.ko FATAL: Error inserting ibm_acpi (/lib/modules/2.6.12-1.1447_FC4/kernel/drivers/acpi/ibm_acpi.ko): No such device No improvement for ACPI updates of kernel-2.6.12-1.1450_FC4. The "ibm-acpi" package (v0.8 to v0.11) seems to lag behind and needs to be adapted to the current ACPI trunk. FWIW, the ibm_acpi.ko loads just fine under the 2.6.11 kernel that was released with FC4. All errata kernels numbered 2.6.12 break this. Are you sure? It worked perfectly for me (T41) from kernel-2.6.11-1.1369_FC4 through kernel-2.6.12-1.1398_FC4: $ uname -r 2.6.12-1.1398_FC4 $ lsmod |grep ibm_acpi ibm_acpi 15997 0 $ dmesg | grep ibm_acpi ibm_acpi: IBM ThinkPad ACPI Extras v0.8 ibm_acpi: http://ibm-acpi.sf.net/ ibm_acpi: dock device not present But it broke for me when I installed kernel-2.6.12-1.1447_FC4. Obviously, it broke for the OP at kernel-2.6.12-1.1420_FC4 (which I never tried). Nope, not sure at all. :-) I think I tested the other three kernels but missed this one. I can indeed confirm that the included 0.8 ibm_acpi as well as the 0.10 from the web site both load fine in 2.6.12-1.1398. Sorry for the incorrect info. Issue resolved for kernel-2.6.13-1.1552_FC5. "ibm-acpi" received an update from Len Brown (v0.12a). Will hopefully apply to FC4 as soon as 2.6.13 is considered stable enough. This bug persists 2.6.12-1.1456_FC4 as tested on my thinkpad x40, which means I keep running kernel 2.6.12-1.1398_FC4. Is there a workaround for this, or should I wait for kernel 2.6.13? There's a preview of the 2.6.13 kernel in updates-testing right now if you want to try that (though it may have other problems too right now, which is why its in -testing, not -final yet) I can confirm that using kernel-2.6.13-1.1524_FC4.i686.rpm from -testing restores the ability to load the ibm_acpi module. Tested on an ThinkPad T30. Same here on T41. So far (after the latest updates-testing selinux-policy-targeted) it looks like all functionality is restored. From the boot messages, it looks like there have been some changes in ibm_acpi. Do they affeect functionality? Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. Apparently fixed in 2.6.13-1.1526_FC4. After upgrading to 2.6.13-1.1526_FC4, /proc/acpi/sleep no longer exists, so I am no longer able to suspend. I have no problem with 2.6.12-1.1398_FC4. (In reply to comment #18) > After upgrading to 2.6.13-1.1526_FC4, /proc/acpi/sleep no longer exists, so I am > no longer able to suspend. I have no problem with 2.6.12-1.1398_FC4. See bug #169200. Not sure how we were all supposed to have divined this change, but that solution works fine. (In reply to comment #19) > (In reply to comment #18) > ... > See bug #169200. Not sure how we were all supposed to have divined this change, > but that solution works fine. Yes, that works. Thanks! |