Custom suspend script doesn't work in 6.0
Posts: 12
I am running a Dell Inspiron 1000 laptop. I was never able to use the KDE utility for suspend to RAM in MEPIS 3.x, but I had a script to manage this that I had pieced together from Web postings, and it worked well. After upgrading to MEPIS 6.0, I still cannot use the (new) KDE utilities, and the custom script will not work either. When I invoke the script with sudo sleep.sh, everything seems to suspend to RAM all right, but it will not come back from suspend. The drives and fan run briefly then stop, and the screen stays entirely black, with no evidence that it is responding to keyboard input. I have to force it to power down. Can anyone advise why the following script, which worked great in 3.x, would now fail in 6.0?
#! /bin/bash
# Switch to text mode screen
chvt 1
# save vbestate
vbetool vbestate save > /tmp/VBESTATE
sync
# Actually suspend...
echo mem > /sys/power/state
# Should now be asleep, but possibly 'echo' returns before
# it has quite happened ...
sleep 1
# restore vbestate
vbetool post
vbetool vbestate restore < /tmp/VBESTATE
rm -f /tmp/VBESTATE
# Switch back to X
chvt 7
# reinitialize network
/etc/init.d/networking restart
My experience with Mepis 6.0 and suspend
Posts: 11
Although I don't have your custom scripts, I too tried Mepis 6.0 on my Acer 3003LCi notebook. Using "suspend to ram" in Kpowersave, the system seemed to suspend similarly to how it does in Ubuntu. However, like you, I have been unable to wake the system from its slumber. I must power cycle the Acer to access the system. I also noticed that the power LED on the front of the Acer does not change from green to amber when in the suspend state. It does this in Ubuntu/Kubuntu.
Next I tried the "suspend to disk" option. I learned that I had to add "resume=/dev/hda3" to my grub boot parameters. This allowed Mepis to hibernate to the swap partition. Unfortunately, when I restarted from hibernate, I no longer had access to the keyboard or touchpad, as both were completely dead. Interestingly, the USB mouse continued to function properly.
Perhaps if I can sort out the differences between Mepis 6.0 and Ubuntu in this power management business, I might be able to get things to work more normally. Unfortunately, at this point, I am completely baffled.
Red