NVIDIA are pushing forward with improving their Linux driver in many areas, with two driver series seeing updated in the past week.
The first is the 390.77 driver, part of their "long-lived branch release". This was released a few days ago, which has these changes:
- Improved compatibility with recent Linux kernels.
- Fixed an intermittent hang of Vulkan applications running fullscreen when flipping is allowed.
- Removed informational messages that were printed by nvidia-modeset.ko whenever a GPU device was allocated or freed.
- Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications.
- Updated the OpenGL driver to allow the use of integer format (SINT/UINT) color attachments with depth attachments in Frame Buffer Objects.
On top of that, there's also the 396.45 driver which is their newer driver series that was released yesterday:
- Added support for the following GPU:
- TITAN V JHH Special Edition
- Improved recovery of Vulkan direct-to-display applications after an application hang or crash.
- Fixed a bug that could cause multi-threaded EGL applications to crash when exiting.
- Improved compatibility with recent Linux kernels.
- Fixed an intermittent hang of Vulkan applications running fullscreen when flipping is allowed.
- Removed informational messages that were printed by nvidia-modeset.ko whenever a GPU device was allocated or freed.
- Fixed a bug that could cause kernel panics when using Quadro SDI Capture hardware.
- Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications.
- Fixed an intermittent crash when launching Vulkan applications.
- Fixed an intermittent crash when launching applications through Wine.
- Fixed a bug that caused the driver, in some low bandwidth DisplayPort configurations, to not implicitly enable display dithering. This resulted in visible banding.
- Fixed intermittent hangs of fullscreen Vulkan applications when focused away (e.g., by using the alt-tab key combination) on non-composited desktops.
- Increased the version numbers of the GLVND libGL, libGLESv1_CM, libGLESv2, and libEGL libraries, to prevent concurrently installed non-GLVND libraries from taking precedence in the dynamic linker cache.
- Updated the OpenGL driver to allow the use of integer format (SINT/UINT) color attachments with depth attachments in Frame Buffer Objects.
Do let us know in the comments how you've been getting on with either driver, help you friendly Linux gamer out if you know a solution to any issues in these newer drivers.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: GuestIs it the "freezing panel when some apps interrupt compositing" bug or a "oops my windows decorations disappeared !" bug ?Yep. The one we all love to hate! :><:
Quoting: GuestTo work around the former, I had removed the automatic composition interruption (and do it manually when required). Would be awesome if this was finally fixed, it's been here for ages.The question is, why should it be necessary at all to disable compositing? :S:
2 Likes, Who?
Quoting: GuestActually I don't think this bug is about Kwin crashes but about the "panel freeze" bug. The panel and desktop would stop being updated, but you could still click on them (and they would react without updating visually).I ended up in using xrandr compositing for compositing + nvidia forcefullcompositionpipeline for vsync.
EXTREMELY annoying...
0 Likes
How about this situation:
KDE Plasma 5, Kwin with OpenGL compositing, have no tearing, have working G-Sync on the main G-Sync monitor while still having the other non-G-Sync monitor (rotated btw) working normally.
So far, it seems impossible. :)
If anyone here is an expert in getting dual X screens working with KDE+nVidia drivers, let me know.
KDE Plasma 5, Kwin with OpenGL compositing, have no tearing, have working G-Sync on the main G-Sync monitor while still having the other non-G-Sync monitor (rotated btw) working normally.
So far, it seems impossible. :)
If anyone here is an expert in getting dual X screens working with KDE+nVidia drivers, let me know.
0 Likes
Quoting: GuestWhat do you currently achieve and what do you want to achieve ?
Config is 90 degree rotated 1920x1080 60Hz non-G-Sync monitor (left) and non-rotated 3440x1440 120Hz G-Sync monitor (right) on Debian sid, KDE Plasma, 1080Ti. Forcing composition pipeline is a tolerable 'hack' but the whole G-Sync feature is sort of wasted unless I disable the non-G-Sync monitor.
Current limitations with Xorg include awesome things like...
*Forced composition pipeline and G-Sync are mutually exclusive
*G-Sync only available in full screen applications
*G-Sync only available on a single X screen (this usually means your whole desktop in most cases since a normal multimonitor setup runs a single X screen spanning all monitors)
*Trying to get dual X screens working properly is about as amusing as repeatedly punching yourself in the d*ck with a cactus
Disabling 2nd monitor is not a solution imho, but it seems to be the only way for now. Xorg is unlikely to be fixed so maybe Wayland will be better at this... maybe nVidia can get G-Sync working in windowed applications... maybe pigs will be able to fly someday... :S:
Last edited by dpanter on 25 July 2018 at 8:33 am UTC
0 Likes
There are several things you must do to enable G-Sync, just settings in OS, driver and monitor etc. Not exactly perfect or dead simple, but not difficult. It's just... a proper b*tch to get it working like I want/need it to. It's madness, really.
Here's a link that doesn't help but is still helpful. ;)
https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/2/
Here's a link that doesn't help but is still helpful. ;)
https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/2/
0 Likes
Patreon
PayPal
See more from me