From: Luke Hammer <lukeh-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: ACPI suspend weirdness on Dell Inspiron 2650
Date: Tue, 11 Feb 2003 16:00:17 +0000 [thread overview]
Message-ID: <3E491E11.20001@ihug.com.au> (raw)
Hi,
I've finallyjust managed to get some kind of suspend state
working on my Dell Inspiron 2650 laptop, using the 2.4.21-pre3 kernel
and the ACPI-20030125-2.4.21-pre3 patch (under RedHat 7.3). I can
get some kind of suspend state working using 'echo 1 >/proc/acpi/sleep'
but I don't think it's the genuine suspend-to-RAM state. For one
thing, as soon as I put it into this state, one of the fans comes on
and stays on (not very good when you're trying to conserve battery
juice, but this is probably a Dell BIOS problem); and secondly, the screen
doesn't actually seem to be turned off - I can still make out an image
on it,
it just looks like the backlighting has been turned off.
Nothing at all seems to happen if I try to echo 3, 4, 4b or 5 to
/proc/acpi/sleep,
which is strange since the ChangeLog for the latest ACPI patch mentions
being able to change settings for the S3 suspend, and it also claims to
incorporate the s4bios patch. If I cat /proc/acpi/sleep I get "S0 S1 S3
S4 S5", so
I'm not sure if I'm doing something wrong, or if ACPI suspend-to-RAM support
isn't fully functional yet.
So I'm wondering if anyone can give me any hints about getting these
real suspend states to work? Any information would be much appreciated.
-Luke
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next reply other threads:[~2003-02-11 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 16:00 Luke Hammer [this message]
[not found] ` <3E491E11.20001-rdE3vRTOlSC6c6uEtOJ/EA@public.gmane.org>
2003-02-11 7:57 ` ACPI suspend weirdness on Dell Inspiron 2650 Jean-Pierre Schwickerath
2003-02-11 11:53 ` Ducrot Bruno
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=3E491E11.20001@ihug.com.au \
--to=lukeh-rde3vrtolsc6c6uetoj/ea@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