Same result with kernel 6.8… what I did was:
- Installed
linux 6.8.0rc6-1
kernel and rebooted
- manually selected kernel 6.8 at grub menu
- launched DDDA with DP module/cable @ side… launched okay with no journal spam
- removed DP cable and module and plugged into dGPU
- launched DDDA, received the blank/black screen and confirmed spam in journal
Below are the journalctl
entries from the point I disconnected the DP module from the side…
Apr 03 11:45:31 AMDRyzen7040 kernel: usb 1-1: USB disconnect, device number 12
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: Checking screens: available: (QScreen(0x62d759d5d5f0, name="eDP-2")) redundant: QHash() fake: QSet() all: (QScreen(0x62d759d5d5f0, name="eDP-2"), QScreen(0x62d75cfa8c10, name="DP-5"))
Apr 03 11:45:31 AMDRyzen7040 kcminit[4500]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4506]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4502]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4527]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 plasmashell[1187]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
Apr 03 11:45:31 AMDRyzen7040 kcminit[4516]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4515]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4519]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4537]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4536]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:31 AMDRyzen7040 kcminit[4548]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:36 AMDRyzen7040 kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: new full-speed USB device number 13 using xhci_hcd
Apr 03 11:45:42 AMDRyzen7040 kernel: amdgpu 0000:03:00.0: [drm] fb1: amdgpudrmfb frame buffer device
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR30 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create XR30 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create XR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: Product: DisplayPort Expansion Card
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: Manufacturer: Framework
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: SerialNumber: ##########
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kernel: hid-generic 0003:32AC:0003.0011: hiddev96,hidraw0: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:c5:00.3-2.4/input1
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4587]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-2/1-2.4"
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4587]: bus: 1, device: 13 was not an MTP device
Apr 03 11:45:42 AMDRyzen7040 kcminit[4615]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 kcminit[4614]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 kcminit[4625]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 kcminit[4610]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 plasmashell[1187]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Apr 03 11:45:42 AMDRyzen7040 plasmashell[1187]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Apr 03 11:45:42 AMDRyzen7040 plasmashell[1187]: Checking screens: available: (QScreen(0x7b2cd41871b0, name="DP-1"), QScreen(0x62d759d5d5f0, name="eDP-2")) redundant: QHash() fake: QSet() all: (QScreen(0x62d759d5d5f0, name="eDP-2"), QScreen(0x7b2cd41871b0, name="DP-1"))
Apr 03 11:45:42 AMDRyzen7040 kcminit[4626]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 kcminit[4637]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 kcminit[4641]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4661]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-2/1-2.4"
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4661]: bus: 1, device: 13 was not an MTP device
Apr 03 11:45:45 AMDRyzen7040 kernel: [UFW BLOCK] IN=enp199s0f3u1 OUT= MAC=01:00:5e:00:00:01:b0:6e:bf:63:49:78:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=52906 DF PROTO=2
Apr 03 11:45:52 AMDRyzen7040 plasmashell[1187]: trying to show an empty dialog
Apr 03 11:45:55 AMDRyzen7040 steam-runtime[4791]: fsync: up and running.
Apr 03 11:45:55 AMDRyzen7040 rtkit-daemon[1040]: Successfully made thread 4820 of process 4807 owned by '1000' high priority at nice level -10.
Apr 03 11:45:55 AMDRyzen7040 rtkit-daemon[1040]: Supervising 11 threads of 5 processes of 1 users.
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[1698]: /bin/sh\0-c\0DRI_PRIME=1 /home/daniel/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=367500 -- /home/daniel/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/daniel/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/daniel/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun '/home/daniel/.local/share/Steam/steamapps/common/DDDA/DDDA.exe'\0
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[4874]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[4874]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[4875]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 11:45:58 AMDRyzen7040 kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input32
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[4875]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 11:45:58 AMDRyzen7040 steam-runtime[4878]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 11:46:00 AMDRyzen7040 steam-runtime[4995]: fsync: up and running.
Apr 03 11:46:03 AMDRyzen7040 steam-runtime[4993]: Setting breakpad minidump AppID = 367500
Apr 03 11:46:03 AMDRyzen7040 steam-runtime[4993]: Steam_SetMinidumpSteamID: Caching Steam ID: 76561197996595002 [API loaded no]
Apr 03 11:46:03 AMDRyzen7040 steam-runtime[5067]: Fossilize INFO: Overriding serialization path: "/home/daniel/.local/share/Steam/steamapps/shadercache/367500/fozpipelinesv6/steamapprun_pipeline_cache".
Apr 03 11:46:05 AMDRyzen7040 kernel: [UFW BLOCK] IN=enp199s0f3u1 OUT= MAC=01:00:5e:00:00:01:b0:6e:bf:63:49:78:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=54709 DF PROTO=2
Apr 03 11:46:05 AMDRyzen7040 steam-runtime[1698]: GameOverlay: started '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayui' (pid 5139) for game process 5067
Apr 03 11:46:05 AMDRyzen7040 steam-runtime[5139]: 04/03 11:46:05 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20240329170910)/tid(5139)
Apr 03 11:46:05 AMDRyzen7040 steam-runtime[5139]: 04/03 11:46:05 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(5139)
Apr 03 11:46:05 AMDRyzen7040 steam-runtime[5139]: minidumps folder is set to /tmp/dumps
Apr 03 11:46:05 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 11:46:05 AMDRyzen7040 kernel: [drm:amdgpu_dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 11:46:05 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 11:46:05 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 11:46:05 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 11:46:05 AMDRyzen7040 kernel: [drm:amdgpu_dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 11:46:06 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 11:46:06 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 11:46:06 AMDRyzen7040 kernel: [drm:amdgpu_dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
What I thought was interesting from this snippet was that kwin_wayland_drm
related errors were already being thrown after connecting the module/cable to the dGPU; prior to launching the game:
Apr 03 11:45:36 AMDRyzen7040 kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: new full-speed USB device number 13 using xhci_hcd
Apr 03 11:45:42 AMDRyzen7040 kernel: amdgpu 0000:03:00.0: [drm] fb1: amdgpudrmfb frame buffer device
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR30 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create XR30 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create XR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: Product: DisplayPort Expansion Card
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: Manufacturer: Framework
Apr 03 11:45:42 AMDRyzen7040 kernel: usb 1-2.4: SerialNumber: ##########
Apr 03 11:45:42 AMDRyzen7040 kwin_wayland[1006]: kwin_wayland_drm: Failed to create AR24 framebuffer for multi-gpu: Invalid argument
Apr 03 11:45:42 AMDRyzen7040 kernel: hid-generic 0003:32AC:0003.0011: hiddev96,hidraw0: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:c5:00.3-2.4/input1
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4587]: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-2/1-2.4"
Apr 03 11:45:42 AMDRyzen7040 mtp-probe[4587]: bus: 1, device: 13 was not an MTP device
------- UPDATE -------
Brief update on Wayland performance/experience now that I’ve gotten a bit of game time in with the DP monitor plugged in on the side (iGPU):
- Firestone (windowed) works well… let it run for ~2hours
- Eternium (windowed) launches another window called
OpenGL Renderer
when it runs, and seems to work normally… only ran it briefly
- DDDA (full screen) also launches
OpenGL Renderer
when it runs, and felt a little more blurry compared to X11. The game defaults to 60 frame rate and disables sync… and playing with these settings seems to smooth out the blurriness (variable frame rate and sync enabled)… which makes sense as a 60 frame rate isn’t where Freesync would shine, just odd it felt like x11 was smoother with it. Played for about 30 min while Firestone was still running minimized.
I was left with an annoying flicker back on the desktop (dimming and un-dimming) that seemed to pulse in time with the movement of the mouse across the desktop/screen (my DP monitor, it is the primary) when I Alt-Tabbed from DDA to the desktop and persisted after DDDA closed.
I tried adjusting compositor latency settings, but the flickering didn’t stop until after I toggled the monitor down to 120hz then back up to 144hz and toggled “adaptive sync” from automatic to always and back to automatic again.
It may be that adjusting the in-game sync and/or frame rate spilled over somehow and affected the desktop… I’ll try pay attention the next time I launch DDDA to see what happens without tweaking any settings. Once the flicker was gone, I relaunched Firestone and Eternium and they did not bring any flicker with them when they launched or after they closed.
Note: All three games have DRI_PRIME=1 %command%
set in the steam launch options.
Hmm, too curious…
- I launched DDDA again, left it’s settings alone, alt-tab to desktop and it flickered as I moved the mouse. Closed the game and the flicker was gone.
- Went into KDE Display Config and changed he default “adaptive sync” from Automatic to Always (left refresh rate at 144hz) and the screen started flickering with mouse movement!?!
- Dropped the refresh rate down to 120hz and the flickering stopped
- Upped refresh rate back to 144hz and the flickering returned
- went into my monitor settings and adjusted FreeSync from
Ultimate Engine
down to Standard Engine
… System saw this event as a “new monitor attach”, had to reset it as my primary and move the running processes back over to it… but the flickering stopped
- Relaunched DDDA, alt-tab to the desktop… no flickering
- Closed DDDA… no flickering
So I guess my new issue under Wayland is that it my Freesync DP Monitor flickers with…
- Monitor Freesync Engine = Ultimate
- KDE Refresh rate = 144hz
- KDE Adaptive Sync = Always
And the workarounds are to either reduce the desktop Refresh Rate or reduce the monitors freesync engine.
Anyone know a setting/tweak under wayland to address this? Pretty sure my login script to enable freesync with xrandr back when I had this monitor on my desktop 2+ years ago under x11 never left me with flickers, and I’m pretty sure I’ve had Ultimate Freesync Engine enabled in the monitor since I bought it. Since then this DP monitor has been slacking of as my steamdeck’s external display… so not pushing 144hz over HDMI as that is limited to 120hz… hmmm
So I wonder if the real issue is that while I have the steamdeck still plugged into the monitor’s HDMI port @ 120hz, that 144hz on the DP port isn’t happy until I reduce the frame rate to 120hz (to match the HDMI) or adjust the Freesync Engine… hmm, wonder if the steamdeck is still happy with the Freesync engine change? Damn, too many variables and maybe’s… I feel I should wait for some feedback as a sanity check.
---- Update 2 ----
Okay, the steamdeck hated the monitor being in Freesync Standard Engine mode… it would not even output to it until I reverted back to the Ultimate Engine. Obviously there is some “must consider all connected sources” in play, so for now that I can be flicker-free in Wayland and keep the steamdeck happy… my KDE/monitor settings will be:
- Monitor Freesync Engine = Ultimate
- KDE Refresh rate = 120hz
- KDE Adaptive Sync = Always
Also tested this with DDDA… no flickers alt-tabing to desktop while it was running, nor after it closed.
— Update 3 —
Spoke too soon it seems… just launched Firestone (maximized the window to cover screen), minimized it and watched the desktop flicker… closed the game and the flickering continued. I obviously don’t have a handle on this issue which I’m starting to think is random and invalidating pretty much all of my hypothesis so far… never experienced this under x11.
Hopefully I’ll learn more in the Flicker issues with KDE Wayland at frame rates >100 fps (#2967) · Issues · drm / amd · GitLab discussion where they talk about increasing the performance features of the GPU… just makes me wonder if that’d be the iGPU or dGPU with what I’m experiencing. And if it’s the iGPU, then maybe the “increase the RAM in BIOS” setup recommendation pertains here? But i recall that being for artifacts which I think would be different, no? Hmm, the desktop is connected to the iGPU… the game is rendered by the dGPU with the DRI_PRIME=1 %command%
, butg the flickering desktop is still drawn by the iGPU, right?