You are not logged in.
Hello everybody,
my system:
OS: Arch Linux x86_64
Host: 83JH (LOQ 17IRX10)
Kernel: Linux 7.2.6-arch2-1
Uptime: 44 mins
Packages: 2075 (pacman)
Shell: bash 5.3.20
Display (DELD0F3): 2560x1440 in 31", 144 Hz [External]
Desktop Environment: KDE Plasma 6.7.5
Window Manager: KWin (X11)
WM Theme: Breeze
Theme: Breeze (Light) [Qt], Breeze [GTK2/3]
Icons: breeze [Qt], breeze [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (60px)
Terminal: terminology 1.14.0
CPU: Intel(R) Core(TM) i7-14700HX (16+12) @ 5.50 GHz
GPU 1: NVIDIA GeForce RTX 5070 Max-Q / Mobile [Discrete]
GPU 2: Intel Raptor Lake-S UHD Graphics @ 1.60 GHz [Integrated]
Memory: 3.94 GiB / 31.05 GiB (13%)
Swap: 0 B / 8.66 GiB (0%)
Disk (/): 369.40 GiB / 922.35 GiB (40%) - btrfs
Local IP (enp8s0): xxx.xxx.xxx.xxx/xx
Battery (L24B4PK4): 76% [AC Connected]
Locale: de_DE.UTF-8
Due the last upgrade of Arch with KDE 6.8, the is no support for X11 anymore. During Wayland session, I have no video connection to my external display.
Under X11 everything runs well.
Installed Nvidia drivers (over pacman), both in the version 615.71.09:
nvidia-open-dkms
nvidia-utils
Maybe you can help me.
Thanks in advance.
Last edited by Klaus150 (Yesterday 14:47:45)
Offline
The issue you are experiencing is caused by missing Direct Rendering Manager (DRM) Kernel Mode Setting variables, which prevents the nvidia-open-dkms driver from communicating properly with the Wayland compositor (KWin) on a multi-GPU/Optimus laptop. Furthermore, KDE Plasma 6.8 has completely dropped native X11 session support, meaning returning to X11 long-term is no longer a viable option on updated systems.
To activate video output to your external monitor under Wayland, apply the following fixes:
1. Enable DRM Kernel Mode Setting (Crucial)
You must explicitly instruct the Linux kernel to load the NVIDIA modesetting parameters early during the boot sequence.
1. Open your GRUB configuration file using a text editor (e.g., sudo nano /etc/default/grub).
2. Locate the line starting with GRUB_CMDLINE_LINUX_DEFAULT.
3. Append nvidia-drm.modeset=1 inside the quotes. It should look similar to this:bash
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia-drm.modeset=1"
Use code with caution.
4. Save the file, exit the text editor, and regenerate your main grub deployment config:bash
sudo grub-mkconfig -o /boot/grub/grub.cfg
Use code with caution.
2. Configure Initramfs Early Loading
Ensure the required NVIDIA kernels are loaded directly into the initial RAM disk image.
1. Edit your main deployment hooks file: sudo nano /etc/mkinitcpio.conf.
2. Look for the MODULES=(...) bracket line and add the following four entries sequentially:bash
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
Use code with caution.
3. Save the file and rebuild your active Arch Linux kernel images:bash
sudo mkinitcpio -P
Use code with caution.
3. Set the Environment Variable for KWin
To force Plasma's window manager to properly recognize your hybrid discrete NVIDIA graphics processor card, enforce the target DRM renderer environment parameter.
1. Create or open the environment profile configuration profile: sudo nano /etc/environment.
2. Append the following lines onto empty rows at the bottom:bash
KWIN_DRM_DEVICES=/dev/dri/by-path/pci-0000:01:00.0-card:/dev/dri/by-path/pci-0000:00:02.0-card
Use code with caution.
(Note: Ensure the exact PCI ID positions match your hardware setup via running ls -l /dev/dri/by-path/ if detection errors continue).
Reboot your machine. After these adjustments take effect, your external screen will successfully receive a video connection during a modern Wayland session
Offline
Thanks for the reply.
In the meantime, I have found the reason for the problem: it was the OPTMUS-MANAGER. Now everything runs well.
Thanks.
Offline
DemonOut, thank you for trying to help.
next time please consult the arch wiki yourself before asking some AI.
The arch linux nvidia driver enables nvidia modeset by default since sometime in 2025 and the KWIN_DRM_DEVICES env var is rarely needed.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline