I just upgraded to kernel 2.6.17.beyond3-1, and hibernation is finally working again (as in the laptop hibernates without crashing). The problem now is that when I start the computer back up, instead of resuming it goes into the usual boot sequence (even though it says that hook [resume] is run). When the system has loaded up, the swap partition is not enabled, moreover running swapon doesn't turn it on (I first have to run makeswap).
Any ideas or suggestions on how I can fix this?
There's a long thread over on the laptop forum about this (I think).
I have the same problem, though my sus-to-RAM doesn't work at all anymore!
Do you have the resume=/dev/hda2 (might be wrong) option set in menu.lst?
If you're suspending to swap (like most people, AFAIK), it's
where hdaX is your swap partition.
To a file is
It's working perfectly for me, btw, with a custom beyond3 kernel.
Yeah, I have the same setup I was using before the suspend breakage in beyond2; my resume2=swap:/dev/vg0/swap (which did work fine). I haven't had time to investigate, but I'm *guessing* it may be that it's not activating the LVM until after it looks for the suspend image. Of course, the simple solution would be not to run swap-on-LVM (which would also have speed benefits, I think). But, I don't really have time to be running around reconfiguring my HD layout atm, and resume from swap-on-LVM did work, and should work again. I'll try to get more details later.
There have been changes to the suspend2 interface. You need to install the new mkinitcpio 0.4.4 from testing and regenerate your image to be able to resume again (these changes don't affect kernel26suspend2 as I held back the newest version until new mkinitcpio would move to current, I have no idea why it is in testing anyway - but beyond already has the newest suspend2 version).
it doesn't work for me.. i installed the new mkiniticpio and even reinstalled the kernel, put resume in the hooks section of the .conf file and it never even tries to resume. does it need to be in a certain order in regards to the filesystem hook or something?
also, my swap isn't being activated as the OP mentioned. i have to run swapon every time. thanks..
Just for the record I am not using LVM, so the problem is not LVM related. menu.lst is setup correctly (everything was working perfectly before 2.6.17). I'll try out the new mkinitcpio now. Thanks for the replies.
Ah, everything works perfectly with mkinitcpio 0.4.4. Thanks a lot, brain0!