You are not logged in.
I tried to enable hibernation on my notebook via KDE Control Center - Battery. It didn't really work, and I disabled it again. Everything works fine, but on startup I now see something like that: "Activating Swap: [FAILED]". Sounds dangerous, but is probably an artifact, as nothing else malfunctions. Looks ugly, sure. What am I to do when confronted with a situation like this? With Windows it's reinstalling, but a Linux is supposed to be totally maintainable (the more so if it's Arch ) and ought to survive indefinitely. What is the recommended approach to a minor trouble like this?
Last edited by Llama (2008-04-12 17:29:36)
Offline
Check the output of:
fdisk -l | grep swap
(as root)
and make sure that the partition it shows is listed in your /etc/fstab.
It should look something like this:
/dev/sdXY swap swap defaults 0 0
Where X is a letter and Y a number. It will be /dev/hdXY is you don't have SATA.
Last edited by Dirhael (2008-04-12 16:39:09)
Offline
You probably have remnants of an old hibernation trial on your swap partition. Just 'mkswap <partition>' should fix this. Then 'swapon -a' if you want to start using it right away.
Offline
Everything's present and correct . Probably works, too, as 256M RAM isn't too much. But why the message?
Offline
bender02, you are one kind magician! Your method works like a charm. Do you care to explain the mechanics of it? How any "remnants" can be left on the swap? I used to think that holding - well, "remnants" is the job of the swap partition. The lack of understanding could be a bit unnerving, you know...
Offline
Hibernation dumps the RAM to the swap partition, if hibernation doesn't work properly it can corrupt the swap. The mkswap command basically cleans and formats the swap partition again and swapon just reactivates the swap so the OS can use it. No magic involved.
Last edited by elliott (2008-04-12 17:30:18)
Offline
Yea, no magic. elliott explained it pretty well.
Offline