Ubuntu
linux-source-2.6.22 package

  1. Bug #94161
  2. Comment #8

Comment 8 for bug 94161

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

More information!

The following methods give me a perfect suspend+resume cycle:

sudo /etc/acpi/sleep.sh force
sudo /usr/sbin/hibernate-ram (after killing ipw daemon)
sudo pmi action suspend

Note that I've installed the "hibernate" package manually while diagnosing the issue.

The following methods have problems:

"Suspend" in KDE Logout Dialog
Suspends OK, resumes to a blank screen. I can switch to a VT (blind), login and sudo reboot (also blind; not even the VTs come back from suspend). The screen comes back to life when I hit the shutdown usplash.

/usr/lib/hal/scripts/hal-system-power-suspend
I get an error message:
org.freedesktop.Hal.Device.UnknownError
No back-end for your operating system

/usr/lib/hal/scripts/linux/hal-system-power-suspend-linux
Script seems to hang; after 30s or so I Ctrl+C'd it with no problem.

sudo /etc/acpi/sleep.sh
Script returns immediately; no error messages get printed.

It's my understanding that all of these roads should lead to Rome (a good suspend+resume cycle), but there are clearly big differences. The really troubling bit is that my screen is dead when I come back from a KDE-initiated suspend.

I use kpowersave... is this a problem? I can try the guidance power manager (as well as echo "mem" > /sys/power/state)...