Support us on Patreon
PayPalIt seems to be a busy weekend! NVIDIA have put out a new version of their Vulkan beta driver and it's an interesting one.
Today, NVIDIA 415.22.05 became available and as expected of this driver series it adds in new Vulkan extensions. Specifically, it adds support for VK_KHR_depth_stencil_resolve, VK_EXT_buffer_device_address, VK_EXT_memory_budget, VK_EXT_memory_priority (only for Windows currently) and VK_EXT_pci_bus_info.
The extra interesting bit is the improvement they listed in this driver version. They mention that it has "Better pipeline creation performance when there is a cache hit" so it will be an interesting driver to test out. Good to see NVIDIA continue working on performance!
Find the driver info here.
For those on Ubuntu wishing to test out the beta driver, there is this PPA which sadly hasn't been updated since October last year. Hopefully they will get moving on that sometime soon. I'm unsure how other distributions handle beta drivers like this, hopefully they make it easy.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
I still wonder why they don't go the AMD way and share development of the base driver with the opensource community.
Would make the proprietary part smaller and easier to maintain and make the OS enthusiasts happy.
Is there any convincing reason why the signed firmware is held back?
Would make the proprietary part smaller and easier to maintain and make the OS enthusiasts happy.
Is there any convincing reason why the signed firmware is held back?
3 Likes, Who?
Quoting: tpauI still wonder why they don't go the AMD way and share development of the base driver with the opensource community.
Would make the proprietary part smaller and easier to maintain and make the OS enthusiasts happy.
Is there any convincing reason why the signed firmware is held back?
Because their ********
0 Likes
nVidia drivers are bad quality which is likely the main reason why they do not open up the code. I'm frustrated on their drivers as they force the card to run on maximum power for 45 seconds every time there's an opengl draw call. Basically it means that if you install Ubuntu and use default Gnome (which uses opengl X composite extension), your graphics card never goes into powersave state and consumes ~4x more power than it should. They have the same issue in Windows, but because of architectural differences it's not as bad in there.
I guess they do that because of nobody has bothered to implement proper power saving feature and because of not running the card in maximum power makes the cards to look bad in benchmarks. IMHO they really should fix the issue and allow cards to run on optimal clocks as laptops get more and more common. :)
I guess they do that because of nobody has bothered to implement proper power saving feature and because of not running the card in maximum power makes the cards to look bad in benchmarks. IMHO they really should fix the issue and allow cards to run on optimal clocks as laptops get more and more common. :)
3 Likes, Who?
Quoting: tpauI still wonder why they don't go the AMD way and share development of the base driver with the opensource community
Because it's Nvidia. Their managements are jerks and don't get what open source collaboration is. Otherwise they would have opened their kernel driver already.
0 Likes
Quoting: GuestI'm waiting the new AMD RX3000 graphics cards and I'll be done with Nvidia and their'e proprietary drivers.
More or less same here.
We might also have the Intel gaming GPU as a choice in the future.
1 Likes, Who?
Avehicle7887 Jan 6, 2019
I see many people saying Nvidia drivers are bad etc without mentioning a few key points. Sure they are closed source and not as friendly as others in the Linux world but:
- They've offered Linux support for a long time, I still remember NV drivers back when Ubuntu was all the rage (Ubuntu 10.04 etc).
- Performance of their drivers is competitive, and it took a while for (Mesa) AMD to catch up (and now sometimes perform better).
- They have contributed fixes to their drivers to help with DXVK.
- Their drivers can be used on some old distros without too much fuss, not something you can easily do with OSS ones.
I'm not saying they are perfect either, the crappy Prime support on mobile GPUs is why I don't buy laptops with NV GPUs, I'd rather have Intel HD if no AMD alternative is available. However they are far from the bad quality type that some people make them out to be.
- They've offered Linux support for a long time, I still remember NV drivers back when Ubuntu was all the rage (Ubuntu 10.04 etc).
- Performance of their drivers is competitive, and it took a while for (Mesa) AMD to catch up (and now sometimes perform better).
- They have contributed fixes to their drivers to help with DXVK.
- Their drivers can be used on some old distros without too much fuss, not something you can easily do with OSS ones.
I'm not saying they are perfect either, the crappy Prime support on mobile GPUs is why I don't buy laptops with NV GPUs, I'd rather have Intel HD if no AMD alternative is available. However they are far from the bad quality type that some people make them out to be.
17 Likes, Who?
This driver comes with vulkan 1.1.96
Cuphead still working (unity games)
^_^
Cuphead still working (unity games)
^_^
1 Likes, Who?
Quoting: mahagrnVidia drivers are bad quality which is likely the main reason why they do not open up the code.
And you base your assumptions on what exactly?
5 Likes, Who?
Quoting: ShmerlBecause it's Nvidia. Their managements are jerks and don't get what open source collaboration is.
So you had an interview with somebody from the Nvidia management?
6 Likes, Who?
I get that people are not happy with the way NVidia is handling things for Linux, but name calling and assuming that their engineers are amateurs is just cheap talk and usually gets you nothing. They do things the way it fits for them, for quite some people this workflow and choices seems to work too. If you don't like their way, just move on.
Back on topic: "Better pipeline creation performance when there is a cache hit" sounds indeed interesting, I would be curious to know how much performance win it yields in real life scenarios.
Back on topic: "Better pipeline creation performance when there is a cache hit" sounds indeed interesting, I would be curious to know how much performance win it yields in real life scenarios.
6 Likes, Who?
See more from me