Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
System Suse 10.2 (upgrade from Suse 10.1) laptop HP NX7010 KDE 3.5.5
Before I upgraded my system I could suspend-to-disk using the KDE suspend to disk option (e.g. in the log-out dialog) and resume successfully when the system was rebooted; so there should be no bios or partition issues since none have changed with the upgrade.
After the upgrade, hibernate (suspend-to-disk) appears to function correctly, saves the memory image and umounts the disks and powers-down.
However when the system is rebooted, it appears to ignore the previous hibernate state and boots normally treating the system as if it were recovering from a power failure (i.e. replaying the systems disk transaction logs).
When I manually issue the command 'swsusp -fhi' the system hibernates and resumes (on power on) perfectly.
Is this a misconfiguration in the 'kpowersave' or is there someway I can force it to call 'swsusp'?
I have a problem like this. My laptop is a IBM T30 and I had openSuSE 10.1. I worked with Suspend to RAM, because Suspend to Disk crashed. With closing the laptop it going automatic in the Suspend to RAM mode.
After an update to openSuSE 10.2, kpowersave doesn't work. With manual execute in the kpowersave-menu to suspend to ram or by editing the kpowersaverc (under .kde/share/config) with the option ActionOnLidClose=SUSPEND2RAM, the laptop doesn't resume.
This is IMO not a KPowersave or powersave issue/bug, but more a pm-utils or a kernel problem since (K)Powersave suspend via HAL and pm-utils instead of themself directly. You (both) should report this to https://bugzilla.novell.com/ for openSUSE products, but please read this sides first (for 10.2):