-
Added support for the following Vulkan extensions:
- VK_EXT_shader_long_vector
- VK_KHR_internally_synchronized_queues
- VK_NV_push_constant_bank
-
Added support for creating Vulkan logical devices from multiple physical devices on select cards via VK_KHR_device_group_creation. This feature can be enabled by setting the environment variable
__VK_ENABLE_DEVICE_GROUPS=1. -
Fixed a Vulkan performance regression in Doom: The Dark Ages introduced in the 590 driver series.
-
Improved performance in Starfield.
-
Added support for FP16 EGL framebuffer configurations on Wayland.
-
Added support for DRM format modifiers for multiplanar YCbCr formats.
-
Added support for mmap on DMABUF file descriptors exported from discrete NVIDIA GPUs.
-
Added support in the nvidia-drm kernel module for the per-plane DRM color pipeline API introduced in Linux v6.19. This allows Wayland compositors to offload color management (e.g. for HDR) to NVIDIA display hardware via the upstream
COLOR_PIPELINEplane property and associated colorops, in place of NVIDIAâs vendor-specific color properties.Some Wayland compositors may not yet correctly handle color pipelines that contain non-bypassable colorops, which can cause a blank screen (e.g. when enabling system HDR). A new âcolor_pipelineâ kernel module parameter has been added to nvidia-drm that may be used to disable DRM color pipeline support as a workaround on affected compositors. See the âWayland Known Issuesâ appendix of the README for further information.
-
Removed support for using the NVIDIA X11 driver with Xinerama.
-
Fixed a regression introduced in 580.65.06, that caused some mode timings, such as 1920x1080@75, to no longer be available.
-
Reverted a change that led to a user regression in 580.105.08 that caused display modes to be invalidated on a number of monitors.
Nvidia-powerd service causes microstutters still an issue. Note that Windows is fine, and freezing the nvidia-powerd process (keeping the power limit high while halting daemonâs activity) fully eliminates stutters, so itâs not related to the power consumption.
Forza Horizon 6 still crashing (Proton Experimental). Screenshot attached. I enabled Proton log (PROTON_LOG=1), but created a 9 gig log file with 84 million rows. (Good thing that i have 64 gigs of ram, just to open required 40 gig and all 20 cores.) I attached the start of the log and the end of the log, in between just spammed with warn:seh:dispatch_exception backtrace: â Exception 0xc000001d.
end_log.txt (161 KB)
start_log.txt (124.7 KB)
drm_info doesnât show COLOR_PIPELINE property.
$ uname -r
7.0.7-p1-gentoo-dist
$ cat /sys/module/nvidia_drm/parameters/color_pipeline
Y
Whatâs required for it to show up?
Just tried the new 610 drivers on Arch via nvidia-open-beta-dkms in the AUR. Enabling HDR and then launching any Steam game will immediately cause Kwin to crash and restart
nvidia-bug-report.log.gz (724.3 KB)
The weird blocky volumetric issue in The Last of Us 2 is still there as well:
In good news though, I am no longer getting Xid 109 errors when enabling /WineDetectionEnabled:False in Pragmata. I finally get raytracing woohoo!
Operating System: Arch Linux
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 64 GiB of RAM (62.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3090 w/ 610.43.02 drivers
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X870E AORUS ELITE WIFI7
i am seeing crashes and regressions in performance in some titles i am still gathering data i will update soon and confirm
Enabling HDR and then launching any Steam game will immediately cause Kwin to crash and restart
Thatâs almost certainly this issue, also mentioned in the release notes:
Some Wayland compositors may not yet correctly handle color pipelines that contain non-bypassable colorops, which can cause a blank screen (e.g. when enabling system HDR). A new âcolor_pipelineâ kernel module parameter has been added to nvidia-drm that may be used to disable DRM color pipeline support as a workaround on affected compositors. See the âWayland Known Issuesâ appendix of the README for further information.
Just to add, the color pipeline code was completely rewritten for kwin 6.7, and the issue doesnât happen there. A kwin dev is working on a patch for 6.6 (edit: backends/drm: don't attepmt to bypass non-bypassable colorops (!9278) · Merge requests · Plasma / KWin · GitLab).
We still get xid 79 fallen off the bus errors with LLM dense models and speculative decoding. The same model without speculative decoding works fine and has a similar temperature and memory usage profile.
It appears I can now run Satisfactory without Xid 109 timeout error and without any descriptor heap variables used. Actually if I enable descriptor heap it will still crash.
I still have micro-stutter in Rocket League, which might be this issue and internally tracked as Bug 5376205.
List of issues that still affect the 610 driver:
- Random black screens when playing intensive games, sometimes resulting in a partial GPU driver crash. It is sometimes possible to switch to a TTY, but attempting to switch back to a graphical session will crash the driver for good.
- Desktop memory usage is excessively high(over 2GB sometimes).
- A large amount of GPU Memory is unaccounted for in
nvidia-smi/ NVML. - Applications crash when VRAM is full.
- Shared RAM under Linux seems broken. Itâs almost like there is an incredibly small amount(256MB) and once thatâs gone things start crashing.
- DLSS3 / DLSS4 / Smooth Motion is broken. It causes massive input lag and micro stuttering.
- Gnome-shell / GDM can freeze on login from a fresh boot. Switching to a TTY and relogging in works around this.
- Ray Tracing is broken on a lot of games, resulting in an XID 109 or some other error.
- Some games show DLSS upscaling options but no frame generation(Portal 2: RTX). Maybe a Proton issue?
- DX12 games have a massive performance penalty.
- VRR causes backlight strobing/flickering.
- Shader cache doesnât save properly, forcing it to be computing again.
- Video decoding from a GTX 960 using Sunshine/Moonlight causes blocky artifacts.
- HDR is broken.
- Performance limiters are broken on Blackwell.
- PRAGMATA and other games have graphical glitches(maybe fixed?).
- Using a secondary dedicated GPU often fails with
[drm:__nv_drm_gem_nvkms_prime_dup [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000c00] Failed to import NVKMS memory to GEM object. This error can happen regardless of whether you usedxvk.deviceFilteror in-game display adapter settings. Other times games start but run at 5 FPS. - Display sometimes fails to wakeup from sleep unless switched to TTY.
Do you even bother to re-test all of those every release? Or are you just shotgun blasting the list every time in hopes someone will pull an all-nighter and fix whatever?
Donât bother, theyâve never seriously reacted to any engagement. Itâs just some weird ritual at this point, and the only thing we can do is to point out all over that this list is next to useless whenever it gets posted again, so that new readers donât get confused.
Direct Scanout (KDE) still broken on hybrid laptop with (amd + nvidia)
Wish, someone from nvidia can actually look into it.
- Added support for DRM format modifiers for multiplanar YCbCr formats
I thought this would fix it, but it didnât
Xid 109: The problem persists. NVIDIA is clearly showing that they have no regard for quality standards; theyâre just blindly churning out drivers in the hope that something will work.
Itâs really unfortunate that the few showstopper issues donât seem to get the attention they need.
Itâd be great if we could get some insight into the issues being worked on, other than just few nondescript things.
Imagine a public bug-tracker⊠;-]
Update to this issue: After Trying again on Fedora 44 with a v4 lto kernel the only broken title is Halo infinite i went from 100fps down to 56 fps and the game crashes the driver . i will add a log soon.
Seems like the issue of XID109 when Drones get shot in Forever Winter is resolved. Will keep testing but havent been able to reproduce.
MH Wilds doesnt even launch if Descriptor Heap is enabled with VKD3D but works fine without it. Seems most of my games are currently working for the most part on this driver.