ubuntu doesn't notice when running on battery

[alex f]

Battery status applet says running on ac power, although it's running only on battery. Once the battery is empty, the laptop simply turns off.

The laptop is a Toshiba M30X-102. Specs are here: http://de.computers.toshiba-europe.com/cgi-bin/ToshibaCSG/selected_product_option.jsp?service=DE&PRODUCT_ID=97932&DISC_MODEL=1

lspci -vv
0000:00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Region 0: Memory at e0000000 (32-bit, prefetchable) [size=256M]
        Capabilities: <available only to root>

0000:00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

0000:00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

0000:00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 96
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
        I/O behind bridge: 00003000-00003fff
        Memory behind bridge: d0100000-d01fffff
        Prefetchable memory behind bridge: d8000000-dfffffff
        BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-

0000:00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 169
        Region 4: I/O ports at 1800 [size=32]

0000:00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 193
        Region 4: I/O ports at 1820 [size=32]

0000:00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03) (prog-if 00 [UHCI])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin C routed to IRQ 185
        Region 4: I/O ports at 1840 [size=32]

0000:00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03) (prog-if 20 [EHCI])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin D routed to IRQ 201
        Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <available only to root>

0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
        Latency: 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
        I/O behind bridge: 00004000-00004fff
        Memory behind bridge: d0200000-d02fffff
        Prefetchable memory behind bridge: 30000000-31ffffff
        BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-

0000:00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
        Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

0000:00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 185
        Region 0: I/O ports at <unassigned>
        Region 1: I/O ports at <unassigned>
        Region 2: I/O ports at <unassigned>
        Region 3: I/O ports at <unassigned>
        Region 4: I/O ports at 1860 [size=16]
        Region 5: Memory at 32000000 (32-bit, non-prefetchable) [size=1K]

0000:00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin B routed to IRQ 11
        Region 4: I/O ports at 1880 [size=32]

0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
        Subsystem: Toshiba America Info Systems: Unknown device ff01
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 177
        Region 0: I/O ports at 1c00 [size=256]
        Region 1: I/O ports at 18c0 [size=64]
        Region 2: Memory at d0000c00 (32-bit, non-prefetchable) [size=512]
        Region 3: Memory at d0000800 (32-bit, non-prefetchable) [size=256]
        Capabilities: <available only to root>

0000:00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03) (prog-if 00 [Generic])
        Subsystem: Toshiba America Info Systems: Unknown device 0001
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin B routed to IRQ 177
        Region 0: I/O ports at 2400 [size=256]
        Region 1: I/O ports at 2000 [size=128]
        Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA])
        Subsystem: Toshiba America Info Systems: Unknown device ff02
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 66 (2000ns min), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin A routed to IRQ 169
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 3000 [size=256]
        Region 2: Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at d0120000 [disabled] [size=128K]
        Capabilities: <available only to root>

0000:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (8000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin A routed to IRQ 209
        Region 0: Memory at d0201000 (32-bit, non-prefetchable) [size=2K]
        Region 1: I/O ports at 4400 [size=128]
        Capabilities: <available only to root>

0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (8000ns min, 16000ns max)
        Interrupt: pin A routed to IRQ 217
        Region 0: I/O ports at 4000 [size=256]
        Region 1: Memory at d0201800 (32-bit, non-prefetchable) [size=256]
        Capabilities: <available only to root>

0000:02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)
        Subsystem: Intel Corporation: Unknown device 2741
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (750ns min, 6000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin A routed to IRQ 225
        Region 0: Memory at d0200000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: <available only to root>

0000:02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
        Subsystem: Toshiba America Info Systems: Unknown device ff01
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 168, Cache Line Size: 0x20 (128 bytes)
        Interrupt: pin A routed to IRQ 169
        Region 0: Memory at d0203000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
        Memory window 0: 30000000-31fff000 (prefetchable)
        Memory window 1: 34000000-35fff000
        I/O window 0: 00004800-000048ff
        I/O window 1: 00004c00-00004cff
        BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
        16-bit legacy interface ports at 0001

0000:02:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (250ns min, 1000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin B routed to IRQ 11
        Region 0: Memory at d0201c00 (32-bit, non-prefetchable) [size=128]
        Capabilities: <available only to root>

0000:02:04.2 0805: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (prog-if 01)
        Subsystem: Toshiba America Info Systems: Unknown device ff01
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (8000ns min, 18000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin B routed to IRQ 177
        Region 0: Memory at d0202000 (32-bit, non-prefetchable) [size=256]
        Capabilities: <available only to root>

0000:02:04.3 FLASH memory: ENE Technology Inc: Unknown device 0520
        Subsystem: Toshiba America Info Systems: Unknown device ff00
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (250ns min, 1000ns max), Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin B routed to IRQ 11
        Region 0: Memory at d0202400 (32-bit, non-prefetchable) [size=128]
        Capabilities: <available only to root>

[alex f (acid-punk)]

The laptop runs Dapper.

[Matthew Garrett (mjg59)]

What does

cat /proc/acpi/battery/*/state

give you?

[alex f (acid-punk)]

The following is an edited shell log, I commented when I inserted or removed battery or ac adapter. The battery-applet and gnome-power-manager echoed these states fine I think. The timeframe for this log is maybe 1 or 2 minutes. Even now several minutes after I removed the battery proc says it's there. This is a standard Ubuntu Kernel, 2.6.15-20-386.

<ac present, battery not inserted>

alex@tosh:~$ cat /proc/acpi/battery/*/state
present: no
alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: on-line

<*fully* charged battery inserted>

alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: charging
present rate: 0 mA
remaining capacity: 40 mAh
present voltage: 20067 mV
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: charging
present rate: 0 mA
remaining capacity: 40 mAh
present voltage: 1635 mV

<pull ac>

alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: off-line

<plug ac>

alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: on-line
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: charging/discharging
present rate: 0 mA
remaining capacity: 5120 mAh
present voltage: 34660 mV
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: ok
charging state: charged
present rate: 0 mA
remaining capacity: 5120 mAh
present voltage: 41060 mV
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: ok
charging state: charged
present rate: 0 mA
remaining capacity: 40 mAh
present voltage: 8802 mV

<pull ac>

alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: off-line
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: discharging
present rate: 0 mA
remaining capacity: 40 mAh
present voltage: 45154 mV
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: charging/discharging
present rate: 0 mA
remaining capacity: 5120 mAh
present voltage: 11364 mV

<plug ac>

alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: on-line

<remove battery>

alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: critical
charging state: discharging
present rate: 0 mA
remaining capacity: 5120 mAh
present voltage: 0 mV
alex@tosh:~$ cat /proc/acpi/battery/*/state
present: yes
capacity state: ok
charging state: charged
present rate: 0 mA
remaining capacity: 5120 mAh
present voltage: ...

[Matthew Garrett (mjg59)]

Daniel, not sure if this is g-p-m or hal, but the kernel seems to be getting things (pretty much) right

[alex f (acid-punk)]

Matthew, my last log was probably not very clear. It seems once I start plugging battery and ac adapter at random that it will also have random results reported in proc.

But the one symptom that I can always reproduce is, that when I boot the laptop with only the battery inserted, proc will always say:

alex@tosh:~$ cat /proc/acpi/battery/*/state
present: no
alex@tosh:~$ cat /proc/acpi/ac_adapter/*/state
state: off-line

Once the battery is empty the laptop will simply shutoff.

[Marco Ferragina (ferama)]

I've also a toshiba m30x with similar problem.
cat /proc/acpi/battery/*/state
present: no

if I do a rmmod battery and modprobe battery several times
I have
cat /proc/acpi/battery/*/state
present: yes
capacity state: ok
charging state: discharging
present rate: 0 mA
remaining capacity: 5200 mAh
present voltage: 15452 mV

But this is incorrect because pc is actually ac powered

[Louis-Xavier Brusset (lxbrusset)]

I am experiencing something similar on Edgy Eft

I have an ASUS A6000 AMD64, I am running Generic 64bits kernel.

on /proc/acpi/ac_adapter/AC0/ file state is empty

on /proc/acpi/battery/BAT0/ files alarm info and state are empty

[Louis-Xavier Brusset (lxbrusset)]

I join result of lshal command

[Louis-Xavier Brusset (lxbrusset)]

So I may resume what's happening :
After I installed Edgy Eft on my computer it seems that everything is configured like I got a desktop computer and not a laptop, the Energy manager does not allow me to configure a battery operated mode, and there seem to be no difference between the time I operate on battery or on AC power.

[Daniele Dellafiore (ildella)]

I am experiencing something very similar on my macbook core2 duo, using feisty. Everything was good but after the 17th of February update Ubuntu does not detect my machine as a laptop.
What is happening:

1. gnome-power-preferences just show me AC power tab options.
2. battery charge monitor applet loads and show correct battery status but says it is using Legacy (non hal) backend.
3. cat /proc/acpi/battery/BAT0/state and info seems pretty good.

so it seems that hal does not detect battery and everyone that just can use hal behave according to this fact.

How may I check why hal is misbehaving?

[Daniele Dellafiore (ildella)]

Some udates: today, after update to ubuntu9 version of hal packages, gnome-power-preferences has stated to show battery tab again and the battery icon appears in the panel.
Then I restarted and everything is as before (not working).

More over, since yesterday afternoon, without any apparent reasone, also legacy backend is not able to get information from battery other than charging state, this is output:

della@della-laptop:~$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: charging
present rate: 0 mW
remaining capacity: 0 mWh
present voltage: 0 mV

[ERICK EDUARDO DIAZ GOMEZ (digees)]

Hi, i have the same problem with compaq presario v3215 in fesity 64 bits, this problem start when update hal
Whats wrong???

[henry2man (henry2man)]

First of all I want to say I'm a newbie in GNU/Linux world. Please forgive me if I write something wrong.

I installed Feisty last Tuesday (May, 22th) and everything works fine with battery / AC status. But since system auto-updated himself yesterday, gnome-power-management always detects my laptop like an usual desktop machine. In Hal device manager "Battery Bay" element also disappeared. But acpi status looks ok:

enrique@PCdeEnrique:/$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: charged
present rate: unknown
remaining capacity: 2144 mAh
present voltage: 12067 mV

enrique@PCdeEnrique:/$ cat /proc/acpi/ac_adapter/ACAD/state
state: on-line

Acpi changes its state when I pull AC cord:

enrique@PCdeEnrique:/$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: discharging
present rate: unknown
remaining capacity: 2208 mAh
present voltage: 12167 mV

enrique@PCdeEnrique:/$ cat /proc/acpi/ac_adapter/ACAD/state
state: off-line

Also, battery monitor shows this message: "Backend legacy (no HAL) activated" (translated from Spanish)

I hope this information will be useful. I don't know if this is a similar but different bug in Hal... please say it if you think it so.

PD: Sorry about my poor English !

[Daniele Dellafiore (ildella)]

I am still experiencing this problem. After latest hal update, LID close is detected and monitor is made blank as stated. But I still need to reinstall hal to make ubuntu detect battery, power manager applet appears on tray and show correct battery status.

Following the info of my battery (they doesn't change, of course, before and after reinstalling hal). After you can see a startup phase of /var/log/acpid

della@della-laptop:~$ cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 50200 mWh
last full capacity: 54220 mWh
battery technology: rechargeable
design voltage: 10950 mV
design capacity warning: 250 mWh
design capacity low: 100 mWh
capacity granularity 1: 10 mWh
capacity granularity 2: 10 mWh
model number: ASMB013
serial number:
battery type: LION013
OEM info: DPON013
della@della-laptop:~$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: charging
present rate: 19208 mW
remaining capacity: 30740 mWh
present voltage: 11894 mV
della@della-laptop:~$ cat /proc/acpi/battery/BAT0/alarm
alarm: unsupported

-- begin of /var/log/acpid --

[Tue May 29 09:57:22 2007] starting up
[Tue May 29 09:57:22 2007] 55 rules loaded
[Tue May 29 09:57:23 2007] client connected from 4878[107:112]
[Tue May 29 09:57:23 2007] 1 client rule loaded
[Tue May 29 09:58:58 2007] received event "ac_adapter ADP1 00000080 00000001"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] executing action "/etc/acpi/power.sh"
[Tue May 29 09:58:58 2007] BEGIN HANDLER MESSAGES
[Tue May 29 09:58:58 2007] END HANDLER MESSAGES
[Tue May 29 09:58:58 2007] action exited with status 0
[Tue May 29 09:58:58 2007] completed event "ac_adapter ADP1 00000080 00000001"
[Tue May 29 09:58:58 2007] received event "processor CPU0 00000080 00000000"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] completed event "processor CPU0 00000080 00000000"
[Tue May 29 09:58:58 2007] received event "processor CPU0 00000081 00000000"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] completed event "processor CPU0 00000081 00000000"
[Tue May 29 09:58:58 2007] received event "processor CPU1 00000080 00000000"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] completed event "processor CPU1 00000080 00000000"
[Tue May 29 09:58:58 2007] received event "processor CPU1 00000081 00000000"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] completed event "processor CPU1 00000081 00000000"
[Tue May 29 09:58:58 2007] received event "battery BAT0 00000080 00000001"
[Tue May 29 09:58:58 2007] notifying client 4878[107:112]
[Tue May 29 09:58:58 2007] executing action "/etc/acpi/power.sh"
[Tue May 29 09:58:58 2007] BEGIN HANDLER MESSAGES
[Tue May 29 09:58:58 2007] END HANDLER MESSAGES
[Tue May 29 09:58:58 2007] action exited with status 0
[Tue May 29 09:58:58 2007] completed event "battery BAT0 00000080 00000001"

[Siebren Bakker (aevum-decessus)]

I have been getting this bug recently as well. I am running a 1.5yr old Compaq Presario v2000 laptop. I've been using Ubuntu Gutsy since tribe 5 came out, and within the last month, after a round of updates, gnome-power-manager says I am running on AC power, with or without AC power present. Also, the battery tab has completely disappeared from the gnome-power-manager preferences gui-window, yet whenever I execute the
cat /proc/acpi/battery/*/state
command in a terminal, it correctly states whether the battery is charging, charged, or discharging depending on it's charge state, and AC power status.

[Sam Peterson (peabodyenator)]

I am experiencing this bug as well. It happened after I manually restarted the dbus service. This is apparently a problem related to how gnome-power-management and dbus interact.

[Sam Peterson (peabodyenator)]

Okay, I tried reinstalling the hal package as suggested above and this fixed the problem while the laptop was booted. However, on reboot, the problem comes back. I think we can safely say at this point that the problem lies with the hal package, not gnome-power-manager..

[Jimbo (jbmech006)]

I too have had this problem in Feisty and Gusty Ubuntu. I have a Toshiba M100 Laptop. I posted this problem several months ago on the Ubuntu forums but no one has replied to it. You'll notice the acpi -V giving a message saying the battery is discharging and the AC is online. This bug is very annoying...

Here are the specs of my system:

*Note: These results are for Feisty, I get the same results in Gusty except for the uname -a of course.

Feisty Ubuntu 7.04
Toshiba Satellite M100
9 Cell Battery
Intel Centrino Core Duo T2400 / 1.83 Ghz

$uname -a
Linux nanode 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux

$acpi -V
Battery 1: discharging, 66%, remaining
No support for device type: thermal
AC Adapter 1: on-line

$hal-find-by-capability --capability battery
/org/freedesktop/Hal/devices/acpi_BAT1

$cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 8600 mAh
last full capacity: 8600 mAh
battery technology: rechargeable
design voltage: 11100 mV
design capacity warning: 420 mAh
design capacity low: 258 mAh
capacity granularity 1: 264 mAh
capacity granularity 2: 3780 mAh
model number: PA3400U
serial number: 3658Q
battery type: Li-Ion
OEM info: TOSHIBA

$cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate: 0 mA
remaining capacity: 5160 mAh
present voltage: 11100 mV

[Jimbo (jbmech006)]

Sorry I mean to post this too, here is a link to my post on the Ubuntu forums:

http://ubuntuforums.org/showthread.php?t=557725

You guys should post there and let others know that this is an issue that more then one person is having problems with

[alex f (acid-punk)]

After a BIOS update this isn't happening anymore to me.

[Sam Peterson (peabodyenator)]

There are a apparently lots of causes for this problem. One cause is the kernel not recognizing the battery properly. If that is the case, then even the "acpi -V" command won't show a battery. However, if that command shows a battery connected, then the problem lies with the hal -> dbus -> gnome-power-manager chain. My problem was the latter, and I just fixed this by

sudo sysv-rc-conf -p

Then going to the hal service and changing each S## level to read S99. That made the hal service start after everything else. I don't know if this has any harmful side effects, but I've booted once so far without any hiccups and now gnome-power-manager finally detects the battery properly, and even sleep/suspends/hibernates and shows the brightness applet properly.

What I find strange is that I never changed this myself and the hal -> dbus -> gnome-power-manager communication worked fine before. The one thing I did which changed this was to restart dbus manually. Ever since I had done that, gnome-power-manager had failed to detect the battery unless I restarted the hal service. I can't imagine why doing that would have changed anything, but it did.

As for the kernel problems, I can't be of any help there. That's a kernel related bug and should probably be filled under the relevant "linux" package.

[Data (ubuntuaddress)]

Does the bug still occur after today's update of hal in hardy?

[Ted Gould (ted)]

Marking incomplete pending the response on the HAL update in Hardy (fixed it for me).

[Dani Alonso (dalonso)]

I'm in hardy. The battery is not recognized at all:

With ac plug:

acpi -V:

     Thermal 1: ok, 27.0 degrees C
     Thermal 2: ok, 27.0 degrees C
  AC Adapter 1: on-line

Without it, running on batteries:

acpi -V:

     Thermal 1: ok, 27.0 degrees C
     Thermal 2: ok, 27.0 degrees C
  AC Adapter 1: off-line

Is this a kernel or gnome-power-manager fault?

[Magnus S (magnuss)]

Hi,
this bug report is getting old, so i'm closing it now. If this issue is still affecting you, please reopen.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[nebcanuck (nebcanuck)]

This is happening for me, too. The behaviour seems to be pretty consistently that:

a) When I am running on battery power with reasonable energy, gnome-power-manager does not recognize that I am on battery. This is confirmed because when I change the power management settings to "always show icon", as opposed to "show icon when battery is present", the plug icon shows up -- indicating no battery but instead AC power.

b) When I get to low battery, suddenly the power-manager icon reappears and the management settings kick in, including power saving features like dimming screen.

Also, with a recent update, my sound has disappeared. I am not sure if this is related or not, since people seem to be suggesting this could be a HAL issue.

[nebcanuck (nebcanuck)]

I should add that I am running Lucid Lynx with all packages updated.

[Esqui (esquiskwerl)]

This also affects me using Dell Mini10v running Lucid alpha 2.

After some recent updates, it now only shows as AC power (and runs on full power profile). Running cat /proc/acpi/battery/BAT1/state in terminal made it work and recognise it was on battery. Killing and restarting the process did not work either.

This will result in reduced battery life.

[Chris Coulson (chrisccoulson)]

Please report a new bug rather than resurrecting a nearly 4 year-old bug. Despite what you might think, the issue you're experiencing is unlikely to be related to this bug, as the underlying architecture is significantly different now

[Maria Perez (eldarel)]

My laptop model is a Compact Presario R3454.
I recently upgraded from Ubuntu 8.04 LTS to 10.04 LTS. Now power manager icon states it's con AC, no matter whether is true or not. When dealing with preferences, battery tab is missing.
Power manager worked fine on 8.0.4 LTS, so it seems there's some kind of regression.
By now, the only way to know if battery status is through /proc/acpi/battery/BAT1/*

Would anyone recommend me to downgrade power management package?