[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Suspend-to-ram kills touchpad



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John O'Hagan on Monday 19 Sep 2005 19:36 wrote:

> Thank you for your reply; but I believe suspend2 is an alternate
> implementation of S4 (suspend to disk), which powers-off the machine, but
> on boot, resumes from an image saved to the swap partition of the hard
> disk. I have this working well using the in-kernel support and the KDE
> front-end.
> 
> What I'm working on is S3 (suspend to RAM), where the machine saves its
> state to RAM and goes into a low power state, just enough to maintain the
> image (and blink an LED!). The advantage of this is speed; just a few
> seconds rather than 30 or so for an S4 resume.

I've been using suspend-to-RAM and suspend-to-DISK without problems with my
Compaq Presario 2203AL laptop with in-kernel suspend code. suspend2 doesn't
work for me at all. And I don't like their dictation or loading and
unloading modules. suspend1 does it without all that.

Some combinations that I use:
Boot kernel with acpi_sleep=s3_bios
Don't use DRM X modules.

That's it.

HTH,

rrs
- -- 
Ritesh Raj Sarraf
RESEARCHUT -- http://www.researchut.com
Gnupg Key ID: 04F130BC
"Stealing logic from one person is plagiarism, stealing from many is
research."
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDLv9R4Rhi6gTxMLwRAsDEAKCaA1UYjpGnjEgQ/NkHX1QAXnqBKQCcDMgo
fJDypwLMp5hRL+5OonDntVA=
=EU76
-----END PGP SIGNATURE-----



Reply to: