regression: Incorrect battery status reported on Acer laptops in edgy

Bug #73266 reported by Tiede
38
Affects Status Importance Assigned to Milestone
GNOME Applets
Expired
Medium
gnome-power-manager (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Feisty by Emilio Pozuelo Monfort

Bug Description

Binary package hint: gnome-power-manager

The battery status is not reported correctly anymore in edgy in some laptops. So far, I have it confirmed on some Acer Aspire 3002 notebooks and on my Acer Aspire 3003WLCi. This problem seems not to be coming from hal, as it seems to report the events properly. This is a regression since it used to work perfectly in Dapper. I tried using a custom dsdt from the sourceforge page to no avail.
Please read these two threads from ubuntuforums.org for more info:
http://ubuntuforums.org/showthread.php?p=1801667 ---> Is ANYONE else with a laptop affected by this bug?
and http://ubuntuforums.org/showthread.php?p=180165 ---> Battery status on Acer Aspire 3002 in Edgy.

The output of lshal -m:
tiede@nobattery:~$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
acpi_ACAD property ac_adapter.present = false
acpi_BAT1 property battery.charge_level.percentage removed
acpi_BAT1 property battery.charge_level.last_full = 0 (0x0)
acpi_BAT1 property battery.charge_level.current = 0 (0x0)
acpi_BAT1 property battery.voltage.current = 1 (0x1)
acpi_BAT1 property battery.reporting.current = 690 (0x2b2)
acpi_BAT1 property battery.rechargeable.is_discharging = true
acpi_BAT1 property battery.charge_level.rate = 1 (0x1)
acpi_BAT1 property battery.reporting.rate = 1974 (0x7b6)
acpi_BAT1 property battery.reporting.current = 687 (0x2af)
acpi_BAT1 property battery.reporting.rate = 1580 (0x62c)
acpi_BAT1 property battery.reporting.current = 676 (0x2a4)
acpi_BAT1 property battery.reporting.rate = 1640 (0x668)
acpi_BAT1 property battery.reporting.current = 662 (0x296)
acpi_BAT1 property battery.reporting.rate = 1635 (0x663)
acpi_BAT1 property battery.reporting.current = 648 (0x288)

This seems to indicate that hal knows the battery is discharging and reports it correctly. For some reason however, gpm does not report the correct charge...
Am I missing something?

Tiede (marcarthur)
description: updated
Revision history for this message
Paul Williams (pwill) wrote :

Confirmed here on an Acer Aspire 3004 WLCi
Running `acpi -V` reports proper battery status.

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Mark as "confirmed" since two users (with two similar Acer computers) have the same problem.

Changed in gnome-power-manager:
status: Unconfirmed → Confirmed
Revision history for this message
Scott Kirkpatrick (scott-noordinaryrabbits) wrote :

Confirmed on an Acer Aspire 3002 WLCi.
'acpi -V' reports proper battery operation.

Revision history for this message
Tiede (marcarthur) wrote :

Strangely, however, acpi -V gives the correct information:
Current output:
tiede@battery_problem:~$ acpi -V
Battery 1: charged, 100%
Thermal 1: ok, 49.0 degrees C
AC Adapter 1: on-line

And if I unplug it and leave it for a minute or two...
tiede@battery_problem:~$ acpi -V
Battery 1: discharging, 97%, 00:27:26 remaining
Thermal 1: ok, 48.0 degrees C
AC Adapter 1: off-line

NOTE: while acpi said I was at 97%, gpm showed 0%...
Do acpi and gpm/hal read the battery info in two different places?

Revision history for this message
Tom M. (wvm7fk202-deactivatedaccount) wrote :

I can verify the exact same behavior happens on my Acer TravelMate 4021WLMi. If I take out the AC power plug, the gnome-power-manager instantly complains that power level is critical and threatens to power off.

Sometimes it doesn't.. it will mark the battery as 50% as soon as I disconnect the power plug (even if acpi displays the power at 98% or so.)

Worked fine in Breezy until I upgraded to edgy. So it does affect gnome-power-manager v2.16.1

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :
Revision history for this message
James Tait (jamestait) wrote :

Acer Ferrari 4005 WLMi, BIOS 3A19, running Edgy.

With standard kernel boot options (command line is root=UUID=e9c019e5-d78a-4cc0-8c4a-129eadbe0e3b ro quiet splash), g-p-m applet never displays. Battery Charge Monitor applet always shows AC power, even with no AC connected. However, CPU frequency is scaled down to 800MHz when I unplug the AC. Some pertinent command line output while on AC:

jtait@ferrari:~$ acpi -V
     Thermal 1: ok, 77.0 degrees C
  AC Adapter 1: on-line

And while on battery:

jtait@ferrari:~$ acpi -V
     Thermal 1: ok, 68.0 degrees C
  AC Adapter 1: off-line

And while switching between the two:

jtait@ferrari:~$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
acpi_ACAD property ac_adapter.present = false
acpi_ACAD property ac_adapter.present = true
acpi_ACAD property ac_adapter.present = false
acpi_ACAD property ac_adapter.present = true

Note that with these boot options, my IEEE1394 interface and Broadcom BCM43xx wireless NIC don't work either. Having looked at the dmesg output from boot, I've tried booting with the irqpoll and pci=routeirq options, which seems to allow all these things to work normally.

Revision history for this message
James Tait (jamestait) wrote :

With the aforementioned kernel boot options (command line is root=UUID=e9c019e5-d78a-4cc0-8c4a-129eadbe0e3b ro quiet splash irqpoll pci=routeirq) I get the correct icon in Battery Charge Monitor, g-p-m applet displays and gives me a notification when I remove AC power, and I get the following output while on AC:

jtait@ferrari:~$ acpi -V
     Battery 1: charged, 100%
     Thermal 1: ok, 73.0 degrees C
  AC Adapter 1: on-line

And while on battery:

jtait@ferrari:~$ acpi -V
     Battery 1: discharging, 98%, 02:02:58 remaining
     Thermal 1: ok, 63.0 degrees C
  AC Adapter 1: off-line

And while switching between the two:

jtait@ferrari:~$ lshal -m

Start monitoring devicelist:
-------------------------------------------------
acpi_ACAD property ac_adapter.present = false
acpi_BAT1 property battery.charge_level.last_full = 3 (0x3)
acpi_BAT1 property battery.charge_level.current = 3 (0x3)
acpi_BAT1 property battery.voltage.current = 1 (0x1)
acpi_BAT1 property battery.reporting.current = 3844 (0xf04)
acpi_BAT1 property battery.rechargeable.is_discharging = true
acpi_BAT1 property battery.remaining_time = 10800 (0x2a30) (new)
acpi_BAT1 property battery.charge_level.rate = 1 (0x1)
acpi_BAT1 property battery.reporting.rate = 1871 (0x74f)
acpi_BAT1 property battery.reporting.current = 3833 (0xef9)
acpi_BAT1 property battery.reporting.rate = 1859 (0x743)
acpi_BAT1 property battery.reporting.current = 3817 (0xee9)
acpi_BAT1 property battery.remaining_time = 5400 (0x1518)
acpi_BAT1 property battery.charge_level.rate = 2 (0x2)
acpi_BAT1 property battery.reporting.rate = 2059 (0x80b)
acpi_BAT1 property battery.reporting.current = 3802 (0xeda)
acpi_BAT1 property battery.remaining_time = 10800 (0x2a30)
acpi_BAT1 property battery.charge_level.rate = 1 (0x1)
acpi_BAT1 property battery.reporting.rate = 1817 (0x719)
acpi_BAT1 property battery.reporting.current = 3789 (0xecd)
acpi_ACAD property ac_adapter.present = true
acpi_BAT1 property battery.remaining_time removed
acpi_BAT1 property battery.charge_level.rate = 3 (0x3)
acpi_BAT1 property battery.charge_level.last_full = 7 (0x7)
acpi_BAT1 property battery.charge_level.current = 7 (0x7)
acpi_BAT1 property battery.voltage.current = 2 (0x2)
acpi_BAT1 property battery.reporting.rate = 1865 (0x749)
acpi_BAT1 property battery.reporting.current = 3779 (0xec3)
acpi_BAT1 property battery.rechargeable.is_discharging = false
acpi_BAT1 property battery.rechargeable.is_charging = true
acpi_BAT1 property battery.charge_level.rate = 0 (0x0)
acpi_BAT1 property battery.reporting.rate = 0 (0x0)

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Just correctly marked the upstream report in order for Launchpad to follow the upstream bug report state.

Changed in gnome-applets:
status: Unknown → Unconfirmed
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

I have just installed the Feisty Fawn nightly build 2007/01/11 and the problem is solved on my Acer 1642zwlmi!!!

Marked as fixed (unmark it if needed).

Best regards
Pochu

Changed in gnome-power-manager:
status: Confirmed → Fix Released
Revision history for this message
Peter Magnusson (kmpm) wrote :

I can confirm that it works with Acer Aspire 3003 LMI and gome-power-manager_2.17.90-0ubuntu2 in feisty. Whatever fixed it should be done for edgy as well as running unplugged is somewhat risky without knowing your battery status.

Revision history for this message
James Tait (jamestait) wrote :

Also now working for me in Feisty.

Revision history for this message
anagor (anagor) wrote :

I can confirm this as a bug on MSI ex600 laptop with the following:
acpi-0.09.3ubuntu1
linux-2.6.24.10.8
gnome-power-manager-2.21.92-0ubuntu1

The power manager does not report the remaining battery percentage.
however acpi -V and cat /proc/acpi/battery/BAT1/state shows correct info:

$ acpi -V
     Battery 1: discharging, 88%, 02:10:40 remaining
     Thermal 1: ok, 40.0 degrees C
  AC Adapter 1: off-line
$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate: 2151 mA
remaining capacity: 4153 mAh
present voltage: 12011 mV

Revision history for this message
akaars (ilyabr) wrote :

The problem still exists in Intrepid and Jaunty with my M912 Gigabyte laptop

# acpi -V
     Battery 0: Discharging, 92%, 02:58:15 remaining
     Battery 0: design capacity 4400 mAh, last full capacity 4288 mAh = 97%
  AC Adapter 0: off-line
     Thermal 0: ok, 42.0 degrees C
     Cooling 0: LCD 9 of 10
     Cooling 1: Processor 0 of 10
     Cooling 2: Processor 0 of 10

According to gpm it's 1:55 remaining (93%)

Changed in gnome-applets:
status: New → Invalid
Changed in gnome-applets:
importance: Unknown → Medium
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.