Red Hat Bugzilla – Bug 166895
Acer 1705SMi and 5002 notebooks not detecting battery
Last modified: 2015-01-04 17:21:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
I get reports of an Acer 1705SMi and 5002 notebook not detecting battery. When uplugged they power off, and cannot boot. I suspect either ACPI or the BIOS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
No battery detected in Gnome tray icon
Reporting on behalf of a FedoraForum thread: http://fedoraforum.org/forum/showthread.php?t=66685
Can you try the latest errata kernel from updates-testing please ? That has an
ACPI update which could fix this.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). 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.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
The switch between power and battery is done in hardware/firmware
and is invisible to the OS. This failure is a system issue, not an OS issue.
I expect you'll see the same issue running a non-Linux OS on this box.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
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_REPORTER 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.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.