From: Matthew Palmer <mpalmer@hezmatt.org>
To: linux-acpi@vger.kernel.org
Subject: Lenovo S10e, charge_full == 0 ?!?
Date: Mon, 1 Jun 2009 07:42:20 +1000 [thread overview]
Message-ID: <20090531214220.GK27997@hezmatt.org> (raw)
[Please Cc me; I'm not subscribed to the list]
Hi,
I've just bought a Lenovo S10e ideapad, and it's going nicely except that
/sys/class/power_supply/BAT0/charge_full is 0, rather than something
pleasantly large and reassuring. This is causing battery monitors to
produce all sorts of crazy results. The rest of the battery parameters seem
OK (nothing abnormally 0 in uevent), including charge_full_design. I've
charged and dischaged the battery a couple of times, just to make sure it's
not some sort of "initialisation" problem.
I've tried with both 2.6.26-2 (out of Debian Lenny), and also 2.6.29-2 (from
Debian Sid), and the results are the same. I'd try a git tree kernel, but
wihch one? Linus' tree? The Linux ACPI tree? If anyone recognises this
problem and can point me at a likely candidate for a fix, I'm happy to try
it out, but randomly firing away at kernel trees, given the likely build
speed on this little netbook, is likely to be an exercise in frustration.
Failing that, does anyone have any pointers as to where I could start in
tracking this down? It seems like it'll be a fairly straightforward bug --
the driver's probably just looking in the wrong place for the value, and
needs a re-education. I'm completely unfamiliar with ACPI and the kernel
code relating to ACPI, though, so perhaps it's a lot more complicated than
that. Worst case, if all else fails, I'm thinking that a "fix" might be to
check if charge_full == 0, and if so use charge_full_design. It's ugly, but
better than the current (hah!) situation.
- Matt
next reply other threads:[~2009-05-31 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 21:42 Matthew Palmer [this message]
2009-06-01 0:40 ` Lenovo S10e, charge_full == 0 ?!? yakui_zhao
2009-06-01 1:45 ` Matthew Palmer
2009-06-01 2:25 ` Zhang Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090531214220.GK27997@hezmatt.org \
--to=mpalmer@hezmatt.org \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox