You are not logged in.
Just pacman system upgraded which included the 555 drivers and now am unable to completely boot to a wayland session. X11 still works just fine and I am posting from a X11 session now. I have nvidia_drm.modset=1 in the grub kernel command line and that has been working fine with the previous drivers (550):
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=2560x1440 nvidia_drm.modeset=1"
nvidia-smi output:
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.58 Driver Version: 555.58 CUDA Version: 12.5 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 4090 Off | 00000000:01:00.0 On | Off |
| 0% 36C P8 20W / 500W | 360MiB / 24564MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 774 G /usr/lib/Xorg 115MiB |
| 0 N/A N/A 1037 G /usr/bin/ksmserver 7MiB |
| 0 N/A N/A 1039 G /usr/bin/kded6 7MiB |
| 0 N/A N/A 1040 G /usr/bin/kwin_x11 28MiB |
| 0 N/A N/A 1068 G /usr/bin/plasmashell 62MiB |
| 0 N/A N/A 1135 G /usr/lib/kactivitymanagerd 6MiB |
| 0 N/A N/A 1137 G ...b/polkit-kde-authentication-agent-1 7MiB |
| 0 N/A N/A 1138 G /usr/lib/org_kde_powerdevil 6MiB |
| 0 N/A N/A 1139 G /usr/lib/xdg-desktop-portal-kde 7MiB |
| 0 N/A N/A 1283 G /usr/bin/kaccess 7MiB |
| 0 N/A N/A 1422 G konsole 6MiB |
+-----------------------------------------------------------------------------------------+
Here are the wayland session errors I get when trying to boot into wayland. Ive gotten these kind of errors in the past when there was an issue with nvidia modeset so I'm assuming for some reason there is an issue with the modest even though it was working fine with the previous version of the drivers:
[ 40.198043] desktop kwin_wayland[1056]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
[ 40.198063] desktop kwin_wayland[1056]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
[ 40.201076] desktop kwin_wayland[1056]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
[ 40.201092] desktop kwin_wayland[1056]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
[ 40.202329] desktop kwin_wayland[1056]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
[ 40.202345] desktop kwin_wayland[1056]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
[ 40.206513] desktop kwin_wayland[1056]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
[ 40.206526] desktop kwin_wayland[1056]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
[ 40.207784] desktop kwin_wayland[1056]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
[ 40.207799] desktop kwin_wayland[1056]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Last edited by Fusion916 (2024-06-29 20:26:41)
Offline
Ok it looks like this is some kind of real bug with either NVIDIA or Plasma.
It appears that this issue only happens if you have HDR enabled at boot. To work around this issue, you can delete:
~/.config/kwinoutputconfig.json
Then reboot, wayland will boot just fine but without HDR enabled. You can thing re-enable HDR after entering the session and everything will work just fine. However if you reboot again with HDR enabled it will hang. So as a workaround you can just make sure you don't reboot with HDR enabled. There is a bug already filed tracking this:
https://bugs.kde.org/show_bug.cgi?id=488941
Hopefully this helps anyone else running into this issue.
Offline
I still get this bug on the new 560.35 drivers
Offline