From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Re: Standby (S1) does not work Date: Mon, 7 Jun 2004 14:29:20 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040607122920.GA11860@elf.ucw.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Michael Grigoriev Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.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