Re: hibernate/sleep howto
Hugo Vanwoerkom wrote:
Ganeshram Iyer wrote:
Ganeshram Iyer wrote:
<snip>
Depending on your kernel version, you may not have any luck using
suspend. I never had luck, but I have not tried recently with the
2.6.12 and 2.6.13 kernels.
From swsusp.txt in /usr/src/linux/Documentation/power:
...
You need to append resume=/dev/your_swap_partition to kernel command
line. Then you suspend by
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
...
Hi!
AFAIK There are 3 versions of hibernation code. Two that are part of the
official kernel and one that need a patch (suspend2). This latter is
more advanced and should perform better but is being actively developed
and changes frequently. The two versions included in the official 2.6.x
kernel are Pavel's swsusp and Patrick Mochel's PM suspend. You have to
check which one is compiled in your kernel. Each one has it's own
starting command.
So I just did that:
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
It stops, i.e suspends the system. Very quick. Pop goes the speaker
and power goes off. Leaves the external modem connected.
Then what. I have no option but hitting the power on button and
selected the lilo image where I had added "resume/dev/hda13", my
swap device.
AFAIK, we have to wait for improvements on the ACPI side in order to
have a wake-on-lid kind of resume.
That's where things went wrong: it just booted and of course found
bad disks etc. rebooted itself and I had to clean things up.
Did you reinstalled lilo after changing it?? Is your "resume=/dev/..."
well written? It should work. There is however the possibility that your
harddrive cache was not written to the disk Some drives have this kind
of problem.. You can use hdparm to disable the cache before the suspend
command and reenable if after.
The hibernate script (hibernate package) handles these matters and
others that arise when using suspension, like the error in the clock
(after resuming, the system clock is at the time when it was suspended.
You have to syncronise it with the hardware clock). It can be customized
to the 3 versions of suspension code and to suspen-to-ram also.
May be somebody else has used 2.6.12 with suspend successfully.
I added the suspend option with the already existeing boot parms.
Maybe that is wrong, who knows.
It will be a while before I try again... ;-)
H
Best regards,
Luís Neves
Reply to: