You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

NVIDIA today launched four new stable Linux graphics drivers, yes four. 545.29.02 is the bigger one with all the new stuff, but they also launched 535.129.03, 525.147.05 and 470.223.02 due to newly disclosed security issues.

So it's a good time to make sure you're up to date to stay secure. From their security bulletin released today all drivers prior to 545.29.02, 535.129.03, 525.147.05 and 470.223.02 are vulnerable so be sure to use those versions at a minimum going forward.

For normal desktop users the problem reported is CVE‑2023‑31022 that notes "NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service". The rest are just Windows issues and for VGPU.

As for the release notes find them below.

545.29.02:

  • Added experimental HDMI 10 bits per component support; enable by loading nvidia-modeset with `hdmi_deepcolor=1`.
  • Added support for the CTM, DEGAMMA_LUT, and GAMMA_LUT DRM-KMS CRTC properties. These are used by features such as the "Night Light" feature in GNOME and the "Night Color" feature in KDE, when they are used as Wayland compositors.
  • Added CERTIFIED-quality support for GeForce and Workstation GPUs to open kernelmodules. Please see the "Open Linux Kernel Modules" chapter in the README for details.
  • Added initial experimental support for runtime D3 (RTD3) power management on Desktop GPUs. Please see the 'PCI-Express Runtime D3 (RTD3) Power Management' chapter in the README for more details.
  • Added support for the EGL_ANDROID_native_fence_sync EGL extension and the VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT and VK_EXTERNAL_FENCE_HANDLE_TYPE_SYNC_FD_BIT Vulkan external handle types when the nvidia-drm kernel module is loaded with the modeset=1 parameter.
  • Added experimental support for framebuffer consoles provided by nvidia-drm. On kernels that implement drm_fbdev_generic_setup and drm_aperture_remove_conflicting_pci_framebuffers, nvidia-drm will install a framebuffer console when loaded with both `modeset=1` and `fbdev=1` kernel module parameters. This will replace the Linux boot console driven by a system framebuffer driver such as efifb or vesafb.
    Note that when an nvidia-drm framebuffer console is enabled, unloading nvidia-drm will cause the screen to turn off.
  • Updated nvidia-installer to allow installing the driver while an existing NVIDIA driver is already loaded.
  • Added support for virtual reality displays, such as the SteamVR platform, on Wayland compositors that support DRM leasing. Support requires xwayland version 22.1.0 and wayland-protocols version 1.22, or later. Tested on sway, minimum version 1.7 with wlroots version 0.15, and also on Kwin, minimum version 5.24.
    Note: Before xwayland 23.2, there is a known issue with HDMI displays where the headset will fail to start a second time after closing SteamVR. This can be worked around by unplugging and replugging in the headset.
  • Fixed a bug that prevented VRR (Variable Refresh Rate) from working with Wayland.
  • Added support to the NVIDIA VDPAU driver for running in Xwayland. Please refer to the "Xwayland support in VDPAU" section of the README for further details.
  • Added libnvidia-gpucomp.so to the driver package. This is a helper library used for GPU shader compilation.
  • Removed libnvidia-vulkan-producer.so from the driver package. This helper library is no longer needed by the Wayland WSI.
  • Fixed a bug that intermittently caused the display to freeze when resuming from suspend on some Ada GPUs.
  • Fixed a bug that could cause monitors to flicker when the performance state changes on Turing GPUs.
  • Added support for HDR signaling via the HDR_OUTPUT_METADATA and Colorspace per-connector DRM properties when nvidia-drm is loaded with the `modeset=1` parameter.
  • Added support for PRIME render offload to Vulkan Wayland WSI.
  • Fixed a bug that could cause modes to fail validation when Option "ModeValidation" "NoExtendedGpuCapabilitiesCheck" is specified in xorg.conf.
  • Fixed a bug which could cause some DisplayPort monitors to flicker.

535.129.03:

  • Fixed a bug that could cause modes to fail validation when Option "ModeValidation" "NoExtendedGpuCapabilitiesCheck" is specified in xorg.conf.
  • Fixed a bug that could cause GPU memory utilization to be reported incorrectly for Multi-Instance GPU (MIG) partitions on Grace Hopper systems.
  • Fixed a bug that intermittently caused the display to freeze when resuming from suspend on some Ada GPUs.
  • Fixed a bug which could cause some DisplayPort monitors to flicker.
  • Fixed a bug that could cause monitors to flicker when the performance state changes on Turing GPUs.

525.147.05:

  • Fixed a bug which could cause some DisplayPort monitors to flicker.
  • Fixed a bug which prevented DKMS from registering kernel modules.
  • Fixed a bug that could cause monitors to flicker when the performance state changes on Turing GPUs.
  • Fixed a bug which caused incorrect reporting of presentation times when using the VK_NV_present_barrier Vulkan extension.

470.223.02:

  • Fixed a bug which caused incorrect reporting of presentation times when using the VK_NV_present_barrier Vulkan extension.
Article taken from GamingOnLinux.com.
9 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
13 comments
Page: «2/2
  Go to:

Pikolo Nov 1, 2023
Quoting: DMGHow can I install specific driver version? I somehow see only version 535.113.01
 
user@pop-os:~$ sudo apt search "NVIDIA driver metapackage"
Sorting... Done
Full Text Search... Done
mir-graphics-drivers-nvidia/jammy 2.7.0-0ubuntu3 amd64
  Display server for Ubuntu - Nvidia driver metapackage

nvidia-driver-390/jammy-security,jammy-updates 390.157-0ubuntu0.22.04.2 amd64
  NVIDIA driver metapackage

nvidia-driver-470/jammy 470.199.02-1pop0~1695931040~22.04~4c2d0ee amd64
  NVIDIA driver metapackage

nvidia-driver-535/jammy,now 535.113.01-1pop0~1695753528~22.04~0561f9e amd64 [installed]
  NVIDIA driver metapackage

user@pop-os:~$ 
It's not in the Ubuntu repo yet - production Nvidia drivers do break stuff, so on Ubuntu they go through phased rollouts. Additionally, for new major versions a new package will be created, and it hasn't been yet https://packages.ubuntu.com/search?suite=default&section=all&arch=any&keywords=nvidia-driver&searchon=names It will be in Ubuntu in 3-5 days if it's not breaking anything for beta testers.

The nvidia drivers beta-testing repo got a build 4 hours ago https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

I strongly discourage updating Nvidia drivers outside of your distribution's preferred channel. It's not easy to fix your mistakes if you're doing this for the first time.

Edit: 535.129.03 is now in the Ubuntu Jammy repository - I think PopOS is built on Ubuntu LTS and Jammy is the current LTS. 545 is not in yet


Last edited by Pikolo on 3 November 2023 at 8:15 am UTC
adolson Nov 4, 2023
"Updated nvidia-installer to allow installing the driver while an existing NVIDIA driver is already loaded."

FINALLY!!!!!!!!! It's almost 2024, what took so bloody long? (I had a memory of, way back in the day, a flag that would skip that check, but couldn't find it last I checked so maybe I'm wrong).
Alpha-Craft Dec 3, 2023
I have tried the new NVIDIA 545 driver on my Fedora machine, but the entire desktop and all apps felt sluggish. It's fairly inconsistent, but is very noticeable and annoying. I had to downgrade back to 535. Therefore, the driver with possible fix to my Horizon Zero Dawn freezing is not currently installed. Right now, I can run the game for a few minutes, until it freezes with an xid 31 error in dmesg. I have heard that others also found the driver to be buggy. Why does the new driver have to be this unstable?
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.