Red Hat Bugzilla – Bug 167281
toshiba_acpi appears to be broken in 2.6.12-1.1447_FC4
Last modified: 2015-01-04 17:21:45 EST
+++ This bug was initially created as a clone of Bug #167218 +++
Description of problem:
With kernel-2.6.12-1.1398_FC4, toshiba_acpi is working, but after upgrade to
kernel-2.6.12-1.1447_FC4 and reboot, it fails to load, saying No such device.
FnFXd, a daemon for managing the Fn key, used for brightness control, sleeping
and so on doesn't work either, since it requires toshiba_acpi to be loaded.
When I boot the previous version, kernel-2.6.12-1.1398_FC4, the module works and
so does FnFXd.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Grab a recent Toshiba laptop (with Toshiba BIOS)
2. Install kernel-2.6.12-1.1447_FC4,
4. when using FnFX, an error message will be printed as soon as it starts,
otherwise search for /proc/acpi/toshiba - should be loaded out of thebox, or
try modprobe toshiba_acpi
Actual Results: toshiba_acpi isn't loaded, saying No such device
Expected Results: toshiba_acpi just works with a Toshiba laptop, as did previously
Same is true for - probably all - IBM Thinkpads. IBM hot buttons do not work
anymore. Loading the ibm_acpi.ko module results in the same error as for the
toshiba_acpi that there's no such device. I guess, this is a result of disabling
the hotkeys in the configuration for the 2.6.12-1.1447 kernel. But the ibm_acpi
module and the hotkey driver were working fine with 2.6.12-1.1398. Actually
related to that, acpi resume is broken now with 2.6.12-1.1447 for a T22 Thinkpad.
Same problem here
Yes, I have quite a few reports of this "broken kernel" breaking the GNOME Power
Manager on FC4. My rawhide image (2.6.13-1.1565_FC5) has no such breakage, but I
appreciate going from 2.6.12 -> 2.6.13 would cause lots of userspace breakage in
a stable FC version. Could we no backport the ACPI patch from 2.6.13 into the
FC4 errata kernel? Many thanks.
I'm not sure this comment really belongs to this bug, but I'm also having
massive ACPI problems on 2.6.12-1.1447 with an HP nc6320. Going back to
2.6.12-1.1398 seems to solve my problems.
this should be fixed in the next update..
You can test this by grabbing the 2.6.13-1.1524 kernel from updates-testing.
2.6.13-1.1524 works for me (on Toshiba Satellite Pro M10)
When will we see this kernel in updates?
Works for me too.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (220.127.116.11). 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.
Works for me with 2.6.13-1.1526_FC4. Closed.