That’s unfortunate. The latest stable update (2024-06-10) finally made KWin Wayland usable on my setup. Since the revert (550.90.07-2 → 550.90.07-3), my Kwin Wayland setup is broken again. With broken I mean: I can log in and I see a mouse cursor, an app (evolution) autostarts successfully but is scaled like 300% and that’s it. No menu, no wallpaper, no keybinding, I can’t click anything.
For the time being I just switch back again to Kwin X11.
But besides: I appreciate all your hard work. Been using Manjaro for years on the same system successfully. With the help of these nice curated stable update posts, updating is smooth with Manjaro. Thanks guys!
Additionally, with the driver version 545 and above, you can also set the experimental nvidia_drm.fbdev=1 parameter, which is required to tell the NVIDIA driver to provide its own framebuffer device instead of relying on efifb or vesafb , which do not work under simpledrm .
Do you mean no virtual keyboard shows even when there is one properly installed and configured? Or, it just doesn’t support it at all?
I imagine so, for as long as the need exists. As you are no doubt aware, these kernels are a little less frequent that the mainstream kernels.
Use your existing kernel until the next RT is released;
it’s only a question of time.
Music production isn’t the only use case for a real-time kernel; albeit the most commonly highlighted. I might question the need for it too, in some cases, but there’s usually a good reason, whether perceived or actual.
It will not work ( Talk:NVIDIA - ArchWiki ), grub options are needed in kernel 6.6.x, in kernel 6.9.x it is also necessary to add to /etc/mkinitcpio.conf : MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm), and without fbdev=1 it will not work.
The best way for Wayland is kernel 6.6.x, simply add to grub nvidia_drm.modeset=1 and optionally nvidia_drm.fbdev=1 and this will make it possible to log in Wayland and x11 without problems.
I have tested kernel 6.10rc3 and it is the same case as 6.9.x.
I am observing the issue that my lockscreen gets stuck after hibernation. Both on X11 and Wayland session. I can not switch to tty, so I have to use the off switch coldly. On X11 at least, the session is killed (I guess) and I’m back at sddm to log in.
I’m using a slideshow of tons of pictures, in subfolders, too. Will report on discuss.kde and also report back here as well, have not loo(c)ked into it more deeply for now.
error: failed retrieving file 'gcc-libs-14.1.1+r58+gfc9fb69ad62-1-x86_64.pkg.tar.zst.sig' from mirror.freedif.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'archlinux-appstream-data-20240526-1-any.pkg.tar.zst' from mirror.freedif.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
I’ve been having issues with LibreOffice fresh, programs freeze when saving or inserting images into documents. I noticed this after upgrading to Plasma 6.
For interested people: tty font changes with setting fbdev=1.
Just out of curiosity; what is the benefit if fbdev is used?
In Arch-Wiki there is only a info, what it does: ...to tell the NVIDIA driver to provide its own framebuffer device... (NVIDIA - ArchWiki)
AFAIK setting fbdev=1 should allow you to have higher resolution and faster console, especially when using high resolution screen, by NVIDIA running its own framebuffer device (and framebuffer not being run by CPU). The downside is that when this framebuffer device fails for some reason, console may not display at all. I think both intel and amd drivers are running their own framebuffer devices by default
And remember to set fbdev=1 only on systems where NVIDIA is your primary GPU. It won’t work for dual-gpu (in terms of iGPU + dGPU) systems
CUDA is broken after 2024-05-29 update, which updated cuda to 12.5, but the nvidia kernel driver is still 12.4 now, so if you compile a cuda program and run it, then it will throw an error “the provided PTX was compiled with an unsupported toolchain.”