[SOLVED] KDE Plasma not detecting monitor correctly

waffle32 · 2025-07-26 00:23:16

Hi all:

I have an ASUS Q27G3XMN monitor, RTX 5070 Ti GPU, and an up-to-date Arch system as of today 25 July.

I'm not sure if this is a known issue or not, but I haven't been able to get the nvidia proprietary driver to work properly with this combination since I built this PC with the 5070. My old system had a GTX 1070 on it, and the above combo worked fine together on the proprietary driver.

The main issue is that either the driver or KDE Plasma is not detecting my monitor's refresh rates and resolutions correctly, so I'm locked to 60 Hz. I don't have this problem on nvidia-open, everything works fine on that, but I would really like to start using the proprietary driver again for its HDR support.

Not sure if this issue belongs in Apps & DEs or Kernel & Hardware. It's probably a driver issue, so posting in Kernel & Hardware, feel free to move as necessary.

This is happening on both X11 and Wayland.

If I run xrandr on proprietary 575.64.05:

Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767
Unknown-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 677mm x 381mm
   2560x1440     59.96*+
   1920x1440     59.97  
   1600x1200     59.87  
   1440x1080     59.99  
   1400x1050     59.98  
   1280x1024     59.89  
   1280x960      59.94  
   1152x864      59.96  
   1024x768      59.92  
   800x600       59.86  
   640x480       59.38  
   320x240       59.29  
   1920x1200     59.88  
   1680x1050     59.95  
   1440x900      59.89  
   1280x800      59.81  
   1152x720      59.97  
   960x600       59.63  
   928x580       59.88  
   800x500       59.50  
   768x480       59.90  
   720x480       59.71  
   640x400       59.95  
   320x200       58.14  
   2048x1152     59.90  
   1920x1080     59.96  
   1600x900      59.95  
   1368x768      59.88  
   1280x720      59.86  
   1024x576      59.90  
   864x486       59.92  
   720x400       59.27  
   640x350       59.28

If I run xrandr on open:

Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767
DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440    179.94*+
   1920x1440    179.92  
   1600x1200    179.86  
   1440x1080    179.92  
   1400x1050    179.92  
   1280x1024    179.91  
   1280x960     179.87  
   1152x864     179.78  
   1024x768     179.84  
   800x600      179.71  
   640x480      179.43  
   320x240      178.06  
   1920x1200    179.89  
   1680x1050    179.94  
   1440x900     179.84  
   1280x800     179.74  
   1152x720     179.84  
   960x600      179.74  
   928x580      179.47  
   800x500      179.63  
   768x480      179.51  
   720x480      179.35  
   640x400      179.55  
   320x200      176.99  
   2048x1152    179.96  
   1920x1080    179.98  
   1600x900     179.77  
   1368x768     179.92  
   1280x720     179.72  
   1024x576     179.77  
   864x486      179.75  
   720x400      179.53  
   640x350      179.74

I've tried using different DisplayPort ports, had no effect. Also disabled the GSP using

NVreg_EnableGpuFirmware=0

, saw no effect.

Any help would be much appreciated.

Last edited by waffle32 (2025-08-05 00:40:44)

seth · 2025-07-26 06:21:04

Unknown-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 677mm x 381mm

That's the simplydumb device, add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters (no, it being set by some modprobe.conf will not help) but before that maybe better post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and

pacman -Qs 'nvidia|kernel'

since this might indicate a broken driver (in any event you'd be running on software emulation)

waffle32 · 2025-07-27 14:35:52

Thanks for your reply.

I had dropped the modesetting kernel parameter after it became enabled by default in nvidia-utils. I added it back, and it made no difference on the proprietary driver.

cat /sys/module/nvidia_drm/parameters/modeset

Y

sudo journalctl -b | curl -F 'file=@-' 0x0.st

curl: (7) Failed to connect to 0x0.st port 80 after 2 ms: Could not connect to server

pacman -Qs 'nvidia|kernel'

local/dkms 3.2.1-1
    Dynamic Kernel Modules System
local/egl-gbm 1.1.2.1-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.19-1
    EGLStream-based Wayland external platform
local/egl-x11 1.0.2-1
    NVIDIA XLib and XCB EGL Platform Library
local/exfatprogs 1.2.9-1
    exFAT filesystem userspace utilities for the Linux Kernel exfat driver
local/fuse2 2.9.9-5
    Interface for userspace programs to export a filesystem to the Linux kernel
local/fuse3 3.17.1-1
    Interface for userspace programs to export a filesystem to the Linux kernel
local/iptables-nft 1:1.8.11-2
    Linux kernel packet control tool (using nft interface)
local/kmod 34.2-1
    Linux kernel module management tools and library
local/lib32-libdrm 2.4.125-1
    Userspace interface to kernel DRM services (32-bit)
local/lib32-libvdpau 1.5-3
    Nvidia VDPAU library
local/lib32-nvidia-utils 575.64.05-1
    NVIDIA drivers utilities (32-bit)
local/libdrm 2.4.125-1
    Userspace interface to kernel DRM services
local/libnetfilter_conntrack 1.0.9-2
    Library providing an API to the in-kernel connection tracking state table
local/libnfnetlink 1.0.2-2
    Low-level library for netfilter related kernel/userspace communication
local/libsysprof-capture 48.0-5
    Kernel based performance profiler - capture library
local/libva-nvidia-driver 0.0.14-1
    VA-API implementation that uses NVDEC as a backend
local/libvdpau 1.5-3
    Nvidia VDPAU library
local/libxnvctrl 575.64.05-1
    NVIDIA NV-CONTROL X extension
local/linux 6.15.8.arch1-1
    The Linux kernel and modules
local/linux-api-headers 6.15-1
    Kernel headers sanitized for use in userspace
local/linux-firmware-nvidia 20250708-1
    Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
local/linux-headers 6.15.8.arch1-1
    Headers and scripts for building modules for the Linux kernel
local/mtdev 1.1.7-1
    A stand-alone library which transforms all variants of kernel MT events to
    the slotted type B protocol
local/nvidia 575.64.05-2
    NVIDIA kernel modules
local/nvidia-settings 575.64.05-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 575.64.05-1
    NVIDIA drivers utilities
local/nvtop 3.2.0-1
    GPUs process monitoring for AMD, Intel and NVIDIA

xrandr is still returning the same output as above on the proprietary driver.

If I run 'sudo journalctl -b | grep nvidia' on nvidia-open:

sudo journalctl -b | grep nvidia

Jul 27 16:42:26 LiDe kernel: nvidia: loading out-of-tree module taints kernel.
Jul 27 16:42:26 LiDe kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jul 27 16:42:26 LiDe kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 238
Jul 27 16:42:26 LiDe kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Jul 27 16:42:26 LiDe systemd-modules-load[282]: Inserted module 'nvidia_uvm'
Jul 27 16:42:26 LiDe kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  575.64.05  Release Build  (root@)  
Jul 27 16:42:26 LiDe kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jul 27 16:42:27 LiDe kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
Jul 27 16:42:27 LiDe kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Jul 27 16:42:27 LiDe kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
Jul 27 16:42:27 LiDe kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
Jul 27 12:47:40 LiDe sudo[2778]:   robbie : TTY=pts/1 ; PWD=/home/robbie ; USER=root ; COMMAND=/usr/bin/cat /sys/module/nvidia_drm/parameters/modeset

journalctl | grep nvidia on nvidia proprietary:

sudo journalctl -b | grep nvidia

Jul 27 16:53:59 LiDe kernel: nvidia: loading out-of-tree module taints kernel.
Jul 27 16:53:59 LiDe kernel: nvidia: module license 'NVIDIA' taints kernel.
Jul 27 16:53:59 LiDe kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jul 27 16:53:59 LiDe kernel: nvidia: module license taints kernel.
Jul 27 16:53:59 LiDe kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Jul 27 16:53:59 LiDe kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Jul 27 16:53:59 LiDe kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Jul 27 16:53:59 LiDe kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  575.64.05  Fri Jul 18 15:45:08 UTC 2025
Jul 27 16:53:59 LiDe systemd-modules-load[283]: Inserted module 'nvidia_uvm'
Jul 27 16:53:59 LiDe kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jul 27 16:53:59 LiDe kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice
Jul 27 16:53:59 LiDe kernel: [drm:nv_drm_register_drm_device [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register device

Edit: I installed linux-zen this morning because I wanted to experiment with it and interestingly (at least to me, maybe not related at all) saw different behavior - if I boot linux-zen 6.15.8 with nvidia-open, it displays the same behavior as nvidia proprietary on mainline kernel. Proprietary driver behavior is unchanged (same as open in this case).

Using the zen kernel, adding nvidia_drm.modeset=1 to kernel command line makes the system not boot at all, hangs when attempting to start graphical interface.

Last edited by waffle32 (2025-07-27 16:55:22)

seth · 2025-07-29 21:32:28

Using the zen kernel, adding nvidia_drm.modeset=1 to kernel command line makes the system not boot at all, hangs when attempting to start graphical interface.

Sounds you've no output besides the simpledrm device there (missing nvidia-dkms or linux-zen-headers?)

cat /sys/module/nvidia_drm/parameters/modeset

is irrelevant - it /has/ to be at the kernel commandline to be useful here.

curl: (7) Failed to connect to 0x0.st port 80 after 2 ms: Could not connect to server

No internet?

sudo journalctl -b > /tmp/journa.txt # usb-walk that to a system w/ internet connection

waffle32 · 2025-07-31 00:20:01

Sorry - Pi-hole was blocking 0x0.st for some reason, I didn't think that output looked right. http://0x0.st/8RUY.txt

This is from a system running kernel 6.15.8 with nvidia proprietary 575.64.05.

with nvidia_drm.modeset=1, the system boots but cannot launch a graphical interface or login manager (SDDM). Without it I can launch a graphical interface, only my display is locked to 60 Hz.

I have nvidia-utils, lib32-nvidia-utils, linux-headers, linux installed usually (and for this boot). I have a pacman hook to regenerate initramfs for every NVIDIA driver update, so I don't usually run into issues on that front.

This is where I think the problem is:

Jul 30 23:56:37 LiDe kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:2c05)
                             NVRM: installed in this system requires use of the NVIDIA open kernel modules.
Jul 30 23:56:37 LiDe kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x56:884)
Jul 30 23:56:37 LiDe kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Jul 30 23:56:37 LiDe kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice
Jul 30 23:56:37 LiDe kernel: [drm:nv_drm_register_drm_device [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register device

Not sure how to fix. The only thing I haven't tried yet is baking nvidia, nvidia-modeset, nvidia_uvm, nvidia_drm into initramfs - it won't fit in my EFI system partition somehow, and I resized it to nearly 700 MB.

This is the same system on nvidia-open 575.64.05 and same kernel. http://0x0.st/8RU5.txt The system works without incident in this example and detects my monitor correctly.

Last edited by waffle32 (2025-07-31 00:35:28)

seth · 2025-08-01 14:27:05

This is the same system on nvidia-open 575.64.05 and same kernel. http://0x0.st/8RU5.txt The system works without incident in this example and detects my monitor correctly.

Jul 30 23:56:37 LiDe kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:2c05)
                             NVRM: installed in this system requires use of the NVIDIA open kernel modules.

It's a blackwell chip, nvidia-open is your only option.
Trying to use nvidia results in the simpledrm (software emulation) being used and thus the 60Hz lock (you're getting a bunch of vesa modes)

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Edit: https://www.reddit.com/r/archlinux/comm … rt_in_kde/

export KWIN_DRM_ALLOW_NVIDIA_COLORSPACE=1

?

Last edited by seth (2025-08-01 14:28:37)

Arch Linux

#1 2025-07-26 00:23:16

[SOLVED] KDE Plasma not detecting monitor correctly

#2 2025-07-26 06:21:04

Re: [SOLVED] KDE Plasma not detecting monitor correctly

#3 2025-07-27 14:35:52

Re: [SOLVED] KDE Plasma not detecting monitor correctly

#4 2025-07-29 21:32:28

Re: [SOLVED] KDE Plasma not detecting monitor correctly

#5 2025-07-31 00:20:01

Re: [SOLVED] KDE Plasma not detecting monitor correctly

#6 2025-08-01 14:27:05

Re: [SOLVED] KDE Plasma not detecting monitor correctly

Board footer