public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
Cc: ACPI List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Alexander Sirotkin <demiurg-l0cyMroinI0@public.gmane.org>,
	ncunningham-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org
Subject: Re: current ACPI status in 2.6.7 kernel
Date: 11 Aug 2004 23:48:16 -0400	[thread overview]
Message-ID: <1092282496.7765.148.camel@dhcppc4> (raw)
In-Reply-To: <411A2EA9.6000000-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>

Alexander,
The status of ACPI S3 suspend/resume in 2.6.7 is...

Run the latest ACPI patch on top of 2.6.7
(indeed, you still need the latest patch for 2.6.8)

build EHCI as a module, and unload it first

echo 3 >/proc/acpi/sleep

(yes, it is on the list to move to sysfs...)

some systems get a double event if wakeup with power button.
I use the LID to wake up my system and that works fine.

many systems come back up from S3, but don't re-enable
the LCD, or some re-enable it, but in the wrong mode.
Sometimes you can wake it up by running X.
Sometiems you can wake it up by switching
virtual consoles.
There is a lot of experimentation in this area, but
we don't really have fixes for this yet that are
universally positive -- ie fix platforms w/o breaking others.

in summary, YMMV;-)

cheers,
-Len




-------------------------------------------------------
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-12  3:48 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
2004-08-11 14:35               ` Nathan Bryant
     [not found]                 ` <411A2EA9.6000000-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-12  3:48                   ` Len Brown [this message]
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=1092282496.7765.148.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=demiurg-l0cyMroinI0@public.gmane.org \
    --cc=nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org \
    --cc=ncunningham-jjFNsPSvq+iXDw4h08c5KA@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