We do often include affiliate links to earn us some pennies. See more here.

Arriving today, NVIDIA have their first bug-fix release of the year with the 410.93 driver as part of their longer supported series.

NVIDIA currently run a few different driver series, with the 410.93 driver being a "long-lived branch release". This means it will see bug fixes for a longer period, while not adding in breaking changes which would be reserved for their short-lived branch releases.

Here's what's changed in 410.93:

  • Added support for the following GPUs:
    • Quadro RTX 8000
  • Fixed a bug that could prevent display detection from working on displays connected to some notebook docking stations.
  • Fixed a bug which could cause VK_KHR_external_semaphore_fd operations to fail.
  • Fixed a build failure, "implicit declaration of function
    'vm_insert_pfn'", when building the NVIDIA DRM kernel module for Linux
    kernel 4.20 release candidates.
  • Fixed a build failure, "unknown type name 'ipmi_user_t'", when building the NVIDIA kernel module for Linux kernel 4.20 release candidates.
  • Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications.
  • Added a new kernel module parameter, NVreg_RestrictProfilingToAdminUsers, to allow restricting the use of GPU performance counters to system administrators only.

Find it on the official NVIDIA site or wait for your distribution to get updated packages through your usual method.

Article taken from GamingOnLinux.com.
Tags: Drivers, NVIDIA
13 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked 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
The comments on this article are closed.
23 comments
Page: «2/3»
  Go to:

legluondunet Jan 4, 2019
Quoting: Guest@legluondunet : you need to check "force compositing pipeline" in the nvidia-settings and save to xorg.conf.
Yes I know but why it is not activated by default? Windows users does not have this bug by default. Even if I activate "force compositing pipeline", the result is not very satisfying: the video now not playing fluid.


Last edited by legluondunet on 4 January 2019 at 2:55 pm UTC
cprn Jan 4, 2019
Quoting: Guest@legluondunet : you need to check "force compositing pipeline" in the nvidia-settings and save to xorg.conf.

Never worked for me, not on GTX 750 Ti + Ubuntu GNOME some years ago, not on GTX 1070 + Manjaro.i3 for last two years or so.
cprn Jan 4, 2019
Quoting: GuestChange your DE or check your settings. It worked for me on i3, KDE, XFCE, MATE etc.

I fiddled with settings for last 5-6 years trying to fix it, exhausted my options, nothing helped, so yeah, I deducted it's DE related long time ago but I'm not going to leave i3wm.
jens Jan 4, 2019
  • Supporter
Somehow I'm not hit by tearing issues. I'm using Fedora with Gnome and kept all NVidia setting at their defaults. Thus:
- Sync to VBlank: Off
- Allow Flipping: On
- Allow G_Sync: On
- Force Composition Pipeline: Off
- Force Full Composition Pipeline: Off

I mostly use mpv als video player with hwdec (GPU) decoding and Vulkan output. Even 4K output seems butter smooth. Within games I prefer to have VSync off, which also does not result in tearing with the exception of very few games, e.g. Two point Hospital, where I have to turn on VSync. I have a Gsync compatible monitor, may that's part of why it just works for me.

I hope this info helps to at least identify some possible issues.


Last edited by jens on 4 January 2019 at 5:43 pm UTC
slaapliedje Jan 4, 2019
Allow G_Sync, assuming you have a gsync monitor, will prevent tearing.

I do love my Gsync monitors, but man were they pricey.
x_wing Jan 4, 2019
Quoting: Guest
Quoting: ThormackAs a Nvidia user myself, I still feel they are doing the bare minimum just so they can say they support Linux.

It still feels more than what the competition is doing.

Why do you say so? Freesync is coming on kernel 4.21. Not to mention how well is working Mesa at performance level.
cprn Jan 5, 2019
Quoting: GuestHave you tried compton?

compton -b --backend glx --paint-on-overlay --vsync opengl-swc --glx-no-stencil

[...]

Yeah, man. Compton is the default compositor on Manjaro.i3 and I tried to run it on both backends, glx and xrender, with every possible vsync method, including vsync disabled and even running i3 without it, then all of that with every combination of GPU driver options that I thought might have any impact on composition (that's how I broke a perfectly fine GTX750, actually), still, tearing. It's either an edge case of applications / configuration I somehow always happen to put on a fresh install (and I endured 3+ of them over last 2 years hoping to blindly fix it) or I'm a very unlucky person and it's a "slightly broken hardware" issue. Somehow. Even though I gradually replaced everything but HDD and screen. Maybe. I don't know. I gave up looking for a cause. It shouldn't be that hard. Nobody can even tell me whether I have to reboot after each configuration change or is the X restart enough or maybe I just need to restart i3 or the compton itself... So I ended up rebooting "just in case" even for compton config changes. It's nerve wrecking.

Thank you for the tip, though. Sorry for the rant.

Edit: BTW, no syncing issues on Nouveau. So... Yeah.


Last edited by cprn on 5 January 2019 at 1:07 am UTC
x_wing Jan 5, 2019
Quoting: Guest
Quoting: x_wing
Quoting: Guest
Quoting: ThormackAs a Nvidia user myself, I still feel they are doing the bare minimum just so they can say they support Linux.

It still feels more than what the competition is doing.

Why do you say so? Freesync is coming on kernel 4.21. Not to mention how well is working Mesa at performance level.

Mesa is not good at performance(especially at price/performance) and has issues with a lot of games.

You mean that a RX 580 is not at the level of a GTX 1060 on Linux (Mesa vs Proprietary)? There are plenty of benchs that prove you're wrong. And, worth mention, that many of the "issues" on the games are dev faults (check for the latest Black Mesa patch to get an idea).

Nowadays Mesa is rock solid. The only big issue is stuttering in some games, but is completely solved by setting your cpu governor to performance (or using Feral tool). Intel & AMD has made an excellent work on their OpenGL & Vulkan open source libraries implementations in the latest years, giving a quality far superior than Nvidia. From my point of view you have a bias.
jens Jan 5, 2019
  • Supporter
Quoting: x_wingThe only big issue is stuttering in some games, but is completely solved by setting your cpu governor to performance (or using Feral tool). Intel & AMD has made an excellent work on their OpenGL & Vulkan open source libraries implementations in the latest years, giving a quality far superior than Nvidia. From my point of view you have a bias.

I think this applies both ways.
I completely agree that Intel and AMD (and related Mesa contributors including RADV people) are doing a great job, though that doesn't necessarily imply that NVidia is doing a bad job. It's just that they do things differently. If AMD/Intel works for you: very cool, I'm glad for you. Nvidia works for me, I'm glad for me and my decision to have bought one of their products :)

PS: I'm also using Feral gamemoded, having your CPU on performance mode matters for NVidia too.


Last edited by jens on 5 January 2019 at 6:05 pm UTC
x_wing Jan 5, 2019
Quoting: jens
Quoting: x_wingThe only big issue is stuttering in some games, but is completely solved by setting your cpu governor to performance (or using Feral tool). Intel & AMD has made an excellent work on their OpenGL & Vulkan open source libraries implementations in the latest years, giving a quality far superior than Nvidia. From my point of view you have a bias.

I think this applies both ways.
I completely agree that Intel and AMD are doing a great job, though that doesn't necessarily imply that NVidia is doing a bad job. It's just that they do things differently. If AMD/Intel works for you: very cool, I'm glad for you. Nvidia works for me, I'm glad for me and my decision to have bought one of their products :)

PS: I'm also using Feral gamemoded, having your CPU on performance mode matters for NVidia too.

But the discussion we have were based on the "Nvidia Fuck you" phrase, and as matter of effect the driver is in the same situation as it used when it came up.

Also, I was answering "It still feels more than what the competition is doing", and no one can say that AMD made less than Nvidia with the AMDGPU driver. In fact, AMDGPU is an excellent kick in the ass for Nvidia, as one of the statements from Nvidia against making a FOS driver were that the current DRM design of Linux would affect the performance.


Last edited by x_wing on 5 January 2019 at 4:53 pm UTC
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring 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!
The comments on this article are closed.