public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Keller <mgkeller-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Battery "design capacity" incorrect
Date: 01 Mar 2003 13:15:26 -0500	[thread overview]
Message-ID: <1046542526.20921.22.camel@comp6161.potsdam.edu> (raw)

I've got a *very minor* problem. In fact, it's almost so trivial it's
cosmetic, but if there is an easy fix it would be one less nuisance!

ACPI is working SPLENDIDLY (2.4.21-pre<something> + acpi patches) and
I'm very happy with it. It does, however, think my battery has a "design
capacity" much higher than it actually is. This results in various
scripts I've written, as well as the Gnome battery applet thinking it's
always only 71% full even when it's fully charged and a-ok. It does the
same with my spares of the same make/model. Below is the output
(/proc/acpi/batter/BAT1/info) for the battery in my Gateway Solo 1450X.
The design capacity should be right around what the "last full capacity"
says. I've confirmed this on Sanyo's site. I would like to note that
everything is **perfect** with a different Sanyo model battery that is a
"extra capacity" battery. Is there any source I can diddle? Proc entries
I can echo some magic number into? etc? Thanks!

present:                 yes
design capacity:         5400 mWh
last full capacity:      3864 mWh
battery technology:      rechargeable
design voltage:          11100 mV
design capacity warning: 250 mWh
design capacity low:     100 mWh
capacity granularity 1:  10 mWh
capacity granularity 2:  25 mWh
model number:            UAL3$
serial number:
battery type:            LION
OEM info:                SANYO

-- 
Matthew Keller
Enterprise Systems Analyst
Computing & Technology Services
State University of New York @ Potsdam
Potsdam, NY USA
http://mattwork.potsdam.edu/



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2003-03-01 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01 18:15 Matthew Keller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-03 17:16 Battery "design capacity" incorrect Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84725A1C3-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-03 19:01   ` Matthew Keller
     [not found]     ` <1046718101.3209.60.camel-a2ysWtvtB4BRjtM+DFHcO/Z8FUJU4vz8@public.gmane.org>
2003-03-03 20:33       ` Troy Schultz
2003-03-04 14:16         ` Richard Black
2003-03-03 19:11 Grover, Andrew

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=1046542526.20921.22.camel@comp6161.potsdam.edu \
    --to=mgkeller-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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