Join us on our own very special Reddit: /r/Linuxers

NVIDIA continue to fix up and improve their Linux drivers, with a brand new Vulkan Beta Driver available today.

This is the testing area where NVIDIA put in new features, add in new Vulkan API support like the provisional vendor-neutral Ray Tracing that went in recently and more that eventually make their way into their normal drivers. Here's the highlights of the Linux 440.66.07 driver:

  • New:
    • Multi thread-capable deferred ray tracing pipeline creation
    • Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces [Linux]
  • Fixes:
    • Added a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory [Linux]
    • Correctly cap the drawCount for vkCmdDrawIndirectCount and vkCmdDrawIndexedIndirectCount on Turing GPUs
    • Fixed descriptor indexing with large arrays and large blocks

You can see the Vulkan Beta Driver on the NVIDIA website. Only use them if you want to test the very latest stuff. You can tell they're the Beta drivers by the extra two digits in the version number.

Note: The newest stable version of the NVIDIA drivers for Linux is 440.64 that released on February 28.

Article taken from GamingOnLinux.com.
15 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more here.
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
19 comments
Page: 1/2»
  Go to:

Kithop 1 April 2020 at 7:10 pm UTC
Not sure if this will include fixes to get their DKMS garbage to compile right against kernel 5.6, but if not, I've had some luck with this patch someone else figured out:

NVIDIA 440.64 - Kernel 5.6

(e.g. for Gentoo users, just grab that raw and drop it in as /etc/portage/patches/x11-drivers/nvidia-drivers-440.64/linux-5.6-compatibility.patch , then re-emerge x11-drivers/nvidia-drivers )

I still regret buying a GTX 980 years ago, now that AMDGPU exists, but still.
Luke_Nukem 1 April 2020 at 9:48 pm UTC
Is there a PPA for beta drivers in Ubuntu? I've relied on packaged driver for so long I've forgotten the basics
poke86 1 April 2020 at 10:07 pm UTC
View PC info
  • Supporter
The way I do it (xubuntu):

- Download the driver
- chmod +x on the package
- log into to tty1, run > sudo service lightdm stop
- launch the package, follow the instructions
- sudo service lightdm start

there you go, there's a chance you might have to do it again next time you update you kernel.

I'm getting 120+ FPS @ 1440p Ultra Nightmare settings now (RTX 2080)
Luke_Nukem 2 April 2020 at 1:06 am UTC
I was able to purge nvidia drivers through apt, and install manually. Also able to keep prime-select to enable gpu offload and power savings, so that's good.

I was kind of hoping this driver might have an impact on Wreckfest performance, and it looks like it definitely did - so the D:E fix might have an impact on other games too.
Alm888 2 April 2020 at 7:54 am UTC
QuoteAdded a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations
Wait, WHAT?!
In other words, "DOOM Eternal" has instructions to specifically place resources in system RAM instead of VRAM if ran on Linux? I mean, Windows® users do not encounter the "resources are in RAM" issue, that mean developers deliberately wrote the application to misbehave on Linux. That's a sabotage!
pete910 2 April 2020 at 8:36 am UTC
View PC info
  • Supporter
  • Top Supporter
Alm888
QuoteAdded a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations
Wait, WHAT?!
In other words, "DOOM Eternal" has instructions to specifically place resources in system RAM instead of VRAM if ran on Linux? I mean, Windows® users do not encounter the "resources are in RAM" issue, that mean developers deliberately wrote the application to misbehave on Linux. That's a sabotage!



How you come to that conclusion when it's fine on AMD in linux.

Think you need to take the tin foil off
Xakep_SDK 2 April 2020 at 8:52 am UTC
Alm888
QuoteAdded a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations
Wait, WHAT?!
In other words, "DOOM Eternal" has instructions to specifically place resources in system RAM instead of VRAM if ran on Linux? I mean, Windows® users do not encounter the "resources are in RAM" issue, that mean developers deliberately wrote the application to misbehave on Linux. That's a sabotage!
Windows driver works bit different in some aspects, game relies on windows behavior. It's likely unintended id fault.


Last edited by Xakep_SDK on 2 April 2020 at 9:02 am UTC
pete910 2 April 2020 at 10:44 am UTC
View PC info
  • Supporter
  • Top Supporter
I say more like a NV driver issue or AMD/Intel would have had to do same.
mirv 2 April 2020 at 11:29 am UTC
View PC info
  • Supporter
  • Top Supporter
pete910I say more like a NV driver issue or AMD/Intel would have had to do same.

I recall something about the way nvidia reports memory capabilities differing between GNU/Linux and Windows, or at the very least performance impacts differing about what is reported. Possibly the GPU and host visible memory regions - the OS will handle it differently, hence why it's fine under Windows but not under GNU/Linux.
AMD architectures work a little different and the particular combination of their memory configurations and what is reported through Vulkan mean it isn't such a problem in this particular case.

Intel don't really have discrete cards yet, so bypass this entire problem; host and GPU memory is the same.

Just a guess based on what I've read about and heard of before, particularly with nvidia for whatever reason. Memory management like this can be a pain, and it's no longer hidden by drivers.
rstrube 2 April 2020 at 3:54 pm UTC
For those of you trying to make the beta driver work with kernel 5.6.x, you'll need to apply a patch to Nvidia's module code in order for it to compile.

I found this which was able to help me get it up and running on Fedora 32 (running kernel 5.6). https://gitlab.com/snippets/1945940

Nice performance improvements overall, he's hoping that the updates make their way into a stable driver release soon!
While you're here, please consider supporting GamingOnLinux on Patreon, Liberapay or Paypal. We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!

You need to Register and Login to comment, submit articles and more.


Or login with...

Livestreams & Videos
None currently, submit yours here!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts