public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
To: acpi-devel@lists.sourceforge.net
Cc: SoftwareSuspend-devel@lists.berlios.de
Subject: Re: [ACPI] Re: status update for current development on ASUS M2N
Date: Mon, 27 Sep 2004 15:28:34 +0200	[thread overview]
Message-ID: <m3d607g7st.fsf@brain.gnuhh.org> (raw)
In-Reply-To: <20040927123320.GA28634@hell.org.pl> (Karol Kozimor's message of "Mon, 27 Sep 2004 14:33:20 +0200")

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

 || On Mon, 27 Sep 2004 14:33:20 +0200
 || Karol Kozimor <sziwan@hell.org.pl> wrote: 

 kk> I had that issue too, with 2.6.9-rc1 I s'pose, but I thought it
 kk> was just bug #3193 revisited and didn't really investigate. Does
 kk> changing swsusp2 to _not_ use ACPI S4 help?

It seems that this is not a compile-time option anymore and solely
determined by /proc/software_suspend/acpi_s4_support, right?

Output of 'cat /proc/software_suspend/acpi_s4_support' is '0'.

So unless something is activating it somewhere, somehow, it seems that
this _is_ with deactivated ACPI S4.

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2004-09-27 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27  8:47 status update for current development on ASUS M2N Georg C. F. Greve
2004-09-27 10:11 ` Nigel Cunningham
2004-09-27 16:48   ` Georg C. F. Greve
     [not found]   ` <1096279213.4222.5.camel-AdgCB+f5QAxwBzq2CxEN2SkBHpOjBR89@public.gmane.org>
2004-09-30  9:59     ` [SoftwareSuspend-devel] " Georg C. F. Greve
2004-09-27 12:33 ` Karol Kozimor
2004-09-27 13:28   ` Georg C. F. Greve [this message]
2004-09-27 13:29     ` [ACPI] " Nigel Cunningham

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=m3d607g7st.fsf@brain.gnuhh.org \
    --to=greve@gnu.org \
    --cc=SoftwareSuspend-devel@lists.berlios.de \
    --cc=acpi-devel@lists.sourceforge.net \
    /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