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.
# for d in /usr/lib /usr/lib64 ; do find $d -type f -iname "libnvidia*" ; echo "" ; done
/usr/lib/libnvidia-ptxjitcompiler.so.384.90
/usr/lib/tls/libnvidia-tls.so.384.90
/usr/lib/libnvidia-ml.so.384.90
/usr/lib/libnvidia-glsi.so.384.90
/usr/lib/libnvidia-tls.so.384.90
/usr/lib/libnvidia-ifr.so.384.90
/usr/lib/libnvidia-compiler.so.384.90
/usr/lib/libnvidia-encode.so.384.90
/usr/lib/libnvidia-fbc.so.384.90
/usr/lib/libnvidia-opencl.so.384.90
/usr/lib/libnvidia-glcore.so.384.90
/usr/lib/libnvidia-eglcore.so.384.90
/usr/lib/libnvidia-fatbinaryloader.so.384.90
/usr/lib64/libnvidia-cfg.so.384.90
/usr/lib64/libnvidia-ptxjitcompiler.so.384.90
/usr/lib64/tls/libnvidia-tls.so.384.90
/usr/lib64/libnvidia-ml.so.384.90
/usr/lib64/libnvidia-glsi.so.384.90
/usr/lib64/libnvidia-tls.so.384.90
/usr/lib64/libnvidia-ifr.so.384.90
/usr/lib64/libnvidia-compiler.so.384.90
/usr/lib64/libnvidia-encode.so.384.90
/usr/lib64/libnvidia-fbc.so.384.90
/usr/lib64/libnvidia-opencl.so.384.90
/usr/lib64/libnvidia-glcore.so.384.90
/usr/lib64/libnvidia-gtk2.so.384.90
/usr/lib64/libnvidia-eglcore.so.384.90
/usr/lib64/libnvidia-fatbinaryloader.so.384.90
/usr/lib64/xorg/modules/libnvidia-wfb.so.384.90
/usr/lib64/libnvidia-egl-wayland.so.1.0.1
/usr/lib64/libnvidia-gtk3.so.384.90
p.s. maybe a test ? does _MY_ 32-bit glxgears work ???
Code:
[konrad@kjhlt6 ~]$ LD_PRELOAD=/usr/lib/tls/libnvidia-tls.so.384.90 /usr/bin/32/glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.366 FPS
300 frames in 5.0 seconds = 59.915 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 53 requests (53 known processed) with 0 events remaining.
[konrad@kjhlt6 ~]$ /usr/bin/glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
303 frames in 5.0 seconds = 60.434 FPS
300 frames in 5.0 seconds = 59.912 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 56 requests (56 known processed) with 0 events remaining.
Last edited by kjhambrick; 10-13-2017 at 12:48 PM.
Reason: maybe a test -- does MY 32-bit glxgears work ???
$ /usr/bin/32/glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.382 FPS
300 frames in 5.0 seconds = 59.912 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 53 requests (53 known processed) with 0 events remaining.
I just bought a new computer today with GT 1030 inside. I've picked the driver from Nvidia site by going through the menus, specifying what card and OS I have. Downloaded what has been offered, without checking version. Installation was clean, simple and flawless, worked like a charm. Without it, I was limited to 1024x768.
kjhambrick, thanks for the feedback. I have no idea why nvidia-installer is glitching on /usr/lib/tls/libnvidia-tls.so.384.90. I'm basically just doing what the .run script does anyway, but just adding options to send the installation to $PKG (ie /tmp/SBo/...) to make a portable package. I am using the nvidia-installer source instead of the pre-built binary in the Nvidia's .run script and blob. I've added a work around for now and will post the update to Slackbuilds.org.
I just bought a new computer today with GT 1030 inside. I've picked the driver from Nvidia site by going through the menus, specifying what card and OS I have. Downloaded what has been offered, without checking version. Installation was clean, simple and flawless, worked like a charm. Without it, I was limited to 1024x768.
askfor, thanks for the tip, I had the same problem!
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 8,680
Original Poster
Rep:
Nivida has released their latest "Long Lived Branch" driver, version 384.98.
Release highlights:
Quote:
Fixed a bug that could cause some eDP G-SYNC displays to flicker at low refresh rates.
Fixed a bug that could cause OpenGL applications to crash after a prolonged DPMS sleep state on a monitor driven with PRIME Sync.
Fixed a bug that artificially limited the maximum pixel clock to 300 MHz when using certain more capable DisplayPort to HDMI adapters.
Fixed a bug that prevented the NVIDIA kernel modules from building for non-SMP Linux kernels.
Updated the output of `nvidia-smi nvlink --status` to include reporting NVLink speed.
Fixed a bug that caused incorrect PCI topology reporting in nvidia-smi on Intel Skylake systems.
Fixed a bug that caused Vulkan X11 swapchains to fail on GPUs without a display engine, such as some Tesla-branded graphics cards and some Optimus laptops.
Fixed a bug that caused fullscreen Vulkan applications to hang on some Kepler GPUs, such as the GeForce GTX 680.
Fixed a bug where the G-SYNC indicator was reporting "normal" instead of "G-SYNC" on Vulkan applications when G-SYNC was enabled.
Its working good! There is one strange bug that was introduced in the last release but its not too big of a deal but its still present. It pauses the desktop for a second when loading a video in QMPlay2 the first time after booting/exiting suspend. It doesn't do it after that even after closing the application & starting it again.
End of NVIDIA Driver Support for 32-bit Operating Systems
Answer ID 4604
Updated 12/21/2017 04:23 PM
When is the NVIDIA driver ending support for 32-bit operating systems?
After Release 390, NVIDIA will no longer release drivers for 32-bit operating systems1 for any GPU architecture. Later driver release versions will not operate, nor install, on 32-bit operating systems. Driver enhancements, driver optimizations, and operating system features in driver versions after Release 390 will not be incorporated back into Release 390 or earlier versions. This impacts the following operating systems:
Microsoft Windows 7
Microsoft Windows 8/8.1
Microsoft Windows 10
Linux
FreeBSD
NVIDIA intends to support critical driver security fixes until January 2019. For more details on product security, see http://www.nvidia.com/security.
1. Applicable to operating systems running on x64 and x32 CPU architectures.
Last edited by cwizardone; 12-22-2017 at 11:58 AM.
I wonder if that means they're multilib support will be gone. If so, does that mean steam will no longer work or just 32bit steam games? I'm not sure if steam requires 32bit driver support to start up.
If 32bit support is completely removed, that may cause gamers in Linux to move to AMD with their open source amdgpu driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.