Date: Thu, 26 Jun 2003 12:10:11 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: mobile@freebsd.org Subject: laptop suspend states behaviour Message-ID: <20030626101011.GA65846@pcwin002.win.tue.nl>
next in thread | raw e-mail | index | archive | help
--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi -mobile,
sorry for this rather longish email but I thought it would pay off to be
thorough.
Anyway, I spent some time yesterday & today putting together a list of sleep
states and the way FreeBSD handles them on my Dell Inspiron 4150. See belo=
w.
All tests were done by setting the 'hw.acpi.lid_switch_state' to one of
{S0,S1,S2,S3,S4}, and then closing & opening the lid. I chose this way beca=
use
I do not know how to resume from a command like 'acpiconf -s S1' -- pressing
keys or mouse buttons does not give me a resume in that case, but the lid
switch almost always works (but see the undefined state S0).
I'm sorry to say that most of the suspend states aren't very useful. Are
people able to use any suspend method on other laptops? Or does everybody j=
ust
powerdown? I've noticed that the time it takes to boot FreeBSD is so small
that I'm going to ditch the suspend partition again - it takes about 2 minu=
tes
to suspend to disk, vs. 30 seconds max to boot (of course the apps I used
won't be started but it won't take me 1:30 to start those again).
I noticed that I could set the hw.acpi.lid_switch sysctl to S0 and S2 even
though they didn't appear in the hw.acpi.supported_sleep_states list. Is it
useful to allow people to shoot themselves in the foot like this?
For the record: this is done on a
FreeBSD 5.1-CURRENT #1: Sat Jun 21 14:49:46 CEST 2003
using the patched Dell DSDT. Every test was done on a clean reboot,
after a shutdown -p (well except for S5 of course :).
Does all of this match other peoples experience?
--Stijn
OVERVIEW OF SLEEP STATE BEHAVIOUR ON MY INSPIRON 4150
---------------------------------------------------------------------------=
----
=46rom textmode console:
S0:
after lid close:
machine does not beep, display stays on, ACPI prints
'acpi_lid0: Lid closed'
after lid open:
nothing further happens, ACPI misses the fact that the lid was opened
again. Further attempts to close the lid are not detected anymore,
even when resetting the hw.acpi.lid_switch_state sysctl. This behaviour
differs from hw.acpi.lid_switch_state=3DNONE, where I can open and close
the lid multiple times and have ACPI detect it fine.
S1:
after lid close:
machine does not beep, display stays on
after lid open:
display doesn't turn back on, but commands appear to work. Starting
X turns the display back on for the virtual console that X runs on,
but switching back to a text console turns the display back off
again. Fn+F8 doesn't work.
S2:
after lid close:
machine does not beep, display turns off
after lid open:
display doesn't turn back on, but commands appear to work. Starting
X turns the display back on for the virtual console that X runs on,
but switching back to a text console turns the display back off
again. Fn+F8 doesn't work.
ACPI does complain about this sleep state (as it should, since it's
unsupported):
acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND
S3:
after lid close:
machine does not beep, and turns itself completely off
after lid open:
N/A -- a forced reboot needed.
S4:
after lid close:
machine does not beep, BIOS suspends to disk, then turns display off
after startup: (opening the lid does nothing, obviously)
BIOS resumes, turns display on, but when nearly finished the display
turns off again. Fn+F8 gets me the display back.
S5:
works like shutdown -p, as expected.
=46rom within X:
S0 and S2:
after lid close:
machine does not beep, display goes blank
after lid open:
display stays blank. Switching to a virtual console turns the display
back on, switching back to X then works.
S1:
after lid close:
machine beeps, switches to virtual console #0 but display stays on.
after lid open:
machine turns display off when resuming, but X turns it back on again.
S3:
after lid close:
machine beeps, display turns off
after lid open:
machine does not turn display back on. pressing keys results in
3 times a beep, 2 times nothing, 3 times a beep, etc ...
Fn+F8 does not work, waiting for > 60 seconds also does not work.
CTRL-ALT-DEL works.
S4:
after lid close:
BIOS suspends to disk, then turns display off
after startup: (opening the lid does nothing, obviously)
BIOS resumes, turns display on, but X comes up garbled. After that
I get the same beep effect when pressing keys that I also get when
resuming from S3. Fn+F8 does not work, waiting for > 60 seconds also
does not work. CTRL-ALT-DEL works.
S5:
works like shutdown -p, as expected.
--=20
The most reliable proof that there are extraterrestrial intelligent
lifeforms out there is that nobody actually tries to get in contact
with us.
-- Dirk Mueller
--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE++saDY3r/tLQmfWcRArGvAJ9mf/phyPl4kZlAWlfIKPOu/hV/0wCeJ7tl
/jQFw1AChTfgMY2FqkW3gB4=
=Qghu
-----END PGP SIGNATURE-----
--OgqxwSJOaUobr8KG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030626101011.GA65846>