Arch Linux

lnex

Member

Registered: 2025-11-24

Posts: 4

Display problem with NVIDIA GPU and Wayland

Hi I met some problem when trying to using a RTX 5070 Ti as display device. My computer is i7-13700K with 5070 Ti, KDE(Wayland) and KWin.

When booting with HDMI connected to iGPU, the system boots normally and everything is fine. In this case, if I plug off the HDMI line and then re-connect it to NVIDIA GPU, the display is still fine, but journal shows some error: journal

If I boot my system with HDMI line connected to NVIDIA GPU, the system will launch but nothing would be shown on my screen including cursor. The journal in this case is: journal

The non-graphic function of NVIDIA GPU seems to work in current status, for nvidia-smi have some output.

My mkinitcpio.conf
grub cfg

BTW I have a windows dual-boot.

> lspci -d ::03xx
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GB203 [GeForce RTX 5070 Ti] (rev a1)

> yay -Q | grep linux
archlinux-appstream-data 20251025-2
archlinux-keyring 20251116-1
linux 6.17.8.arch1-1
linux-api-headers 6.17-1
linux-firmware-intel 20251111-1
linux-firmware-nvidia 20251111-1
linux-firmware-other 20251111-1
linux-firmware-realtek 20251111-1
linux-firmware-whence 20251111-1
linux-headers 6.17.8.arch1-1
syslinux 6.04.pre3.r3.g05ac953c-4
util-linux 2.41.2-1
util-linux-libs 2.41.2-1

> yay -Q | grep nvidia
lib32-nvidia-utils-beta 580.105.08-1
lib32-opencl-nvidia-beta 580.105.08-1
linux-firmware-nvidia 20251111-1
nvidia-open 580.105.08-5
nvidia-settings 580.105.08-1
nvidia-utils-beta 580.105.08-1
opencl-nvidia 580.105.08-4

I have spent some time to debug this problem, but I cannot figure out the problem. If anyone could help, I will appreciate so much.

Last edited by lnex (2025-11-24 19:18:41)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,086

Re: Display problem with NVIDIA GPU and Wayland

Nov 25 02:50:22 lnex-pc sddm[1168]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Nov 25 02:50:22 lnex-pc sddm[1168]: Display server started.
Nov 25 02:50:22 lnex-pc sddm[1168]: Socket server starting...
Nov 25 02:50:22 lnex-pc sddm[1168]: Socket server started.
Nov 25 02:50:22 lnex-pc sddm[1168]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Nov 25 02:50:22 lnex-pc sddm[1168]: Greeter starting...
Nov 25 02:50:22 lnex-pc sddm-helper[1183]: [PAM] Starting...
Nov 25 02:50:22 lnex-pc sddm-helper[1183]: [PAM] Authenticating...
Nov 25 02:50:22 lnex-pc sddm-helper[1183]: [PAM] returning.
Nov 25 02:50:22 lnex-pc sddm-helper[1183]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=962) by (uid=0)
Nov 25 02:50:22 lnex-pc systemd-logind[954]: New session 'c1' of user 'sddm' with class 'greeter' and type 'x11'.
Nov 25 02:50:22 lnex-pc systemd[1]: Created slice User Slice of UID 962.
Nov 25 02:50:22 lnex-pc systemd[1]: Starting User Runtime Directory /run/user/962...
Nov 25 02:50:22 lnex-pc systemd[1]: Finished User Runtime Directory /run/user/962.
Nov 25 02:50:22 lnex-pc systemd[1]: Starting User Manager for UID 962...

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General for either case.

http://0x0.st/KW2o.txt actually has

sddm-greeter-qt6[1196]: Adding view for "HDMI-3" QRect(0,0 3840x2160)

and

New session '2' of user 'lnex' with class 'user' and type 'wayland'.

- https://0x0.st/KW2X.txt does not. Did you possibly mix up the two?

http://0x0.st/KW2o.txt later runs into

Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:02:40 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:02:45 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:04:49 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:05:54 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:06:06 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:06:13 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数
Nov 25 03:07:28 lnex-pc kwin_wayland[1335]: Failed to create framebuffer: 无效的参数 // "Invalid parameter"

Unrelated, but: disable systemd-networkd and iwd, if you want to use iwd as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

lnex

Member

Registered: 2025-11-24

Posts: 4

Re: Display problem with NVIDIA GPU and Wayland

[Xorg log] Boot with NVIDIA GPU
[Xorg log] Boot with iGPU

And I actually mixed up two logs, sry for this.

BTW, thank you for nm-related issues.

lnex

Member

Registered: 2025-11-24

Posts: 4

Re: Display problem with NVIDIA GPU and Wayland

I find out the solution. Previous error seems to be sddm-greeter failed to launched on NVIDIA GPU, it runs in X11 mode by default. I follow https://wiki.archlinux.org/title/SDDM#KDE_Plasma_/_KWin to force sddm-greeter running in Wayland mode, and the system could boot with NVIDIA GPU and display is fine. But I do not know why sddm-greeter failed to launch in previous setting.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,086

Re: Display problem with NVIDIA GPU and Wayland

Server runs modesetting on intel in regular PRIME
http://0x0.st/KWy2.txt has

[     9.769] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): connected
[     9.769] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): Internal TMDS
[     9.769] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): 42666.7 MHz maximum pixel clock
…
[     9.847] (II) NVIDIA(G0): Validated MetaModes:
[     9.847] (II) NVIDIA(G0):     "NULL"
[     9.847] (II) NVIDIA(G0): Virtual screen size determined to be 640 x 480
[     9.956] (WW) NVIDIA(G0): Cannot find size of first mode for SKG H27P22P (DFP-0); cannot
[     9.956] (WW) NVIDIA(G0):     compute DPI from SKG H27P22P (DFP-0)'s EDID.
[     9.956] (==) NVIDIA(G0): DPI set to (75, 75); computed from built-in default
…
[    15.290] (--) NVIDIA(GPU-0): DFP-0: disconnected
[    15.290] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[    15.290] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[    15.290] (--) NVIDIA(GPU-0): 
[    25.851] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): connected
[    25.851] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): Internal TMDS
[    25.851] (--) NVIDIA(GPU-0): SKG H27P22P (DFP-0): 42666.7 MHz maximum pixel clock

[   631.092] (EE) NVIDIA(G0): Failed to allocate display software resources.
[   631.092] (WW) NVIDIA(G0): Failed to set the display configuration
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 0 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 1 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 2 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 3 failed: Insufficient permissions
[   631.092] (EE) NVIDIA(G0): Failed to allocate display software resources.
[   631.092] (WW) NVIDIA(G0): Failed to set the display configuration
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 0 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 1 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 2 failed: Insufficient permissions
[   631.092] (WW) NVIDIA(G0):  - Setting a mode on head 3 failed: Insufficient permissions
[   631.093] (WW) NVIDIA(G0): Failed to set DPMS to off

looks like and effort to set the mode via nvidia-settings?

You might have to explicitly setup the output redirection, https://wiki.archlinux.org/title/PRIME# … offloading in /usr/share/sddm/scripts/Xsetup

xrandr --listproviders

Using sddm/wayland just completely sidesteps this.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

lnex

Member

Registered: 2025-11-24

Posts: 4

Re: Display problem with NVIDIA GPU and Wayland

It's pretty weird that I have such output:

❯ xrandr --listproviders
Providers: number : 0

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,086

Re: Display problem with NVIDIA GPU and Wayland

This doesn't work on wayland.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc