autotldr@lemmings.world
on 06 Mar 2024 18:00
nextcollapse
This is the best summary I could come up with:
Previously the open-source (out-of-tree) kernel modules were just certified for their data center GPUs while now they are basically acknowledging that they are in good shape too for GeForce and workstation products.
It was back in May 2022 that NVIDIA announced their open-source GPU kernel driver plans for Turing GPus and newer.
Since then they’ve continued advancing this out-of-tree code that is bundled as part of their distributed driver package.
NVIDIA’s open kernel modules option is NOT to be confused with the upstream open-source Nouveau driver effort.
But there are some known limitations in the open kernel driver with not yet having G-SYNC support on notebooks and vRAM is not preserved across power management yet.
During the benchmarking not only was the raw performance analyzed but also the GPU power consumption between these alternative kernel drivers.
The original article contains 440 words, the summary contains 136 words. Saved 69%. I’m a bot and I’m open source!
The autotldr-bot only summarized the first page, so here are some more quotes. Basically, the performance was almost identical, with two notable exceptions.
Across a variety of demanding GPU benchmarks the NVIDIA R550 open kernel driver continued to perform on-par with the proprietary driver for these GeForce RTX 40 graphics cards.
While running Blender 4.0 the proprietary kernel driver seemed to yield slightly better performance. It was just fractions of a second but was rather consistently showing the proprietary driver having that slight advantage here, unlike in other workloads.
There was the small advantage too that during periods of brief downtime using the open kernel driver appeared to deliver slightly lower GPU power consumption than the proprietary driver.
Does anyone have an idea what’s the point with the proprietary driver now? Does it have any features missing in the open driver?
kugmo@sh.itjust.works
on 06 Mar 2024 21:13
nextcollapse
You have to use the proprietary driver with GTX 1000 series cards and older to get good performance. 900 and 1000 series cards are cucked with no re-clocking on nouveau because they require signed firmware.
You’re right, the new open source driver does not support the 1000 series and older, only Turing (2000 series) and above.
kugmo@sh.itjust.works
on 06 Mar 2024 23:14
collapse
And 16 series, but that is also Turing.
survivalmachine@beehaw.org
on 06 Mar 2024 23:12
nextcollapse
Is the open driver more stable in Wayland now? 535, I couldn’t use Wayland at all. 545, the open driver was still giving me all kinds of problems, but proprietary driver was flawless. Just upgraded and nothing broke, so I guess I’ll try flipping back to open again and giving it a try, but the point of the proprietary driver has been stability, at least for some of us. [Arch/Wayland/hyprland/rtx3060]
Molecular0079@lemmy.world
on 07 Mar 2024 00:32
collapse
Does it have any features missing in the open driver?
The main difference for me is the inability to preserve video memory during suspend and hibernate. Without it, sleep and hibernate will cause all sorts of weird graphical glitches upon resume.
threaded - newest
This is the best summary I could come up with:
Previously the open-source (out-of-tree) kernel modules were just certified for their data center GPUs while now they are basically acknowledging that they are in good shape too for GeForce and workstation products.
It was back in May 2022 that NVIDIA announced their open-source GPU kernel driver plans for Turing GPus and newer.
Since then they’ve continued advancing this out-of-tree code that is bundled as part of their distributed driver package.
NVIDIA’s open kernel modules option is NOT to be confused with the upstream open-source Nouveau driver effort.
But there are some known limitations in the open kernel driver with not yet having G-SYNC support on notebooks and vRAM is not preserved across power management yet.
During the benchmarking not only was the raw performance analyzed but also the GPU power consumption between these alternative kernel drivers.
The original article contains 440 words, the summary contains 136 words. Saved 69%. I’m a bot and I’m open source!
The autotldr-bot only summarized the first page, so here are some more quotes. Basically, the performance was almost identical, with two notable exceptions.
Does anyone have an idea what’s the point with the proprietary driver now? Does it have any features missing in the open driver?
You have to use the proprietary driver with GTX 1000 series cards and older to get good performance. 900 and 1000 series cards are cucked with no re-clocking on nouveau because they require signed firmware.
You’re right, the new open source driver does not support the 1000 series and older, only Turing (2000 series) and above.
And 16 series, but that is also Turing.
Is the open driver more stable in Wayland now? 535, I couldn’t use Wayland at all. 545, the open driver was still giving me all kinds of problems, but proprietary driver was flawless. Just upgraded and nothing broke, so I guess I’ll try flipping back to open again and giving it a try, but the point of the proprietary driver has been stability, at least for some of us. [Arch/Wayland/hyprland/rtx3060]
You can see the differences in the official README here: us.download.nvidia.com/…/kernel_open.html
The main difference for me is the inability to preserve video memory during suspend and hibernate. Without it, sleep and hibernate will cause all sorts of weird graphical glitches upon resume.