595 release feedback & discussion

[aplattner]

Driver Details | NVIDIA

• Added support for the VK_EXT_descriptor_heap extension.
• Fixed a bug that caused GPU hangs and Xid errors in Black Myth: Wukong.
• Added support for DRI3 version 1.2.
• Added support for the VK_EXT_present_timing extension.
• Fixed hang when NVIDIA Smooth Motion is enabled in applications that use VK_KHR_present_id2.
• Modified nvidia.ko to handle video memory preservation on its own when the open kernel modules are in use if NVreg_UseKernelSuspendNotifiers=1 is enabled. When the proprietary driver is in use, or if kernel suspend notifiers are disabled, video memory preservation requires using the /proc/driver/nvidia/suspend interface for suspend and resume notifications.
• See the chapter titled “Configuring Power Management Support” in the README for more information.
• Enabled the nvidia-drm.ko modeset=1 parameter by default.
• Updated the driver to allow nvidia-smi to reset GPUs while nvidia-drm is loaded with the modeset=1 parameter enabled, as long as no other processes are using the GPU.
• Added a new application profile - CudaNoStablePerfLimit - that allows CUDA-using apps to reach P0 PState. See the ‘Application Profiles’ appendix of the driver README for details.
• 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 adaptive sync displays to go blank when connected with an active USB-C-to-HDMI adapter.
• Fixed a bug that could cause Vulkan swapchains to stop presenting new frames on X11.

[lytastic]

Is the hdr extension not included?

[faz]

installing and checking now. will edit this comment with results

edit: looks like its included. HDR working in MPV without the vk layer

ghost of tsushima also working great

[nvidia998]

The good news: HDR works without the layer.

@aplattner:
The bad news: this driver has the same bug as the new GRD 595.71 on Windows, which was fixed in Hotfix driver 595.76:

When the graphics card is overclocked, GPU voltage may become capped, preventing it from boosting to expected levels [5934973]

590.48.01-6: 3135 MHz

595.45.04-0: 2970 MHz

Please ignore that the scene is not the same, it doesn’t matter.

[Lastique]

@aplattner Is the 595.45.04 Linux driver affected by the issues of the 595 driver series on Windows? Specifically, GPU fans not spinning and low voltages preventing overclocking.

Edit: Apparently, the comment above by @nvidia998 already answered that (thanks).

[nvidia998]

The fans seem to work fine:

I also looked in my case to confirm.

Nvidia bug 5934973 is unrelated to fans.

[faz]

well hopefully we get a hotfix on the linux side too.

[airlinese]

Update on bug 5507242: it seems to be solved with newest nvidia-open 595.45.04 driver; steps described in original report here 580 release feedback & discussion - #248 by airlinese doesn’t reproduce the freeze on 5070ti mobile. (I don’t really use my 3060 mobile laptop anymore, so cannot test for it.)

[dinosaur]

It looks like v595 finally got the “exploding meshes” (bug 5649065) in Second Life fixed: I’m still stress-testing it, but so far could not reproduce this bug on my two most powerful PCs (RTX 5070 Ti and RTX 3070).

However, the Performance mode idle clocks are still broken (see the last paragraph in this post): by the way, do you have a ticket number for that bug ?

[wierzbiniak95]

I’ve been testing the new 595.45.04 driver, but unfortunately, several issues persist.

1. Screen recording on nvidia is still broken and only produces corrupted files (Plasma 6 .6.1).
   

   

2. When it comes to gaming via steam, I can hear the audio, but the screen is either completely black or flickering in one corner. Proton Experimental logs point to :

err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
info:  Presenter: Actual swapchain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Color space:  VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: no)
info:    Buffer size:  3440x1440
info:    Image count:  4

Age of Empires II DE (Black Screen):
steam-813780.tar.gz (305.5 KB)
Indiana Jones: The Great Circle (flickering)
steam-2677660.tar.gz (183.7 KB)

Games in the Heroic Games Launcher have stopped working altogether, crashing after Rockstar or Red Launcher initialize.

launch-Witcher3-Heroic-Flatpak.log (42.2 KB)
launch-Hogwarts-Legacy-Heroic-Flatpak.log (29.5 KB)

nvidia-bug-report.log.gz (780.6 KB)

[abchauhan]

@wierzbiniak95

Screen recording on nvidia is still broken and only produces corrupted files (Plasma 6 .6.1).

Hi @wierzbiniak95 , Have you received a NVIDIA tracking bug ID for this?

Games in the Heroic Games Launcher have stopped working altogether, crashing after Rockstar or Red Launcher initialize.

Is this a NVIDIA driver regression? What was the last passing driver version on your systems? Thanks

Hi @RyzenDew ,

Thank you for the report. Will check if we have any bugs for this. Does S.T.A.L.K.E.R 2 continue to crash on the 595 driver? We were tracking the S.T.A.L.K.E.R 2 issue on 5740841

[faz]

No change with bug ID 5374195 . Issues with Low Framerate Compensation (LFC) when using Gsync compatible Variable Refresh Rate (VRR)

Bug report originally filed here: 580 release feedback & discussion - #354 by amrits

Was claimed to have been checked with the team with no update: 590 release feedback & discussion - #241 by amrits

[luanv.oliveira]

@wierzbiniak95

Screen recording on nvidia is still broken and only produces corrupted files (Plasma 6 .6.1).

see Fix nvGetConfigAttributes by adding a missing check for entrypoint by xxmicloxx · Pull Request #423 · elFarto/nvidia-vaapi-driver · GitHub

[RyzenDew]

Re9 issue seems to be my arch install was fracked remove it from tracking also stalker 2 works again fully! wonderful job!

[DAUNTIN_01]

Black texture in borderland 2

discolored and Black textures on borderland pre-sequel

This was also on 590.48 drivers and stills presist to 595 drivers

nvidia-bug-report.log.gz (769.6 KB)

Edit: -notexturestreaming was the issue

[BlueGoliath]

List of issues that still affect the 595 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 universally lowers FPS and can cause 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?
• Dragging the HDR slider under Gnome can cause a driver crash(maybe fixed?).
• 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.
• 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 use dxvk.deviceFilter or in-game display adapter settings. Other times games start but run at 5 FPS.

• Fixed a bug that prevented the PowerMizer preferred mode dropdown menu in the nvidia-settings control panel from functioning correctly on Wayland.

There are zero NVML or nvidia-settings changes in 595 for this. Copy/paste error?

[Tekstryder]

@BlueGoliath

List of issues that still affect the 595 driver

You tested and confirmed all of those in just the past few hours? Wow!

You didn’t reference a single Nvidia internal bug tracking number in that list.

For each issue you encounter:

1. Submit an nvidia-bug-report after reproducing with the 595 driver.
2. Be sure to follow the bug reporting guidelines and attach your bug report in your post.

==== starts here ====
Reporting BUG

Synopsis:
Brief Description:
Steps to Reproduce and Frequency:
System Configuration: [System model][Operating System][Desktop Environment][GPU][Monitors - Model and Refresh Rates]
Linux Bug Report:
Additional details: [Screenshots, Screencapture, console output, logs or any details that can help with debugging]

====ends here ====

Perhaps consider opening a dedicated thread per unique issue and link to it from these general release-series discussion threads.

[gtschemer]

@BlueGoliath

List of issues that still affect the 595 driver:

Speaking as an embedded software engineer (though not for Nvidia, I just have an Nvidia card), this is a very unhelpful list. I encourage you to not post this list if you want items on it to be addressed, since it is unlikely to help as-is.

Since your post implies you tested all of these issues on 595, I am taking this in good faith and replying under that assumption. However, you mention that HDR is broken, yet multiple users have already reported HDR working in 595. This is a critical item, so you are strongly encouraged to mention which games HDR did not function for you.

I realize providing helpful feedback may be difficult for end users, so I am taking a moment to go through the bullet points in the hopes that it helps understand the sort of information that developers need to test and resolve issues.

General note: Your post did not include which distribution you used, nor which graphics card you are using to test, nor your system specifications, nor a Nvidia bug report archive file. This makes reproduction very difficult.

Specific items:

• 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.
  What is an “intensive game”? 1 or 2 specific examples tested with 595 would be extremely helpful, along with exactly which level and what you were doing in them. Which desktop environment, which distribution, a Nvidia bug report archive etc. would also be needed.

• Desktop memory usage is excessively high(over 2GB sometimes).
  What does this mean? Is is extremely common for memory usage on desktops to exceed 2GB on various operating systems. Are you talking about normal RAM or GPU RAM? It is very common for GPU memory usage to exceed 2GB. Is this during games? While sitting idle after a reboot? Do you have a screenshot of a system monitor breakdown of memory usage, or similar statistical dump that is common for such analysis? What does this have to do with an Nvidia driver if it’s referring to non-GPU memory?

• A large amount of GPU Memory is unaccounted for in nvidia-smi / NVML.
  I assume this has been previously discussed and you are unhappy with the answer. To engage with the issue in any productive way, a link to the previous thread(s) would be extremely helpful.

• Applications crash when VRAM is full.
  Which application did this with 595?

• 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.
  I assume this has been previously discussed. Again, linking the previous thread(s) for context would be extremely helpful for anyone trying to analyze this.

• DLSS3 / DLSS4 / Smooth Motion is broken. It universally lowers FPS and can cause massive input lag and micro stuttering.
  In which game was this observed with 595? Do you have screenshots of the stuttering with the feature on and off in 595?

• Gnome-shell / GDM can freeze on login from a fresh boot. Switching to a TTY and relogging in works around this.
  Did this occur in 595? Is it specific to Gnome or does it happen in KDE? Has it been reported and checked by Gnome developers at any point?

• Ray Tracing is broken on a lot of games, resulting in an XID 109 or some other error.
  Since there are a lot of games, what are 2 such games that produce XID 109 with driver 595?

• Some games show DLSS upscaling options but no frame generation(Portal 2: RTX). Maybe a Proton issue?
  Proton issues are likely outside the scope of the Nvidia driver. Has this been reported to the Proton team for analysis?

• Dragging the HDR slider under Gnome can cause a driver crash(maybe fixed?).

• DX12 games have a massive performance penalty.
  As you are no doubt aware, the 595 driver enabled a new interface which is under development for Proton. Since the vkd3d development effort is incomplete and unreleased, obviously its impact is not yet measurable.

• VRR causes backlight strobing/flickering
  Did this happen with previous versions before 580? Does this happen more or less with 595? Does it happen with both Gnome and KDE? What monitor model(s) exhibit it? What frame rate(s) exhibit it? Does it only happen during games, moving windows, or other specific circumstances?

• Shader cache doesn’t save properly, forcing it to be computing again.
  How was this tested with 595, and specifically with which games?

• Video decoding from a GTX 960 using Sunshine/Moonlight causes blocky artifacts.
  Were you using the GTX 960 in your other tests for 595?

• HDR is broken.
  Multiple user reports specifically reported that HDR started working with 595, without the need for any additional layers or hacks. Which graphics card and games still show broken HDR on your system? What is your monitor model? Is it only Gnome, or also KDE?

• Performance limiters are broken on Blackwell.

• PRAGMATA and other games have graphical glitches.
  What are the other games? What are the graphical glitches?

• 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 use dxvk.deviceFilter or in-game display adapter settings. Other times games start but run at 5 FPS.
  What are the models of primary and secondary GPUs? Did you try removing the secondary GPU and testing suing only the primary?

Hopefully these sorts of questions help users understand the thought process and information that engineers need.

[BlueGoliath]

Is that only an issue in specific areas? I loaded up a save on 590.48 and was not able to see it in Three Horns Divide.

I did get a crash about not enough VRAM when initially attempting to use Proton Experimental. Switching to Proton 10 got me in-game.