The poor quality of Linux drivers since 555 and 560 has kept me in 550 since January to upgrade things, which has problems, but far less than either 555 or 560. I upgraded then to test KDE 6.0 and ideally Wayland, but found Wayland+Nvidia still a mess, and remains largely so with small steps forward in 555/560 to fix explicit sync issues, but break everything else in the process. Particularly gaming that I enjoy now with Proton.
Watching 555/560 in these threads has made me rethink my strategy in any desktop/gaming system I buy in the future ever including Nvidia again, as at this point over some 15 years of Nvidia Linux drivers personally, I just give up and will try AMD for some hope of actual Wayland use.
AMD may not be entirely better, but it simply canāt be this bad to rub against any and every Linux graphics feature that Nvidia has across 20 years of GPU history. Thereās a reason Steam chose AMD over Nvidia for the Steam Deck, not to mention Playstation and Xboxā¦
amd is no better right now itās a huge flux and a mess sure 560 has minor issues but most of them are solved in whatever driver comes next so whining about it instead of waiting helps no one here. just report bugs and move on.
560 for me has been the best driver nvidia has had in ages! and it will only get better from here.
Gave 560.35.03 a try again on my Razer laptop (Intel + RTX3070), but the GPU is still unable to get into D3cold when no external displays are connected, both in open and closed drivers mode, with or without GSP.
Running Ubuntu 24.10 with Gnome+Wayland.
Still staying on Nouveau for now to have a somewhat usable battery life.
Iām having a severe performance issue with Vulkan apps running in XWayland. The frame rate is extremely low with this combination. All other combinations (Wayland+Vulkan, Wayland+OpenGL, XWayland+OpenGL) work great with very high performance. This performance issue is regardless of the VkPresentModeKHR. The framerate gets worse with window size (see video).
To reproduce, compile GitHub - krh/vkcube: Spinning Vulkan Cube, and run once with ./vkcube -m wayland to observe everything works great. Then run again with ./vkcube -m xcb, maximize the window, and see the extremely bad framerate.
I donāt know if itās related, but simply running glxgears and maximizing the window is also horrible for me. Yet, glxgears uses OpenGL instead of Vulkan.
Iām on 560.35.03 (with GTX1660Ti). I validated that the test program (vkcube) is running on the GPU through nvidia-smi. Also mangohud confirms this:
Hey @courteauxmartijn Im afraid to say its Hyprland issue , Hyprland has so many issues with nvidia, poorly implemented protocols etc. Iād suggest try gnome and kwin, if you prefer window managers use sway, although its unsupported on nvidia but their implementation is way better.
just tested 565, gamescope mouse cursor being cut off is fixed, however wayland native osu!lazer still crashes under vulkan renderer, and gamescope minecraft 1.8.9 still has quite intense flickering
Not sure if the Unreal Engine Editor problem is ever going to be fixed in 565, for some reason the 4060Ti wasnāt compatible with 535 where UE editor was functional so forced to update to 560 and this happens almost immediately after opening a project from 5.1 and migrating it to 5.4.
Operating System: Arch Linux
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 Ć 12th Gen IntelĀ® Coreā¢ i5-12400F
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
Manufacturer: ASUS
Does anyone know why NVENC no longer works in 560 driver? In older drivers and older GPUs the GPU load was always at least 40% while video conversion with NVENC (Handbrake). But now with this driver the GPU load is 1-2% and the whole load goes to the CPU which means NVENC is no longer working. The Intel CPU does NOT have an integrated GPU, like some older generations.
Why is that and how do I make NVENC work in this driver? The exact version is 560.35.03-18 from Arch repo and the GPU is RTX 3060.
Edit: after nearly 12 hours of testing and experimenting, I found out that NVENC is actually working and Handbrake is using it. The output file has the expected size and quality, so NVENC is working. But for whatever reason the GPU isnāt being loaded at all and conky indicates the most of the loads goes to the CPU. IDK, maybe nowadays GPUs are too powerful and with large VRAM sizes to even indicate any load. Whatever the cause of this misleading display, a handbrake encoding log clearly indicates itās using NVENC for the conversion.
So There is a temp fix to flipping of the Wayward driver - So if you revert to the standard X driver you can eliminate some the problems in the meantime; Until Nvidia makes it priority. In the GUI logon screen there is an icon in lower right hand corner. You can select the display driver from that. Good Luck.
When can Linux users expect a solution to the Wayland Driver issue? At present the driver still presents problems to a majority of users and we are forced to revert back to standard X Display. Many of us believe you have no intentions of resolving the problem.
