public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Eustice <kfe-764C0pRuGfqVc3sceRu5cw@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Losing lid events after resume (2.6.6)
Date: Mon, 17 May 2004 10:04:24 -0700	[thread overview]
Message-ID: <20040517170424.GA19417@cs.ucla.edu> (raw)
In-Reply-To: <20040517103818.GA1669-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

> > I'm running Fedora Core 1 with a 2.6.6 kernel (with ACPI patches from
> > here applied) on an HP Omnibook 4150B. I've got a lid.sh script that
> > is triggered with the lid button is pressed, and does a "echo standby
> > > /sys/power/state". Initially, this works well. I close the lid, it
> > goes to sleep. I open the lid and press the power button, it wakes
> > up. And then goes right back to sleep. (I don't currently have any
> 
> Are you sure it is not because you receive "lid open" event?

Yup. After going to standby mode, ACPI no longer registers any event
other than the powerbutton events.

Kevin
-- 
Kevin Eustice
Graduate Student Researcher
The Laboratory for Advanced System Research @ UCLA CS
kfe-764C0pRuGfqVc3sceRu5cw@public.gmane.org
http://lasr.cs.ucla.edu/kfe

Computer Science is no more about computers than astronomy is about
telescopes.
	--E. W. Dijkstra



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

  parent reply	other threads:[~2004-05-17 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 18:10 Losing lid events after resume (2.6.6) Kevin Eustice
     [not found] ` <20040513181051.GA29398-764C0pRuGfqVc3sceRu5cw@public.gmane.org>
2004-05-13 23:36   ` Nigel Cunningham
     [not found]     ` <200405140936.52230.ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
2004-05-14 19:59       ` Kevin Eustice
     [not found]         ` <20040514195940.GA19569-764C0pRuGfqVc3sceRu5cw@public.gmane.org>
2004-05-14 21:59           ` Kevin Eustice
2004-05-17 10:38   ` Pavel Machek
     [not found]     ` <20040517103818.GA1669-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-05-17 17:04       ` Kevin Eustice [this message]
     [not found]         ` <20040517170424.GA19417-764C0pRuGfqVc3sceRu5cw@public.gmane.org>
2004-05-17 18:52           ` Eric Valette
     [not found]             ` <40A909D3.1080009-GANU6spQydw@public.gmane.org>
2004-05-17 23:39               ` Nate Lawson

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=20040517170424.GA19417@cs.ucla.edu \
    --to=kfe-764c0prugfqvc3sceru5cw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@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