DP Dual Monitors, AMD RX5700 XT - Primary Display loses signal after opening any random app

English Hardware
1

In my daily driver desktop i got an dual screen setup (Extending configuration, no mirrored): 30 inch 2560x1600 Dell UP3017 display and an 27 inch 2560x1440 HP ZDisplay, it worked perfectly fine no issues with drivers nor glitches. Until after a while opening any application there’s a chance the primary display (Dell UP3017) loses connection and only the secondary is left on, KDE’s Display Configuration still shows the display as active, the fix is just turn off and turn on the screen both in the monitor power button or doing in the Display Configuration from KDE, doing a screen setting change then revert it to reenable it.

Until after a couple months always thought slightly different display sizes messes the aging XRandr, so i got another Dell UP3017 display to replace the HP ZDIsplay, so might solve the problem and i was wrong the problem is still present, i have no idea how to solve this, the problem always manifest randomly when you’re opening any app, i think it has slightly higher chance the issue again if open any image file with Gwenview, no idea how access the X11/xrandr logs

inXi -aCGMSz output:

System:
  Kernel: 6.13.1-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.13.1-1-default
    root=UUID=346a7963-4334-4f3a-a942-227b16f4c2c4 splash=silent quiet
    hid_apple.fnmode=0 security=apparmor mitigations=off
  Desktop: KDE Plasma v: 6.3.0 tk: Qt v: N/A info: frameworks v: 6.10.0
    wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20250211
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE AX V2 v: x.x
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: FD date: 06/08/2023
CPU:
  Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 4098 min/max: 550/4663 boost: enabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 4098 2: 4098 3: 4098
    4: 4098 5: 4098 6: 4098 7: 4098 8: 4098 9: 4098 10: 4098 11: 4098 12: 4098
    13: 4098 14: 4098 15: 4098 16: 4098 bogomips: 108593
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Vulnerable
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 status: Vulnerable: __user pointer sanitization and
    usercopy barriers only; no swapgs barriers
  Type: spectre_v2 status: Vulnerable; IBPB: disabled; STIBP: disabled;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
    XT / 5700/5700 XT] vendor: Sapphire NITRO+ driver: amdgpu v: kernel
    arch: RDNA-1 code: Navi-1x process: TSMC n7 (7nm) built: 2019-20 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1,DP-2
    empty: HDMI-A-1,HDMI-A-2 bus-ID: 0a:00.0 chip-ID: 1002:731f class-ID: 0300
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1600 s-dpi: 96 s-size: 1353x423mm (53.27x16.65")
    s-diag: 1418mm (55.81")
  Monitor-1: DP-1 pos: primary,right model: Dell UP3017 serial: <filter>
    built: 2019 res: mode: 2560x1600 hz: 60 scale: 100% (1) dpi: 101 gamma: 1.2
    size: 641x401mm (25.24x15.79") diag: 756mm (29.8") ratio: 16:10 modes:
    max: 2560x1600 min: 720x400
  Monitor-2: DP-2 pos: left model: Dell UP3017 serial: <filter> built: 2018
    res: mode: 2560x1600 hz: 60 scale: 100% (1) dpi: 101 gamma: 1.2
    size: 641x401mm (25.24x15.79") diag: 756mm (29.8") ratio: 16:10 modes:
    max: 2560x1600 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 5700 XT (radeonsi navi10 LLVM
    19.1.7 DRM 3.59 6.13.1-1-default) device-ID: 1002:731f memory: 7.81 GiB
    unified: no
  API: Vulkan v: 1.4.304 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 5700 XT (RADV NAVI10) driver: N/A device-ID: 1002:731f
    surfaces: xcb,xlib
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
2

What does ‘xrandr’ report during this state (no primary monitor)?
xrandr --listmonitors
xrandr --listactivemonitors

You could also monitor output from kscreen-console monitor perhaps.
kscreen-console monitor 2>&1 | tee capture.log

3

Check the ‘primary’ monitor settings - not using “auto select” (or equivalent)? Just in case that is impacting here somehow. Does Plasma Wayland work for you? If so, is the behaviour the same there?

Depending on the findings, this might need a bug report to resolve.

4

I tried to trigger the bug, seems are the greater the chances if i try to open applications or files when i have running a Youtube video from Brave browser in the background.

When the display signal is lost but xrandr still finds the display as active:

xrandr --listmonitors
Monitors: 2
 0: +*DP-1 2560/641x1600/401+2560+0  DP-1
 1: +DP-2 2560/641x1600/401+0+0  DP-2

xrandr --listactivemonitors
Monitors: 2
 0: +*DP-1 2560/641x1600/401+2560+0  DP-1
 1: +DP-2 2560/641x1600/401+0+0  DP-2

The kscreen-console monitor log: START: Requesting ConfigReceived config. Took 8 millisecondsRemember to enab - Pastebin.com

5

i do not have Wayland installed, and also i checked Display Configuration settings from KDE System Settings, couldn’t find any property or check for Auto-Select screen.

6

If you reverse the monitor connections, does the issue move to the other monitor, or stay with whatever is connected to DP-1?

7

Swapped the connections, my secondary monitor (now the main) still works fine, while the other, signal lost.

On close inspection, seems like KDE already recognized the output change and just rearranged my windows to stay the same from the older set up.

8

So, specific to the monitor?

9

For test purposes you can stop KScreen2 from running via
kcmshell6 kcm_kded
It might be interesting to see if it has any effect here. (Of course for multi-monitor setups it is recommended by the Plasma team to leave it running for dynamic display management.)

10

Yes, you do. (Plasma supports both X11 and Wayland environments). Choose the session type at the login screen.

With respect to “auto select” I was referring to the display input settings on the monitor itself, not KDE.

11

Alright i didn’t know i had Wayland installed, since i set “Automatic Login” while was installing OpenSUSE, and the installer defaulted to X11.

Seems like the problem is gone under Wayland, really tried hard to trigger the issue and seems it’s gone (Had to tweak the display settings a bit, since the scale was set in 105% and made the fonts look blurry)

12

With Plasma Wayland, display management is handled by KWin Wayland compositor directly, rather than via KScreen2 as a separate background service.

1 Like
13

After using Wayland for a week , seems the monitor losing signal but the OS still detects the monitor as active problem is gone, and my X11 applications works fine under xwayland, so if someone else had that weird trouble with moniitor losing signal like that, it might need to switch to Wayland.

Also i read that X11 had a very rough history with multimonitor setups and several extensions were developed to mitigate it to a extent.

14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.