pmu_battery is not loaded automatically, so ibook battery detection does not work

[Olivier Hervieu]

Both on 9.10 and 10.04, the pmu_battery module is not loaded so ibook battery detection does not work.
To fix the problem just do modprobe pmu_battery.

It will be great to have a native detection of ibook g4 battery.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-18-powerpc 2.6.32-18.27
Regression: No
Reproducible: Yes
TestedUpstream: No
ProcVersionSignature: Ubuntu 2.6.32-18.27-powerpc 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-powerpc ppc
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SoundByLayout [SoundByLayout], device 0: Master []
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: powerpc
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SoundByLayout [SoundByLayout], device 0: Master []
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: olivier 1196 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SoundByLayout'/'SoundByLayout'
   Mixer name : 'SoundByLayout'
   Components : ''
   Controls : 13
   Simple ctrls : 12
Date: Wed Mar 31 17:13:58 2010
HibernationDevice: RESUME=/dev/hda5
PciMultimedia:

ProcCmdLine: root=/dev/hda3 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
SourcePackage: linux

[Pablo (pablo-redhat-bugs)]

Description of problem:

There is no "Running on Battery" tab on gnome-power-preferences; all settings work as if the computer was always plugged in, and the icon on the notification area is always of a plugged-in computer, with no charge information. When the battery gets too low, the computer just shuts down without warning.

I'm marking it as a g-p-m bug because other programs see the battery just fine. PowerDevil under KDE gives me all options for the battery, as does xfce4-power-manager.

/proc/apm shows the battery status:
$ cat /proc/apm
1.13 1.2 0x02 0x00 0x00 0x01 97% 61 min

hal sees it just fine:
$ lshal |grep battery
udi = '/org/freedesktop/Hal/devices/pmu_battery_0_0'
  battery.charge_level.current = 2048 (0x800) (int)
  battery.charge_level.design = 2126 (0x84e) (int)
  battery.charge_level.last_full = 2126 (0x84e) (int)
  battery.charge_level.percentage = 96 (0x60) (int)
  battery.charge_level.rate = 0 (0x0) (int)
  battery.is_rechargeable = true (bool)
  battery.present = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.rechargeable.is_discharging = true (bool)
  battery.remaining_time = 4096 (0x1000) (int)
  battery.technology = 'unknown' (string)
  battery.type = 'primary' (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery' (string)
  info.udi = '/org/freedesktop/Hal/devices/pmu_battery_0_0' (string)
  linux.pmu_path = '/proc/pmu/battery_0' (string)

Version-Release number of selected component (if applicable):

gnome-power-manager-2.26.1-3.fc11.ppc

Other components in use:
hal-0.5.12-26.20090226git.fc11.ppc
kernel-2.6.29.3-155.fc11.ppc

and the desktop power managers:
xfce4-power-manager-0.8.0-0.2.beta1.fc11.ppc
kdebase-workspace-4.2.3-4.fc11.ppc (for PowerDevil)

How reproducible:

Happens every time on my computer, even after reinstalling Rawhide. Not sure if other iBook users have the same problem.

Additional info:

The exact model of the affected laptop:
$ cat /proc/cpuinfo
processor : 0
cpu : 7455, altivec supported
clock : 798.720000MHz
revision : 3.3 (pvr 8001 0303)
bogomips : 48.41
timebase : 18432000
platform : PowerMac
model : PowerBook6,3
machine : PowerBook6,3
motherboard : PowerBook6,3 MacRISC3 Power Macintosh
detected as : 287 (iBook G4)
pmac flags : 0000001b
L2 cache : 256K unified
pmac-generation : NewWorld
Memory : 640 MB

[Richard (richard-redhat-bugs)]

What does devkit-power --verbose print?

[Pablo (pablo-redhat-bugs)]

$ devkit-power --verbose
TI:07:49:07 TH:0x10018b70 FI:egg-debug.c FN:egg_debug_init,306
 - Verbose debugging 1 (on console 1)DKP_VERBOSE

It's possible that DeviceKit isn't picking up the battery. That would explain why hal-based power managers work, and why this bug doesn't appear on either Debian or Ubuntu.

[Richard (richard-redhat-bugs)]

So, what's the output of "ls /sys/class/power_supply/*/*"

[Pablo (pablo-redhat-bugs)]

$ ls /sys/class/power_supply/*/*
ls: impossível acessar /sys/class/power_supply/*/*: Arquivo ou diretório não encontrado (file not found, power_supply is an empty dir)

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[shaun (shaun-redhat-bugs)]

I have the exact same problem, along with very similar output to all of the above commands. Will we have to wait for F12 for this to be resolved?

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Jeremy Foshee (jeremyfoshee)]

Hi Olivier,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Olivier Hervieu (ohe)]

Same problem with last kernel and final release of karmic.

[Bug (bug-redhat-bugs)]

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Lino Mastrodomenico (l-mastrodomenico)]

FYI this bug is also present in Debian testing (squeeze), I've reported it in Debian bug #589231.

[Onkar Shinde (onkarshinde)]

How is anyone supposed to test latest kernel? The kernel mainline builds are available only for i386 and amd64. This is powerpc specific issue.

[penalvch (penalvch)]

Olivier Hervieu, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[penalvch (penalvch)]

No OR response requested in 2012.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.