You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2019-10-25 12:22:42
- merc68k
- Member
- Registered: 2015-02-27
- Posts: 11
Monitors black out after resuming from suspend
Hi all, I am a long-time XFCE user on Arch Linux.
I recently changed my displays so that I am now running dual Dell U2415 (in case that is relevant) displays, connected via mini-displayport, daisy-chained together.
Before that, I was running one U2415 connected via displayport, with an older DVI monitor.
All of this is through the integrated Intel HD graphics on my i5 6600.
With the daisy-chained screens, I have an issue sometimes coming out of suspend. Both displays will activate when first waking up the machine, and I will see the unlock screen, but after two or three seconds, both screens go black. At this point, I can switch to a different virtual console (i.e. ctrl-alt-F2, F3, etc), and the displays there are fine, but the xorg console is dead (the screens go into power save mode).
If I kill the display manager (lxdm), then it gets restarted, and the graphical display works again on both screens, and I can log in and work normally. It's just obviously a bit of a hassle to lose my place each time this happens.
I was using a different display manager (sddm I think) initially, but I changed to lxdm just to see if that would fix the problem.
Any ideas what I could try here?
Offline
#2 2019-10-25 19:34:35
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 11,489
Re: Monitors black out after resuming from suspend
What does your Xorg.0.log file and the journal say at the time of this event?
A second thing to do is to run xfsettingsd in debug mode and send the output to a log file:
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon > /tmp/xf.log 2>&1...and go through a suspend/resume event. Once you've recovered, post back the contents of the xf.log file.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#3 2019-10-25 20:16:23
- merc68k
- Member
- Registered: 2015-02-27
- Posts: 11
Re: Monitors black out after resuming from suspend
I didn't think about checking the logs for some reason, haha.
From the journal:
Oct 25 07:32:49 archie64 systemd-logind[651]: Operation 'sleep' finished.
Oct 25 07:32:49 archie64 kernel: video LNXVIDEO:00: Restoring backlight state
Oct 25 07:32:49 archie64 kernel: PM: suspend exit
[...]
Oct 25 07:32:57 archie64 kernel: e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 25 07:33:00 archie64 xscreensaver[1015]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=masonj
Oct 25 07:33:02 archie64 systemd[1]: systemd-rfkill.service: Succeeded.
Oct 25 07:33:02 archie64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 kernel: audit: type=1131 audit(1572003182.286:220): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 xscreensaver[1015]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=masonj
Oct 25 07:33:02 archie64 systemd[1]: man-db.service: Succeeded.
Oct 25 07:32:57 archie64 bluetoothd[598]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc
Oct 25 07:32:57 archie64 kernel: usb 1-9.1.4.3: New USB device found, idVendor=0451, idProduct=ca01, bcdDevice= 1.00
Oct 25 07:32:57 archie64 kernel: usb 1-9.1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 25 07:32:57 archie64 kernel: usb 1-9.1.4.3: Product: Texas Instruments USBtoI2C Solution
Oct 25 07:32:57 archie64 kernel: usb 1-9.1.4.3: Manufacturer: Texas Instruments
Oct 25 07:32:57 archie64 kernel: [37B blob data]
Oct 25 07:32:57 archie64 kernel: hid-generic 0003:0451:CA01.0007: hiddev2,hidraw4: USB HID v1.00 Device [Texas Instruments Texas Instruments USBtoI2C Solution] on usb-0000:00:14.0-9.1.4.3/input0
Oct 25 07:32:57 archie64 connman-vpnd[649]: eth1 {newlink} index 3 address x mtu 1500
Oct 25 07:32:57 archie64 connman-vpnd[649]: eth1 {newlink} index 3 operstate 6 <UP>
Oct 25 07:32:57 archie64 connmand[601]: eth1 {RX} 6194633 packets 2413573062 bytes
Oct 25 07:32:57 archie64 connmand[601]: eth1 {TX} 4363381 packets 914730844 bytes
Oct 25 07:32:57 archie64 connmand[601]: eth1 {newlink} index 3 address x mtu 1500
Oct 25 07:32:57 archie64 connmand[601]: eth1 {newlink} index 3 operstate 6 <UP>
Oct 25 07:32:57 archie64 kernel: e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 25 07:33:00 archie64 xscreensaver[1015]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=masonj
Oct 25 07:33:02 archie64 systemd[1]: systemd-rfkill.service: Succeeded.
Oct 25 07:33:02 archie64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 kernel: audit: type=1131 audit(1572003182.286:220): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 xscreensaver[1015]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=masonj
Oct 25 07:33:02 archie64 systemd[1]: man-db.service: Succeeded.
Oct 25 07:33:02 archie64 systemd[1]: Started Daily man-db regeneration.
Oct 25 07:33:02 archie64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 kernel: audit: type=1130 audit(1572003182.866:221): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:02 archie64 kernel: audit: type=1131 audit(1572003182.866:222): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=man-db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:06 archie64 audit[958]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 pid=958 comm="xfdesktop" exe="/usr/bin/xfdesktop" sig=11 res=1
Oct 25 07:33:06 archie64 kernel: xfdesktop[958]: segfault at 10000020a ip 00007f1b07c4f3bc sp 00007fff04a9a558 error 4 in libgobject-2.0.so.0.6200.1 (deleted)[7f1b07c49000+32000]
Oct 25 07:33:06 archie64 kernel: Code: fc 03 00 00 77 38 48 c1 e8 02 48 8d 15 7d 6d 04 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 2d 48 83 e6 fc 45 31 c0 48 85 c0 74 0e <f6> 40 16 04 74 05 48 85 f6 75 29 45 31 c0 44 89 c0 c3 66 90 48 83
Oct 25 07:33:06 archie64 kernel: audit: type=1701 audit(1572003186.557:223): auid=1000 uid=1000 gid=1000 ses=1 pid=958 comm="xfdesktop" exe="/usr/bin/xfdesktop" sig=11 res=1
Oct 25 07:33:06 archie64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-32300-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:06 archie64 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Oct 25 07:33:06 archie64 systemd[1]: Started Process Core Dump (PID 32300/UID 0).
Oct 25 07:33:06 archie64 kernel: audit: type=1130 audit(1572003186.570:224): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-32300-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s>
Oct 25 07:33:07 archie64 systemd-coredump[32301]: Process 958 (xfdesktop) of user 1000 dumped core.
Stack trace of thread 958:
#0 0x00007f1b07c4f3bc n/a (/usr/lib/libgobject-2.0.so.0.6200.1 (deleted))
Oct 25 07:33:07 archie64 systemd[1]: systemd-coredump@0-32300-0.service: Succeeded.
Oct 25 07:33:07 archie64 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-32300-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 07:33:07 archie64 kernel: audit: type=1131 audit(1572003187.313:225): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-32300-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s>
Oct 25 07:33:13 archie64 unix_chkpwd[32316]: password check failed for user (masonj)
Oct 25 07:33:13 archie64 xscreensaver[1015]: pam_unix(xscreensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=masonj
Oct 25 07:33:15 archie64 xscreensaver[1015]: FAILED LOGIN 1 ON DISPLAY ":0.0", FOR "masonj"
Oct 25 07:33:23 archie64 systemd[1]: Started Getty on tty2.I wonder if the xfdesktop crash there is the cause of the problems.
As for the xorg log, I'm not sure how to interpret the timestamp in there, but from the file timestamps, I think this is the relevant log, with the line at 53457.972 being the first thing printed after sleeping:
[ 43857.272] (II) UnloadModule: "libinput"
[ 53457.972] (II) intel(0): Enabled output DP1-8
[ 53457.990] (II) intel(0): Enabled output DP1-8
[ 53457.991] (II) intel(0): Enabled output DP1-8
[ 53458.010] (II) intel(0): Enabled output DP1-8
[ 53458.013] (II) intel(0): Enabled output DP1-8
[ 53458.014] (II) intel(0): Enabled output DP1-1
[ 53458.188] (II) event3 - Logitech USB Gaming Mouse: SYN_DROPPED event - some input events have been lost.
[ 53458.310] (II) intel(0): switch to mode 1920x1200@60.0 on DP1-1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 53458.398] (II) intel(0): switch to mode 1920x1200@60.0 on DP1-8 using pipe 1, position (1920, 0), rotation normal, reflection none
[ 53468.474] (II) intel(0): Enabled output DP1-8
[ 53468.654] (II) intel(0): Enabled output DP1-1
[ 53468.656] (II) intel(0): Enabled output DP1-8
[ 53468.658] (II) intel(0): Enabled output DP1-1
[ 53468.846] (EE) intel(0): Failed to prepare CRTC for page flipping, disabling TearFree
[ 53484.793] (II) event2 - Power Button: device removed
[ 53484.820] (II) event8 - Video Bus: device removed
[ 53484.864] (II) event1 - Power Button: device removed
[ 53484.907] (II) event0 - Sleep Button: device removed
[ 53484.931] (II) event4 - Logitech Gaming Keyboard G810: device removed
[ 53484.950] (II) event5 - Logitech Gaming Keyboard G810 Keyboard: device removed
[ 53484.970] (II) event7 - Logitech Gaming Keyboard G810 Consumer Control: device removed
[ 53485.000] (II) event3 - Logitech USB Gaming Mouse: device removed
[ 53485.040] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 53491.212] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 53491.212] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 0, disabling CRTC:48
[ 53491.549] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling CRTC:66
[ 53492.225] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 53492.225] (II) event2 - Power Button: device is a keyboard
[ 53492.227] (II) event8 - Video Bus: is tagged by udev as: Keyboard
[ 53492.228] (II) event8 - Video Bus: device is a keyboard
[ 53492.230] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 53492.230] (II) event1 - Power Button: device is a keyboard
[ 53492.232] (II) event0 - Sleep Button: is tagged by udev as: Keyboard
[ 53492.232] (II) event0 - Sleep Button: device is a keyboard
[ 53492.235] (II) event4 - Logitech Gaming Keyboard G810: is tagged by udev as: Keyboard
[ 53492.236] (II) event4 - Logitech Gaming Keyboard G810: device is a keyboard
[ 53492.239] (II) event5 - Logitech Gaming Keyboard G810 Keyboard: is tagged by udev as: Keyboard
[ 53492.239] (II) event5 - Logitech Gaming Keyboard G810 Keyboard: device is a keyboard
[ 53492.242] (II) event7 - Logitech Gaming Keyboard G810 Consumer Control: is tagged by udev as: Keyboard
[ 53492.242] (II) event7 - Logitech Gaming Keyboard G810 Consumer Control: device is a keyboard
[ 53492.302] (II) event3 - Logitech USB Gaming Mouse: is tagged by udev as: Mouse
[ 53492.302] (II) event3 - Logitech USB Gaming Mouse: device set to 800 DPI
[ 53492.303] (II) event3 - Logitech USB Gaming Mouse: device is a pointer
[ 53529.803] (II) event2 - Power Button: device removed
[ 53529.823] (II) event8 - Video Bus: device removed
[ 53529.880] (II) event1 - Power Button: device removed
[ 53529.900] (II) event0 - Sleep Button: device removed
[ 53529.921] (II) event4 - Logitech Gaming Keyboard G810: device removed
[ 53529.940] (II) event5 - Logitech Gaming Keyboard G810 Keyboard: device removed
[ 53529.960] (II) event7 - Logitech Gaming Keyboard G810 Consumer Control: device removed
[ 53530.000] (II) event3 - Logitech USB Gaming Mouse: device removed
[ 53530.040] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.328] (II) UnloadModule: "libinput"
[ 53546.336] (II) Server terminated successfully (0). Closing log file.I'll try what you suggested with xfsettingsd and report back.
Thanks,
Offline
#4 2019-10-25 22:29:32
- ToZ
- Administrator
- From: Canada
- Registered: 2011-06-02
- Posts: 11,489
Re: Monitors black out after resuming from suspend
A couple of things from your logs:
There are a lot of xscreensaver "authentication failed" messages in your journal. Can you disable xscreensaver and see if that makes a difference?
-These entries from your Xorg log file:
[ 53491.212] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 0, disabling CRTC:48 [ 53491.549] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling CRTC:66Googling this brings up a couple of interesting links including this one. You appear to be using the intel driver. Do you have any specific intel configs? Have you tried the modesetting driver?
-And yes, xfdesktop crashing. But it wouldn't disable the screen.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
#5 2019-10-28 00:22:03
- merc68k
- Member
- Registered: 2015-02-27
- Posts: 11
Re: Monitors black out after resuming from suspend
@ToZ, thanks for those suggestions. Maybe I will try disabling Xscreensaver and switching to the modesetting driver. I don't have any Intel-specific config, but I seem to remember when I initially installed (which was not that long ago) there was some issue that wasn't resolved until I used the Intel driver.
It's been a few days and a few suspend/resume cycles now since this last occurred, so I haven't been able get get much more information yet.
Offline
#6 2019-11-17 13:36:14
- merc68k
- Member
- Registered: 2015-02-27
- Posts: 11
Re: Monitors black out after resuming from suspend
Just a small update on this, I haven't had a lot of time to diagnose further, but I did realize that this doesn't actually have to do with suspend/resume, but rather with powering off the displays.
I can reproduce the problem if I power off the main screen (the one which is connected directly to the PC) and then power it back on after a few seconds. The display will appear normally on both screens for about 5 seconds, then both will go black. If I repeat this, I can often get the displays back again for another 5 seconds, then they go black again.
Killing the display manager (lxdm) will get me back to a login prompt and from there everything is fine again.
I do seem to reliably get xfdesktop dumping core when this happens:
Nov 17 08:18:54 archie64 kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
Nov 17 08:18:54 archie64 systemd-coredump[52958]: Process 48048 (xfdesktop) of user 1000 dumped core.
Stack trace of thread 48048:
#0 0x00007f7f33d323bc g_type_check_instance_is_a (libgobject-2.0.so.0)
#1 0x00005622ae9e30f7 n/a (xfdesktop)
#2 0x00007f7f33d4fd5a g_closure_invoke (libgobject-2.0.so.0)
#3 0x00007f7f33d3d88e n/a (libgobject-2.0.so.0)
#4 0x00007f7f33d4198a g_signal_emit_valist (libgobject-2.0.so.0)
#5 0x00007f7f33d427f0 g_signal_emit (libgobject-2.0.so.0)
#6 0x00007f7f33f3db04 gdk_pixbuf_loader_close (libgdk_pixbuf-2.0.so.0)
#7 0x00007f7f33e33c74 n/a (libgio-2.0.so.0)
#8 0x00007f7f33e33ca9 n/a (libgio-2.0.so.0)
#9 0x00007f7f33c632bf g_main_context_dispatch (libglib-2.0.so.0)
#10 0x00007f7f33c65201 n/a (libglib-2.0.so.0)
#11 0x00007f7f33c66113 g_main_loop_run (libglib-2.0.so.0)
#12 0x00007f7f3444060f gtk_main (libgtk-3.so.0)
#13 0x00005622ae9eaea4 n/a (xfdesktop)
#14 0x00005622ae9eb262 n/a (xfdesktop)
#15 0x00007f7f33c5b733 n/a (libglib-2.0.so.0)
#16 0x00007f7f33c6308a n/a (libglib-2.0.so.0)
#17 0x00007f7f33c63350 g_main_context_dispatch (libglib-2.0.so.0)
#18 0x00007f7f33c65201 n/a (libglib-2.0.so.0)
#19 0x00007f7f33c65241 g_main_context_iteration (libglib-2.0.so.0)
#20 0x00007f7f33e16a3e g_application_run (libgio-2.0.so.0)
#21 0x00005622ae9db05e main (xfdesktop)
#22 0x00007f7f33a35153 __libc_start_main (libc.so.6)
#23 0x00005622ae9db0ae _start (xfdesktop)
Stack trace of thread 48050:
#0 0x00007f7f33b029ef __poll (libc.so.6)
#1 0x00007f7f33c65170 n/a (libglib-2.0.so.0)
#2 0x00007f7f33c65241 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f7f33c65292 n/a (libglib-2.0.so.0)
#4 0x00007f7f33c41c11 n/a (libglib-2.0.so.0)
#5 0x00007f7f33bde4cf start_thread (libpthread.so.0)
#6 0x00007f7f33b0d2d3 __clone (libc.so.6)
Stack trace of thread 52877:
#0 0x00007f7f33b07e9d syscall (libc.so.6)
#1 0x00007f7f33c1611b g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f7f33c93f43 n/a (libglib-2.0.so.0)
#3 0x00007f7f33c3b13b n/a (libglib-2.0.so.0)
#4 0x00007f7f33c41c11 n/a (libglib-2.0.so.0)
#5 0x00007f7f33bde4cf start_thread (libpthread.so.0)
#6 0x00007f7f33b0d2d3 __clone (libc.so.6)
Stack trace of thread 48051:
#0 0x00007f7f33b029ef __poll (libc.so.6)
#1 0x00007f7f33c65170 n/a (libglib-2.0.so.0)
#2 0x00007f7f33c66113 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f7f33dd3ba8 n/a (libgio-2.0.so.0)
#4 0x00007f7f33c41c11 n/a (libglib-2.0.so.0)
#5 0x00007f7f33bde4cf start_thread (libpthread.so.0)
#6 0x00007f7f33b0d2d3 __clone (libc.so.6)
Nov 17 08:18:54 archie64 systemd[1]: systemd-coredump@8-52957-0.service: Succeeded.... and I just noticed the intel drm error:
Nov 17 08:18:54 archie64 kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22Searching this online led me to: https://bugs.freedesktop.org/show_bug.cgi?id=97135
And this: https://bugs.freedesktop.org/show_bug.cgi?id=111632.
I'll see where these lead me.
Offline
#7 2019-11-19 22:34:12
- merc68k
- Member
- Registered: 2015-02-27
- Posts: 11
Re: Monitors black out after resuming from suspend
Another bit of information, the same problem occurs even at the display manager (login) UI, before Xfce has started, and, even using the modesetting driver instead of the Intel driver.
So perhaps this is more of an Xorg issue than it is Xfce, which the bugs I posted in my last comment also would suggest (if indeed they are related).
Offline
#8 2019-11-28 19:40:54
- avorop
- Member
- Registered: 2019-11-28
- Posts: 1
Re: Monitors black out after resuming from suspend
I have similar problem. If I let my display enter power-saving mode, then it never comes back. Even power button does not work. I have to hold it for 5 seconds to power it off. It works as expected otherwise. There was no problem with previous version of XFCE. I don't see any errors or warnings in Xorg.log. My system has 2 graphic cards Intel and Radeon.
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun PRO [Radeon HD 8570A/8570M]
Both drivers are loaded by xorg. I'm really at loss now. What to change?
Offline
#9 2020-02-27 12:09:48
- MichaelF91
- Member
- Registered: 2020-02-26
- Posts: 1
Re: Monitors black out after resuming from suspend
Another bit of information, the same problem occurs even at the display manager (login) UI, before Xfce has started, and, even using the modesetting driver instead of the Intel driver.
So perhaps this is more of an Xorg issue than it is Xfce, which the bugs I posted in my last comment also would suggest (if indeed they are related).
Did you manage to get anywhere with this? I'm in a similar position, I've got two dell monitors daisy chained via display port running off integrated Intel HD530(?) graphics on Ubuntu 19.10.
Sometimes, the monitors won't turn on correctly when I boot up the PC, but I can get them back either by rebooting once or twice, or by unplugging and re-plugging in the DP cable a couple of times.
The only error message I've been able to find is this one: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
I, too, found the links you mentioned previously, but they were a bit of a dead end, unfortunately.
Offline
Pages: 1
- Registered users online in this topic: 0, guests: 1
- [Bot] ClaudeBot
[ Generated in 0.010 seconds, 9 queries executed - Memory usage: 640.29 KiB (Peak: 673.13 KiB) ]