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: > >> Paul Menzel wrote: > >>> Am Montag, den 24.11.2008, 09:26 -0800 schrieb Kok, Auke: > >>>> Nathan Coulson wrote: > >>>>> On Sun, Nov 23, 2008 at 8:33 AM, Paul Menzel > >>>>> <[EMAIL PROTECTED]> wrote: > >>>>>> Dear Michael, > >>>>>> (I am also answering to the list.) > >>>>>> > >>>>>> > >>>>>> thank you for your answer. > >>>>>> > >>>>>> Am Sonntag, den 23.11.2008, 16:23 +0100 schrieb Michael Gaber: > >>>>>> > >>>>>>> Paul Menzel schrieb: > >>>>>>>> [snip] > >>>>>>>> 1. Hmm, I do not know why the output no ACPI power usage estimate > >>>>>>>> available. It was shown before dumping. It was between 0,1 and 0,4 > >>>>>>>> Watts. Running PowerTOP it is also not shown. Strange … > >>>>>>> perhaps because you're testing it while being plugged in? > >>>>>>> acpi power estimate is only available when running on battery > >>>>>> No. The cable was not plugged in. And as I said, before the dump it was > >>>>>> shown. > >>>>> I have never seen any power estimates in powertop the whole time I > >>>>> have experimented with it, and I have never heard of anyone else > >>>>> getting estimates before either. I just assumed it was not possible. > >>>> This feature works based on the battery charge level and the code has > >>>> been working > >>>> on my laptop since the beginning. Recently we found out that some > >>>> batteries > >>>> (drivers?) report their charge levels differently which broke the > >>>> ability for > >>>> powertop to calculate estimates, and I have gotten one patch for that to > >>>> fix this > >>>> for PPC systems. > >>>> > >>>> It's possible that the proc data for your system is ordered differently. > >>>> Can you > >>>> send me the output of the following command, while unplugged from AC? > >>>> > >>>> grep -r . /proc/acpi/battery > >>>> > >>>> maybe that will show me enough information to figure out what's wrong > >>>> with that code. > >>> Here you go. > >>> > >>> $ grep -r . /proc/acpi/battery > >>> /proc/acpi/battery/BAT0/alarm:alarm: unsupported > >>> /proc/acpi/battery/BAT0/state:present: yes > >>> /proc/acpi/battery/BAT0/state:capacity state: ok > >>> /proc/acpi/battery/BAT0/state:charging state: discharging > >>> /proc/acpi/battery/BAT0/state:present rate: unknown > >>> /proc/acpi/battery/BAT0/state:remaining capacity: 90 mAh > >>> /proc/acpi/battery/BAT0/state:present voltage: 8190 mV > >>> /proc/acpi/battery/BAT0/info:present: yes > >>> /proc/acpi/battery/BAT0/info:design capacity: 5200 mAh > >>> /proc/acpi/battery/BAT0/info:last full capacity: 100 mAh > >>> /proc/acpi/battery/BAT0/info:battery technology: rechargeable > >>> /proc/acpi/battery/BAT0/info:design voltage: 8400 mV > >>> /proc/acpi/battery/BAT0/info:design capacity warning: 10 mAh > >>> /proc/acpi/battery/BAT0/info:design capacity low: 5 mAh > >>> /proc/acpi/battery/BAT0/info:capacity granularity 1: 52 mAh > >>> /proc/acpi/battery/BAT0/info:capacity granularity 2: 52 mAh > >>> /proc/acpi/battery/BAT0/info:model number: 701 > >>> /proc/acpi/battery/BAT0/info:serial number: > >>> /proc/acpi/battery/BAT0/info:battery type: LION > >>> /proc/acpi/battery/BAT0/info:OEM info: ASUS > >> this seems to make sense now, it looks like your battery is dead: > >> > >>> /proc/acpi/battery/BAT0/info:design capacity: 5200 mAh > >>> /proc/acpi/battery/BAT0/info:last full capacity: 100 mAh > >>> /proc/acpi/battery/BAT0/state:remaining capacity: 90 mAh > >> I think powertop filters these obviously wrong numbers and it's likely > >> that the > >> '90 mAh' number doesn't change over time. > >> > >> since powertop makes estimates based on deltas, it can't computate > >> anything from this. > >> > >> 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. $ grep -r . /proc/acpi/battery /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate: unknown /proc/acpi/battery/BAT0/state:remaining capacity: 100 mAh /proc/acpi/battery/BAT0/state:present voltage: 8262 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 5200 mAh /proc/acpi/battery/BAT0/info:last full capacity: 100 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 8400 mV /proc/acpi/battery/BAT0/info:design capacity warning: 10 mAh /proc/acpi/battery/BAT0/info:design capacity low: 5 mAh /proc/acpi/battery/BAT0/info:capacity granularity 1: 52 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 52 mAh /proc/acpi/battery/BAT0/info:model number: 701 /proc/acpi/battery/BAT0/info:serial number: /proc/acpi/battery/BAT0/info:battery type: LION /proc/acpi/battery/BAT0/info:OEM info: ASUS It looks like it is using percentage instead of absolute values. My guess it I could only see the estimates, when it changed one percent. Maybe [1] is interesting for you too. Thanks, Paul [1] http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-October/001477.html
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
