Every article tag can be clicked to get a list of all articles in that category. Every article tag also has an RSS feed! You can customize an RSS feed too!
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: «3/3
  Go to:

cprn Jan 7, 2019
Quoting: Guest[...] Also, do not use the compton config together with the nvidia composition options - that combo made my screen tear.

I believe I tried every possible solution but just to be clear: which one helped you with tearing?
  • driver composition options without compton (at all? just without vsync option?) or
  • compton without driver composition options



Last edited by cprn on 7 January 2019 at 8:49 am UTC
slaapliedje Jan 7, 2019
Quoting: cprn
Quoting: Guest[...] Also, do not use the compton config together with the nvidia composition options - that combo made my screen tear.

I believe I tried every possible solution but just to be clear: which one helped you with tearing?
  • driver composition options without compton (at all? just without vsync option?) or
  • compton without driver composition options

I'd really like to see a video of what one considers too much tearing and no tearing.

I never notice that much tearing unless I'm trying to wiggle my windows around as fast as possible. Or if I'm attempting to play a 4k Youtube video when I have clocked down the video card to minimum for battery saving.
cprn Jan 8, 2019
Quoting: slaapliedjeI'd really like to see a video of what one considers too much tearing and no tearing. [...]

Does tearing come up on screen captured videos? Is that even possible to capture it? I thought it's something that happens between your GPU and the monitor. The only way is to record it with an external camera, I think. Here's an example of the amount of the screen tearing I'm getting, although it's not mine:

https://www.youtube.com/watch?v=FEs8HSnOki8


Last edited by cprn on 8 January 2019 at 5:25 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.