APMD-List:
Archives

  From: Avery Pennarun <apenwarr@worldvisions.ca>
  To  : Nino Margetic <nino@well.ox.ac.uk>
        <apmd-list@worldvisions.ca>
  Date: Wed, 23 Jun 1999 20:09:03 -0400

Re: apmd-3.0beta5-8

Hi Nino,

I'm Cc:'ing my reply to the apmd-list.  Hope you don't mind.


On Wed, Jun 23, 1999 at 10:20:28PM +0100, Nino Margetic wrote:

> I am running RH60 with 2.2.9 and apmd-3.0beta5-8 on a Tecra 8000. When I
> have two batteries (main + selectbay) connected apmd starts beeping way
> too early - when total capacity of batteries reaches approx 49%.
> 
> cat /proc/apm gives
> 1.9 1.2 0x02 0x00 0x01 0x02 49% 161 min
> and
> cat /etc/sysconfig/apmd gives
> APMD_OPTIONS="-p 10 -w 5 -W"
> 
> I also get loads of messages in the console window which correspond to
> beeps:
> 
> Jun 23 16:09:06 localhost apmd[103]: Battery Low Notification from APM
> BIOS (49% 2:41)
> Jun 23 16:09:22 localhost apmd[103]: Battery Low Notification from APM
> BIOS (49% 2:37)
> 
> If I kill apmd, both beeps and messages stop. Have you seen this before?
> Is there a way around this problem?

The APM BIOS in your laptop is actually responsible for producing this
message - and the battery level for the event can't be changed, I think. 
Perhaps one of your two batteries is nearly dead at this point?

The apmd warning level is completely separate from the BIOS-generated
message.  Perhaps we should disregard the BIOS message entirely.

Craig, is there any reason why we aren't passing "synthetic battery low"
messages on to the apmd_proxy?

Does anyone find any use for the BIOS-generated warnings?  Perhaps we should
just ignore them.

Avery