[0x08000800]: data fabric sync flood event

ninjachicken1 · 2026-09-21 00:14:10

I've been experiencing the following error on my desktop:

Sep 20 22:17:47 archlinux kernel: x86/amd: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: System Fatal error.
Sep 20 22:17:47 archlinux kernel: fbcon: Taking over console
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: CPU:12 (19:21:2) MC5_STATUS[-|UE|MiscV|AddrV|PCC|TCC|SyndV|-|-|-]: 0xbea0000000000108
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: Error Addr: 0x01ffffffc2188462
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: IPID: 0x000500b000000000, Syndrome: 0x000000004d000000
Sep 20 22:17:47 archlinux kernel: 
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: Execution Unit Ext. Error Code: 0
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: cache level: RESV, tx: GEN, mem-tx: GEN

It can happen randomly, sometimes within 10 minutes of turning my computer on in the morning, sometimes after a few hours. It also happens consistently after launching Palworld (fairly graphically intense game) for a few minutes.

After this happens, regardless of whether it's random or because I attempted to play Palworld, it takes a few seconds to load kernel modules on boot and 13 seconds into that the GPU is initialized and my desktop becomes extremely laggy until I turn it off and leave it a few minutes.

Apparently "[0x08000800]: an uncorrected error caused a data fabric sync flood event" is a common bug that nobody's figured out the exact cause of, with no specific fix that works for everybody. Supposedly it's connected to a linux kernel update.

Comparing the above error to a previous example, I noticed that aside from the CPU core and the Error Addr, the errors are identical:

Sep 20 18:29:22 archlinux kernel: x86/amd: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: System Fatal error.
Sep 20 18:29:22 archlinux kernel: fbcon: Taking over console
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: CPU:3 (19:21:2) MC5_STATUS[-|UE|MiscV|AddrV|PCC|TCC|SyndV|-|-|-]: 0xbea0000001000108
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: Error Addr: 0x00006ffffbc7eaf2
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: IPID: 0x000500b000000000, Syndrome: 0x000000004d000000
Sep 20 18:29:22 archlinux kernel: 
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: Execution Unit Ext. Error Code: 0
Sep 20 18:29:22 archlinux kernel: [Hardware Error]: cache level: RESV, tx: GEN, mem-tx: GEN

Here's my system specs:

Kernel: 7.2.6-arch2-1
DE: Plasma 6.7.5
CPU: AMD Ryzen 7 5800X3D (16) @ 4.552GHz
GPU: NVIDIA GeForce RTX 4090

GPU Driver: nvidia-open-dkms 615.71.09-1

Here's a couple of relevant journals using systemd.log_level=debug:

https://paste.c-net.org/SolvedFiles - in this session I launched Palworld to reproduce the crash. (also, that URL is taunting me)
https://paste.c-net.org/BuckleAttracts - this is the session immediately afterwards, with the lag issue.

Relevant configuration files:
Both of these services launch after a 5 second timer.

[Unit]
Description=Set 5800X3D power limit

[Service]
Type=oneshot
ExecStart=python3 /usr/local/bin/ruv.py -c 8 -o -30

[Unit]
Description=Set NVIDIA power limit

[Service]
Type=oneshot
# ExecStart=/usr/bin/nvidia-smi -pl 405
ExecStart=/usr/bin/nvidia-smi -pl 450

I've tried everything here: https://wiki.archlinux.org/title/Ryzen# … k_freezing
Aside from the boot parameters, which you can see in the logs, I've done some other things:
1. I updated my BIOS. I was on F15, and it turns out there's been a bunch of improvements since then specific to my CPU.
2. I set Power Supply Idle Control to Typical Current Idle as described here. This option wasn't there before the BIOS update.
3. Doing this made some error messages appear that didn't appear before: "GPU has fallen off the bus". A bit of searching suggested this was because my GPU wasn't getting enough power, suggesting the GPU undervolt was responsible. I set the script back to the default 450.

After doing this I played Palworld for about 5 hours without any issues. I went to bed satisfied that I'd fixed it, only for everything to stop working again. That was Friday night and I've been at this all weekend.

Thanks to the good old rubber duck method I've discovered that "GPU has fallen off the bus" was showing up when I launched Palworld for that journal I posted, just as I'm about to finish typing this and go to bed. Hopefully it will help me figure it out in the morning. If anyone can put a second pair of eyes on this I'd be grateful.

mmy8x · 2026-09-21 04:40:32

ninjachicken1 wrote:

I've been experiencing the following error on my desktop:
Sep 20 22:17:47 archlinux kernel: x86/amd: Previous system reset reason [0x08000800]: an uncorrected error caused a data fabric sync flood event
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: System Fatal error.
Sep 20 22:17:47 archlinux kernel: fbcon: Taking over console
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: CPU:12 (19:21:2) MC5_STATUS[-|UE|MiscV|AddrV|PCC|TCC|SyndV|-|-|-]: 0xbea0000000000108
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: Error Addr: 0x01ffffffc2188462
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: IPID: 0x000500b000000000, Syndrome: 0x000000004d000000
Sep 20 22:17:47 archlinux kernel: 
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: Execution Unit Ext. Error Code: 0
Sep 20 22:17:47 archlinux kernel: [Hardware Error]: cache level: RESV, tx: GEN, mem-tx: GEN
It can happen randomly, sometimes within 10 minutes of turning my computer on in the morning, sometimes after a few hours. It also happens consistently after launching Palworld (fairly graphically intense game) for a few minutes.
After this happens, regardless of whether it's random or because I attempted to play Palworld, it takes a few seconds to load kernel modules on boot and 13 seconds into that the GPU is initialized and my desktop becomes extremely laggy until I turn it off and leave it a few minutes.

After what happens? My guess is that the machine reboots, then prints this error and becomes sluggish until power cycled?

Random idea: add usbcore.autosuspend=-1 boot parameter and see if it helps. There is a known HW/FW bug in AMD USB controllers which causes machines to freeze or reboot randomly.

seth · 2026-09-21 06:21:39

Journal of the previous boot ends w/ the nvidia GPU falling off the bus.
The lane before it has an mt7xxx chip which is blamed as cause/trigger by eg. https://pcforum.amd.com/s/question/0D5P … se-further and those chips have a track record for causing bus errors (typically resulting in themselves not showing up)

=> can you live w/o the wifi for a while?

That being said and wrt to #2

Sep 20 22:12:17 MetalGear (udev-worker)[527]: 6:0:0:0: sd-device-monitor(worker): Passed 313 byte to netlink monitor.
Sep 20 22:12:17 MetalGear (udev-worker)[527]: Notify message sent to '@10353203418429332851': "PROCESSED=1"
Sep 20 22:12:17 MetalGear (udev-worker)[536]: 3-3:1.2: sd-device: Created database file '/run/udev/data/+usb:3-3:1.2' for '/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-3/3-3:1.2'.
Sep 20 22:12:17 MetalGear (udev-worker)[536]: 3-3:1.2: Running built-in command "kmod load"
Sep 20 22:12:17 MetalGear (udev-worker)[536]: Loading module: usb:v045Ep02EAd0301dcFFdsc47dpD0icFFisc47ipD0in02
Sep 20 22:12:17 MetalGear (udev-worker)[551]: 3-2.3: /usr/lib/udev/rules.d/69-libmtp.rules:38 PROGRAM="/usr/lib/udev/mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}": Running command "/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-2/3-2.3 3 7"
Sep 20 22:12:17 MetalGear (udev-worker)[551]: 3-2.3: Found callout binary: "/usr/lib/udev/mtp-probe".
Sep 20 22:12:17 MetalGear (udev-worker)[551]: 3-2.3: Starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-2/3-2.3 3 7'
Sep 20 22:12:17 MetalGear (udev-worker)[566]: hidraw6: /usr/lib/udev/rules.d/60-persistent-hidraw.rules:7 IMPORT{builtin}="usb_id": Importing properties from results of builtin command "usb_id".
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: Preserve permissions of /dev/usb/hiddev4, uid=0, gid=0, mode=0600
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: Successfully created symlink '/dev/char/180:100' to '/dev/usb/hiddev4'
Sep 20 22:12:17 MetalGear (udev-worker)[543]: hiddev1: Preserve permissions of /dev/usb/hiddev1, uid=0, gid=0, mode=0600
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: sd-device: Created database file '/run/udev/data/c180:100' for '/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-4/3-4:1.2/usbmisc/hiddev4'.
Sep 20 22:12:17 MetalGear (udev-worker)[543]: hiddev1: Successfully created symlink '/dev/char/180:97' to '/dev/usb/hiddev1'
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: sd-device: Created database file '/run/udev/data/c180:100' for '/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-4/3-4:1.2/usbmisc/hiddev4'.
Sep 20 22:12:17 MetalGear kernel: ccp 0000:08:00.1: could not enable MSI-X (-22), trying MSI
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: Device processed (SEQNUM=3782, ACTION=add, UUID=256a2e88-9a2c-48d7-9d46-453da502eeca)
Sep 20 22:12:17 MetalGear kernel: ccp 0000:08:00.1: could not enable MSI (-22)
Sep 20 22:12:17 MetalGear (udev-worker)[548]: hiddev4: sd-device-monitor(worker): Passed 310 byte to netlink monitor.
Sep 20 22:12:17 MetalGear kernel: ccp 0000:08:00.1: initialization failed
Sep 20 22:12:17 MetalGear (udev-worker)[543]: hiddev1: sd-device: Created database file '/run/udev/data/c180:97' for '/devices/pci0000:00/0000:00:08.1/0000:08:00.3/usb3/3-1/3-1:1.1/usbmisc/hiddev1'.
Sep 20 22:12:17 MetalGear kernel: ccp 0000:08:00.1: probe with driver ccp failed with error -22

08:00 is one of the USBs

Sidebar: please don't use systemd.log_level=debug unless specifically asked to.
It turns the noise to signal ratio into the absurd territory.

ninjachicken1 · 2026-09-21 14:26:39

mmy8x wrote:

After what happens? My guess is that the machine reboots, then prints this error and becomes sluggish until power cycled?

You're mostly right - usually it's until I let it boot into a sluggish session, then power it off for a few minutes, and also boot into UEFI and then exit without saving for some reason.

Unfortunatley today, I had a crash happen a few minutes in (when it does crash a few minutes in, it's usually first thing in the morning after turning my computer off for the night, maybe that's a clue). That was 4 hours ago and after trying everything I usually do (including leaving my pc off for 30 minutes multiple times), I'm still lagging.

One thing I've noticed today is that my NVME temp is fluctuating wildly, and my GPU has show bursts of high VRAM usage with no apparent temperature changes.

mmy8x wrote:

Random idea: add usbcore.autosuspend=-1 boot parameter and see if it helps. There is a known HW/FW bug in AMD USB controllers which causes machines to freeze or reboot randomly.

I've tried this and my next boot went slightly smoother until I launched my browser. It might be a placebo though.

seth wrote:

can you live w/o the wifi for a while?

Yes. Could you tell me how to disable it? I'm struggling to even use Duckduckgo at the moment.

seth wrote:

Sidebar: please don't use systemd.log_level=debug unless specifically asked to.
It turns the noise to signal ratio into the absurd territory.

Sorry, I've turned it of now. Unfortunately the morning crash happened as soon as I read that sentence and reached to my keyboard to do that, so If I upload that log it was before I disabled it.

seth · 2026-09-21 17:06:38

Yes. Could you tell me how to disable it?

BIOS/UEFI settings - anything in the OS won't help if it's actually poisoning the bus.
(The alternative would then involve a screwdriver)

ninjachicken1 · 2026-09-21 20:00:07

seth wrote:

Yes. Could you tell me how to disable it?
BIOS/UEFI settings - anything in the OS won't help if it's actually poisoning the bus.
(The alternative would then involve a screwdriver)

After checking, I don't thing there's an option for that in my BIOS, and the screwdriver alternative isn't an option for me.

Today's the worst this issue's ever been. I only got two sessions that weren't sluggish, and both crashed after a short period of time. I've rolled back to a snapshot from a couple of months ago - I'm now using the linux 6.7.8-arch1-1 kernel and nvidia-dkms 535.113.01-2 driver, and things are stable again. I'm going to start by trying to upgrade my nvidia drivers without updating the kernel and see if it breaks anything.

seth · 2026-09-21 20:19:37

If it's not the HW directly and we blame the wifi chip you can just "module_blacklist=mt7921e", https://wiki.archlinux.org/title/Kernel … and_line_2

ninjachicken1 · 2026-09-28 00:46:18

I've had some life distractions pulling me away from this, but in the process of upgrading the drivers and kernel separately, getting so fed up I decided to try installing another distro on a different partition, and failing to add it to my bootloader and trying to figure out why, and then attempting and failing at switching to linux-lts as a solution, I remembered a bunch of stuff and figured out some other stuff.

When I update the drivers and not the kernel, my system slows down, and when I update the kernel without the drivers vulkan doesn't detect the GPU and I can only use my primary monitor at a low resolution.

A while back, around the time Baldurs Gate 3 was new, updating my Nvidia drivers past 535.113.01-2 was preventing my system from loading KDE, and it would hang at "Reached target Graphical Interface". Updating the kernel without the drivers also caused issues (I don't remember what, might have been the vulkan issue I mentioned). The solution I ended up settling on was to add the following packages to ignored and figure things out when I'd dealt with more pressing issues in my life:

lib32-nvidia-utils lib32-opencl-nvidia nvidia-dkms nvidia-settings nvidia-utils opencl-nvidia linux linux-firmware linux-firmware-marvell linux-firmware-whence linux-headers

Life got much worse instead of easing up until very recently, then Palworld came out and suddenly I couldn't play it with my current drivers. I forgot specifically what the problem with updating the drivers was by that point, so I unblocked those updates and switched to nvidia-open-dkms.

After figuring out it was a driver issue, and trying to figure out how to get things working on the linux-lts kernel, I started coming across information relating to nvidia drivers older than 560 and 545, which I don't think was there when I first ran into this issue. It's telling me that modeset=1 is required for drivers older than 560, and something was changed in 545?

I've unfortunately forgot most of the things I've tried because of a violent incident in my house and the aftermath (I'm safe, I'm just a witness). What I remember trying:
- https://wiki.archlinux.org/title/NVIDIA … ff_the_bus
- nvidia_drm.fbdev=1 (https://forums.linuxmint.com/viewtopic.php?t=424779)

Is there a list of things you need to do when upgrading past 535? Because from what I can tell it's not as simple as running a pacman update and there's no summary that I can find. One section of the Arch Wiki even says to just roll back the drivers like I have.

seth · 2026-09-28 06:59:42

When I update the drivers and not the kernel, my system slows down … updating my Nvidia drivers past 535.113.01-2

https://wiki.archlinux.org/title/System … nsupported
You'd have to at least use the dkms modules, otherwise they will completely fail, nouveau is blacklisted and you end up running on the simpledrm software emulation.

Check

lspci -k -d ::03xx
glxinfo -B

for a quick status oversight.

It's telling me that modeset=1 is required for drivers older than 560, and something was changed in 545?

nvidia_drm.modeset=1 is always "required" but also the default since a while.

seth wrote:

If it's not the HW directly and we blame the wifi chip you can just "module_blacklist=mt7921e", https://wiki.archlinux.org/title/Kernel … and_line_2

ninjachicken1 · 2026-09-30 02:31:34

"module_blacklist=mt7921e" doesn't work.

I've uninstalled linux-lts - aside from the fact that it's overcomplicating things, I realised I didn't have linux-lts-headers installed. With linux-lts-headers installed, linux-lts has the same issues as linux.

I also noticed that simpledrm wasn't being disabled, so I added module_blacklist=simpledrm initcall_blacklist=simpledrm_platform_driver_init. It stopped simpledrm from running, but that didn't fix anything.

This is what I got from those commands and the kernel modules loaded at the time:

rootfstype=btrfs loglevel=3 lsm=landlock,lockdown,yama,integrity,apparmor,bpf nvidia_drm.modeset=1 acpi_enforce_resources=lax amd_iommu=off module_blacklist=simpledrm initcall_blacklist=simpledrm_platform_driver_init

lspci -k -d ::03xx  
06:00.0 VGA compatible controller: NVIDIA Corporation AD102 [GeForce RTX 4090] (rev a1)  
       Subsystem: NVIDIA Corporation Device 165b  
       Kernel driver in use: nvidia  
       Kernel modules: nouveau, nvidia_drm, nvidia

glxinfo -B           
name of display: :0  
display: :0  screen: 0  
direct rendering: Yes  
Memory info (GL_NVX_gpu_memory_info):  
   Dedicated video memory: 24564 MB  
   Total available memory: 24564 MB  
   Currently available dedicated video memory: 22607 MB  
OpenGL vendor string: NVIDIA Corporation  
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2  
OpenGL core profile version string: 4.6.0 NVIDIA 615.71.09  
OpenGL core profile shading language version string: 4.60 NVIDIA  
OpenGL core profile context flags: (none)  
OpenGL core profile profile mask: core profile  
  
OpenGL version string: 4.6.0 NVIDIA 615.71.09  
OpenGL shading language version string: 4.60 NVIDIA  
OpenGL context flags: (none)  
OpenGL profile mask: (none)  
  
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 615.71.09  
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

And a journal from that session:
https://paste.c-net.org/WomenIntrigue
And the same journal with -p 3:
https://paste.c-net.org/MinusSparing

Looking at that last one, and having run grep -i "drm" on the journal, I noticed something interesting in these two lines:.

Sep 29 23:09:06 archlinux kernel: [drm] [nvidia-drm] [GPU ID 0x00000600] Loading driver
Sep 29 23:09:42 MetalGear kernel: snd_hda_intel 0000:06:00.1: no codecs initialized

0x00000600 has the same number of zeros as 0000:06:00.1, so I assume they both refer to the same thing. Not sure why it says intel when I'm using NVIDIA graphics with an AMD CPU.

Last edited by ninjachicken1 (2026-09-30 02:33:13)

seth · 2026-09-30 14:38:17

"module_blacklist=mt7921e" doesn't work … With linux-lts-headers installed, linux-lts has the same issues

So it's nvidia-open, not the mt7921e chip/module

added module_blacklist=simpledrm

Frt, that part won't do anything.

Sep 29 23:09:42 MetalGear kernel: snd_hda_intel 0000:06:00.1: GPU sound probed, but not operational: please add a quirk to driver_denylist

r/n there's actually no "data fabric sync flood event" but

Sep 29 23:10:22 MetalGear kwin_x11[1116]: Freeze in OpenGL initialization detected
Sep 29 23:10:22 MetalGear kwin_x11[1116]: Application::crashHandler() called with signal 6; recent crashes: 1
Sep 29 23:10:23 MetalGear systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully.
Sep 29 23:10:23 MetalGear kwin_x11[1116]: KCrash: Application 'kwin_x11' crashing... crashRecursionCounter = 2
Sep 29 23:10:23 MetalGear systemd-coredump[1371]: Process 1116 (kwin_x11) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Sep 29 23:10:23 MetalGear systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Sep 29 23:10:23 MetalGear systemd[1]: Created slice Slice /system/systemd-coredump.
Sep 29 23:10:23 MetalGear systemd[1]: Started Process Core Dump (PID 1371/UID 0).
Sep 29 23:10:23 MetalGear systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Sep 29 23:10:24 MetalGear kscreen_backend_launcher[1318]: XRandRCrtc  441  m_timestamp update  0  =>  83866
Sep 29 23:10:24 MetalGear kscreen_backend_launcher[1318]:         Result:  0  timestamp:  83866
Sep 29 23:10:24 MetalGear kscreen_backend_launcher[1318]: XRandROutput 445 update 
                                                                   m_connected: 0 
                                                                   m_crtc XRandRCrtc(0x5627c65299a0) 
                                                                   CRTC: 441 
                                                                   MODE: 448 
                                                                   Connection: 0
Sep 29 23:10:24 MetalGear kscreen_backend_launcher[1318]: RRSetCrtcConfig (change output) 
                                                                   Output: 487 ( "DP-2" ) 
                                                                   CRTC: 442 
                                                                   Pos: QPoint(0,2160) 
                                                                   Mode: KScreen::Mode(Id: "448" , Size: QSize(3840, 2160) @ 119.88 ) Preferred: "446" 
                                                                   Rotation: KScreen::Output::None
Sep 29 23:10:24 MetalGear systemd-coredump[1372]: Process 1116 (kwin_x11) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1146:
                                                  #0  0x00007fece509a11c n/a (libc.so.6 + 0x9a11c)
                                                  #1  0x00007fece503e5d0 raise (libc.so.6 + 0x3e5d0)
                                                  #2  0x00007fece8d72f29 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7f29)
                                                  #3  0x00007fece503e6f0 n/a (libc.so.6 + 0x3e6f0)
                                                  #4  0x00007fece509a11c n/a (libc.so.6 + 0x9a11c)
                                                  #5  0x00007fece503e5d0 raise (libc.so.6 + 0x3e5d0)
                                                  #6  0x00007fece5025685 abort (libc.so.6 + 0x25685)
                                                  #7  0x00007fece5897369 n/a (libQt6Core.so.6 + 0x97369)
                                                  #8  0x00007fece58981a1 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x981a1)
                                                  #9  0x00007fece881ba68 n/a (libkwin-x11.so.6 + 0x41ba68)
                                                  #10 0x00007fece59eeff3 n/a (libQt6Core.so.6 + 0x1eeff3)
                                                  #11 0x00007fece5a0146f _ZN6QTimer10timerEventEP11QTimerEvent (libQt6Core.so.6 + 0x20146f)
                                                  #12 0x00007fece59e6b49 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1e6b49)
                                                  #13 0x00007fece6b0325f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x10325f)
                                                  #14 0x00007fece59822b8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x1822b8)
                                                  #15 0x00007fece5b648f5 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x3648f5)
                                                  #16 0x00007fece5c9a439 n/a (libQt6Core.so.6 + 0x49a439)
                                                  #17 0x00007fece4895c76 n/a (libglib-2.0.so.0 + 0x61c76)
                                                  #18 0x00007fece4897ed7 n/a (libglib-2.0.so.0 + 0x63ed7)
                                                  #19 0x00007fece4898055 g_main_context_iteration (libglib-2.0.so.0 + 0x64055)
                                                  #20 0x00007fece5c96f32 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x496f32)
                                                  #21 0x00007fece598f664 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x18f664)
                                                  #22 0x00007fece5ab7ce2 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2b7ce2)
                                                  #23 0x00007fece5b72285 n/a (libQt6Core.so.6 + 0x372285)
                                                  #24 0x00007fece5098042 n/a (libc.so.6 + 0x98042)
                                                  #25 0x00007fece512072c n/a (libc.so.6 + 0x12072c)
                                                  
                                                  Stack trace of thread 1116:
                                                  #0  0x00007fece50a08f2 n/a (libc.so.6 + 0xa08f2)
                                                  #1  0x00007fece5094c79 n/a (libc.so.6 + 0x94c79)
                                                  #2  0x00007fece50974ec pthread_cond_wait (libc.so.6 + 0x974ec)
                                                  #3  0x00007fece8dfc986 n/a (libxcb.so.1 + 0xd986)
                                                  #4  0x00007fece8dfdba5 xcb_wait_for_reply64 (libxcb.so.1 + 0xeba5)
                                                  #5  0x00007fece7504a4e _XReply (libX11.so.6 + 0x46a4e)
                                                  #6  0x00007fecdc17c358 n/a (libGLX_nvidia.so.0 + 0xa7358)
                                                  #7  0x00007fecdc12c8ea n/a (libGLX_nvidia.so.0 + 0x578ea)
                                                  #8  0x00007fecdc17a521 n/a (libGLX_nvidia.so.0 + 0xa5521)
                                                  #9  0x00007fecdc17a928 n/a (libGLX_nvidia.so.0 + 0xa5928)
                                                  #10 0x00007fecd4fe3023 n/a (libnvidia-glcore.so.615.71.09 + 0x9e3023)
                                                  #11 0x00007fecd4fe85d1 n/a (libnvidia-glcore.so.615.71.09 + 0x9e85d1)
                                                  #12 0x00007fecd5036d67 n/a (libnvidia-glcore.so.615.71.09 + 0xa36d67)
                                                  #13 0x00007fecd4fe897c n/a (libnvidia-glcore.so.615.71.09 + 0x9e897c)
                                                  #14 0x00007fecdc129460 n/a (libGLX_nvidia.so.0 + 0x54460)
                                                  #15 0x00007fecdc157202 n/a (libGLX_nvidia.so.0 + 0x82202)
                                                  #16 0x00007fece481685f n/a (libGLX.so.0 + 0x1385f)
                                                  #17 0x00007fece4818bc9 n/a (libGLX.so.0 + 0x15bc9)
                                                  #18 0x00007fece481bc08 n/a (libGLX.so.0 + 0x18c08)
                                                  #19 0x00007fecdc758def n/a (libqxcb-glx-integration.so + 0x9def)
                                                  #20 0x00007fecdc75a961 n/a (libqxcb-glx-integration.so + 0xb961)
                                                  #21 0x00007fece65c98f2 _ZN14QOpenGLContext6createEv (libQt6Gui.so.6 + 0x5c98f2)
                                                  #22 0x00007fecdc75b9ef n/a (libqxcb-glx-integration.so + 0xc9ef)
                                                  #23 0x00007fecdc75c4ad n/a (libqxcb-glx-integration.so + 0xd4ad)
                                                  #24 0x000055a73a7f8a1c n/a (kwin_x11 + 0x3fa1c)

kwin_x11 aborts

Sep 29 23:10:22 MetalGear kwin_x11[1116]: Freeze in OpenGL initialization detected

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Does the GPU (still) respond to nvidia-smi ?

Why is this

Sep 29 23:09:43 MetalGear nvidia-smi[687]: Power limit for GPU 00000000:06:00.0 was set to 405.00 W from 450.00 W.

ninjachicken1 · 2026-10-01 02:50:26

The power limit is from the script at the start - the system got so slow and unusable I went back to an old snapshot and forgot to disable it again, my bad. I've now disabled that and the CPU power limit service.

The GPU still responds to nvidia-smi.

My Xorg log:

[    55.122] (--) Log file renamed from "/var/log/Xorg.pid-843.log" to "/var/log/Xorg.0.log"
[    55.123] 
X.Org X Server 1.21.1.24
X Protocol Version 11, Revision 0
[    55.123] Current Operating System: Linux MetalGear 7.2.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 21 Sep 2026 18:51:14 +0000 x86_64
[    55.123] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=36c932fc-4dab-44c5-9dc2-1cc17ea96c28 rw rootflags=subvol=@ rootfstype=btrfs loglevel=3 lsm=landlock,lockdown,yama,integrity,apparmor,bpf nvidia_drm.modeset=1 acpi_enforce_resources=lax amd_iommu=off module_blacklist=simpledrm initcall_blacklist=simpledrm_platform_driver_init
[    55.123]  
[    55.123] Current version of pixman: 0.46.4
[    55.123] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    55.123] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    55.123] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct  1 03:34:16 2026
[    55.124] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    55.124] (==) No Layout section.  Using the first Screen section.
[    55.124] (==) No screen section available. Using defaults.
[    55.124] (**) |-->Screen "Default Screen Section" (0)
[    55.124] (**) |   |-->Monitor "<default monitor>"
[    55.124] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    55.124] (**) Allowing byte-swapped clients
[    55.124] (==) Automatically adding devices
[    55.124] (==) Automatically enabling devices
[    55.124] (==) Automatically adding GPU devices
[    55.124] (==) Automatically binding GPU devices
[    55.124] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    55.124] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc".
[    55.124] 	Entry deleted from font path.
[    55.124] 	(Run 'mkfontdir' on "/usr/share/fonts/misc").
[    55.125] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[    55.125] 	Entry deleted from font path.
[    55.125] 	(Run 'mkfontdir' on "/usr/share/fonts/TTF").
[    55.125] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    55.125] 	Entry deleted from font path.
[    55.125] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    55.125] 	Entry deleted from font path.
[    55.125] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    55.125] 	Entry deleted from font path.
[    55.125] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    55.125] 	Entry deleted from font path.
[    55.125] (==) FontPath set to:
	
[    55.125] (==) ModulePath set to "/usr/lib/xorg/modules"
[    55.125] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    55.125] (II) Module ABI versions:
[    55.125] 	X.Org ANSI C Emulation: 0.4
[    55.125] 	X.Org Video Driver: 25.2
[    55.125] 	X.Org XInput driver : 24.4
[    55.125] 	X.Org Server Extension : 10.0
[    55.125] (++) using VT number 2

[    55.125] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    55.126] (II) xfree86: Adding drm device (/dev/dri/card0)
[    55.126] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:06:00.0/drm/card0
[    55.164] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    55.259] (--) PCI:*(6@0:0:0) 10de:2684:10de:165b rev 161, Mem @ 0xfb000000/16777216, 0xd0000000/268435456, 0xe0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[    55.259] (II) LoadModule: "glx"
[    55.259] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    55.261] (II) Module glx: vendor="X.Org Foundation"
[    55.261] 	compiled for 1.21.1.24, module version = 1.0.0
[    55.261] 	ABI class: X.Org Server Extension, version 10.0
[    55.261] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[    55.261] 	loading driver: nvidia
[    55.261] (==) Matched nvidia as autoconfigured driver 0
[    55.261] (==) Matched nouveau as autoconfigured driver 1
[    55.261] (==) Matched nv as autoconfigured driver 2
[    55.261] (==) Matched modesetting as autoconfigured driver 3
[    55.261] (==) Matched fbdev as autoconfigured driver 4
[    55.261] (==) Matched vesa as autoconfigured driver 5
[    55.261] (==) Assigned the driver to the xf86ConfigLayout
[    55.261] (II) LoadModule: "nvidia"
[    55.261] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    55.265] (II) Module nvidia: vendor="NVIDIA Corporation"
[    55.265] 	compiled for 1.16.99.901, module version = 1.0.0
[    55.265] 	Module class: X.Org Video Driver
[    55.265] (II) LoadModule: "nouveau"
[    55.265] (WW) Warning, couldn't open module nouveau
[    55.265] (EE) Failed to load module "nouveau" (module does not exist, 0)
[    55.265] (II) LoadModule: "nv"
[    55.265] (WW) Warning, couldn't open module nv
[    55.265] (EE) Failed to load module "nv" (module does not exist, 0)
[    55.265] (II) LoadModule: "modesetting"
[    55.265] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    55.266] (II) Module modesetting: vendor="X.Org Foundation"
[    55.266] 	compiled for 1.21.1.24, module version = 1.21.1
[    55.266] 	Module class: X.Org Video Driver
[    55.266] 	ABI class: X.Org Video Driver, version 25.2
[    55.266] (II) LoadModule: "fbdev"
[    55.266] (WW) Warning, couldn't open module fbdev
[    55.266] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    55.266] (II) LoadModule: "vesa"
[    55.266] (WW) Warning, couldn't open module vesa
[    55.266] (EE) Failed to load module "vesa" (module does not exist, 0)
[    55.266] (II) NVIDIA dlloader X Driver  615.71.09  Fri Sep  4 22:06:07 UTC 2026
[    55.266] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    55.266] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    55.383] (II) Loading sub module "fb"
[    55.383] (II) LoadModule: "fb"
[    55.383] (II) Module "fb" already built-in
[    55.383] (II) Loading sub module "wfb"
[    55.383] (II) LoadModule: "wfb"
[    55.383] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    55.383] (II) Module wfb: vendor="X.Org Foundation"
[    55.383] 	compiled for 1.21.1.24, module version = 1.0.0
[    55.383] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    55.406] (WW) Falling back to old probe method for modesetting
[    56.011] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    56.011] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    56.011] (==) NVIDIA(0): RGB weight 888
[    56.011] (==) NVIDIA(0): Default visual is TrueColor
[    56.011] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    56.011] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[    56.011] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    56.011] (**) NVIDIA(0): Enabling 2D acceleration
[    56.011] (II) Loading sub module "glxserver_nvidia"
[    56.011] (II) LoadModule: "glxserver_nvidia"
[    56.011] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    56.092] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    56.092] 	compiled for 1.16.99.901, module version = 1.0.0
[    56.092] 	Module class: X.Org Server Extension
[    56.092] (II) NVIDIA GLX Module  615.71.09  Fri Sep  4 22:06:07 UTC 2026
[    56.092] (II) NVIDIA: The X server supports PRIME Render Offload.
[    56.209] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:6:0:0
[    56.209] (--) NVIDIA(0):     DFP-0
[    56.209] (--) NVIDIA(0):     DFP-1
[    56.209] (--) NVIDIA(0):     DFP-2
[    56.209] (--) NVIDIA(0):     DFP-3
[    56.209] (--) NVIDIA(0):     DFP-4
[    56.209] (--) NVIDIA(0):     DFP-5 (boot)
[    56.209] (--) NVIDIA(0):     DFP-6
[    56.582] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce RTX 4090 (AD102-A) at PCI:6:0:0
[    56.582] (II) NVIDIA(0):     (GPU-0)
[    56.582] (--) NVIDIA(0): Memory: 25153536 kBytes
[    56.582] (--) NVIDIA(0): VideoBIOS: 95.02.20.00.01
[    56.582] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    57.528] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    57.528] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    57.528] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[    57.528] (--) NVIDIA(GPU-0): 
[    57.529] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): connected
[    57.529] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): Internal DisplayPort
[    57.529] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): 2670.0 MHz maximum pixel clock
[    57.529] (--) NVIDIA(GPU-0): 
[    57.579] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    57.579] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    57.579] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    57.579] (--) NVIDIA(GPU-0): 
[    57.678] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): connected
[    57.678] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): Internal DisplayPort
[    57.678] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): 2670.0 MHz maximum pixel clock
[    57.678] (--) NVIDIA(GPU-0): 
[    57.727] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    57.727] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    57.727] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[    57.727] (--) NVIDIA(GPU-0): 
[    57.826] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): connected
[    57.826] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): Internal DisplayPort
[    57.826] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): 2670.0 MHz maximum pixel clock
[    57.826] (--) NVIDIA(GPU-0): 
[    57.903] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    57.903] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[    57.903] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[    57.903] (--) NVIDIA(GPU-0): 
[    62.503] (==) NVIDIA(0): 
[    62.503] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    62.503] (==) NVIDIA(0):     will be used as the requested mode.
[    62.503] (==) NVIDIA(0): 
[    62.509] (II) NVIDIA(0): Validated MetaModes:
[    62.509] (II) NVIDIA(0):    
[    62.509] (II) NVIDIA(0):     "DFP-5:nvidia-auto-select,DFP-1:nvidia-auto-select,DFP-3:nvidia-auto-select"
[    62.509] (II) NVIDIA(0): Virtual screen size determined to be 11520 x 2160
[    65.407] (--) NVIDIA(0): DPI set to (137, 137); computed from "UseEdidDpi" X config
[    65.407] (--) NVIDIA(0):     option
[    65.407] (II) UnloadModule: "modesetting"
[    65.407] (II) Unloading modesetting
[    65.409] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    65.409] (II) NVIDIA:     access.
[    65.417] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    65.417] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    65.417] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    65.417] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    65.417] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    65.417] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    65.417] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    65.417] (II) NVIDIA(0):     Config Options in the README.
[    65.435] (II) NVIDIA(0): Setting mode "DFP-5:nvidia-auto-select,DFP-1:nvidia-auto-select,DFP-3:nvidia-auto-select"
[    66.986] (II) NVIDIA(0): Disabling shared memory pixmaps
[    66.986] (==) NVIDIA(0): Backing store enabled
[    66.986] (==) NVIDIA(0): Silken mouse enabled
[    66.986] (==) NVIDIA(0): DPMS enabled
[    66.986] (II) Loading sub module "dri2"
[    66.986] (II) LoadModule: "dri2"
[    66.986] (II) Module "dri2" already built-in
[    66.986] (II) NVIDIA(0): [DRI2] Setup complete
[    66.986] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    66.986] (II) Initializing extension Generic Event Extension
[    66.986] (II) Initializing extension SHAPE
[    66.986] (II) Initializing extension MIT-SHM
[    66.986] (II) Initializing extension XInputExtension
[    66.986] (II) Initializing extension XTEST
[    66.987] (II) Initializing extension BIG-REQUESTS
[    66.987] (II) Initializing extension SYNC
[    66.987] (II) Initializing extension XKEYBOARD
[    66.987] (II) Initializing extension XC-MISC
[    66.987] (II) Initializing extension SECURITY
[    66.987] (II) Initializing extension XFIXES
[    66.987] (II) Initializing extension RENDER
[    66.987] (II) Initializing extension RANDR
[    66.987] (II) Initializing extension COMPOSITE
[    66.987] (II) Initializing extension DAMAGE
[    66.987] (II) Initializing extension MIT-SCREEN-SAVER
[    66.987] (II) Initializing extension DOUBLE-BUFFER
[    66.987] (II) Initializing extension RECORD
[    66.987] (II) Initializing extension DPMS
[    66.987] (II) Initializing extension Present
[    66.987] (II) Initializing extension DRI3
[    66.987] (II) Initializing extension X-Resource
[    66.987] (II) Initializing extension XVideo
[    66.987] (II) Initializing extension XVideo-MotionCompensation
[    66.987] (II) Initializing extension GLX
[    66.988] (II) Initializing extension GLX
[    66.988] (II) Indirect GLX disabled.
[    66.988] (II) GLX: Another vendor is already registered for screen 0
[    66.988] (II) Initializing extension XFree86-VidModeExtension
[    66.988] (II) Initializing extension XFree86-DGA
[    66.988] (II) Initializing extension XFree86-DRI
[    66.988] (II) Initializing extension DRI2
[    66.988] (II) Initializing extension NV-GLX
[    66.988] (II) Initializing extension NV-CONTROL
[    66.988] (II) Initializing extension XINERAMA
[    67.406] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[    67.406] (II) No input driver specified, ignoring this device.
[    67.406] (II) This device may have been added with another device file.
[    67.407] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
[    67.407] (II) No input driver specified, ignoring this device.
[    67.407] (II) This device may have been added with another device file.
[    67.407] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event18)
[    67.407] (II) No input driver specified, ignoring this device.
[    67.407] (II) This device may have been added with another device file.
[    67.408] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event19)
[    67.408] (II) No input driver specified, ignoring this device.
[    67.408] (II) This device may have been added with another device file.
[    67.408] (II) config/udev: Adding input device Microsoft X-Box One S pad (/dev/input/event10)
[    67.408] (II) No input driver specified, ignoring this device.
[    67.408] (II) This device may have been added with another device file.
[    67.409] (II) config/udev: Adding input device Microsoft X-Box One S pad (/dev/input/js2)
[    67.409] (II) No input driver specified, ignoring this device.
[    67.409] (II) This device may have been added with another device file.
[    67.410] (II) config/udev: Adding input device HD-Audio Generic Rear Mic (/dev/input/event11)
[    67.410] (II) No input driver specified, ignoring this device.
[    67.410] (II) This device may have been added with another device file.
[    67.410] (II) config/udev: Adding input device HD-Audio Generic Front Mic (/dev/input/event12)
[    67.410] (II) No input driver specified, ignoring this device.
[    67.410] (II) This device may have been added with another device file.
[    67.411] (II) config/udev: Adding input device HD-Audio Generic Line (/dev/input/event13)
[    67.411] (II) No input driver specified, ignoring this device.
[    67.411] (II) This device may have been added with another device file.
[    67.411] (II) config/udev: Adding input device HD-Audio Generic Line Out (/dev/input/event14)
[    67.411] (II) No input driver specified, ignoring this device.
[    67.411] (II) This device may have been added with another device file.
[    67.411] (II) config/udev: Adding input device HD-Audio Generic Front Headphone (/dev/input/event15)
[    67.411] (II) No input driver specified, ignoring this device.
[    67.411] (II) This device may have been added with another device file.
[    67.412] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    67.412] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    67.412] (II) LoadModule: "libinput"
[    67.412] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    67.413] (II) Module libinput: vendor="X.Org Foundation"
[    67.413] 	compiled for 1.21.1.13, module version = 1.5.0
[    67.413] 	Module class: X.Org XInput Driver
[    67.413] 	ABI class: X.Org XInput driver, version 24.4
[    67.413] (II) Using input driver 'libinput' for 'Power Button'
[    67.414] (**) Power Button: always reports core events
[    67.414] (**) Option "Device" "/dev/input/event1"
[    67.417] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    67.417] (II) event1  - Power Button: device is a keyboard
[    67.417] (II) event1  - Power Button: device removed
[    67.422] (**) Option "config_info" "udev:/sys/devices/platform/LNXPWRBN:00/input/input1/event1"
[    67.422] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    67.422] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    67.422] (II) event1  - Power Button: device is a keyboard
[    67.423] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    67.423] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    67.423] (II) Using input driver 'libinput' for 'Power Button'
[    67.423] (**) Power Button: always reports core events
[    67.423] (**) Option "Device" "/dev/input/event0"
[    67.424] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    67.424] (II) event0  - Power Button: device is a keyboard
[    67.424] (II) event0  - Power Button: device removed
[    67.430] (**) Option "config_info" "udev:/sys/devices/platform/PNP0C0C:00/input/input0/event0"
[    67.430] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    67.430] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    67.430] (II) event0  - Power Button: device is a keyboard
[    67.431] (II) config/udev: Adding input device PC Speaker (/dev/input/event9)
[    67.431] (II) No input driver specified, ignoring this device.
[    67.431] (II) This device may have been added with another device file.
[    67.434] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) (/dev/input/event2)
[    67.434] (II) No input driver specified, ignoring this device.
[    67.434] (II) This device may have been added with another device file.
[    67.434] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) (/dev/input/js0)
[    67.434] (II) No input driver specified, ignoring this device.
[    67.434] (II) This device may have been added with another device file.
[    67.435] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) #2 (/dev/input/event3)
[    67.435] (II) No input driver specified, ignoring this device.
[    67.435] (II) This device may have been added with another device file.
[    67.435] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) #2 (/dev/input/js3)
[    67.435] (II) No input driver specified, ignoring this device.
[    67.435] (II) This device may have been added with another device file.
[    67.435] (II) config/udev: Adding input device ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB (/dev/input/event4)
[    67.435] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: Applying InputClass "libinput keyboard catchall"
[    67.435] (II) Using input driver 'libinput' for 'ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB'
[    67.435] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: always reports core events
[    67.435] (**) Option "Device" "/dev/input/event4"
[    67.436] (II) event4  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: is tagged by udev as: Keyboard
[    67.436] (II) event4  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: device is a keyboard
[    67.436] (II) event4  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: device removed
[    67.441] (**) Option "config_info" "udev:/sys/devices/virtual/input/input22/event4"
[    67.441] (II) XINPUT: Adding extended input device "ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB" (type: KEYBOARD, id 8)
[    67.441] (II) event4  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: is tagged by udev as: Keyboard
[    67.441] (II) event4  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vKB: device is a keyboard
[    67.442] (II) config/udev: Adding input device ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM (/dev/input/event5)
[    67.442] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: Applying InputClass "libinput pointer catchall"
[    67.442] (II) Using input driver 'libinput' for 'ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM'
[    67.442] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: always reports core events
[    67.442] (**) Option "Device" "/dev/input/event5"
[    67.442] (II) event5  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: is tagged by udev as: Mouse
[    67.442] (II) event5  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: device is a pointer
[    67.443] (II) event5  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: device removed
[    67.455] (II) libinput: ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.455] (II) libinput: ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.455] (II) libinput: ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.455] (**) Option "config_info" "udev:/sys/devices/virtual/input/input23/event5"
[    67.455] (II) XINPUT: Adding extended input device "ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM" (type: MOUSE, id 9)
[    67.455] (**) Option "AccelerationScheme" "none"
[    67.455] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: (accel) selected scheme none/0
[    67.455] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: (accel) acceleration factor: 2.000
[    67.455] (**) ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: (accel) acceleration threshold: 4
[    67.455] (II) event5  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: is tagged by udev as: Mouse
[    67.455] (II) event5  - ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM: device is a pointer
[    67.456] (II) config/udev: Adding input device ckb2: CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard vM (/dev/input/mouse0)
[    67.456] (II) No input driver specified, ignoring this device.
[    67.456] (II) This device may have been added with another device file.
[    67.456] (II) config/udev: Adding input device ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB (/dev/input/event6)
[    67.456] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: Applying InputClass "libinput keyboard catchall"
[    67.456] (II) Using input driver 'libinput' for 'ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB'
[    67.456] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: always reports core events
[    67.456] (**) Option "Device" "/dev/input/event6"
[    67.457] (II) event6  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: is tagged by udev as: Keyboard
[    67.457] (II) event6  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: device is a keyboard
[    67.457] (II) event6  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: device removed
[    67.465] (**) Option "config_info" "udev:/sys/devices/virtual/input/input24/event6"
[    67.465] (II) XINPUT: Adding extended input device "ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB" (type: KEYBOARD, id 10)
[    67.465] (II) event6  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: is tagged by udev as: Keyboard
[    67.465] (II) event6  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vKB: device is a keyboard
[    67.466] (II) config/udev: Adding input device ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM (/dev/input/event7)
[    67.466] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: Applying InputClass "libinput pointer catchall"
[    67.466] (II) Using input driver 'libinput' for 'ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM'
[    67.466] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: always reports core events
[    67.466] (**) Option "Device" "/dev/input/event7"
[    67.466] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: is tagged by udev as: Mouse
[    67.466] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: device is a pointer
[    67.467] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: device removed
[    67.478] (II) libinput: ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.478] (II) libinput: ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.478] (II) libinput: ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: Step value 0 was provided, libinput Fallback acceleration function is used.
[    67.478] (**) Option "config_info" "udev:/sys/devices/virtual/input/input25/event7"
[    67.478] (II) XINPUT: Adding extended input device "ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM" (type: MOUSE, id 11)
[    67.478] (**) Option "AccelerationScheme" "none"
[    67.478] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: (accel) selected scheme none/0
[    67.478] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: (accel) acceleration factor: 2.000
[    67.478] (**) ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: (accel) acceleration threshold: 4
[    67.478] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: is tagged by udev as: Mouse
[    67.478] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: device is a pointer
[    67.479] (II) config/udev: Adding input device ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM (/dev/input/mouse1)
[    67.479] (II) No input driver specified, ignoring this device.
[    67.479] (II) This device may have been added with another device file.
[    67.647] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) #2 (/dev/input/js3)
[    67.647] (II) No input driver specified, ignoring this device.
[    67.647] (II) This device may have been added with another device file.
[    67.648] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) (/dev/input/js0)
[    67.648] (II) No input driver specified, ignoring this device.
[    67.648] (II) This device may have been added with another device file.
[    67.652] (II) config/udev: Adding input device Microsoft X-Box One S pad (/dev/input/js2)
[    67.652] (II) No input driver specified, ignoring this device.
[    67.652] (II) This device may have been added with another device file.
[    67.673] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) #2 (/dev/input/event3)
[    67.674] (II) No input driver specified, ignoring this device.
[    67.674] (II) This device may have been added with another device file.
[    67.674] (II) config/udev: Adding input device Xbox Gamepad (userspace driver) (/dev/input/event2)
[    67.674] (II) No input driver specified, ignoring this device.
[    67.674] (II) This device may have been added with another device file.
[    67.679] (II) config/udev: Adding input device Microsoft X-Box One S pad (/dev/input/event10)
[    67.679] (II) No input driver specified, ignoring this device.
[    67.679] (II) This device may have been added with another device file.
[    69.087] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    69.088] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    69.088] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[    69.088] (--) NVIDIA(GPU-0): 
[    69.236] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): connected
[    69.236] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): Internal DisplayPort
[    69.236] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): 2670.0 MHz maximum pixel clock
[    69.236] (--) NVIDIA(GPU-0): 
[    69.287] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    69.287] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    69.287] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    69.287] (--) NVIDIA(GPU-0): 
[    69.388] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): connected
[    69.388] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): Internal DisplayPort
[    69.388] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): 2670.0 MHz maximum pixel clock
[    69.388] (--) NVIDIA(GPU-0): 
[    69.486] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    69.486] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    69.486] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[    69.486] (--) NVIDIA(GPU-0): 
[    69.537] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): connected
[    69.537] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): Internal DisplayPort
[    69.537] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): 2670.0 MHz maximum pixel clock
[    69.537] (--) NVIDIA(GPU-0): 
[    69.586] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    69.586] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[    69.586] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[    69.586] (--) NVIDIA(GPU-0): 
[    76.813] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    76.813] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    76.813] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[    76.813] (--) NVIDIA(GPU-0): 
[    77.268] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): connected
[    77.268] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): Internal DisplayPort
[    77.268] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): 2670.0 MHz maximum pixel clock
[    77.268] (--) NVIDIA(GPU-0): 
[    77.421] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    77.421] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    77.421] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    77.421] (--) NVIDIA(GPU-0): 
[    77.448] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): connected
[    77.448] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): Internal DisplayPort
[    77.448] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): 2670.0 MHz maximum pixel clock
[    77.448] (--) NVIDIA(GPU-0): 
[    77.478] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    77.478] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    77.478] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[    77.478] (--) NVIDIA(GPU-0): 
[    77.750] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): connected
[    77.750] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): Internal DisplayPort
[    77.750] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): 2670.0 MHz maximum pixel clock
[    77.750] (--) NVIDIA(GPU-0): 
[    77.776] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    77.776] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[    77.776] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[    77.776] (--) NVIDIA(GPU-0): 
[    78.360] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select @3840x2160 +0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, DP-0: 3840x2160_120 @2160x3840 +3840+480 {ViewPortIn=2160x3840, ViewPortOut=3840x2160+0+0, Rotation=90}, DP-2: nvidia-auto-select @3840x2160 +7680+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}"
[    80.512] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select @3840x2160 +0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, DP-0: 3840x2160_120 @2160x3840 +3840+480 {ViewPortIn=2160x3840, ViewPortOut=3840x2160+0+0, Rotation=90}, DP-2: 3840x2160_120 @3840x2160 +0+2160 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}"
[    82.507] (II) NVIDIA(0): Setting mode "DP-4: 3840x2160_30 @3840x2160 +0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, DP-0: 3840x2160_120 @2160x3840 +3840+480 {ViewPortIn=2160x3840, ViewPortOut=3840x2160+0+0, Rotation=90}, DP-2: 3840x2160_120 @3840x2160 +0+2160 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}"
[    89.408] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    89.408] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    89.408] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[    89.408] (--) NVIDIA(GPU-0): 
[    89.410] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): connected
[    89.410] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): Internal DisplayPort
[    89.410] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): 2670.0 MHz maximum pixel clock
[    89.410] (--) NVIDIA(GPU-0): 
[    89.483] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    89.483] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    89.483] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    89.483] (--) NVIDIA(GPU-0): 
[    89.560] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): connected
[    89.560] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): Internal DisplayPort
[    89.560] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): 2670.0 MHz maximum pixel clock
[    89.560] (--) NVIDIA(GPU-0): 
[    89.707] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    89.707] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    89.707] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[    89.707] (--) NVIDIA(GPU-0): 
[    89.708] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): connected
[    89.708] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): Internal DisplayPort
[    89.708] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): 2670.0 MHz maximum pixel clock
[    89.708] (--) NVIDIA(GPU-0): 
[    89.858] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    89.858] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[    89.858] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[    89.858] (--) NVIDIA(GPU-0): 
[   106.713] (--) NVIDIA(GPU-0): DFP-0: disconnected
[   106.713] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[   106.713] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[   106.713] (--) NVIDIA(GPU-0): 
[   106.866] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): connected
[   106.866] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): Internal DisplayPort
[   106.866] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-1): 2670.0 MHz maximum pixel clock
[   106.866] (--) NVIDIA(GPU-0): 
[   106.916] (--) NVIDIA(GPU-0): DFP-2: disconnected
[   106.916] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[   106.916] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[   106.916] (--) NVIDIA(GPU-0): 
[   107.016] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): connected
[   107.016] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): Internal DisplayPort
[   107.016] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-3): 2670.0 MHz maximum pixel clock
[   107.016] (--) NVIDIA(GPU-0): 
[   107.116] (--) NVIDIA(GPU-0): DFP-4: disconnected
[   107.116] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[   107.116] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[   107.116] (--) NVIDIA(GPU-0): 
[   107.468] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): connected
[   107.468] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): Internal DisplayPort
[   107.468] (--) NVIDIA(GPU-0): DELL G3223Q (DFP-5): 2670.0 MHz maximum pixel clock
[   107.468] (--) NVIDIA(GPU-0): 
[   107.615] (--) NVIDIA(GPU-0): DFP-6: disconnected
[   107.615] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[   107.615] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[   107.615] (--) NVIDIA(GPU-0): 
[   117.375] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   117.454] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   117.675] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   159.385] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   159.807] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   159.909] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   160.130] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   160.733] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   160.733] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   161.481] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: client bug: event processing lagging behind by 72ms, your system is too slow
[   165.456] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: client bug: event processing lagging behind by 22ms, your system is too slow
[   166.730] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: client bug: event processing lagging behind by 23ms, your system is too slow
[   169.440] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: client bug: event processing lagging behind by 88ms, your system is too slow
[   195.749] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   195.951] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   196.048] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   196.786] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   196.986] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   196.986] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   199.584] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: client bug: event processing lagging behind by 71ms, your system is too slow
[   199.584] (EE) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
[   289.305] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   327.149] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   327.822] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   327.975] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   328.523] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   394.913] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   395.064] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   396.412] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   396.563] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   396.711] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   396.711] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   424.964] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   425.137] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   427.547] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   427.696] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   428.442] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   428.442] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   469.472] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   482.219] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   482.367] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   482.972] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   489.401] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   489.401] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   512.518] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   512.596] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   512.818] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   513.418] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   513.570] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   513.570] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   665.560] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   666.461] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   666.779] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   666.880] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   667.840] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   667.840] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   786.070] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   792.381] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   792.456] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   861.799] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   861.922] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   862.049] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   862.098] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   862.852] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   862.852] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   892.088] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   894.037] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   894.192] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   894.722] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   894.874] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   894.874] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.
[   933.767] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   934.066] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   934.518] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   934.616] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   934.817] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: SYN_DROPPED event - some input events have been lost.
[   934.817] (II) event7  - ckb1: CORSAIR SCIMITAR RGB ELITE Gaming Mouse vM: WARNING: log rate limit exceeded (5 msgs per 30s). Discarding future messages.

Last edited by ninjachicken1 (2026-10-01 02:51:15)

seth · 2026-10-01 08:55:53

Log file: "/var/log/Xorg.0.log", Time: Thu Oct 1 03:34:16 2026
7.2.7-arch1-1 + NVIDIA GLX Module 615.71.09

GLX is fine in that log but it also is already running for ~15 minutes.
I assume it doesn't reflect a boot like in #10 where kwin crashed right away?

the system got so slow and unusable I went back to an old snapshot

So w/ the configuration of that journal X11/glx apparently didn't work at all and the Xorg log you posted seems like you upgraded the system again?
Please try to avoid operating on a moving target, focus on the fully updated system.

Do you currently experience
* the data fabric sync flood event hardware errors?
* a "slow and unusable" system?
* steam crashes of other nature (w/o spurious reboots etc)?

ninjachicken1 · 2026-10-01 13:53:38

Yes, that was a boot where kwin crashed. Here is the journal: https://paste.c-net.org/EdwardDented

Unfortunately I'm not in a position in my life where I can go without a working system for a long period of time.

* I haven't had a random data fabric sync flood event hardware error for a while. These normally happened during boots where the system was running as normal, but those don't happen anymore.
* The system is now always slow and unusable when fully updated - I don't get boots where kwin doesn't crash anymore.
* Because the system is so slow, I haven't tried running Steam for a while.

seth · 2026-10-01 14:04:28

Sep 30 22:32:00 MetalGear kwin_x11[1068]: Freeze in OpenGL initialization detected
Sep 30 22:32:00 MetalGear kwin_x11[1068]: Application::crashHandler() called with signal 6; recent crashes: 1
Sep 30 22:32:01 MetalGear kwin_x11[1068]: KCrash: Application 'kwin_x11' crashing... crashRecursionCounter = 2
Sep 30 22:32:01 MetalGear systemd-coredump[1338]: Process 1068 (kwin_x11) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Sep 30 22:32:02 MetalGear systemd-coredump[1339]: Process 1068 (kwin_x11) of user 1000 dumped core.
                                                  #27 0x000055c370876a1c n/a (kwin_x11 + 0x3fa1c)
                                                  #41 0x000055c37086e38b n/a (kwin_x11 + 0x3738b)
                                                  #44 0x000055c370871d45 n/a (kwin_x11 + 0x3ad45)
Sep 30 22:32:02 MetalGear drkonqi-coredump-processor[1340]: "/usr/bin/kwin_x11" 1068 "/var/lib/systemd/coredump/core.kwin_x11.1000.916f1143c0104da0850f03fa1f88f92e.1068.1790803921000000.zst"
Sep 30 22:32:04 MetalGear systemd[993]: plasma-kwin_x11.service: Main process exited, code=dumped, status=6/ABRT
Sep 30 22:32:04 MetalGear systemd[993]: plasma-kwin_x11.service: Failed with result 'core-dump'.
Sep 30 22:32:04 MetalGear systemd[993]: plasma-kwin_x11.service: Consumed 1.716s CPU time over 19.968s wall clock time, 50.8M memory peak.
Sep 30 22:32:04 MetalGear systemd[993]: plasma-kwin_x11.service: Scheduled restart job, restart counter is at 1.
Sep 30 22:32:06 MetalGear drkonqi-coredump-launcher[1349]: KCrash metadata not marked complete. Please file a bug at bugs.kde.org giving as much detail about the crash as possible and maybe include the file "/home/ben/.cache/kcrash-metadata/kwin_x11.916f1143c0104da0850f03fa1f88f92e.1068.ini"
Sep 30 22:32:25 MetalGear kwin_x11[1352]: Compositing disabled: video driver seems unstable. If you think it's a false positive, please try again in a few minutes.
Sep 30 22:32:25 MetalGear kwin_x11[1352]: Compositing is not possible

So it seems kwin_x11 initially crashes/aborts w/ a "GL freeze" of sorts, then disables compositing and then runs uncomposited but w/o abort.

At that point

glxinfo -B
eglinfo -B
glxgears # this will run forever, but the behavior and output after 30s or so is interesting
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/ for the last one

Also try to run the session on a single monitor.

Virtual screen size determined to be 11520 x 2160

I'd rather expect boundaries at 16k than 8k but who knows.
Also this could be a VRR related problem

ninjachicken1 · 2026-10-01 15:39:42

Disabled all monitors in KDE Display Configuration but one. Refresh rate is set to 119.88 Hz. Rebooted after applying these settings, but before running these commands:

glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24564 MB
    Total available memory: 24564 MB
    Currently available dedicated video memory: 23499 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 615.71.09
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

eglinfo -B                                                                                       
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.2.3-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.2.3-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.2.3-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

glxgears # this will run forever, but the behavior and output after 30s or so is interesting     
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
221 frames in 5.0 seconds = 44.135 FPS
600 frames in 5.0 seconds = 119.891 FPS
600 frames in 5.0 seconds = 119.876 FPS
600 frames in 5.0 seconds = 119.918 FPS
600 frames in 5.0 seconds = 119.892 FPS
600 frames in 5.0 seconds = 119.903 FPS
600 frames in 5.0 seconds = 119.892 FPS
600 frames in 5.0 seconds = 119.892 FPS
600 frames in 5.0 seconds = 119.886 FPS
600 frames in 5.0 seconds = 119.862 FPS

glxgears was left on for about 7 minutes, didn't copy all of it, only the first result stands out.

seth · 2026-10-01 16:20:30

only the first result stands out

Yup.

seth wrote:

Also try to run the session on a single monitor.

Also

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

ninjachicken1 · 2026-10-01 17:23:06

I ran the glxgears command you gave me again after rebooting, while my browser was loading. Check this out:

glxgears # this will run forever, but the behavior and output after 30s or so is interesting
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
46 frames in 5.0 seconds =  9.163 FPS
39 frames in 5.1 seconds =  7.654 FPS
49 frames in 5.1 seconds =  9.598 FPS
47 frames in 5.1 seconds =  9.217 FPS
52 frames in 5.1 seconds = 10.198 FPS
48 frames in 5.1 seconds =  9.391 FPS
51 frames in 5.1 seconds = 10.004 FPS
55 frames in 5.1 seconds = 10.787 FPS
53 frames in 5.1 seconds = 10.395 FPS
47 frames in 5.1 seconds =  9.217 FPS
44 frames in 5.1 seconds =  8.631 FPS
51 frames in 5.1 seconds = 10.003 FPS
50 frames in 5.1 seconds =  9.806 FPS
50 frames in 5.1 seconds =  9.805 FPS
45 frames in 5.1 seconds =  8.826 FPS
47 frames in 5.1 seconds =  9.218 FPS
50 frames in 5.1 seconds =  9.806 FPS
49 frames in 5.1 seconds =  9.610 FPS
55 frames in 5.1 seconds = 10.791 FPS
50 frames in 5.1 seconds =  9.807 FPS
46 frames in 5.1 seconds =  9.008 FPS
51 frames in 5.1 seconds =  9.941 FPS
49 frames in 5.1 seconds =  9.611 FPS
60 frames in 5.1 seconds = 11.654 FPS
55 frames in 5.1 seconds = 10.762 FPS
44 frames in 5.1 seconds =  8.632 FPS
49 frames in 5.1 seconds =  9.611 FPS
57 frames in 5.0 seconds = 11.342 FPS
53 frames in 5.0 seconds = 10.560 FPS
51 frames in 5.1 seconds = 10.001 FPS
47 frames in 5.1 seconds =  9.217 FPS
44 frames in 5.1 seconds =  8.633 FPS
57 frames in 5.1 seconds = 11.177 FPS
55 frames in 5.1 seconds = 10.788 FPS
46 frames in 5.1 seconds =  9.023 FPS
40 frames in 5.1 seconds =  7.852 FPS
48 frames in 5.1 seconds =  9.416 FPS
28 frames in 5.1 seconds =  5.457 FPS
40 frames in 5.1 seconds =  7.848 FPS
38 frames in 5.0 seconds =  7.592 FPS
50 frames in 5.1 seconds =  9.808 FPS
44 frames in 5.1 seconds =  8.630 FPS
51 frames in 5.1 seconds = 10.004 FPS
59 frames in 5.0 seconds = 11.710 FPS
49 frames in 5.1 seconds =  9.612 FPS
52 frames in 5.1 seconds = 10.200 FPS
51 frames in 5.1 seconds = 10.051 FPS
45 frames in 5.1 seconds =  8.781 FPS
43 frames in 5.1 seconds =  8.436 FPS
53 frames in 5.1 seconds = 10.396 FPS
58 frames in 5.1 seconds = 11.376 FPS
46 frames in 5.1 seconds =  9.006 FPS
47 frames in 5.1 seconds =  9.216 FPS
47 frames in 5.1 seconds =  9.222 FPS
52 frames in 5.0 seconds = 10.348 FPS
51 frames in 5.0 seconds = 10.149 FPS
44 frames in 5.1 seconds =  8.640 FPS
47 frames in 5.1 seconds =  9.218 FPS
50 frames in 5.1 seconds =  9.806 FPS
56 frames in 5.1 seconds = 10.985 FPS
52 frames in 5.1 seconds = 10.200 FPS
54 frames in 5.1 seconds = 10.594 FPS
47 frames in 5.1 seconds =  9.219 FPS
49 frames in 5.1 seconds =  9.611 FPS
65 frames in 5.1 seconds = 12.721 FPS
50 frames in 5.1 seconds =  9.808 FPS
40 frames in 5.1 seconds =  7.846 FPS
^C
glxgears  31.25s user 0.75s system 9% cpu 5:43.03 total

Figured I'd run the other two in case they're relevant as well:

eglinfo -B                                                                                       
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.2.3-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.2.3-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.2.3-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

glxinfo -B                                                                                  
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24564 MB
    Total available memory: 24564 MB
    Currently available dedicated video memory: 22281 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 615.71.09
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I'm now realising

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

wasn't part of the previous line.

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
/sys/class/drm/card0
/sys/class/drm/card0/edid: No such file or directory
=================
/sys/class/drm/card0-DP-1
edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac 8c 42 55 32 30 37
13 21 01 04 b5 47 28 78 3b 1e 75 af 4f 42 a7 24
0f 50 54 a5 4b 00 71 4f 81 00 81 80 a9 40 b3 00
d1 c0 d1 00 a9 c0 4d d0 00 a0 f0 70 3e 80 30 20
35 00 c4 8f 21 00 00 1a 00 00 00 ff 00 32 58 4d
31 34 50 33 0a 20 20 20 20 20 00 00 00 fc 00 44
45 4c 4c 20 47 33 32 32 33 51 0a 20 00 00 00 fd
0c 30 90 50 50 86 01 0a 20 20 20 20 20 20 02 b9

02 03 3a f1 51 61 60 76 75 10 1f 3f 40 5f 5e 5d
22 21 04 12 03 01 23 09 07 07 83 01 00 00 6d 1a
00 00 02 0b 30 90 00 04 73 14 73 2f e2 00 d5 e3
05 c3 01 e6 06 05 01 73 73 21 86 6f 80 a0 70 38
40 40 30 20 35 00 c4 8f 21 00 00 1a 6f c2 00 a0
a0 a0 55 50 30 20 35 00 c4 8f 21 00 00 1a 56 5e
00 a0 a0 a0 29 50 30 20 35 00 c4 8f 21 00 00 1a
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da

70 12 79 03 00 03 01 50 47 e8 01 04 ff 0e 4f 00
07 80 1f 00 6f 08 36 00 28 00 07 00 d0 a3 01 04
ff 0e 4f 00 07 80 1f 00 6f 08 7e 00 70 00 07 00
fa e6 00 04 ff 09 9f 00 4f 80 1f 00 9f 05 45 00
3d 00 04 00 59 87 00 04 7f 07 9f 00 2f 80 1f 00
37 04 4c 00 02 00 04 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 90

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: DEL
    Model: 17036
    Serial Number: 925905493 (0x37303255)
    Made in: week 19 of 2023
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 71 cm x 40 cm
    Gamma: 2.20
    DPMS levels: Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6835, 0.3095
    Green: 0.2607, 0.6542
    Blue : 0.1416, 0.0615
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x1c:  1280x800    59.810326 Hz  16:10    49.702 kHz     83.500000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    DMT 0x45:  1920x1200   59.884600 Hz  16:10    74.556 kHz    193.250000 MHz
    DMT 0x53:  1600x900    60.000000 Hz  16:9     60.000 kHz    108.000000 MHz (RB)
  Detailed Timing Descriptors:
    DTD 1:  3840x2160   59.996625 Hz  16:9    133.312 kHz    533.250000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   54 Vpol N
    Display Product Serial Number: '2XM14P3'
    Display Product Name: 'DELL G3223Q'
    Display Range Limits:
      Monitor ranges (Range Limits Only): 48-144 Hz V, 335-335 kHz H, max dotclock 1340 MHz
  Extension blocks: 2
Checksum: 0xb9

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
    VIC 118:  3840x2160  120.000000 Hz  16:9    270.000 kHz   1188.000000 MHz
    VIC 117:  3840x2160  100.000000 Hz  16:9    225.000 kHz   1188.000000 MHz
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC  63:  1920x1080  120.000000 Hz  16:9    135.000 kHz    297.000000 MHz
    VIC  64:  1920x1080  100.000000 Hz  16:9    112.500 kHz    297.000000 MHz
    VIC  95:  3840x2160   30.000000 Hz  16:9     67.500 kHz    297.000000 MHz
    VIC  94:  3840x2160   25.000000 Hz  16:9     56.250 kHz    297.000000 MHz
    VIC  93:  3840x2160   24.000000 Hz  16:9     54.000 kHz    297.000000 MHz
    VIC  34:  1920x1080   30.000000 Hz  16:9     33.750 kHz     74.250000 MHz
    VIC  33:  1920x1080   25.000000 Hz  16:9     28.125 kHz     74.250000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC   1:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2
    Feature Caps: 0x0b
    Minimum Refresh Rate: 48 Hz
    Maximum Refresh Rate: 144 Hz
    Flags 1.x: 0x00
    Flags 2.x: 0x04
    Maximum luminance: 115 (603.666 cd/m^2)
    Minimum luminance: 20 (0.037 cd/m^2)
    Maximum luminance (without local dimming): 115 (603.666 cd/m^2)
    Minimum luminance (without local dimming): 47 (0.205 cd/m^2)
  Video Capability Data Block:
    YCbCr quantization: Selectable (via AVI YQ)
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: Always Overscanned
    IT scan behavior: Always Overscanned
    CE scan behavior: Always Overscanned
  Colorimetry Data Block:
    xvYCC601
    xvYCC709
    BT2020YCC
    BT2020RGB
    Gamut Boundary Description Metadata Profile P0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 115 (603.666 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 33 (0.101 cd/m^2)
  Detailed Timing Descriptors:
    DTD 2:  1920x1080  119.982181 Hz  16:9    137.260 kHz    285.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   56 Vpol N
    DTD 3:  2560x1440  119.997589 Hz  16:9    182.996 kHz    497.750000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   77 Vpol N
    DTD 4:  2560x1440   59.950550 Hz  16:9     88.787 kHz    241.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   33 Vpol N
Checksum: 0xda  Unused space in Extension Block: 15 bytes

----------------

Block 2, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Standalone display device
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  3840x2160  143.962777 Hz  16:9    318.878 kHz   1250.000000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront   41 Vsync   8 Vback    6 Vpol N
    DTD:  3840x2160  119.880112 Hz  16:9    274.166 kHz   1074.730000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront  113 Vsync   8 Vback    6 Vpol N
    DTD:  2560x1440  143.969127 Hz  16:9    217.393 kHz    591.310000 MHz (aspect 16:9, no 3D stereo)
               Hfront   80 Hsync  32 Hback   48 Hpol P
               Vfront   62 Vsync   5 Vback    3 Vpol N
    DTD:  1920x1080  143.981451 Hz  16:9    166.587 kHz    346.500000 MHz (aspect 16:9, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync   5 Vback   69 Vpol N
  Checksum: 0x1f
Checksum: 0x90
=================
/sys/class/drm/card0-DP-2
edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac 8c 42 55 39 31 37
13 21 01 04 b5 47 28 78 3b 1e 75 af 4f 42 a7 24
0f 50 54 a5 4b 00 71 4f 81 00 81 80 a9 40 b3 00
d1 c0 d1 00 a9 c0 4d d0 00 a0 f0 70 3e 80 30 20
35 00 c4 8f 21 00 00 1a 00 00 00 ff 00 33 59 4d
31 34 50 33 0a 20 20 20 20 20 00 00 00 fc 00 44
45 4c 4c 20 47 33 32 32 33 51 0a 20 00 00 00 fd
0c 30 90 50 50 86 01 0a 20 20 20 20 20 20 02 af

02 03 3a f1 51 61 60 76 75 10 1f 3f 40 5f 5e 5d
22 21 04 12 03 01 23 09 07 07 83 01 00 00 6d 1a
00 00 02 0b 30 90 00 04 73 14 73 2f e2 00 d5 e3
05 c3 01 e6 06 05 01 73 73 21 86 6f 80 a0 70 38
40 40 30 20 35 00 c4 8f 21 00 00 1a 6f c2 00 a0
a0 a0 55 50 30 20 35 00 c4 8f 21 00 00 1a 56 5e
00 a0 a0 a0 29 50 30 20 35 00 c4 8f 21 00 00 1a
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da

70 12 79 03 00 03 01 50 47 e8 01 04 ff 0e 4f 00
07 80 1f 00 6f 08 36 00 28 00 07 00 d0 a3 01 04
ff 0e 4f 00 07 80 1f 00 6f 08 7e 00 70 00 07 00
fa e6 00 04 ff 09 9f 00 4f 80 1f 00 9f 05 45 00
3d 00 04 00 59 87 00 04 7f 07 9f 00 2f 80 1f 00
37 04 4c 00 02 00 04 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 90

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: DEL
    Model: 17036
    Serial Number: 925972821 (0x37313955)
    Made in: week 19 of 2023
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 71 cm x 40 cm
    Gamma: 2.20
    DPMS levels: Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6835, 0.3095
    Green: 0.2607, 0.6542
    Blue : 0.1416, 0.0615
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x1c:  1280x800    59.810326 Hz  16:10    49.702 kHz     83.500000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    DMT 0x45:  1920x1200   59.884600 Hz  16:10    74.556 kHz    193.250000 MHz
    DMT 0x53:  1600x900    60.000000 Hz  16:9     60.000 kHz    108.000000 MHz (RB)
  Detailed Timing Descriptors:
    DTD 1:  3840x2160   59.996625 Hz  16:9    133.312 kHz    533.250000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   54 Vpol N
    Display Product Serial Number: '3YM14P3'
    Display Product Name: 'DELL G3223Q'
    Display Range Limits:
      Monitor ranges (Range Limits Only): 48-144 Hz V, 335-335 kHz H, max dotclock 1340 MHz
  Extension blocks: 2
Checksum: 0xaf

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
    VIC 118:  3840x2160  120.000000 Hz  16:9    270.000 kHz   1188.000000 MHz
    VIC 117:  3840x2160  100.000000 Hz  16:9    225.000 kHz   1188.000000 MHz
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC  63:  1920x1080  120.000000 Hz  16:9    135.000 kHz    297.000000 MHz
    VIC  64:  1920x1080  100.000000 Hz  16:9    112.500 kHz    297.000000 MHz
    VIC  95:  3840x2160   30.000000 Hz  16:9     67.500 kHz    297.000000 MHz
    VIC  94:  3840x2160   25.000000 Hz  16:9     56.250 kHz    297.000000 MHz
    VIC  93:  3840x2160   24.000000 Hz  16:9     54.000 kHz    297.000000 MHz
    VIC  34:  1920x1080   30.000000 Hz  16:9     33.750 kHz     74.250000 MHz
    VIC  33:  1920x1080   25.000000 Hz  16:9     28.125 kHz     74.250000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC   1:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2
    Feature Caps: 0x0b
    Minimum Refresh Rate: 48 Hz
    Maximum Refresh Rate: 144 Hz
    Flags 1.x: 0x00
    Flags 2.x: 0x04
    Maximum luminance: 115 (603.666 cd/m^2)
    Minimum luminance: 20 (0.037 cd/m^2)
    Maximum luminance (without local dimming): 115 (603.666 cd/m^2)
    Minimum luminance (without local dimming): 47 (0.205 cd/m^2)
  Video Capability Data Block:
    YCbCr quantization: Selectable (via AVI YQ)
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: Always Overscanned
    IT scan behavior: Always Overscanned
    CE scan behavior: Always Overscanned
  Colorimetry Data Block:
    xvYCC601
    xvYCC709
    BT2020YCC
    BT2020RGB
    Gamut Boundary Description Metadata Profile P0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 115 (603.666 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 33 (0.101 cd/m^2)
  Detailed Timing Descriptors:
    DTD 2:  1920x1080  119.982181 Hz  16:9    137.260 kHz    285.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   56 Vpol N
    DTD 3:  2560x1440  119.997589 Hz  16:9    182.996 kHz    497.750000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   77 Vpol N
    DTD 4:  2560x1440   59.950550 Hz  16:9     88.787 kHz    241.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   33 Vpol N
Checksum: 0xda  Unused space in Extension Block: 15 bytes

----------------

Block 2, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Standalone display device
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  3840x2160  143.962777 Hz  16:9    318.878 kHz   1250.000000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront   41 Vsync   8 Vback    6 Vpol N
    DTD:  3840x2160  119.880112 Hz  16:9    274.166 kHz   1074.730000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront  113 Vsync   8 Vback    6 Vpol N
    DTD:  2560x1440  143.969127 Hz  16:9    217.393 kHz    591.310000 MHz (aspect 16:9, no 3D stereo)
               Hfront   80 Hsync  32 Hback   48 Hpol P
               Vfront   62 Vsync   5 Vback    3 Vpol N
    DTD:  1920x1080  143.981451 Hz  16:9    166.587 kHz    346.500000 MHz (aspect 16:9, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync   5 Vback   69 Vpol N
  Checksum: 0x1f
Checksum: 0x90
=================
/sys/class/drm/card0-DP-3
edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac 8c 42 55 32 30 30
34 20 01 04 b5 47 28 78 3b 1e 75 af 4f 42 a7 24
0f 50 54 a5 4b 00 71 4f 81 00 81 80 a9 40 b3 00
d1 c0 d1 00 a9 c0 4d d0 00 a0 f0 70 3e 80 30 20
35 00 c4 8f 21 00 00 1a 00 00 00 ff 00 46 33 48
53 30 50 33 0a 20 20 20 20 20 00 00 00 fc 00 44
45 4c 4c 20 47 33 32 32 33 51 0a 20 00 00 00 fd
0c 30 90 50 50 86 01 0a 20 20 20 20 20 20 02 98

02 03 3a f1 51 61 60 76 75 10 1f 3f 40 5f 5e 5d
22 21 04 12 03 01 23 09 07 07 83 01 00 00 6d 1a
00 00 02 0b 30 90 00 04 73 14 73 2f e2 00 d5 e3
05 c3 01 e6 06 05 01 73 73 21 86 6f 80 a0 70 38
40 40 30 20 35 00 c4 8f 21 00 00 1a 6f c2 00 a0
a0 a0 55 50 30 20 35 00 c4 8f 21 00 00 1a 56 5e
00 a0 a0 a0 29 50 30 20 35 00 c4 8f 21 00 00 1a
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da

70 12 79 03 00 03 01 50 47 e8 01 04 ff 0e 4f 00
07 80 1f 00 6f 08 36 00 28 00 07 00 d0 a3 01 04
ff 0e 4f 00 07 80 1f 00 6f 08 7e 00 70 00 07 00
fa e6 00 04 ff 09 9f 00 4f 80 1f 00 9f 05 45 00
3d 00 04 00 59 87 00 04 7f 07 9f 00 2f 80 1f 00
37 04 4c 00 02 00 04 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 90

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: DEL
    Model: 17036
    Serial Number: 808464981 (0x30303255)
    Made in: week 52 of 2022
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 71 cm x 40 cm
    Gamma: 2.20
    DPMS levels: Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6835, 0.3095
    Green: 0.2607, 0.6542
    Blue : 0.1416, 0.0615
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x1c:  1280x800    59.810326 Hz  16:10    49.702 kHz     83.500000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    DMT 0x45:  1920x1200   59.884600 Hz  16:10    74.556 kHz    193.250000 MHz
    DMT 0x53:  1600x900    60.000000 Hz  16:9     60.000 kHz    108.000000 MHz (RB)
  Detailed Timing Descriptors:
    DTD 1:  3840x2160   59.996625 Hz  16:9    133.312 kHz    533.250000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   54 Vpol N
    Display Product Serial Number: 'F3HS0P3'
    Display Product Name: 'DELL G3223Q'
    Display Range Limits:
      Monitor ranges (Range Limits Only): 48-144 Hz V, 335-335 kHz H, max dotclock 1340 MHz
  Extension blocks: 2
Checksum: 0x98

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
    VIC 118:  3840x2160  120.000000 Hz  16:9    270.000 kHz   1188.000000 MHz
    VIC 117:  3840x2160  100.000000 Hz  16:9    225.000 kHz   1188.000000 MHz
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC  63:  1920x1080  120.000000 Hz  16:9    135.000 kHz    297.000000 MHz
    VIC  64:  1920x1080  100.000000 Hz  16:9    112.500 kHz    297.000000 MHz
    VIC  95:  3840x2160   30.000000 Hz  16:9     67.500 kHz    297.000000 MHz
    VIC  94:  3840x2160   25.000000 Hz  16:9     56.250 kHz    297.000000 MHz
    VIC  93:  3840x2160   24.000000 Hz  16:9     54.000 kHz    297.000000 MHz
    VIC  34:  1920x1080   30.000000 Hz  16:9     33.750 kHz     74.250000 MHz
    VIC  33:  1920x1080   25.000000 Hz  16:9     28.125 kHz     74.250000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC   1:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2
    Feature Caps: 0x0b
    Minimum Refresh Rate: 48 Hz
    Maximum Refresh Rate: 144 Hz
    Flags 1.x: 0x00
    Flags 2.x: 0x04
    Maximum luminance: 115 (603.666 cd/m^2)
    Minimum luminance: 20 (0.037 cd/m^2)
    Maximum luminance (without local dimming): 115 (603.666 cd/m^2)
    Minimum luminance (without local dimming): 47 (0.205 cd/m^2)
  Video Capability Data Block:
    YCbCr quantization: Selectable (via AVI YQ)
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: Always Overscanned
    IT scan behavior: Always Overscanned
    CE scan behavior: Always Overscanned
  Colorimetry Data Block:
    xvYCC601
    xvYCC709
    BT2020YCC
    BT2020RGB
    Gamut Boundary Description Metadata Profile P0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 115 (603.666 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 33 (0.101 cd/m^2)
  Detailed Timing Descriptors:
    DTD 2:  1920x1080  119.982181 Hz  16:9    137.260 kHz    285.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   56 Vpol N
    DTD 3:  2560x1440  119.997589 Hz  16:9    182.996 kHz    497.750000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   77 Vpol N
    DTD 4:  2560x1440   59.950550 Hz  16:9     88.787 kHz    241.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   33 Vpol N
Checksum: 0xda  Unused space in Extension Block: 15 bytes

----------------

Block 2, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Standalone display device
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  3840x2160  143.962777 Hz  16:9    318.878 kHz   1250.000000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront   41 Vsync   8 Vback    6 Vpol N
    DTD:  3840x2160  119.880112 Hz  16:9    274.166 kHz   1074.730000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront  113 Vsync   8 Vback    6 Vpol N
    DTD:  2560x1440  143.969127 Hz  16:9    217.393 kHz    591.310000 MHz (aspect 16:9, no 3D stereo)
               Hfront   80 Hsync  32 Hback   48 Hpol P
               Vfront   62 Vsync   5 Vback    3 Vpol N
    DTD:  1920x1080  143.981451 Hz  16:9    166.587 kHz    346.500000 MHz (aspect 16:9, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync   5 Vback   69 Vpol N
  Checksum: 0x1f
Checksum: 0x90
=================
/sys/class/drm/card0-HDMI-A-1
EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty.
=================

seth wrote:

Also try to run the session on a single monitor.

Is that not what I'm doing when I disabled the other monitors in KDE Display and Configuration?

ninjachicken1 · 2026-10-01 17:33:29

Another glxgears from after my last post, when I noticed the framerate was improving:

glxgears # this will run forever, but the behavior and output after 30s or so is interesting        
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
46 frames in 5.1 seconds =  9.025 FPS
42 frames in 5.1 seconds =  8.240 FPS
36 frames in 5.1 seconds =  7.059 FPS
568 frames in 5.0 seconds = 113.494 FPS
598 frames in 5.0 seconds = 119.483 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.882 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.880 FPS
598 frames in 5.0 seconds = 119.481 FPS
598 frames in 5.0 seconds = 119.481 FPS

seth · 2026-10-01 20:35:20

Is that not what I'm doing when I disabled the other monitors in KDE Display and Configuration?

Does "xrandr -q" say they're disabled?
Also

xwininfo -root | grep geometry

reports 3840x2160 ?

    Display supports continuous frequencies
    Display supports continuous frequencies
    Display supports continuous frequencies

Can you disable that in the monitor OSDs?

ninjachicken1 · 2026-10-03 02:43:32

seth wrote:

Does "xrandr -q" say they're disabled?

Nope. I've now physically unplugged the displayport cables from the other two monitors. Is there a way to disable them through linux without unplugging them?

seth wrote:

Also
xwininfo -root | grep geometry
reports 3840x2160 ?

Yes. It did so before and after unplugging the monitors.

seth wrote:

    Display supports continuous frequencies
    Display supports continuous frequencies
    Display supports continuous frequencies

Can you disable that in the monitor OSDs?

I have no idea what that means or what it might be called in my monitor OSDs. Duckduckgo hasn't been helpful in figuring that out.

Here's everything you asked for again now that I've unplugged the other monitors, except glxgears, which will be in my next post after a reboot.

glxinfo -B                                                                                       
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24564 MB
    Total available memory: 24564 MB
    Currently available dedicated video memory: 22968 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 615.71.09
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 615.71.09
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 615.71.09
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 615.71.09
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
pci id for fd 38: 10de:2684, driver (null)
pci id for fd 39: 10de:2684, driver (null)
MESA-EGL: warning: egl: failed to create dri2 screen
MESA-EGL: warning: pci id for fd 26: 10de:2684, driver (null)
eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.2.4-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.2.4-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.2.4-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

eglinfo -B  0.92s user 5.17s system 78% cpu 7.757 total

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
/sys/class/drm/card0
/sys/class/drm/card0/edid: No such file or directory
=================
/sys/class/drm/card0-DP-1
EDID of '/sys/class/drm/card0-DP-1/edid' was empty.
=================
/sys/class/drm/card0-DP-2
edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac 8c 42 55 39 31 37
13 21 01 04 b5 47 28 78 3b 1e 75 af 4f 42 a7 24
0f 50 54 a5 4b 00 71 4f 81 00 81 80 a9 40 b3 00
d1 c0 d1 00 a9 c0 4d d0 00 a0 f0 70 3e 80 30 20
35 00 c4 8f 21 00 00 1a 00 00 00 ff 00 33 59 4d
31 34 50 33 0a 20 20 20 20 20 00 00 00 fc 00 44
45 4c 4c 20 47 33 32 32 33 51 0a 20 00 00 00 fd
0c 30 90 50 50 86 01 0a 20 20 20 20 20 20 02 af

02 03 3a f1 51 61 60 76 75 10 1f 3f 40 5f 5e 5d
22 21 04 12 03 01 23 09 07 07 83 01 00 00 6d 1a
00 00 02 0b 30 90 00 04 73 14 73 2f e2 00 d5 e3
05 c3 01 e6 06 05 01 73 73 21 86 6f 80 a0 70 38
40 40 30 20 35 00 c4 8f 21 00 00 1a 6f c2 00 a0
a0 a0 55 50 30 20 35 00 c4 8f 21 00 00 1a 56 5e
00 a0 a0 a0 29 50 30 20 35 00 c4 8f 21 00 00 1a
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 da

70 12 79 03 00 03 01 50 47 e8 01 04 ff 0e 4f 00
07 80 1f 00 6f 08 36 00 28 00 07 00 d0 a3 01 04
ff 0e 4f 00 07 80 1f 00 6f 08 7e 00 70 00 07 00
fa e6 00 04 ff 09 9f 00 4f 80 1f 00 9f 05 45 00
3d 00 04 00 59 87 00 04 7f 07 9f 00 2f 80 1f 00
37 04 4c 00 02 00 04 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 90

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: DEL
    Model: 17036
    Serial Number: 925972821 (0x37313955)
    Made in: week 19 of 2023
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 71 cm x 40 cm
    Gamma: 2.20
    DPMS levels: Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6835, 0.3095
    Green: 0.2607, 0.6542
    Blue : 0.1416, 0.0615
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x1c:  1280x800    59.810326 Hz  16:10    49.702 kHz     83.500000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    DMT 0x45:  1920x1200   59.884600 Hz  16:10    74.556 kHz    193.250000 MHz
    DMT 0x53:  1600x900    60.000000 Hz  16:9     60.000 kHz    108.000000 MHz (RB)
  Detailed Timing Descriptors:
    DTD 1:  3840x2160   59.996625 Hz  16:9    133.312 kHz    533.250000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   54 Vpol N
    Display Product Serial Number: '3YM14P3'
    Display Product Name: 'DELL G3223Q'
    Display Range Limits:
      Monitor ranges (Range Limits Only): 48-144 Hz V, 335-335 kHz H, max dotclock 1340 MHz
  Extension blocks: 2
Checksum: 0xaf

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  97:  3840x2160   60.000000 Hz  16:9    135.000 kHz    594.000000 MHz
    VIC  96:  3840x2160   50.000000 Hz  16:9    112.500 kHz    594.000000 MHz
    VIC 118:  3840x2160  120.000000 Hz  16:9    270.000 kHz   1188.000000 MHz
    VIC 117:  3840x2160  100.000000 Hz  16:9    225.000 kHz   1188.000000 MHz
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC  63:  1920x1080  120.000000 Hz  16:9    135.000 kHz    297.000000 MHz
    VIC  64:  1920x1080  100.000000 Hz  16:9    112.500 kHz    297.000000 MHz
    VIC  95:  3840x2160   30.000000 Hz  16:9     67.500 kHz    297.000000 MHz
    VIC  94:  3840x2160   25.000000 Hz  16:9     56.250 kHz    297.000000 MHz
    VIC  93:  3840x2160   24.000000 Hz  16:9     54.000 kHz    297.000000 MHz
    VIC  34:  1920x1080   30.000000 Hz  16:9     33.750 kHz     74.250000 MHz
    VIC  33:  1920x1080   25.000000 Hz  16:9     28.125 kHz     74.250000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC   1:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2
    Feature Caps: 0x0b
    Minimum Refresh Rate: 48 Hz
    Maximum Refresh Rate: 144 Hz
    Flags 1.x: 0x00
    Flags 2.x: 0x04
    Maximum luminance: 115 (603.666 cd/m^2)
    Minimum luminance: 20 (0.037 cd/m^2)
    Maximum luminance (without local dimming): 115 (603.666 cd/m^2)
    Minimum luminance (without local dimming): 47 (0.205 cd/m^2)
  Video Capability Data Block:
    YCbCr quantization: Selectable (via AVI YQ)
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: Always Overscanned
    IT scan behavior: Always Overscanned
    CE scan behavior: Always Overscanned
  Colorimetry Data Block:
    xvYCC601
    xvYCC709
    BT2020YCC
    BT2020RGB
    Gamut Boundary Description Metadata Profile P0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 115 (603.666 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 33 (0.101 cd/m^2)
  Detailed Timing Descriptors:
    DTD 2:  1920x1080  119.982181 Hz  16:9    137.260 kHz    285.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   56 Vpol N
    DTD 3:  2560x1440  119.997589 Hz  16:9    182.996 kHz    497.750000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   77 Vpol N
    DTD 4:  2560x1440   59.950550 Hz  16:9     88.787 kHz    241.500000 MHz (708 mm x 399 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   33 Vpol N
Checksum: 0xda  Unused space in Extension Block: 15 bytes

----------------

Block 2, DisplayID Extension Block:
  Version: 1.2
  Extension Count: 0
  Display Product Type: Standalone display device
  Video Timing Modes Type 1 - Detailed Timings Data Block:
    DTD:  3840x2160  143.962777 Hz  16:9    318.878 kHz   1250.000000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront   41 Vsync   8 Vback    6 Vpol N
    DTD:  3840x2160  119.880112 Hz  16:9    274.166 kHz   1074.730000 MHz (aspect 16:9, no 3D stereo)
               Hfront    8 Hsync  32 Hback   40 Hpol P
               Vfront  113 Vsync   8 Vback    6 Vpol N
    DTD:  2560x1440  143.969127 Hz  16:9    217.393 kHz    591.310000 MHz (aspect 16:9, no 3D stereo)
               Hfront   80 Hsync  32 Hback   48 Hpol P
               Vfront   62 Vsync   5 Vback    3 Vpol N
    DTD:  1920x1080  143.981451 Hz  16:9    166.587 kHz    346.500000 MHz (aspect 16:9, no 3D stereo)
               Hfront   48 Hsync  32 Hback   80 Hpol P
               Vfront    3 Vsync   5 Vback   69 Vpol N
  Checksum: 0x1f
Checksum: 0x90
=================
/sys/class/drm/card0-DP-3
EDID of '/sys/class/drm/card0-DP-3/edid' was empty.
=================
/sys/class/drm/card0-HDMI-A-1
EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty.
=================

ninjachicken1 · 2026-10-03 03:15:14

glxgears # this will run forever, but the behavior and output after 30s or so is interesting        
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
602 frames in 5.0 seconds = 120.288 FPS
600 frames in 5.0 seconds = 119.864 FPS
600 frames in 5.0 seconds = 119.845 FPS
600 frames in 5.0 seconds = 119.859 FPS
600 frames in 5.0 seconds = 119.864 FPS
600 frames in 5.0 seconds = 119.867 FPS
600 frames in 5.0 seconds = 119.874 FPS
600 frames in 5.0 seconds = 119.876 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.877 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.882 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.865 FPS
600 frames in 5.0 seconds = 119.864 FPS
600 frames in 5.0 seconds = 119.867 FPS
600 frames in 5.0 seconds = 119.868 FPS
600 frames in 5.0 seconds = 119.868 FPS
600 frames in 5.0 seconds = 119.871 FPS
600 frames in 5.0 seconds = 119.871 FPS
600 frames in 5.0 seconds = 119.874 FPS
600 frames in 5.0 seconds = 119.875 FPS
600 frames in 5.0 seconds = 119.872 FPS
600 frames in 5.0 seconds = 119.872 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.877 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.876 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.877 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.882 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.875 FPS
600 frames in 5.0 seconds = 119.882 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.883 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.882 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.881 FPS
561 frames in 5.1 seconds = 110.021 FPS
57 frames in 5.0 seconds = 11.398 FPS
54 frames in 5.0 seconds = 10.698 FPS
50 frames in 5.1 seconds =  9.806 FPS
280 frames in 5.0 seconds = 55.954 FPS
600 frames in 5.0 seconds = 119.885 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.878 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.881 FPS
600 frames in 5.0 seconds = 119.876 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.878 FPS
331 frames in 5.1 seconds = 64.804 FPS
49 frames in 5.1 seconds =  9.588 FPS
54 frames in 5.1 seconds = 10.593 FPS
52 frames in 5.1 seconds = 10.199 FPS
45 frames in 5.1 seconds =  8.829 FPS
43 frames in 5.1 seconds =  8.434 FPS
52 frames in 5.1 seconds = 10.200 FPS
194 frames in 5.0 seconds = 38.683 FPS
586 frames in 5.0 seconds = 117.074 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.879 FPS
600 frames in 5.0 seconds = 119.880 FPS
600 frames in 5.0 seconds = 119.884 FPS
371 frames in 5.1 seconds = 72.123 FPS
50 frames in 5.1 seconds =  9.809 FPS
50 frames in 5.1 seconds =  9.808 FPS
49 frames in 5.1 seconds =  9.612 FPS
61 frames in 5.1 seconds = 11.965 FPS
60 frames in 5.1 seconds = 11.826 FPS
67 frames in 5.1 seconds = 13.214 FPS
54 frames in 5.1 seconds = 10.592 FPS
55 frames in 5.1 seconds = 10.789 FPS
53 frames in 5.1 seconds = 10.395 FPS
56 frames in 5.1 seconds = 10.986 FPS
56 frames in 5.1 seconds = 10.981 FPS
60 frames in 5.1 seconds = 11.772 FPS
58 frames in 5.1 seconds = 11.376 FPS
55 frames in 5.1 seconds = 10.784 FPS
57 frames in 5.1 seconds = 11.234 FPS
60 frames in 5.1 seconds = 11.719 FPS
48 frames in 10.0 seconds =  4.823 FPS
115 frames in 5.1 seconds = 22.357 FPS
102 frames in 5.1 seconds = 20.016 FPS
68 frames in 5.1 seconds = 13.337 FPS
53 frames in 5.1 seconds = 10.394 FPS
56 frames in 5.1 seconds = 10.986 FPS
63 frames in 5.1 seconds = 12.356 FPS

After rebooting I launched glxgears as soon as I could. The framerate was slow for a while, but returned to a smooth rate before I was able to run it. After 5 minutes I launched Librewolf: at this point framerate drops, the glxgears window gets covered by my browser causing it to show a steady framerate, and drops again once I've positioned glxgears somewhere it won't get covered. It picks back up again when the window showing this thread is loaded up. After this I alt-tab to a browser window with the youtube video I was watching - the framerate plummets while I am changing windows and stays in the low tens after that, even before I've hit play. I fail to get a decent framerate on youtube until after I decide I've seen enough and close glxgears.

Also, I have no audio, which I have not attempted to troubleshoot as my windows-style taskbar disappears when I disable/unplug the other monitors. I'm going to treat this as outside the scope of this thread unless I'm told it's important.

seth · 2026-10-03 06:23:33

I have no idea what that means or what it might be called in my monitor OSDs. Duckduckgo hasn't been helpful in figuring that out.

https://wiki.archlinux.org/title/Variable_refresh_rate - "GSYNC"

Yes. It did so before and after unplugging the monitors.

That would suggest they were disabled.

at this point framerate drops, the glxgears window gets covered by my browser causing it to show a steady framerate, and drops again once I've positioned glxgears somewhere it won't get covered

Assuming it'S not just VRR and just to be sure: this isn't a wayland session after all?

loginctl session-status

ninjachicken1 · 2026-10-03 19:34:04

There's an option on my monitor OSD's called AMD Freesync Premium Pro, which I have now turned off for all monitors. It doesn't make "Display supports continuous frequencies" go away, is this enough? Here's the manual, all three monitors are the same model.

Pretty certain it's not wayland, but I will verify. I did switch to a wayland session a few days ago to see what would happen, and the framerate still sucked.

seth · 2026-10-03 19:47:20

After 5 minutes I launched Librewolf

What about concurrent glxgears windows? Do they behave the same?
What about vkcube? (vulkan-tools)
What about chromium or firefox?

What if you disable VRR/GSYNC in nvidia-settings? What if you configure the output(s) to run at 60Hz?

Arch Linux

#1 2026-09-21 00:14:10

[0x08000800]: data fabric sync flood event

#2 2026-09-21 04:40:32

Re: [0x08000800]: data fabric sync flood event

#3 2026-09-21 06:21:39

Re: [0x08000800]: data fabric sync flood event

#4 2026-09-21 14:26:39

Re: [0x08000800]: data fabric sync flood event

#5 2026-09-21 17:06:38

Re: [0x08000800]: data fabric sync flood event

#6 2026-09-21 20:00:07

Re: [0x08000800]: data fabric sync flood event

#7 2026-09-21 20:19:37

Re: [0x08000800]: data fabric sync flood event

#8 2026-09-28 00:46:18

Re: [0x08000800]: data fabric sync flood event

#9 2026-09-28 06:59:42

Re: [0x08000800]: data fabric sync flood event

#10 2026-09-30 02:31:34

Re: [0x08000800]: data fabric sync flood event

#11 2026-09-30 14:38:17

Re: [0x08000800]: data fabric sync flood event

#12 2026-10-01 02:50:26

Re: [0x08000800]: data fabric sync flood event

#13 2026-10-01 08:55:53

Re: [0x08000800]: data fabric sync flood event

#14 2026-10-01 13:53:38

Re: [0x08000800]: data fabric sync flood event

#15 2026-10-01 14:04:28

Re: [0x08000800]: data fabric sync flood event

#16 2026-10-01 15:39:42

Re: [0x08000800]: data fabric sync flood event

#17 2026-10-01 16:20:30

Re: [0x08000800]: data fabric sync flood event

#18 2026-10-01 17:23:06

Re: [0x08000800]: data fabric sync flood event

#19 2026-10-01 17:33:29

Re: [0x08000800]: data fabric sync flood event

#20 2026-10-01 20:35:20

Re: [0x08000800]: data fabric sync flood event

#21 2026-10-03 02:43:32

Re: [0x08000800]: data fabric sync flood event

#22 2026-10-03 03:15:14

Re: [0x08000800]: data fabric sync flood event

#23 2026-10-03 06:23:33

Re: [0x08000800]: data fabric sync flood event

#24 2026-10-03 19:34:04

Re: [0x08000800]: data fabric sync flood event

#25 2026-10-03 19:47:20

Re: [0x08000800]: data fabric sync flood event

Board footer