You are not logged in.
Pages: 1
Topic closed
Hi!
Whenever my laptop returns from sleep, and even after a manual screen lock, a blank screen appears.
The only way to wake it up is by pressing Ctrl+Alt+F1.
I am using a IdeaPad Z580 laptop with gnome 3.22.
$ xset -q
...
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 0
...
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is On
The display driver details are:
*-display
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:30 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:3000(size=64) memory:c0000-dffff
Any help?
Thanks!
Last edited by nonZero (2016-11-23 22:06:56)
Offline
Gnome on wayland? (the default - and in case, the xset output is rubbish)
Offline
I am not running Wayland (It caused trouble when launching gnome apps and was disabled via /etc/gdm/custom.conf).
Offline
"disabled via /etc/gdm/custom.conf"
That disables wayland for *gdm*, but the default gnome session is now gnome on wayland - you got to explicitly select "gnome on xorg". Confirmative?
Offline
I don't have prior experience with wayland, but I can reload gnome with Alt+F2, "r", I have $DISPLAY and not $WAYLAND_DISPLAY and I don't suffer from all the problems I had before disabling wayland, so I guess it is xorg gnome, right?
Offline
Right, so this is not it.
Can you ssh into the system, "export DISPLAY=:0" and query the dpms state as well as "xset dpms force on" if it's not.
Then try to open a new eg. xterm.
The question is whether the the output is suspended and doesn't wake for eg. input or the compositor simply displays some invalidated textures.
Offline
Did you mean to ssh when the computer is locked? I'll check this out later today when I got another PC.
Just to be clear: The monitor is off until I hit Ctrl+Alt+F1. For example: An external monitor will displays the monitor's built in "no signal". (But this is not related to the external monitor - the same problem occurs also when there is no external monitor attached.)
Offline
Yes. The idea is to inspect and try on the system w/o changing the systems state (which inevitably will happen when altering the VT)
The "No Signal" message suggests you're simply still in dpms.
Offline
When sshing into the locked PC, xset -q does return "Monitor is Off". DPMS is always on.
Only Ctrl+Alt+F1 turns it on, and not a regular keystroke (or mouse move).
Offline
Tried
xset dpms force on
(This should activate the screen)
Offline
It does turn on the monitor, but when it goes to lock/sleep again, it turns off again, and does not wake up on keystroke (as it should).
Offline
Yes, that means the entire problem is that input doesn't impact the dpms state (but everything else is just fine)
What's the output of "xinput" while the screen is off, notably, does it differ from the output while on?
Next test would be whether simply "xset dpms force off" (ie. avoiding whatever gnome does to suspend the screen) allows you to reactivate it with input events.
Offline
After running "xset -dpms", DPMS is turned off, and my monitor is always on, even if blank, and I can wake up the computer with any key - so this is related to DPMS.
xinput returns a list of devices, which does not change on lock. I couldn't make `xinput test` print any event information.
Offline
Correction: xset dpms force on does not wake up the monitor!
I tried:
sleep 1 && xset dpms force standby && sleep 8 && xset dpms force on
Which does not wake my monitor.
See also:
https://bbs.archlinux.org/viewtopic.php?id=215930
Which is around when I started suffering from this.
I am running:
$ uname -r
4.8.4-1-ARCH
Offline
Do you use the intel or the modesetting Xorg driver? (i somehow doubt the kernel thing)
Does it happen with the other?
Offline
Hi!
I use:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
Offline
just uninstalling xf86-video-intel and restarting X11 should get you the modesetting driver.
Offline
Solved: Using DRI2 instead of DRI3 solves the problem: https://wiki.archlinux.org/index.php/in … RI3_issues
(via: https://bbs.archlinux.org/viewtopic.php … 2#p1671422 )
Offline
I tired all solutions mentioned in this thread but nothing worked. Instead, I wrote a script that used `xrandr` to turn off the external display and turn it back on. Then used udevadm to call the script when monitor tries to turn back on. This worked every time. I have written a blog post on this:
Offline
This thread is 7½ years old - whatever was the problem then isn't your problem and whatever worked then might no exist anymore today.
Please don't necrobump. Let alone solved threads. Let alone only to report that they don't actually apply to you.
Offline
Closing this old thread.
Offline
Pages: 1
Topic closed