On Fri, Feb 19, 2010 at 10:37 AM, Javier Vasquez <j.e.vasquez.v@gmail.com> wrote:

Hi all,

Previously I was having the following settings:

/etc/default/grub ---------------------- GRUB_CMDLINE_LINUX_DEFAULT='resume=/dev/sda5'

grub.cfg ----------- linux   /vmlinuz26 root=/dev/sda7 ro  resume=/dev/sda5

I have installed:

acpitool 0.5.1-1 kernel26 2.6.32.8-1

And fro quiet a long time I've been using the kernel suspend feature through acpitool, so in order to suspend I've always done:

acpitool -S

As of now, it seems storing the state into the swap area is working. Problem is that when booting, the kernel is not even trying to see if there's state stored in the swap, since I don't see any message about it, and all I'm getting is plain boot.

So I suspect the kernel is not compiled with built in support for suspend to disk.  Is this true?

Add the "resume" hook to the end of the HOOKS list in /etc/mkinitcpio.conf and rebuild your initramfs. This has to be added manually now with the non-klibc mkinitcpio.

On 2/19/10, Thomas Bächler <thomas@archlinux.org> wrote:

Am 19.02.2010 16:40, schrieb Ray Kohler:

...

Add the "resume" hook to the end of the HOOKS list in /etc/mkinitcpio.conf and rebuild your initramfs. This has to be added manually now with the non-klibc mkinitcpio.

Actually, all documentation I knew of always said it was necessary to add it. The old and much-hated "kinit" always applied some kind of magic we had no control of, including resuming although not told to do so. So, dumping kinit may have removed undocumented features - mainly because I didn't even know those features existed.

Ok, the mkinit hook worked... I never used it before with klibc mkinitcpio and didn't have trouble, so I never had to look for it. Thanks a lot, -- Javier.