Bugzilla – Bug 145025
suspend to disk
Last modified: 2006-01-24 18:38:35 UTC
When I try to suspend to disk it goes through the usual stoppage messages but at the very end it comes back up to a screen saver for me to unlock and doesn't completely stop. I can keep doing this over and over once I unlock the screen.
Please provide some information about the system you're using, and run hwinfo and attach the output to this report. Please also try booting with acpi=off and see if that changes anything.
Also attach dmesg after unsucessful suspend attempt.
Created attachment 64777 [details] output of hwinfo on my machine attaching the output of hwinfo you requested
Created attachment 64782 [details] output of dmesg command after a failed suspend to disk
when you say boot with acpi=off is that something you want me to set in the BIOS or as a kernel option? if it's a kernel option where do I put that setting? Sorry, haven't gotten that into the whole kernel optionions and some of the very deep linux stuff like that.
you do not have a "resume= " option in the kernel boot commandline. Add "resume=/dev/hda5" to your kernell commandline in /boot/grub/menu.lst and reboot. An interesting question would be why this was not added automatically during installation. Did you do an upgrade from a previous version or was this a new installation?
you do not need to do the acpi=off stuff yet. Open /boot/grub/menu.lst with an editor (you need to be root to do this), find the section title SUSE LINUX 10.0.42 root (hd0,0) kernel /vmlinuz root=/dev/hda..... initrd /initrd and add "resume=/dev/hda5" to the end of the "kernel" line. Save the file and reboot. After this, suspend should work (or fail in a different way ;-)
this was an upgrade from 10.0. I will try the fix in a bit when I get a chance and let you know.
I added the resume=/dev/hda5 and it worked just fine. In fact it seems to be much faster than it was under 10.0. SO I guess the only problem was that it wasn't put there automatically as stated in an earlier post.
ok, the resume= missing is probably a yast bug. Please attach the logfiles as described in http://www.opensuse.org/Bug_Reporting_FAQ#YaST and the YaST hackers will take care of this bug.
Created attachment 64838 [details] yast logs
Upgrade from 10.0 ? Then this is a duplicate. *** This bug has been marked as a duplicate of 133993 *** *** This bug has been marked as a duplicate of 133993 ***