public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Lorenz <martin-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: sleep states - maybe a dumb question...
Date: Fri, 26 Mar 2004 14:15:06 +0100	[thread overview]
Message-ID: <40642CDA.6070007@lorenz.eu.org> (raw)

Dear folks,

maybe this is a very dumb question, but I did not find an answer in the 
docs. (or I was not looking at the right place)

I see two different sleep-state capabilities on my laptop (run by a 
transmeta cursoe CPU) running 2.6.4 vanilla kernel and a debian unstable 
system.

# cat /proc/acpi/sleep
S0 S3 S4 S5

# cat /sys/power/state
standby mem disk

as I understand 'standby' is synonymous to 'S1', which is not showing up 
in the /proc version...

when issuing echo -n standby > /sys/power/state the system acts as if it 
would go to standby (switch to console, some output saying so, etc.) but 
resumes immediately.

what does that mean?
does my laptop lack S1/standby capability?

thanks for an explanation
-- 
martin lorenz
--
	They that can give up essential liberty
	to obtain a little temporary safety
	deserve neither liberty nor safety.
				-- Benjamin Franklin



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

             reply	other threads:[~2004-03-26 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 13:15 Martin Lorenz [this message]
     [not found] ` <40642CDA.6070007-2WKW0nu+7nMiq3RsQ1AnAw@public.gmane.org>
2004-03-28 13:31   ` sleep states - maybe a dumb question Pavel Machek

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=40642CDA.6070007@lorenz.eu.org \
    --to=martin-2wkw0nu+7nmiq3rsq1anaw@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