screen stays blank after resume from suspend

[Jimmy P]

After pressing fn+f4, my laptop is suspended to memory. When I press enter to wake it up, the screen stays off. If I hit ctrl-alt-f1 I get a console, at which point I can hit alt-f7 to show X again.

My machine is an acer travelmate 4650 with intel 915 chipset / display.

[Jimmy P (jimmypoor2004)]

Sorry, this is on ubuntu dapper flight 3.

[Erik De Wael (erik-dewael)]

For me (Acer Travelmate 634LC), also with a Flight 3, when I want to wake it up, screen stays blank but I can't get any tty or anything else. I've to reboot...

[Rinaldo Maldera (rmaldera-deactivatedaccount)]

I'm having the same problem of Erik de Wael with an Inspiron 9300. If i get it to wake up from suspend OR restart X with Ctrl+Alt+Backspace my screen stays blank. I also have to reboot...

[Tormod Volden (tormodvolden)]

I experience the same as in the original bug description, but it is enough to move the mouse to get X back again (probably the screensaver/blanking is still active after resume).

Shouldn't the screen turn on, to show the user that the resume is complete?

However, after sleep/resume all my virtual consoles stay black and I can't find a way to revive them. Only X on console 7 works.

I have a savage TwisterK card and "via" chipset. Clean dapper flight 4 install.

[Jeremy Apthorp (nornagon)]

I have the same problem as Erik de Wael with an Asus z71v. Graphics card is an nvidia GeForce Go 6600, I'm using nvidia-glx from dapper.

Suspend (to both disk and ram) worked when I was using breezy with a stock kernel, but not when I installed a kernel from https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/21256 to fix the sound issues this laptop has when running breezy (specifically, http://www.sh.nu/~crimsun/linux-image-2.6.12-9-386_2.6.12-9.22_i386.deb). With that kernel, I get the same problem as I do now.

[Matthew Garrett (mjg59)]

If you're using nvidia-glx, please try without. It still breaks things, and we don't have the source code available to fix them.

[Jeremy Apthorp (nornagon)]

I tried using the nv driver instead... same thing. :(

[Alan Pater (alan-pater)]

Same issue on this HP compaq nw8000. Using 'ati' driver. Dapper Flight 5.

 https://wiki.ubuntu.com/LaptopTestingTeam/HPNW8000.

Are there some tests we could be performing, or other information we can provide?

[Florian Boucault (fboucault)]

This bug do not annoy me anymore since I have removed vga=792 in my kernel options. Tests required.

[Jeremy Apthorp (nornagon)]

I did some fiddling around with installing nvidia-glx-legacy and friends, but I ended up getting rid of that and installing 1.0.8178 again. Now when I resume from suspend-to-disk, I get a frozen white screen.

Also, when using the proprietary nvidia drivers, pressing Ctrl-Alt-F[1-6] results in a black screen (but I can switch back by pressing C-A-F7), and when I try to restart X (C-A-Bksp), the laptop freezes.

In response to Kaleo's comment, I tried editing /boot/grub/menu.lst to try to remove that option, but it wasn't there to begin with...

[Jimmy P (jimmypoor2004)]

I tried dapper flight 6 on the same acer travelmate 4650 with intel 915 chipset.

Now after suspending to memory and hitting some keys I don't get the display back, but my wireless led lights back up. I no longer (as opposed to flight 3) get a console after hitting ctrl-alt-f1, the screen just stays blank.

[ruffneckc (ruffneckc)]

I have the same issue as Erik De Wael.

I'm on a Dell 700m (Intel 855 Integrated video chipset) using Dapper 6.06 Beta.

Suspending/Resuming worked fine in Breezy.

[Alan Pater (alan-pater)]

Full resume, including the screen, now works for me on this HP compaq nw8000. I am using the latest updates on Dapper, with the open r300 xorg video drivers and kernel 2.6.15-21-686.

[Jeremy Apthorp (nornagon)]

Asus z71v, nvidia 6600 Go, kernel 2.6.15-21-386, nvidia-kernel 8756, edge dapper:

Suspend-to-ram and suspend-to-disk work pretty much perfectly.

[Jeremy Apthorp (nornagon)]

Update: On closer inspection, not quite perfectly. Quite often when I resume from StR, my hard drive somehow fails to be remounted. I can't fix it on the fly, because there's either no mount or no sudo (or both), so I have to hard-poweroff.

May 5 09:58:52 localhost kernel: [4364681.940000] ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
May 5 09:58:52 localhost kernel: [4364681.940000] ata1: status=0x51 { DriveReady SeekComplete Error }
May 5 09:58:52 localhost kernel: [4364681.940000] ata1: error=0x04 { DriveStatusError }

^- that is repeated in /var/log/syslog.0 about three times.

[htoug (hetoug)]

I have the same problem on a Thinkpad x40 using kernel 2.6.15-22-686, kernel 2.6.15-22-386, kernel 2.6.15-21-386 and kernel 2.6.15-20-386.
kernel 2.6.15-19-386 and earlier are OK.

[htoug (hetoug)]

A small clarification:
Using kernel 2.6.15-19-386 the screen switches to 'Non-X' mode and some lines are written (also found in kern.log):
Stopping tasks: =========================================================================|
GTM info 78,14,0,0,13
ACPI: PCI interrupt for device 0000:02:01.0 disabled
ACPI: PCI interrupt for device 0000:02:00.0 disabled
ACPI: PCI interrupt for device 0000:00:1f.5 disabled
ACPI: PCI interrupt for device 0000:00:1d.7 disabled

This does not happen in newer kernels.
But I cannot see any significant difference in the kern.log entries.
kernel 2.6.15-20-386 has this as the last bit of the resume log:
May 17 20:59:27 localhost kernel: [4296499.071000] hub 3-0:1.0: USB hub found
May 17 20:59:27 localhost kernel: [4296499.071000] hub 3-0:1.0: 2 ports detected
May 17 20:59:43 localhost kernel: [4296514.005000] mtrr: base(0xe0910000) is not aligned on a size(0x300000) boundary
May 17 20:59:51 localhost kernel: Kernel logging (proc) stopped.
May 17 20:59:51 localhost kernel: Kernel log daemon terminating.
May 17 21:01:08 localhost kernel: Inspecting /boot/System.map-2.6.15-19-386

The two 'hub' lines are found in the kernel-19 logs. I can't recall just how impatient I was (whether i pressed the power button before or after 20:59:43).
If it can help I can retry and wait longer before powering down.

[Paul Sladen (sladen)]

htoug: could you confirm. Are you referring to Hibernate, rather than Suspend issues. The line "I can retry and wait longer before powering down" is leading me to wonder. If your bug is about hibernate, please could you file a new bug.

[ruffneckc (ruffneckc)]

Resume from suspend seems to be working normal now on my 700m. I have to log out of my gnome session first to get the option to SUSPEND. I'm running all the latest updates including kernel 2.6.15-22-686.

[Wander Boessenkool (wander)]

On a Dell Latitude d510 with intel i915 graphics resuming from a suspend leaves the screen blank when a kernel vga= 791 parameter is passed. Omitting this parameter from the kernel commandline makes resume work again. This is with kernel 2.6.15-23

[Martin Bergner (martin-bergner)]

This does now happen to me with dapper and a i915 graphics card, somewhere around kernel 2.6.15-23 it worked without a problem, but now, it doesn't anymore. I now use the 2.6.15-27, but it doesn't work with 2.6.15-23 anymore, so I suspect it has nothing to do with the kernel.

[Jon Skanes (jon-skanes)]

I seem to be having similar problems using Feisty on a Compaq Evo N410C. On starting after suspend, the screen seems to be fine except the resolution has changed. The resolution difference appears as the console output being in a much smaller block in the center of the console. I can see console log messages until X restores. Once X restores, if i switch to a VC, there is a strange fading effect and the VC doesn't show video.

I'm using the Xorg ati radeon driver on the following hardware:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
        Subsystem: Compaq Computer Corporation Unknown device 00b4
        Flags: bus master, stepping, 66MHz, medium devsel, latency 66, IRQ 11
        Memory at 48000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 3000 [size=256]
        Memory at 40400000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at 40420000 [disabled] [size=128K]
        Capabilities: <access denied>

I tried using the radeon fb driver but alas it doesn't handle suspend at all.

[Jon Skanes (jon-skanes)]

After some fiddling, vga=0x318 solves the problem for me.

[Brandon (blr246)]

I have the same issue running Feisty on an IBM ThinkPad T42 with the ATI Xorg driver. Screen does not turn back on after resume from suspend-to-ram.

[laksdjfaasdf (laksdjfaasdf)]

Same problem here on Feisty with Thinkpad Z61m with Intel GMA 950. Screen stays black with a blinking cursor after returning from suspend to RAM. I can switch to graphical sesssion with <Ctrl><Alt><F7>.

My Ubuntu hardware database ID is: 5c7c6fc63c95a2b52efffca3492e4c3f

[sibidiba (sibidiba)]

On a laptop with
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
running a daily update of Hardy alpha5
resume from suspend works fine. Before 2.6.24-11 I needed a manual switch to the console and back to X. (acpi-support's option for this had no effect)
Can't test hibernate, I don't have a swap partition.

Seems fixed for me.

[Axel Pospischil (apos)]

I am running an IBM Thinkpad R31 with Hardy/8.0
Hardware:
 - VGA compatible controller: Intel Corporation 82830 CGC

Software:
 - linux-image-generic 2.6.24.17.19
 - xserver-xorg-video- 2:2.2.1-1ubuntu13
 - xserver-xorg-core 2:1.4.1~git20080131
 - acpi-support 0.109
 - acpid 1.0.4-5ubuntu9

After resume the screen keeps blank.
It is NOT possible to switch to a console.
It IS possible to switch to the X session via Ctrl+Alt+F7 and get the login window.

Tried to enable "DOUBLE_CONSOLE_SWITCH=true" in /etc/acpi/default, but with no positive result.

I remember that in after an initial installation of hardy this to work.

[Axel Pospischil (apos)]

p.s.: problem occurs after resume from HIBERNATION.

[Axel Pospischil (apos)]

Could solve the problem on my IBM Thinkpad R31 with Hardy/8.04 with a "quick and dirty" fix.

It seams, that
  /etc/acpi/suspend.d/75-console-switch .sh
does not store the CONSOLE var of the last running console in the correct way.

First Solution:
I know my ubuntu is running on chvt 7, so I changed
  CONSOLE=`fgconsole` to
  CONSOLE=7
in /etc/acpi/suspend.d/75-console-switch.sh

Second Solution:
I moved "/etc/acpi/resume.d/65-console-switch.sh" to "03-console-switch.sh", so the CONSOLE var is read in earlier.

Both solutions work for me.

P.S.: I don't need "DOUBLE_CONSOLE_SWITCH=true" in /etc/acpi/default (which is indeed checked in "/etc/acpi/resumed.d/65-console.sh")

[Axel Pospischil (apos)]

After some search on the internet I am now aware the hardy __is_not_using_acpi_suspend__ any more.

Instead "pm-utils" and the scripts in "/etc/pm/" and " /usr/lib/pm-utils/" are responsible for taking care of hibernation/supend.

So it is not clear, if the last post really solved the problem. It works now for me, but sometimes I have to switch manually to Console 9 instead of 7.

[Mike L (mle616)]

This is still affecting precise.

[penalvch (penalvch)]

Jimmy P, lease execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 28959

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]