[Gutsy Beta] Black screen when resume from Suspend to RAM

Yes... it works fine with i810, with no other settings changed.

Does not work with a i945 though =/
both intel and i810 fail to resume, giving me only a black screen and disk activity. CTRL+ALT+BKSPACE does not work, nor does CTRL+ALT+DEL. The only option after that is a hard reset =/

Any thoughts on that?
I'm running gutsy beta on a Toshiba Satellite A205-S4797

I have been playing with this and have determined the following
(rebooting/hard-powering-off in between tests):

Three times I tested suspending with the Intel driver. It seems to
resume correctly and then reaches the password prompt to unlock the
screen. I enter my password, press enter and it freezes. This occurred
each of the three times. Sometimes it froze while the prompt was still
on the screen, sometimes it disappeared first leaving a black screen.

I then dpkg-reconfigure xserver-xorg and changed the driver to i810.
This works perfectly and never hanged. I tried this three times with
no issues.

I then dpkg-reconfigure xserver-xorg and changed the driver to Intel.
I used the configuration editor to stop the screen locking on suspend.
I then rebooted and tried again. It behaved the same as the initial
Intel tests: appearing to work, but hanging before the desktop is
displayed - leaving a black screen.

Turning off the desktop effects makes the suspending work properly and
it does not hang.

Looks similar to bug # 138094 if the mouse is still moveable. But it happens for me with i810 too afaik.
Do you have played any Video while or before suspending?

I've got this problem too. I suspect that it's a compiz problem because it persists with the i810 driver. I've disabled compiz in the meantime, and suspend works for me.

I've just upgraded through update-manager -d to gutsy. Didn't have this problem in Feisty. I've got a Dell 640m with intel chipset

Also of note.

This bug happens on any screen blanking event, not just after suspend. Keyboard works fine on unlocking password prompt, but then the screen remains blank and the keyboard doesn't work at all. Caps lock, Ctrl-alt-Backspace, nothing.

I have the same exact problem here. Im using the experimental modsetting driver and my video card is the intel 855gm. When i disable compiz fusion suspend works perfectly. I had compiz fusion on feisty and suspend worked there too.

quote

Also of note.

This bug happens on any screen blanking event, not just after suspend. Keyboard works fine on unlocking password prompt, but then the screen remains blank and the keyboard doesn't work at all. Caps lock, Ctrl-alt-Backspace, nothing.

end quote

same here too

Same issue. Though interestingly for me when I suspend without Compiz Fusion it works, re-enable Compiz Fusion and then suspend works in Compiz Fusion now.

One maybe workaround for this problem:

You could make a sh script to kill compiz on suspend (the script should be put in /etc/acpi/suspend.d/ )
This script would be something like just:

killall compiz.real

and one to start compiz in resume: (located at /etc/acpi/resume.d/ ) like this:

compiz --replace &

I'm pretty sure everything would work this way.

If you're on 855(GM?) hardware and want Compiz (or anything with textures) to resume ok, you might need to be running a patched version of the -intel driver.

http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-intel_2.1.1-0ubuntu10~pcjc2.2_i386.deb

This encorporates all other unreleased fixes I've been working on, and an additional line which aims to reset the 3D state of the card after VT switch. This may help after suspend, and has been reported to help issues with textures on 855 hardware after remove.

Please let me know if this helps.

Dear Peter,

This worked fine for me. Thank you for the patched version of the driver.

Best wishes

I have an "Intel Corporation 82852/855GM Integrated Graphics Device" and tried the patched driver above on my up-to-date Gutsy, but it didn't help at all.

All I see after Resume is black screen and my mouse cursor. Restart of my notebook was only via syscalls possible.

I will wait for a better driver version and have reverted back to the 'i810' driver.

satkata, please try the patched driver linked from the comment above:

http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-intel_2.1.1-0ubuntu10~pcjc2.2_i386.deb

Let me know if it improves matters at all.

Hi Peter,

the patched driver doesn't work for me. I tried it again, but got black screen and mouse cursor, that I was able to move around and nothing more.
The only difference this time was, that CTRL-ALT-Backspace brought me to the Login-Window.
Unfortunately, when I tried to login, the session loaded somewhere to the middle (I could see my desktop and panel), but the Login-Mask with 'Username and Password' field stayed and there was no response. When I then pushed the restart button on GDM, it showed me some kind of failsafe-login window and then actually proceeded with the restart.

The only difference for me in comparison to the driver from the repos was, that there was no annoying flattering of the screen while GDM was loading,

In another, kind of related, bug report, has somebody suggested to remove 'xscreensaver-gl' and test again, because eventually 'gnome-screensaver' could have something to do with it, but this had no effect too.

Tell me, if I can help you with more information. (Logs?xorg.conf?, etc.)

By the way, suspend with the 'i810' driver works on my pc only with modified Xorg.conf.

I must have these lines:

        Option "DRI" "true"
 Option "VBERestore" "true" # disables some kind of VBE Restore workaround
 Option "XAANoOffscreenPixmaps"

 under the "DEVICE" Section, else freezes my notebook on resume. I tried these lines with the 'intel' driver too, but didn't help.

Hi Peter,

I finally can suspend/resume with the Intel driver without any problems. I had luck to come across another bug 153329, where you have posted and are suggesting testing cases with '/etc/default/acpi-support', so what I did is just disabling everything relating to Video/PCI/VBERestore:

I disabled there here:
# Should we save and restore state using the VESA BIOS Extensions?
#SAVE_VBE_STATE=true

# The file that we use to save the vbestate
#VBESTATE=/var/lib/acpi-support/vbestate

# Should we attempt to warm-boot the video hardware on resume?
#POST_VIDEO=true

# Save and restore video state?
#SAVE_VIDEO_PCI_STATE=true

and additionally:
# Comment this out to disable screen locking on resume
#LOCK_SCREEN=true

The funny thing is, although through ACPI disabled, I still get the screen locked on resume, not that I am bothering about that, but it is still weird.

I don't know, if those disabled options could have some effect to the power consumption when suspended, but I am set for now. :)

LOCK_SCREEN only locks the console. Locking Gnome is another option under gconf.

I made a test today and reverted to the default "intel" driver from the repositories with generic xorg.conf and modified '/etc/default/acpi-support' file. To make my notebook resume properly, with both drivers (patched and official one) I only need to disable the following options:

# Should we save and restore state using the VESA BIOS Extensions?
#SAVE_VBE_STATE=true
# The file that we use to save the vbestate
#VBESTATE=/var/lib/acpi-support/vbestate

The other options, that I have had disabled in my previous post do not effect suspend/resume on my notebook.

I know, that the following is a bit out of place in this bug, but there are a lot of misleading described bug reports out there and I don't know how to describe this problem correctly. You can laugh about it, but it is really a problem sometimes. :)

The official driver from the repos can handle switching to a hot-plugged external monitor. Resolution auto adjustment is not perfect, but still.
With the patched driver from Peter, switching to a hot-plugged external monitor leads to black screen and system freeze, where even syscalls don't help.

I've collected the reports from people commenting on bugs 138256 and 150109: https://wiki.ubuntu.com/X/Bugs/ScreenModeChange

I think there's more than two bugs represented here, but in many cases we don't have enough data. Please look at the above page and fill in the missing data.

I've also created a page summarizing how to analyze and work around these issues. It would be worthwhile for anyone experiencing these issues to review and try these steps, and then report their findings on the appropriate bug

https://wiki.ubuntu.com/X/Debugging#head-0b6e9c6b60fa07cda4013a1c51239f1c14c4f89d

I just tested Hardy Alpha 1.

I have not had time to run the tests on the page that Bryce linked to, but thought I would quickly post my findings.

Suspend to RAM works correctly but, on resume, the screen seeps a pale blue colour from the bottom of the screen to the top. There is no mouse cursor visible and clicking or pressing keys does not bring up the "unlock" prompt. Pressing Ctrl+Alt+F1 does bring up the unlock prompt on top of a black screen. All then works as expected.

Hardy Alpha 2 behaves as Alpha 1 did. I'll work through the wiki page
https://wiki.ubuntu.com/X/Debugging#head-0b6e9c6b60fa07cda4013a1c51239f1c14c4f89d

Disable Compiz (change Appearance > Effects to none):
No change - C+A+F1 then C+A+F7 to recover.

Disable all power management (how? What do you mean by this?)

Log out of X, and log into the console, and try suspend/resume (or hibernate, or whatever) from there
Again, I don't know the command to suspend from the commandline, but I am fairly confident that it is X because I can C+A+F-key and fix it.

Switch virtual consoles and back (alt-ctrl-f1, alt-ctrl-f7 or f8 or f9)
As above, this fixes the issue.

If laptop, close lid and reopen
Using the lid-close button hangs my laptop Bug #138256

Attach another external monitor
Bug #156062 - I can no longer use an attached monitor.

Edit /etc/default/acpi-support - I will save this comment now in case I lose it and then continue testing.

In /etc/default/acpi-support, set SAVE_VBE_STATE=false
No change

Reverting that and then In /etc/default/acpi-support, set SAVE_VIDEO_PCI_STATE=true
No change (I haven't restarted X, GDM or the machine in between these - do I need to?)

Reverting that and then In /etc/default/acpi-support, set POST_VIDEO=false
No change

Reverting that and then In /etc/default/acpi-support, set USE_DPMS=true
Already set as this

Add the VBERestore option in Devices section of /etc/X11/xorg.conf (restarting x)
No change

Remove the VBERestore option in Devices section of /etc/X11/xorg.conf (restarting x)
No change

$ cat /proc/acpi/video/*/DOS
DOS setting: <4>
DOS setting: <4>
$ sudo rmmod video
$ cat /proc/acpi/video/*/DOS
cat: /proc/acpi/video/*/DOS: No such file or directory

I hope that something in there helps. Let me know if there are any more tests that you need.

Hmm, well another common issue relating to hangs when doing suspend/resume is bug #138256. To see if you're seeing an instance of that, could you try adding this to your xorg.conf?

 Section "Device"
    ...
    Option "ForceEnablePipeA" "true"
  EndSection

If it does, then please give the laptop's model name and number, and the output of `lspci -vvnn | grep -A1 "VGA compat"` and I can add a quirk for it.

Sorry Bryce,

I forgot about this bug. Suspend and resume now works perfectly in Hardy.

Setting as fixed released. Someone can change it back to confirmed if they are still having issues with Hardy.

Excellent, thanks for marking it fixed.

On Sat, May 03, 2008 at 05:15:34AM -0000, Aaron Whitehouse wrote:
> Setting as fixed released. Someone can change it back to confirmed if
> they are still having issues with Hardy.
>
> ** Changed in: xserver-xorg-video-intel (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> [Gutsy Beta] Black screen when resume from Suspend to RAM
> https://bugs.launchpad.net/bugs/150109
> You received this bug notification because you are a member of Ubuntu-X,
> which is subscribed to xserver-xorg-video-intel in ubuntu.