FS#9338 - No battery status with kernel26-2.6.24-1

Attached to Project: Arch Linux
Opened by Vojtěch Gondžala (vogo) - Friday, 25 January 2008, 21:35 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 08 February 2008, 20:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
if I try `acpitool -B`, I get "Battery status : <not available>" because
in /proc/acpi aren't any information about battery
2.6.23 works good

Additional info:
* machime: A8He laptop
* package version: kernel26-2.6.24-1
* load modules:
Module Size Used by
i2c_dev 6276 0
i2c_core 19328 1 i2c_dev
ipv6 248388 12
appletalk 30688 2
ipx 23972 2
p8022 2048 1 ipx
psnap 3332 2 appletalk,ipx
llc 6036 2 p8022,psnap
p8023 1920 1 ipx
i915 22144 2
drm 70420 3 i915
l2cap 20608 6
coretemp 6016 0
snd_seq_oss 29440 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 47056 5 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6924 2 snd_seq_oss,snd_seq
joydev 9664 0
hci_usb 13596 0
bluetooth 50916 4 l2cap,hci_usb
snd_pcm_oss 36896 0
snd_mixer_oss 14464 1 snd_pcm_oss
firewire_ohci 16128 0
firewire_core 36544 1 firewire_ohci
crc_itu_t 2304 1 firewire_core
sdhci 15364 0
ohci1394 28848 0
rtc_cmos 7584 0
rtc_core 15496 1 rtc_cmos
rtc_lib 2944 1 rtc_core
mmc_core 43524 1 sdhci
ieee1394 79800 1 ohci1394
video 16016 0
output 3200 1 video
serio_raw 5636 0
pcspkr 2944 0
sg 26640 0
psmouse 36496 0
ehci_hcd 32524 0
snd_hda_intel 289952 4
snd_pcm 68996 3 snd_pcm_oss,snd_hda_intel
snd_timer 19204 3 snd_seq,snd_pcm
snd_page_alloc 8072 2 snd_hda_intel,snd_pcm
snd_hwdep 7300 1 snd_hda_intel
snd 44772 16 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore 6368 1 snd
uhci_hcd 22672 0
r8169 26244 0
intel_agp 21780 1
agpgart 27352 3 drm,intel_agp
thermal 13084 0
evdev 9344 7
fan 3844 0
button 6544 0
battery 6656 0
ac 3712 0
ppp_generic 23828 0
slhc 5632 1 ppp_generic
cpufreq_powersave 1920 1
cpufreq_ondemand 7180 0
cpufreq_conservative 6664 0
acpi_cpufreq 11420 1
freq_table 3984 2 cpufreq_ondemand,acpi_cpufreq
processor 29400 4 thermal,acpi_cpufreq
asus_laptop 15736 0
led_class 3332 1 asus_laptop
usbcore 125420 4 hci_usb,ehci_hcd,uhci_hcd
ext3 121864 2
jbd 43028 1 ext3
mbcache 6912 1 ext3
sr_mod 14884 0
cdrom 33824 1 sr_mod
sd_mod 22656 4
pata_acpi 5248 0
ata_piix 14724 4
ata_generic 5252 0
libata 137712 3 pata_acpi,ata_piix,ata_generic

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 08 February 2008, 20:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  no repsonse the last 5 days
Comment by Bob Fanger (NebyGemini) - Friday, 25 January 2008, 22:39 GMT
My Acer Aspire 5024 laptop also stopped displaying the battery status (in enlightenment). I haven't investigated the battery problem yet. Still busy with the not working wireless (b43 driver).
Comment by Pierre Schmitz (Pierre) - Friday, 25 January 2008, 22:39 GMT
tpowa will fix this with next release.
Comment by Petar Bogdanovic (pebo) - Saturday, 26 January 2008, 00:46 GMT
It should work if you tell your tools to get the information from
/sys/class/power_supply/ instead of /proc/acpi/battery/.
Comment by Tobias Powalowski (tpowa) - Saturday, 26 January 2008, 10:58 GMT
fixed in 2.6.24-2
Comment by Mateusz Jędrasik (imachine) - Wednesday, 30 January 2008, 06:37 GMT
there is a bit more to this.

I think not only should CONFIG_ACPI_PROCFS_POWER be set to 'y', but CONFIG_ACPI_SYSFS_POWER be set to 'n'. Currently (with both of them to'y') I'm having issues like the battery monitor thinking the battery is at default capacity - despite the fact it's saying it only had about 79% of original capacity as last full charge, now when I boot up I get 79% hanging in there non stop, then eventually it will decide it's full, when I unplug, it will charge up to some strange number, sometimes up to 100%, sometimes again to 79% (79% of original capacity, current max capacity).

please try sorting it out. more here:

http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/f18ef97710f92b59/69889bf87404225d
Comment by Tobias Powalowski (tpowa) - Wednesday, 30 January 2008, 07:19 GMT
which program you use?
the programs needs to read /proc or /sys, i doubt one reads both at the moment.
the link you posted doesn't tell anything about the fact that both systems are acitve, which shouldn't cause any issue.
Comment by Tobias Powalowski (tpowa) - Sunday, 03 February 2008, 17:17 GMT
bump any news on this?

Loading...