Re: Suspend and Hibernate in Etch not working on Asus L3400Tp laptop
On Wed, 2007-08-08 at 20:19 -0600, Bob Proulx wrote:
> If I try to suspend, the screen locker comes on, and after I type my
> password, it says:
> "Suspend Problem
> Your computer failed to suspend. Check the PAQ page for common
> Same with trying to hibernate:
> "Hibernate Problem
> HAL failed to hibernate. Check the FAQ page for common problems."
Very likely error messages would be logged to /var/log/syslog. Look
through that file and see what you find.
The only entry I found was:
@:~$ cat /var/log/syslog
Aug 9 09:57:58 gnome-power-manager: Suspending computer because user clicked suspend from tray menu
By what method did you attempt to suspend? Did you use the gnome
applet? Or did you use the hibernate script? Or some other method?
Yes, I used the gnome-power-manager applet.
Thanks to Michael who also pointed me to the hibernate script, I'm able now to hibernate, but need to access it as root via a terminal. My preference though, is to access it through the applet.
If the two that you tried did not work let me recommend the s2ram and
s2disk alternatives. It has a table of known workarounds for some
laptops and may work using one of the predefined recipes.
apt-get install uswsusp
Thanks, was apparently already installed
Then simply run it.
Machine is unknown.
This machine can be identified by:
sys_vendor = "ASUSTeK Computer Inc."
sys_product = "L3000E/T series Notebook PC"
sys_version = "0001"
bios_version = "0207"
See http://en.opensuse.org/S2ram for details.
If you report a problem, please include the complete output above.
This seems to lock my laptop
Also depending upon your laptop you may need a newer kernel than is
available in Debian Etch Stable. This can be installed from Sid
without needing to pull other packages. (As an aside this is required
for running powertop for example.)
> In Fedora 6 it did both extremely well. What could be the problem /
Suspend to disk and ram have been some of the most hardware dependent
issues for laptops. Some work fine and other give endless trouble. A
lot of the programs are scripted with table driven workarounds. This
means that every distro and every laptop will be a unique
combination. Others with different laptops may have the exact
opposite result from yours.
Maybe an idea to copy the fedora workaround tables?