You are not logged in.
Previous session working 100% fine. Then I do the followinig upgrades:
[2024-10-01T09:04:01-0700] [ALPM] upgraded linux (6.10.10.arch1-1 -> 6.11.1.arch1-1)
[2024-10-01T09:04:02-0700] [ALPM] upgraded linux-headers (6.10.10.arch1-1 -> 6.11.1.arch1-1)
[2024-10-01T09:04:02-0700] [ALPM] upgraded nvidia-utils (560.35.03-3 -> 560.35.03-4)
[2024-10-01T09:04:03-0700] [ALPM] upgraded nvidia (560.35.03-6 -> 560.35.03-9)
[2024-10-01T09:04:03-0700] [ALPM] upgraded qt6-base (6.7.3-1 -> 6.7.3-2)
System completely fails to reboot. Blank screen when after entering wayland session. Usually when this happens it has something to do with HDR, however disabling HDR does not fix the issue so it seems unrelated. Plus journalctl does nto show any graphics rendering related errors.
After downgrading these packages to previous version, everything works fine again.
Offline
Same problem here. Downgrading Kernel and Nvidia packages fixes the issue.
Edit: adding nvidia_drm.fbdev=1 kernel parameter solved the issue for 6.11.1 kernel.
Last edited by ITALIEN (2024-10-02 01:20:09)
Offline
Same problem for me. I was able to switch to X instead of Wayland using the Desktop switcher and continue working. Will wait for upgraded packages to fix the broken Wayland after this update.
Offline
Please try following, this should fix the issue, with above patch pulled in:
```
sudo pacman -U https://pkgbuild.com/~ptr1337/kernel-testing/simplefb-skip/linux-6.11.1.arch1-2-x86_64.pkg.tar.zst https://pkgbuild.com/~ptr1337/kernel-testing/simplefb-skip/linux-headers-6.11.1.arch1-2-x86_64.pkg.tar.zst[/url]
```
https://github.com/archlinux/linux/comm … 78a9411924
Please use this together with nvidia-dkms.
Last edited by ptr1337 (2024-10-01 20:15:45)
Offline
@Fusion916 Thanks, downgrading the packages you mentioned did the trick. I am using hyprland and nvidia-dkms.
Offline
Same problem here. Downgrading Kernel and Nvidia packages fixes the issue.
Edit: adding nvidia_drm.fbdev=1 kernel parameter solved the issue for 6.11.1 kernel.
Thank you for your suggestion, adding nvidia_drm.fbdev=1 kernel parameter solved the issue for me too (without downgrading any packages).
Still, I get the following in the logs:
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:48 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:47 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Oct 02 10:35:46 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x506: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuf>
Oct 02 10:35:46 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. Framebuffer name must be generated before being bound.
Oct 02 10:35:46 lucdesktop kwin_wayland[877]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Oct 02 10:35:46 lucdesktop kwin_wayland[877]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Oct 02 10:35:46 lucdesktop kwin_wayland[877]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Oct 02 10:35:44 lucdesktop kwin_wayland[877]: <Unknown File>:97: TypeError: Cannot read property 'translucencyWindowTypeAnimation' of undefined
Environment:
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 6.11.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce GTX 1080
NVIDIA driver version: 560.35.03-9
Last edited by iq2luc (2024-10-02 07:48:05)
Offline
Unfortunately adding nvidia_drm.fbdev=1 kernel parameter generates another issue for me: I lose the Linux console completely.
Back to X for now.
Offline
same probleme on hyprland, downgraded :
-linux
-linux-headers
-nvidia
-nvidia-utils
-qt6-base
that fixed the issue
Offline
Had the same problem and *mostly* the same solution. Downgrading QT6 broke SDDM, so I had to update that back to 6.7.3-2.
Offline
I did not need to downgrade qt6-base. See parallel thread: https://bbs.archlinux.org/viewtopic.php … 0#p2199950
Offline
Like others I also downgraded the kernal and nvidia drivers to get a stable system back - after disabling the phantom fb screen in hyprland config, hyprland was running at very high cpu usage prior to this...
I noticed nvidia-dkms 560.35.03-5 came out of testing today so did a system upgrade. Unfortunately I still have the very high cpu hyprland usage... any thoughts? EDIT fbdev and modeset are enabled.
Last edited by BennehBoy (2024-10-03 19:30:33)
Offline
For me the nvidia-dkms 560.35.03-5 package has solved the Wayland black screen issue. i do not use Hyprland, but Plasma, and do not see (using top) any abnormal CPU consumption.
Offline
Is this issue fixed now? I got an update this morning of the nvidia package and etc. and I can see that the gitlab issues have been closed but I don't see what solution is to enabling "nvidia_drm.fbdev=1"?
Offline
The issue is fixed (for me). I updated this morning and rebooted without issues. I don't have fbev as a kernel parameter so its not needed (for me).
Offline
Also fixed for me, linux 6.11-2 & nvidia-open-dkms 560.35.03-12 updates today have removed the performance problems.
Offline
I just removed fbdev kernel parameter from my grub file and I confirm that my KDE+Wayland+nvidia session runs fine. But I have lost the console still. I have run 'grub-mkconfig -o /boot/grub/grub.cfg' after I changed '/etc/default/grub'.
Offline
linux 6.11.2.arch1-1
nvidia-dkms 560.35.03-5
wayland 1.23.1-1
kwin 6.1.5-2
plasma-desktop 6.1.5-1
+
no related kernel parameters (defaults to modeset=1 and fbdev=1)
/sys/module/nvidia_drm/parameters/modeset = Y
/sys/module/nvidia_drm/parameters/fbdev = Y
=>
KDE + Wayland works but the console is lost
Offline
I managed to get back the Linux console too, see: https://bbs.archlinux.org/viewtopic.php … 1#p2200421
Offline
Had the same problem. Fixed by switching to nouveau drivers and downgrading linux and linux-headers. Switching to nouveau was probably not necessary.
Offline
I am on the closed source nvidia drivers and the latest update works fine again with hyprland too. I made no changes to configs or kernel parameters at any point, and did not switch to nouveau.
Offline