Nothing on display after suspend/resume

rangalo · External Since: Jun 25, 2007 Posts: 1

Hi,

I am using sidux (based on sid).

I changed my /boot/grub/menu.lst to configure suspend/resume and added
resume=UUID=<swap-uuid> like this ...
The UUID provided belongs to my swap partition which is almost 1GB.

After that, I can suspend my computer using

powersave -u # -u is for suspend to ram (suspend to disk doesn't work
at all, it just hangs while suspending)

command, but while resuming, I get only a black screen, I see a lot of
activity of my hard-disk and I can hear the fans running, so I think
that resume is working, but there is something with the display.

Any, ideas ?

Below is the relevant parts of /boot/grub/menu.lst

------------------------------------Menu.lst--------------
# kopt=root=UUID=353cc61f-ede4-46c1-8d7f-b678de74678a ro quiet vga=791
resume=UUID=25184dd8-abc9-41c8-ae89-7c7ef875fed4 # in case the kernel
is changed

.......
.......
title Debian GNU/Linux, kernel 2.6.21.3-slh-up-4 Default
root (hd0,4)
kernel /boot/vmlinuz root=UUID=353cc61f-ede4-46c1-8d7f-
b678de74678a ro quiet vga=791 resume=UUID=25184dd8-abc9-41c8-
ae89-7c7ef875fed4 #for normal resume
initrd /boot/initrd.img
----------------------------------------

thanks & regards,
Hardik

--
To UNSUBSCRIBE, email to debian-laptop-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

user · External Since: Jun 25, 2007 Posts: 5

Try to change the consoles -- to the 1st and then to the 7th (chvt 1;
chvt 7).

On Mon, Jun 25, 2007 at 11:30:46AM -0000, rangalo wrote:
> Hi,
>
> I am using sidux (based on sid).
>
> I changed my /boot/grub/menu.lst to configure suspend/resume and added
> resume=UUID=<swap-uuid> like this ...
> The UUID provided belongs to my swap partition which is almost 1GB.
>
>
> After that, I can suspend my computer using
>
> powersave -u # -u is for suspend to ram (suspend to disk doesn't work
> at all, it just hangs while suspending)
>
> command, but while resuming, I get only a black screen, I see a lot of
> activity of my hard-disk and I can hear the fans running, so I think
> that resume is working, but there is something with the display.
>
> Any, ideas ?
>
> Below is the relevant parts of /boot/grub/menu.lst
>
> ------------------------------------Menu.lst--------------
> # kopt=root=UUID=353cc61f-ede4-46c1-8d7f-b678de74678a ro quiet vga=791
> resume=UUID=25184dd8-abc9-41c8-ae89-7c7ef875fed4 # in case the kernel
> is changed
>
> ......
> ......
> title Debian GNU/Linux, kernel 2.6.21.3-slh-up-4 Default
> root (hd0,4)
> kernel /boot/vmlinuz root=UUID=353cc61f-ede4-46c1-8d7f-
> b678de74678a ro quiet vga=791 resume=UUID=25184dd8-abc9-41c8-
> ae89-7c7ef875fed4 #for normal resume
> initrd /boot/initrd.img
> ----------------------------------------
>
> thanks & regards,
> Hardik
>
>
> --
> To UNSUBSCRIBE, email to debian-laptop-REQUEST.TakeThisOut@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org
>

--
I'm a gambler
And I'm a runner.
But you knew it
when you laid down.
I'm a picture
of ugly stories.
I'm a killer and I'm a clown.
(Alice Cooper)

--
To UNSUBSCRIBE, email to debian-laptop-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

Kevin Mitchell · External Since: Jun 25, 2007 Posts: 1

Hey Hardik,
First of all, I think you only need to worry about your menu.lst and
swap partition if your trying to suspend to disk (or suspend to both
disk and ram simultaneously), though for all I know powersaved may
want everything just so to do anything. If you're only trying to
suspend to ram, the problem is likely that the video card is a little
groggy as a result of the software procedure for suspending.

I'm not too sure about powersave, but I use acpid which comes with a
bunch of scripts in /etc/acpi/ among which is sleep.sh. This script
sources a bunch of scripts init-style in /etc/acpi/suspend.d on
suspend and similarly from /etc/acpi/resume.d on resume. The trick is
that out of the box, running sleep.sh gave me the same behaviour as
you describe. It turned out that the scripts were trying too hard to
avoid this exact issue and ended up making matters worse. If the
switching virtual consoles trick doesn't work for you, this might be
what's happening with powersave. It might be posting your display or
something silly which breaks the resume. See if you can't customise
exactly the steps taken by powersave to suspend, or try using acpid
and customising to fit your system.

You can also try just the bare bones low level suspend with
echo -n mem > /sys/power/state
this is the penultimate step for acpid, and actually worked for me
just by itself, though without the niceties of tidying up first.

Kevin

On 6/25/07, rangalo <hard.mehta DeleteThis @gmail.com> wrote:
> Hi,
>
> I am using sidux (based on sid).
>
> I changed my /boot/grub/menu.lst to configure suspend/resume and added
> resume=UUID=<swap-uuid> like this ...
> The UUID provided belongs to my swap partition which is almost 1GB.
>
>
> After that, I can suspend my computer using
>
> powersave -u # -u is for suspend to ram (suspend to disk doesn't work
> at all, it just hangs while suspending)
>
> command, but while resuming, I get only a black screen, I see a lot of
> activity of my hard-disk and I can hear the fans running, so I think
> that resume is working, but there is something with the display.
>
> Any, ideas ?
>
> Below is the relevant parts of /boot/grub/menu.lst
>
> ------------------------------------Menu.lst--------------
> # kopt=root=UUID=353cc61f-ede4-46c1-8d7f-b678de74678a ro quiet vga=791
> resume=UUID=25184dd8-abc9-41c8-ae89-7c7ef875fed4 # in case the kernel
> is changed
>
> ......
> ......
> title Debian GNU/Linux, kernel 2.6.21.3-slh-up-4 Default
> root (hd0,4)
> kernel /boot/vmlinuz root=UUID=353cc61f-ede4-46c1-8d7f-
> b678de74678a ro quiet vga=791 resume=UUID=25184dd8-abc9-41c8-
> ae89-7c7ef875fed4 #for normal resume
> initrd /boot/initrd.img
> ----------------------------------------
>
> thanks & regards,
> Hardik
>
>
> --
> To UNSUBSCRIBE, email to debian-laptop-REQUEST DeleteThis @lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org
>
>

--
To UNSUBSCRIBE, email to debian-laptop-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

Stuart Prescott · External Since: Feb 20, 2007 Posts: 3

Hi Hardik,

I found this page very useful in getting the right incantations for both
suspend to ram and suspend to disk:

http://en.opensuse.org/S2ram

Once I had it working with those from tools from the terminal (no X), I then
went on to do it under X and it all worked nicely. The options can then be
permanently saved in the config file for powersave.

For one laptop, I also needed the patch from:

http://forge.novell.com/pipermail/powersave-commit/2007-January/001086.html

to permit some extra options for suspend.

Hope that helps.

cheers
Stuart

--
Stuart Prescott www.nanoNANOnano.net

--
To UNSUBSCRIBE, email to debian-laptop-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org