- Raised the minimum supported Wayland version to 1.20.
- Fixed a bug that prevented the PowerMizer preferred mode dropdown menu in the nvidia-settings control panel from functioning correctly on Wayland.
- Raised the minimum supported glibc version to 2.27.
- Improved the performance of recreating Vulkan swapchains. This helps prevent stuttering when resizing Vulkan application windows.
- Raised the minimum supported X.Org xserver version to 1.17 (video driver ABI version 19).
- Fixed a bug that caused the Dots Per Inch (DPI) to be incorrectly reported for some monitors such as the Samsung Odyssey Neo G9.
- Fixed several problems that prevented Vulkan applications from working on Venus VirtIO virtual GPU.
- Fixed a bug that could cause system freezes on
PREEMPT_RTkernels.
4 Likes
Thank you for the updoot. DX12 bros, our day will come eventually.
Edit: I will compare 585 in Wukong later today, but I am not expecting an improvement.
2 Likes
Sadly, this new version still suffers from the same show stopper bug (corrupted mesh vertices coordinates under OpenGL after a while) as v580. See: 580 release feedback & discussion - #765 by dinosaur
Also, the driver still fails to respect the Performances mode clock settings and lowers the clocks to a few hundreds MHz when idle while they should stay above 2400MHz (as they do with v575 and older drivers). See: 580 release feedback & discussion - #353 by dinosaur
nvidia-bug-report.log.gz (664.2 KB)
Back again to 575.64.05 for me.
1 Like
The Supported Products tab on the driver release page still lists Maxwell as supported, even though these are now only supported by the legacy driver.
1 Like
Thanks for noticing that. I’ll make sure that gets updated.
2 Likes
The issue mentioned here is still very much around - I do think it has improved somewhat, maybe because of the DPI fixes? I experience similar flickering on desktop with Samsung Odyssey G934S at 5K@240Hz. The flickering of the bottom-right side seems to be a tad random, but easily reproduced by minimizing and maximizing a window.
There’s also some initial black screen flickering when starting full-screen native or Proton games which enable G-Sync / Adaptive sync. This behaviour seems to be less pronounced with the newest 590 drivers. Here are my logs:
nvidia-bug-report.log.gz (723.9 KB)
1 Like
please tell me the GSP issue on Legion laptops is fixed…
also not sure to understand why a major release for bug fixes?
I tested 590, and bugs, that I mention here and Path of Exile 2 ( tracking number `5507517’ ) still reproducible on my end at least.
In case if any NVIDIA developer has been assigned to flickering issues, the comment from the Wayland Proton developer may provide useful.
nvidia-bug-report.log.gz (1.1 MB)
Stalker 2 now crashes when going in game
Monster Hunter Wilds is still broken
i will add more issues later ( Reserved )
4 Likes
The Supported Products tab also still shows Pascal. Is this also incorrect? Based on the deprecation schedule, 580 was the last for their support.
Yup, it simply is incorrect and the list needs to be updated.
See
1 Like
Is there a reason this couldn’t have been fixed in 580 a long time ago?
3 Likes
Also, the driver still fails to respect the Performances mode clock settings and lowers the clocks to a few hundreds MHz when idle while they should stay above 2400MHz (as they do with v575 and older drivers). See: 580 release feedback & discussion - #353 by dinosaur
It has done that for years, it’s just very weird. I think laptop users were complaining about high clocks so they changed something and broke it.
I’m speaking about desktop graphics card, not about laptop GPUs, and none of the drivers ever idled at low clock frequency in performances mode for any of my cards before v580 came out !
And FYI, I have been using NVIDIA Linux drivers for 20 years, with 9 different card models…
1 Like
This driver does not appear to include the Vulkan HDR metadata or present timing extensions that were present in the 580.94.11 Vulkan Beta driver. Will the stable 590 include the VK_EXT_hdr_metadata and VK_EXT_present_timing extensions?
3 Likes
no need to cashout at the devs, the fix needs a new Vulkan extension that is in such early development that it isn’t even public yet, accounting for the time it would take for the extension to be finished + published, nvidia to implement it on their driver and vkd3d to implement it as well, i wouldn’t count on it getting released in the next ~6 months to 1,5 years
1 Like
Why is there no DX12 FIX?! how long has this been a God Da*n issue?! You guys have been talking about this fix FOR MONTHS!!! NeXt MaJoR rElEaSe
AND YALL CANT BE BOTHERED TO FIX THE SINGLE BIGGEST DRIVER ISSUE YOU HAVE HAD FOR LITERALLY YEARS! I stg my next card will be AMD this is honestly pathetic
And before anybody comes at me for being over the top. No. This is flat out ridiculous. I’ve been patient and quiet and haven’t said anything while I (and everyone else) has had to cope with the fact that our hard earned Nvidia cards perform worse in current games. There’s no reason high end hardware should perform like mid range hardware. It’s not acceptable. RTX 5090 being outperformed CONSISTENTLY by an RX 9070 XT in DX12 games. Every release that doesn’t have this performance fix is a slap in the face of every Nvidia customer who uses Linux.
Nvidia and it’s lack of action is the single biggest thing holding back Linux. Because they refuse to fix the issues that matter and keep fixing the minor problems rather than tackling the ones that actually make everyone have a worse experience.
Enough is enough.
590 beta driver not bringing one damn new feature worth writing home about.
You think you’re angry? Try going a month without your GPU between 2 RMAs, one of which you had to pay out of pocket for because of shipping, only to find out the issues were driver bugs.
And then, on top of that, have Nvidia’s employees go out of there way to ignore your bug reports and threaten you with a forum ban for mild expressions of anger.
Your anger is nothing. Trust me.
1 Like
Nvidia could have and should have communicated what the issue was a long time ago. Just like the VRAM issues.
4 Likes