On 03/04/17 13:54, Tim Jackson wrote:
To add to this thread, I have the exact same problem using fully-updated
(as of today, including libdrm-2.4.76-1) F25, GNOME and X11 session. To
be a bit more specific: for me, when the problem occurs (after the
screen locks and the monitors power down), I *can* "wake up" the screen,
*and* I get a (moveable) mouse cursor, but behind the cursor is just a
static copy of whatever happened to be on the screen prior to it going
to sleep. In most cases, black (presumably because GNOME blanked the
screen prior to lock). Or, if I happened to be on the login screen when
the monitors went to sleep, possibly a static copy of the login screen.
As outlined by previous posters, I can't find any way out of this other
than hard rebooting, which is a pretty nasty solution if I had unsaved
stuff.
On one occasion, the machine apparently fully crashed (not even
pingable), but I can't reproduce that.
The following kernels are affected:
kernel-4.10.5-200.fc25.x86_64
kernel-4.10.6-200.fc25.x86_64
If I roll back to kernel-4.9.14-200.fc25.x86_64 the problem goes away.
lspci -k -nn says:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119
[GeForce GT 610] [10de:104a] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:840d]
Kernel driver in use: nouveau
Kernel modules: nouveau
I have two screens connected via DVI and HDMI respectively.
To answer Ed Greshko's debugging questions:
1. Are you using the nouveau driver or the nVidia driver for your card?
nouveau. In fact this is a pretty fresh install of Fedora all round,
without much extra.
2. Are you running GNOME under Wayland or X11?
X11.
If you are using X11, and since you can ssh into the system, what is
the output if you do...
ssh systemB
export DISPLAY=:0
xrandr
The following (which is exactly the same as under a normal working
session):
Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 16384 x 16384
DVI-I-1 connected 1280x1024+1280+0 (normal left inverted right x axis y
axis) 338mm x 270mm
1280x1024 60.02 + 75.02*
1152x864 75.00
1024x768 75.03 60.00
800x600 75.00 60.32
640x480 75.00 59.94
720x400 70.08
HDMI-1 connected primary 1280x1024+0+0 (normal left inverted right x
axis y axis) 338mm x 270mm
1280x1024 60.02 + 75.02*
1152x864 75.00
1024x768 75.03 60.00
800x600 75.00 60.32
640x480 75.00 59.94
720x400 70.08
Using my system as an example, does doing something like this bring the
monitor back?
[snip xrandr blah --off, xrandr blah --auto]
Note that from my description, the monitors are already on and awake, so
they don't really need to be "brought back". But sure, turning them off
and on with xrandr turns them off and on again. It doesn't change the
underlying problem.
Is there any known BZ about this?
Tim
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Looks like bugzill 1435000 is the one we are looking at.
https://bugzilla.redhat.com/show_bug.cgi?id=1435000
Robin
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
