From: Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>
To: Mirko Hessel-von Molo
<mirkoh-o02PS0xoJP9Fq/OQ1YuiuFE6Nkaw1PD6@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: end-user support: Battery alarm
Date: Thu, 10 Mar 2005 14:31:48 -0500 [thread overview]
Message-ID: <4230A0A4.40705@bartol.udel.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0503101243230.2656-100000-VM6JIClXveXd8wHfNjLPk+mvS+53ZQfghC4ANOJQIlc@public.gmane.org>
Mirko Hessel-von Molo wrote:
> Dear all,
>
> I have a probably stupid question for which I couldn't find the
> answer anywhere else.
>
> Is it true that a 'battery' event is raised by the kernel when the
> 'current capacity' given in /proc/acpi/battery/BAT0/state goes below
> the limit defined in /proc/acpi/battery/BAT0/alarm?
>
> I'm trying to use the battery alarm to make my system warn the user
> and shutdown, if necessary.
>
> My setup is the following: I'm using a Dell Latitude D800 with BIOS A07,
> running under Linux with Kernel 2.6.7 (not the latest one, I know).
> As I 'organically evolved' the system from a RedHat 7.3 base install,
> I'm reluctant to upgrade to some distro which provides acpi support.
>
> So far, I got pretty much everything to work, ac_adapter and battery events
> are raised when the power supply changes. However, no event is
> raised when the battery capacity goes below the warn level. I can't remember
> where I have read this, but somehow I got the idea that this should be the
> case.
>
> Does anyone have an idea where my problem could be?
>
Yes; I've no doubt that this is due to a broken DSDT. Unless Dell has
put something in the DSDT that causes periodic polling of the battery
level, there is no way a notification will be sent when the battery
passes the trip point. There is certainly nothing in the Linux kernel
that handles the polling.
cheers,
Rich
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-10 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 11:53 end-user support: Battery alarm Mirko Hessel-von Molo
[not found] ` <Pine.LNX.4.44.0503101243230.2656-100000-VM6JIClXveXd8wHfNjLPk+mvS+53ZQfghC4ANOJQIlc@public.gmane.org>
2005-03-10 19:31 ` Rich Townsend [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=4230A0A4.40705@bartol.udel.edu \
--to=rhdt-obnux95toyn10jlvftc4ga@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mirkoh-o02PS0xoJP9Fq/OQ1YuiuFE6Nkaw1PD6@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