From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Nico Schottelius
<nico-linux-acpi-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3/S2 Problems
Date: Mon, 25 Jul 2005 16:56:33 +0200 [thread overview]
Message-ID: <20050725145633.GA8485@elf.ucw.cz> (raw)
In-Reply-To: <20050724234742.GA18565-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Hi!
> echo -n 2 > /proc/acpi/sleep
> -> present with the nice ascii printout that it sleeps, but
> it awakes immeditally.
Are you sure your system support S2? (cat /proc/acpi/sleep)
> echo -n 3 > /proc/acpi/sleep
> -> works partly. System sleeps. But:
> --> After first sleep, everything is ok.
> --> After second sleep, the console is broken
> (many coloured blocks)
> X is still ok.
> --> After third and every following sleep:
> console broken (grey/coloured blocks)
> X broken (everything seems to be printed doubled like
> ll)
Strange, see Doc*/power/video.txt, tell me what tricks you are using.
> System:
> Compaq EVO N400C notebook
> Linux 2.6.12.3
>
> Btw,
> o is there any tool to do sleep / a nice frontend to acpi
> for the console
no.
> o where can I find the specification of ACPI sleep states?
ACPI spec from intel?
--
teflon -- maybe it is a trademark, but it should not be.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
prev parent reply other threads:[~2005-07-25 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 23:47 S3/S2 Problems Nico Schottelius
[not found] ` <20050724234742.GA18565-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
2005-07-25 14:56 ` Pavel Machek [this message]
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=20050725145633.GA8485@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nico-linux-acpi-xuaVFQXs+5hIG4jRRZ66WA@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