From: Len Brown <len.brown@intel.com>
To: David Ford <david+powerix@blue-labs.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ACPI/battery status on Dell Inspiron 8200 broken, 2.6.2-rc3
Date: 02 Feb 2004 13:08:56 -0500 [thread overview]
Message-ID: <1075745336.2389.72.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0023E8445@hdsmsx402.hd.intel.com>
David,
Please try this patch
http://bugzilla.kernel.org/attachment.cgi?id=1965&action=view
and note in this bug report if it works for you.
http://bugzilla.kernel.org/show_bug.cgi?id=1766
thanks,
-Len
On Mon, 2004-02-02 at 02:29, David Ford wrote:
> Battery status got lost in either rc2 or rc3. It worked in rc1.
>
> powerix klaptopdaemon # cat /proc/acpi/battery/BAT0/info
> present: yes
> design capacity: 0 mWh
> last full capacity: 0 mWh
> battery technology: non-rechargeable
> design voltage: 0 mV
> design capacity warning: 0 mWh
> design capacity low: 0 mWh
> capacity granularity 1: 0 mWh
> capacity granularity 2: 0 mWh
> model number:
> serial number:
> battery type:
> OEM info:
>
> powerix klaptopdaemon # cat /proc/acpi/battery/BAT0/state
> present: yes
> capacity state: ok
> charging state: unknown
> present rate: 0 mA
> remaining capacity: 0 mAh
> present voltage: 0 mV
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next parent reply other threads:[~2004-02-02 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0023E8445@hdsmsx402.hd.intel.com>
2004-02-02 18:08 ` Len Brown [this message]
2004-02-02 7:29 ACPI/battery status on Dell Inspiron 8200 broken, 2.6.2-rc3 David Ford
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=1075745336.2389.72.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=david+powerix@blue-labs.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.