Paul Menzel wrote: > Am Mittwoch, den 26.11.2008, 16:10 -0300 schrieb Felipe Sateler: >> Paul Menzel wrote: >> >>> Am Mittwoch, den 26.11.2008, 12:41 -0300 schrieb Felipe Sateler: >>>> Paul Menzel wrote: >>>> >>>>> Am Montag, den 24.11.2008, 13:32 -0800 schrieb Kok, Auke: >>>>>> Paul Menzel wrote: >>>>>>> Am Montag, den 24.11.2008, 12:52 -0800 schrieb Kok, Auke: >>>>>>>> Does that battery actually work reasonably long or is it dead? >>>>>>> Well I worked with it, i. e., power cable was *not* plugged in, for >>>>>>> about 2 hours today. So I think it is not dead. >>>>>> ok, can you charge it to full, unplug and redo the proc output? I'd like >>>>>> to see 'remaining capacity' show a meaningful number... >>>>> Sorry for the delay. Here you go. >>>> <snip> >>>> >>>> What does the /sys/class/power_device/BAT0/* files have to say? AIUI, more >>>> attention is paid to the /sys interface than the /proc one. If the output >>>> in /sys is sane, maybe it would be better to drop reading from /proc (or >>>> use >>>> first /sys, and fallback to /proc). >>> Looks the same. >>> >>> $ cat /sys/class/power_supply/BAT0/charge_full >>> 100000 >>> $ cat /sys/class/power_supply/BAT0/charge_full_design >>> 5200000 >>> $ cat /sys/class/power_supply/BAT0/charge_now >>> 100000 >>> >>> I hope this is enough. Otherwise I would be greatful for a hint to read >>> out all the values with one command. >> There's probably something wrong in your kernel, then. You might want to >> report >> a bug. Either that or your battery is broken. > > Well, others seem to have the same problem [1].
nod, and like I stated earlier, there's not much that we can fix in powertop as the kernel is blatantly providing us with false information. so either this needs to be escalated to the kernel (ACPI? battery module?) or ends up being a BIOS issue, which is highly likely. Auke _______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
