From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Michael Grigoriev <mag-wxkiEGMmYARAfugRpC6u6w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Standby (S1) does not work
Date: Mon, 7 Jun 2004 14:29:20 +0200 [thread overview]
Message-ID: <20040607122920.GA11860@elf.ucw.cz> (raw)
In-Reply-To: <pan.2004.06.07.00.34.31.1417-wxkiEGMmYARAfugRpC6u6w@public.gmane.org>
Hi!
> > In possibly related news, I noticed this abnormality:
> >
> > # cat /sys/power/state
> > standby mem disk
> >
> > # cat /proc/acpi/sleep
> > S0 S3 S4 S4bios S5
> >
> > Notice that proc does not even list S1!
>
> Further research shows that S1 does in fact not exist. _S1 is not defined
> in the DSDT. I thought S1 is like the most basic ACPI mode and everybody
> would have it, no? Do you think that it is actually not supported by
> hardware, or is it just that the didn't bother adding it to the
> DSDT?
S1 is basically useless, no wonder hw manufacturers do not support
it. It was workaround for old windows...
Pavel
> Would it be a safe experiment to try throwing something like
>
> Name (\_S1, Package (0x03)
> {
> 0x02,
> 0x02,
> 0x00
> })
>
> into the DSDT?
You are not linkely to fry anything.
--
934a471f20d6580d5aad759bf0d97ddc
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
prev parent reply other threads:[~2004-06-07 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 15:05 Standby (S1) does not work Michael Grigoriev
2004-06-07 0:34 ` Michael Grigoriev
[not found] ` <pan.2004.06.07.00.34.31.1417-wxkiEGMmYARAfugRpC6u6w@public.gmane.org>
2004-06-07 12:29 ` 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=20040607122920.GA11860@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mag-wxkiEGMmYARAfugRpC6u6w@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