Date: Sat, 20 Mar 2010 21:55:20 +0100 From: Dan Lukes <dan@obluda.cz> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-acpi@freebsd.org Subject: Re: Funny battery values (nx6325) Message-ID: <4BA53638.1080500@obluda.cz> In-Reply-To: <20100320091234.GA45738@uriah.heep.sax.de> References: <20100319233643.G85436@sola.nimnet.asn.au> <20100320002156.L85436@sola.nimnet.asn.au> <1269000185.47240.28.camel@RabbitsDen> <4BA34277.1000509@obluda.cz> <20100319144604.N85436@sola.nimnet.asn.au> <20100319155246.L85436@sola.nimnet.asn.au> <20100319155246.L85436@sola.nimnet.asn.au> <4BA2EFE8.60004@obluda.cz> <20100319144426.GV52442@uriah.heep.sax.de> <20100320091234.GA45738@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Joerg Wunsch wrote: > Battery state reporting went a little funny. As expected, it > initially dropped quickly until it reported a remaining runtime of > 0:00 (as that time was based on the nonsensical 279 mAh level). At > that point, the report was stuck at the same values for maybe 30 or 40 > minutes, until ACPI eventually reported a "battery is seriously low" > event. Then, it started to report actual data (battery voltage, > current draw) again. > > Alas, the reported values now are still way off: > > remi# acpiconf -i0 > Design capacity: 791 mAh > Last full capacity: 791 mAh Three or four cycles of charging / depth depleting may recalibrate the internals and reported values may become more appropriate. You should not stop the discharging prematurely - it affect the results. If you run notebook mostly on AC adapter so the battery is never discharged so much then internal circuits become confused about battery capacity. It's common behavior - nothing special to notebooks. Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BA53638.1080500>