public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Herman Sheremetyev <herman-6MNMYbGzEYJWk0Htik3J/w@public.gmane.org>
To: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: current ACPI status in 2.6.7 kernel
Date: Wed, 11 Aug 2004 10:10:24 -0400	[thread overview]
Message-ID: <1092233424.1977.21.camel@camel> (raw)
In-Reply-To: <411A1CC5.5030401-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>

On Wed, 2004-08-11 at 09:19, Nathan Bryant wrote:
<snip>
> Oh, and there's that annoying little problem where acpid sees the button 
> press that I have to use to resume, as a shutdown event...
</snip>

I don't have this issue myself since hitting any button on my laptop
wakes it up but I think it would be possible to get around this problem
by putting something like this into your acpid script that handles the
button press:

if test ! -e /tmp/button_lock
then
	/sbin/shutdown
fi

Then in your suspend script add:

touch /tmp/button_lock
echo -n mem > /sys/power/state
rm /tmp/button_lock 

It would need to be tweaked a bit since the rm may get executed before
the suspend completes and maybe acpid will get the button event some
time after resume so there might need to be a sleep statement but in
general I think it would solve the problem.

-Herman
	



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  parent reply	other threads:[~2004-08-11 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  8:05 current ACPI status in 2.6.7 kernel Alexander Sirotkin
     [not found] ` <411881B1.9000903-l0cyMroinI0@public.gmane.org>
2004-08-10 10:02   ` Nigel Cunningham
     [not found]     ` <1092132146.2666.3.camel-AdgCB+f5QAxwBzq2CxEN2SkBHpOjBR89@public.gmane.org>
2004-08-10 13:56       ` Alexander Sirotkin
     [not found]         ` <4118D40D.5030404-l0cyMroinI0@public.gmane.org>
2004-08-10 16:34           ` Nathan Bryant
     [not found]             ` <4118F918.7070909-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-10 17:13               ` Nathan Bryant
     [not found]                 ` <4119024B.5060602-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-11  7:48                   ` Alexander Sirotkin
     [not found]                     ` <4119CF6A.8020807-l0cyMroinI0@public.gmane.org>
2004-08-11 13:19                       ` Nathan Bryant
     [not found]                         ` <411A1CC5.5030401-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-11 13:56                           ` Bernard Blackham
2004-08-11 14:10                           ` Herman Sheremetyev [this message]
2004-08-11 14:35               ` Nathan Bryant
     [not found]                 ` <411A2EA9.6000000-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-12  3:48                   ` Len Brown
2004-08-12  7:48                     ` Karol Kozimor
2004-08-12 20:34                     ` Ow Mun Heng

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=1092233424.1977.21.camel@camel \
    --to=herman-6mnmybgzeyjwk0htik3j/w@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