From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Dennis Noordsij" <dennis.noordsij@wiral.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: APM battery status reporting
Date: Fri, 9 Mar 2001 18:00:05 -0500 [thread overview]
Message-ID: <002101c0a8ec$af793b80$305079a5@zeusinc.com> (raw)
In-Reply-To: <E14bUio-0005ls-00@the-village.bc.nu>
> > tested in previous kernels. Then again my dmesg says the BIOS is
probably
> > buggy (same BIOS though as mentioned in those posts). Apmd does notice
the
> > change from mains to battery and vice versa (I have disabled Speedstep
so now
> > everything actually survives this transition :-).
> > So to end all the confusion, is there a patch out there that enables
battery
> > status reporting for me (and other Dell owners :-) ?
>
> Yes but the update you need is a new BIOS revision. Ask Dell
>
The BIOS update has been around forever from Compal (the people who actually
OEM the unit for Dell), you can get their generic BIOS at
http://software.tuxtops.com. This probably violates your Dell warranty but I
know many who use it and we've now installed it on all the 5000e systems we
own, without any problem.
I'm not sure why Dell is taking so long to get an update to it consumers,
but it probably has something to do with the fact that Linux isn't a
supported platform on this machine. Their official stance appears to be
"APM isn't supported on this laptop, only ACPI." That's pretty bogus since
everything but this one system call works, and even that works with the
Compal generic BIOS, so I'd more likely guess it's just not high on the
priority list because it's not important enough for their largest user base
which is of course Windows.
Later,
Tom
prev parent reply other threads:[~2001-03-09 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 20:41 APM battery status reporting Dennis Noordsij
2001-03-09 21:46 ` Alan Cox
2001-03-09 23:00 ` Tom Sightler [this message]
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='002101c0a8ec$af793b80$305079a5@zeusinc.com' \
--to=ttsig@tuxyturvy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dennis.noordsij@wiral.com \
--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.