Support us on Patreon
PayPalGet ready to upgrade your NVIDIA drivers once again, as NVIDIA has today rolled out the 465.24.02 stable driver.
This is not to be confused with the Vulkan Beta 455.50.12 that rolled out yesterday that's aimed at developers and serious enthusiasts. This is a stable driver release that you should be okay to upgrade with. Most of this 465.24.02 driver is following on from the 465.19.01 Beta that was released back in March.
It brings in new Vulkan extension support including:
- VK_KHR_synchronization2
- VK_KHR_workgroup_memory_explicit_layout
- VK_KHR_zero_initialize_workgroup_memory
Plus the nvidia-settings panel should be "more consistent about displaying layout controls which are only applicable for some displays or GPUs connected to the system". There's also "runtime D3 Power Management is now enabled by default on supported notebook systems with Ampere or newer", the NVIDIA X driver will now allow "OpenGL applications running on an X server that has left the active virtual terminal (VT) to continue running on the GPU, but with a limited frame rate", support for both the RTX A4000 / RTX A5000 and there's quite a few bug fixes too - here's the list:
- Fixed a bug that could prevent some hardware configurations with large numbers of displays connected to the same GPU from working correctly.
- Fixed a bug that could cause multi-threaded GLX applications to hang while attempting to handle an XError.
- Fixed a potential crash in the Vulkan driver when clearing images with multiple layers.
- Fixed a bug with the host-visible device-local memory heap, where if an allocation failed due to space constraints, it could cause the application to crash on future Vulkan function calls.
- Fixed corruption in the Vulkan driver that sometimes occurred with shadow rendering with image arrays.
- Fixed an issue with OpenGL where imported Vulkan buffers would fail with GL_OUT_OF_MEMORY when marked as resident.
- Fixed a bug that caused the NVIDIA driver to retain an incorrect memory mapping of the UEFI system console when booting with the kernel parameter pci=realloc. This could cause the console to corrupt memory in use by the NVIDIA driver, and vice versa.
- Fix a Vulkan clamping bug where fragment depth values would not be clamped to the range [0,1] if VK_EXT_depth_range_unrestricted was not enabled.
- Fix a bug related to SPIR-V 1.4 non-Input/Output entry point variables.
- Fixed a bug in compilation of SPIR-V intersection shaders when modules with multiple entry points are used.
Full announcement can be found here.
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.
8 comments
Comandante Ñoñardo Apr 14, 2021
hmmm.
The release of the Metro Exodus port and the release of this driver maybe is not a coincidence.
The release of the Metro Exodus port and the release of this driver maybe is not a coincidence.
1 Likes, Who?
Just in time for Metro Exodus... if that even matters :)
xpander@archlinux ~ $ nvidia-smi -q | grep Version
Driver Version : 465.24.02
CUDA Version : 11.3
1 Likes, Who?
I hope it updates quickly in Debian 11, because the truth is that these drivers have great improvements. Not to mention that it has a more recent version of Vulkan and not 1.2.155
1 Likes, Who?
In my case works ok with dxvk 1.8.1 and come with same 1.2.168 vulkan version present in before 465 beta driver
3 Likes, Who?
GeoGalvanic Apr 15, 2021
Plus the nvidia-settings panel should be "more consistent about displaying layout controls which are only applicable for some displays or GPUs connected to the system".
I swear that entire panel needs a major overhaul. I think this is the first time they've touched it in literally years though, so... fingers crossed?
0 Likes
I swear that entire panel needs a major overhaul. I think this is the first time they've touched it in literally years though, so... fingers crossed?
pls no! nvidia-setings is pretty good imo, we don't need a bloat or moderninzation of the GUI.. its nice atm. i saw some screenshots what they have on windows and its just awful, so please no.
2 Likes, Who?
Comandante Ñoñardo Apr 16, 2021
I swear that entire panel needs a major overhaul. I think this is the first time they've touched it in literally years though, so... fingers crossed?
pls no! nvidia-setings is pretty good imo, we don't need a bloat or moderninzation of the GUI.. its nice atm. i saw some screenshots what they have on windows and its just awful, so please no.
But it allow you to have per game settings in an easy way... On Linux you can't.
Is not about the aspect, is the functionality.
1 Likes, Who?
I swear that entire panel needs a major overhaul. I think this is the first time they've touched it in literally years though, so... fingers crossed?
pls no! nvidia-setings is pretty good imo, we don't need a bloat or moderninzation of the GUI.. its nice atm. i saw some screenshots what they have on windows and its just awful, so please no.
But it allow you to have per game settings in an easy way... On Linux you can't.
Is not about the aspect, is the functionality.
per game settings are there for the nvidia-settings also, but yeah i agree its not the most straight forward. could use overhaul there ofc.. but other than that i think the linux version of the settings is much more readable.
ofc more options would be nice but overhaul the whole gui is not what i would wish for. if you look into all the modern GUI designs these days its just
0 Likes
See more from me