Following on from the NVIDIA Beta 495.29.05 earlier this month, today NVIDIA has a fresh 495.44 stable driver release that builds upon it with some additional extras. This is the big one for Wayland fans, since it now works with the GBM API.
With this API now hooked up, it should mean a better Wayland experience and it's something that the KDE Plasma team are already working on supporting too.
You will also find in this release an indicator (on supported desktops) for showing Resizable BAR and the minimum Kernel version got bumped from 2.6.32 to 3.10. Additionally these new extensions are supported:
- VK_KHR_present_id
- VK_KHR_present_wait
- VK_KHR_shader_subgroup_uniform_control_flow
- EGL_NV_robustness_video_memory_purge
There's also a healthy dose of bug fixes and other changes noted below:
- Fixed a bug that could cause the X server to crash when starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This functionality is now provided by other driver libraries.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are present when an NVIDIA NVSwitch device is detected in the system. Previously, nvidia.ko would fail to load into the kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes to a vertex shader would corrupt the interpolation qualifiers for the shader.
- Fixed a bug in the Vulkan driver where individual components of barycentric inputs could not be read.
- Fixed a bug where VK_NVX_binary_import was advertised as supported on unsupported platforms. This caused calls to vkCreateDevice to fail if applications attempted to enable VK_NVX_binary_import on such platforms.
- Added a new command line option, "--no-peermem", to nvidia-installer.Selecting this option prevents the installation of the nvidia-peermem kernel module.
- Fixed a regression which prevented DisplayPort and HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors from functioning correctly in variable refresh rate mode, resulting in issues such as flickering.
- Fixed a bug that can cause a kernel crash in SLI Mosaic configurations.
Since this is a stable driver release all users should be okay to upgrade.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
It's still not an install an go to get it working. You have to compile and install a couple dev version libraries to get it working. One is Xwayland. Forget about installing it on anything but the most bleeding edge rolling release distros. I would say it is still very much beta.470 seems to already be in Debian Testing / Sid. Only a matter of time until it is backported to Bullseye. Pretty sure it doesn't require bleeding edge, just wait for your distribution to package it.
Nvidia has the requirements listed here https://us.download.nvidia.com/XFree86/Linux-x86_64/495.44/README/xwayland.html
The xwayland with that commit is released now see https://www.gamingonlinux.com/2021/07/xwayland-2112-is-out-now-with-support-for-hardware-accelerated-nvidia-on-the-470-driver
I have now played several games on Ubuntu 21.10 with the 470 and 495 drivers and all had hardware accelerated graphics. On Gnome and Plasma.
What I had to do on Ubuntu 21.10 (and yammy the upcoming 22.04) was
enable DRM KMS either via inserting nvidia-drm.modeset=1 into grub or by creating a /etc/modprobe.d/zz-nvidia-modeset.conf file with that
Installing libnvidia-egl-wayland1
gsettings set org.gnome.mutter experimental-features [\"kms-modifiers\"]
and then just choosing either Ubuntu on wayland, or plasma on wayland before logging in.
For Debian Bullseye you would also need a newer xwayland and libnvidia-egl-wayland1 but they will maybe be available in backports too
Last edited by Redface on 4 November 2021 at 7:13 am UTC
0 Likes
LordDaveTheKind Dec 3, 2021
Driver 495.44 seems to have broken the RTX with VKD3D-Proton on Manjaro, in games such as The Ascent or Ghostrunner. Here a conversation in Reddit where we found the issue:
https://www.reddit.com/r/SteamPlay/comments/r3p9zc/comment/hmpoki2/?utm_source=share&utm_medium=web2x&context=3
https://www.reddit.com/r/SteamPlay/comments/r3p9zc/comment/hmpoki2/?utm_source=share&utm_medium=web2x&context=3
0 Likes
Patreon
PayPal
See more from me