NVIDIA have released the first Beta for the 580 driver series, with NVIDIA Beta driver 580.65.06 bringing mostly bug fixes. There's also an additional bit of Wayland protocol support included.
Since this is a Beta driver, it's not recommended just yet for everyday use. You'll want to be quite up to date though, with NVIDIA recently revealing more security issues in their drivers.
Highlights from the driver:
- Fixed a bug that could cause Vulkan applications to hang when destroying swapchains after a lost device event.
- Fixed a bug that could allow atomic commit and other DRM operations to return success status despite having failed due to handling an interrupt: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/832
- Fixed a bug that could cause GTK 4 applications to crash when using the Vulkan backend on Wayland.
- Fixed a bug that could intermittently cause llama.cpp to crash on exit when using the Vulkan backend: https://github.com/ggml-org/llama.cpp/issues/10528
- Added support for the fifo-v1 Wayland protocol on Vulkan.
- Updated GPU clock value reporting in nvidia-settings, NVML, and nvidia-smi to show clocks before thermal and idle slowdowns for better consistency with the equivalent functionality on Windows.
- Fixed compatibility with Bigscreen Beyond Head Mounted Displays.
- Fixed a bug that could result in a black screen when setting specific modes on HDMI displays.
- Fixed a bug that caused blank or frozen screens under the following conditions: nvidia-drm is loaded with the modeset=1 and fbdev=1 parameters, using a Maxwell or Pascal series GPU, and more than one display device of differing resolutions are connected.
- Fixed a bug that caused nvidia-suspend.service to fail when available system memory is low.
- Enabled RMIntrLockingMode by default. This feature can help reduce stutter especially when using virtual reality. This feature was originally introduced in the r570 series. It can be disabled by loading nvidia.ko with the `NVreg_RegistryDwords=RMIntrLockingMode=0` kernel module parameter.
- Implemented another feature that can reduce time spent in the interrupt top half for low latency display interrupts by deferring the work until later. This feature is experimental and disabled by default. This feature can be enabled by loading nvidia.ko with the `NVreg_RegistryDwords=RmEnableAggressiveVblank=1` kernel module parameter.
- Fixed a bug that could cause blank rendering on some single-buffered GLX applications when running on Xwayland.
- Fixed a bug that could cause a kernel use-after-free on pre-Turing GPUs.
- Fixed a bug that could cause OpenGL applications and compositors to stall when using NVIDIA as a PRIME Display Offload sink ("Reverse PRIME"), potentially resulting in a black screen.
- Fixed a bug that led to increasing memory usage in X11 OpenGL and Vulkan applications after suspend/resume cycles.
- Fixed a bug that could cause 32-bit x86 applications running on recent builds of glibc to crash on dlopen().
Source: NVIDIA
Some you may have missed, popular articles from the last month:
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.
No dx12 perf gains or losses from quick testing of UE5 game(StarRupture playtest) and Cyberpunk.
Cant complain about perf though. Seems to be close enough to windows for me at least.
Well they didn't mention anything about vkd3d-proton or dx12 in the changelogs either so i guess that was obvious.
5800X3D, RTX 3080, Arch Linux, MATE Desktop.
Cant complain about perf though. Seems to be close enough to windows for me at least.
Well they didn't mention anything about vkd3d-proton or dx12 in the changelogs either so i guess that was obvious.
5800X3D, RTX 3080, Arch Linux, MATE Desktop.
0 Likes
Some of those look like they're finally addressing some of the VR issues that have been causing major problems for over a year now.
0 Likes