SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Release highlight:
Fixed kernel module build problems with Linux kernel 5.4.0 release candidates.
Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available.
Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions.
November 13th, 2019 - Windows 436.64, Linux 435.27.06
Fixes:
Fixed memory leak after destroying ray tracing pipeline
Improved responsiveness of X11 driver when 'NVIDIA: Wait for channel idle timed out' messages occur
Improved fullscreen exclusive support for non-primary monitors
Improved G-Sync support for borderless windows
Further improvements when system is under low-memory stress
Edit in: It will not build with the 5.4-rc7 kernel in /testing.
Last edited by cwizardone; 11-14-2019 at 10:44 AM.
Added support for the following GPUs:
GeForce GTX 1650 SUPER
Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2.
Updated nvidia-settings to allow continued interaction with other pages and help content while editing application profiles.
Hello all,
For those that use the SBo scripts for Nvidia, new buildscripts for 440.36 are now in pending. These scripts work on both 14.2 (stable) and 15.0 (current); for current you will need kernel-5.4.0 from /testing in order to successfully compile the kernel module interface.
Hightlights:
libglvnd only.
nvidia-switch removed - no longer needed.
*.la removed
nouveau blacklist still required.
Please note, use "CURRENT=yes ./nvidia-driver" when on 15.0. This is to keep Nvidia installer from stomping on the existing libglvnd package. As always it works here (so far). On one of my boxes (GTX 1060 w/ 4K monitor, GTX660 w/ 2x 1080p monitors,) I experienced occasional stutters running Borderlands 2 (native, Steam), but this could just be my weird setup. The current Ryzen box completed several phoronix test suite GPU benchmarks successfully (GTX 950, hoping for a AMD Navi card soon).
Hello all,
For those that use the SBo scripts for Nvidia, new buildscripts for 440.36 are now in pending. These scripts work on both 14.2 (stable) and 15.0 (current); for current you will need kernel-5.4.0 from /testing in order to successfully compile the kernel module interface.
Hightlights:
libglvnd only.
nvidia-switch removed - no longer needed.
*.la removed
nouveau blacklist still required.
Please note, use "CURRENT=yes ./nvidia-driver" when on 15.0. This is to keep Nvidia installer from stomping on the existing libglvnd package. As always it works here (so far). On one of my boxes (GTX 1060 w/ 4K monitor, GTX660 w/ 2x 1080p monitors,) I experienced occasional stutters running Borderlands 2 (native, Steam), but this could just be my weird setup. The current Ryzen box completed several phoronix test suite GPU benchmarks successfully (GTX 950, hoping for a AMD Navi card soon).
Let me know if you catch any bugs.
And how did you managed to convince the NVIDIA driver to work with Xorg's /usr/lib64/xorg/modules/extensions/libglx.so ?
At least after my own experiments with nvidia-legacy390-driver, there's still a need to switch this library with nvidia-switch even if I managed to install in parallel with MESA and/or Xorg the other libraries.
I talk, of course, about slackware-current.
Last edited by ZhaoLin1457; 11-29-2019 at 04:50 PM.
At least after my own experiments with nvidia-legacy390-driver
Did I refer to legacy drivers in my post? Correct Answer: No.
Nvidia renamed its version of glx in the newer drivers a while back, and libglvnd wrappers take care or sorting libs all out, as well as symlinks pointing to the correct verions. I haven't needed to back up Mesa files in a while in the mainline drivers. Mesa added libglvnd support back in 2017. Of course, 14.2 being "ancient" it may still be a bit wonky with the older Mesa, as you end up with some duplicates, such as libGL.so.1.2.0 vs libGL.so.1.2.0, but on current this is no longer an issue, assuming the libglvnd package in Slackware-15.0 gets updated. The Nvidia binary driver will always use the newest release. Thus, I do foresee cases where you may need to upgrade to the latest libglvnd release from github. Of course, I could have overlooked something somewhere as well.
The legacy builds are a whole different wrinkle. These older versions will still need nvidia-switch to assist in sorting out the libs and symlinks.
Code:
ls -l /usr/lib64/xorg/modules/extensions/
total 13708
-rwxr-xr-x 1 root root 1503 Oct 18 2017 libglx.la
-rwxr-xr-x 1 root root 285992 Oct 18 2017 libglx.so
lrwxrwxrwx 1 root root 29 Nov 28 19:16 libglxserver_nvidia.so -> libglxserver_nvidia.so.440.36
-rwxr-xr-x 1 root root 13166704 Nov 29 02:53 libglxserver_nvidia.so.440.36
Did I refer to legacy drivers in my post? Correct Answer: No.
Nvidia renamed its version of glx in the newer drivers a while back, and libglvnd wrappers take care or sorting libs all out, as well as symlinks pointing to the correct verions. I haven't needed to back up Mesa files in a while in the mainline drivers. Mesa added libglvnd support back in 2017. Of course, 14.2 being "ancient" it may still be a bit wonky with the older Mesa, as you end up with some duplicates, such as libGL.so.1.2.0 vs libGL.so.1.2.0, but on current this is no longer an issue, assuming the libglvnd package in Slackware-15.0 gets updated. The Nvidia binary driver will always use the newest release. Thus, I do foresee cases where you may need to upgrade to the latest libglvnd release from github. Of course, I could have overlooked something somewhere as well.
The legacy builds are a whole different wrinkle. These older versions will still need nvidia-switch to assist in sorting out the libs and symlinks.
Code:
ls -l /usr/lib64/xorg/modules/extensions/
total 13708
-rwxr-xr-x 1 root root 1503 Oct 18 2017 libglx.la
-rwxr-xr-x 1 root root 285992 Oct 18 2017 libglx.so
lrwxrwxrwx 1 root root 29 Nov 28 19:16 libglxserver_nvidia.so -> libglxserver_nvidia.so.440.36
-rwxr-xr-x 1 root root 13166704 Nov 29 02:53 libglxserver_nvidia.so.440.36
Either way, 14.2 is dead to me. Long live 15.0!
Sorry to hear that. My 14.2 Multilib install running 5.4.1 kernel with nVidia 440.36 works better than ever as tested by Unigine Superposition. The only updates I have performed on 14.2 are security patches and applying a modified Pure Alsa upgrade adapted from -Current.
I'm excited by the prospect of 15.0 but my 14.2 is alive and well. I may have performed one Mesa libs update since 14.2's initial release but that was over a year ago and of no consequence that I recall.
Sorry to hear that. My 14.2 Multilib install running 5.4.1 kernel with nVidia 440.36 works better than ever as tested by Unigine Superposition. The only updates I have performed on 14.2 are security patches and applying a modified Pure Alsa upgrade adapted from -Current.
I'm excited by the prospect of 15.0 but my 14.2 is alive and well. I may have performed one Mesa libs update since 14.2's initial release but that was over a year ago and of no consequence that I recall.
Well, I was only partly joking about 14.2 - that is still my main box until 15.0 is released, for my home computing needs and gaming with Steam., et al, via Nvidia GPU. I just wouldn't have time to keep slackware64-current multilib running with all the changes! 440.36 is running well so far here on both 14.2 (GTX 1060) and 15.0 (kernel 5.4.1 GTX 950). If AMD Navi (with or without h/w ray tracing) can get me to 4K 60+fps gaming, at a price I can afford with just the open source drivers, then I will consider dropping Nvidia.
The new wrinkle is the integration into Mesa of libglvnd (and that new package) which will make it more difficult to integrate newer Nvidia drivers into 14.2. Upgrading the kernel is not enough, you will soon need the newest Mesa and xorg-server, and probably more.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,157
Original Poster
Rep:
Quote:
NVIDIA Looks To Have Some Sort Of Open-Source Driver Announcement For 2020
Written by Michael Larabel in NVIDIA on 5 December 2019 at 01:55 PM EST.
Start looking forward to March when NVIDIA looks to have some sort of open-source driver initiative to announce -- likely contributing more to Nouveau and we're crossing our fingers they will have sorted out the signed firmware situation to unblock those developers from delivering re-clocking support to yield better driver performance.......
Added support for the following GPU:
Quadro T2000 with Max-Q Design
Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications.
Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system.
Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko.
Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
