public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Summers <jsummers-5f/76mLIbwCHXe+LvDLADg@public.gmane.org>
To: Listacpi <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Learning ACPI
Date: Fri, 28 Jan 2005 14:24:51 -0600	[thread overview]
Message-ID: <41FA9F93.4090105@cs.ou.edu> (raw)


Hello List,

I have recently undertaken the project of getting power management under 
control on several of my faculty's laptops and other systems.  For the 
most part we are running on FC3 and Dell laptops.  My test machine is a 
  Dell Inspiron 5100 with the bios at the latest A32.

The first thing I noticed was that when the power button is pressed 
nothing happens.  Ignoring that, I was more interested in turning off 
the power to the lid when it was closed.

By remotely accessing the machine and monitoring the LID/state file I 
observed that indeed it was being updated properly (open or closed). 
But no events were firing off.  I placed a simple action to send a 
message to syslog via the logger utility and it never happens.  Also I 
never see any thing written to the acpid log file other than upon 
startup it loads two rules, the sample one for the power button and the 
one I put in for handling the lid event.

Looking through the DSDT database I noticed a mention of something 
called a lost interrupt for 5100's using the A26/28 bios.  I didn't 
think that was the issue since the state file was being updated correctly.

Dmesg output looks good for ACPI stuff.

Can someone give me some ideas on what the problem might be?

I guess I am not understanding how, if the acpid is correctly monitoring 
the lid state then why would it not fire the events/actions?  I can 
porvide more info, dmesg output etc...

TIA
-- 
Jim Summers
School of Computer Science-University of Oklahoma
-------------------------------------------------


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

             reply	other threads:[~2005-01-28 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 20:24 Jim Summers [this message]
     [not found] ` <41FA9F93.4090105-5f/76mLIbwCHXe+LvDLADg@public.gmane.org>
2005-01-29 16:13   ` Learning ACPI Karol Kozimor
     [not found]     ` <20050129161334.GA28055-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-01-31 14:17       ` Jim Summers

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=41FA9F93.4090105@cs.ou.edu \
    --to=jsummers-5f/76mlibwchxe+lvdladg@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