[SOLVED] NVidia's Latest Long Term Driver, 361.28. Please see correction in post #7.

cwizardone · 05-21-2016, 08:53 PM

Quote:

Originally Posted by Drakeo

Not having that problem yet on the 367.18 GTX-960 slack current

After installing the 367.18-beta driver the wallpaper for all my KDE virtual desktops (4) disappeared, as did the one "activities" (second desktop) I had setup. I reconfigured the wallpaper for the virtual desktops, but did not create a new "activity."
This morning, all but one of the wallpapers were missing, so as I said, the 367.18-beta driver was un-installed and replaced with the 364.19 driver. Once done, all the wallpaper that had been there before and the one "activity" reappeared. It couldn't be magic

so there has to be a configuration file for each version of the video driver stored somewhere on the HD?

cwizardone · 06-13-2016, 05:53 PM

The newest Long Term Nvidia driver, version 367.27, has been released.
https://www.nvidia.com/object/unix.html

Quote:

Linux x64 (AMD64/EM64T) Display Driver

Version: 367.27
Release Date: 2016.6.13
Operating System: Linux 64-bit
Language: English (US)
File Size: 73.38 MB

Release Highlights:

Added support for the following GPUs:
GeForce GTX 1080
GeForce GTX 1070
Added support for VDPAU Feature Set H to the NVIDIA VDPAU driver. GPUs with VDPAU Feature Set H are capable of hardware-accelerated decoding of 8192x8192 (8k) H.265/HEVC video streams.
Fixed a bug that caused the X server to sometimes skip displaying Vulkan frames when the Composite extension is enabled.
Fixed a bug that would cause OpenGL applications to crash when creating a context on one X display connection, then making it current with no associated drawable on another X display connection. This fixes a crash when starting some versions of Matlab.
Fixed OpenGL presentation to SDI through the GLX_NV_video_out and GLX_NV_present_video extensions, which was broken by the introduction of the nvidia-modeset kernel module in 358.09.
Fixed a bug that caused an incorrect offset to be applied when using the full composition pipeline on a display whose image has both a rotation and a ViewportOut offset applied.
Fixed a bug that could cause nvidia-settings to crash on some systems when responding to events such as hotplugging DisplayPort devices.
Fixed a bug that could cause crashes in OpenGL applications which use glTextureView() with a non-zero minlevel.
Enhanced the Display Device information page in nvidia-settings with additional information for DisplayPort devices to reflect attributes which are specific to DisplayPort connections.
Fixed a bug which could cause deleted application profiles to appear when editing rules in the nvidia-settings control panel.
Fixed a bug that caused hangs when a G-SYNC monitor is unplugged and a non-G-SYNC monitor is connected while G-SYNC is active.
Fixed a bug that caused "nvidia-modeset: ERROR: GPU:0: Activating G-SYNC failed" to be printed to the system log if a G-SYNC monitor is connected and stereo is enabled in xorg.conf on a configuration that doesn't support it.
Added the NV_robustness_video_memory_purge OpenGL extension, which
allows applications to know when a mode switching or power event purged the contents of FBOs and BOs residing in video memory.
Fixed a bug that prevented HDMI 2.0 4K monitors from waking up from sleep or hot-replug.
Fixed a bug that could lead to a system crash if there was a peer-to-peer mapping still active during CUDA context teardown.

1337_powerslacker · 06-13-2016, 06:05 PM

Quote:

Originally Posted by cwizardone

The newest Long Term Nvidia driver, version 367.27, has been released.
https://www.nvidia.com/object/unix.html

Updated and working fine. Tested with Darkplaces Quake, and runs beautifully. No problems here!

cwizardone · 06-14-2016, 02:25 PM

Quote:

Originally Posted by 1337_powerslacker

Updated and working fine. Tested with Darkplaces Quake, and runs beautifully. No problems here!

Ditto.
It has been installed and running for just about 24 hours and is working
perfectly.... so far.

cwizardone · 11-18-2016, 02:58 PM

Version 375.20, is the latest "long term" driver from NVIDIA:

https://www.nvidia.com/Download/driv...x/111596/en-us

Among other things it,

Quote:

Added support for X.Org xserver ABI 23 (xorg-server 1.19)

kjhambrick · 11-18-2016, 03:20 PM

Thanks cwizardone !

Installed NVIDIA-Linux-x86_64-375.20.run 64-bit + 32-bit Drivers on slackware64 14.2 + Multilib ( 4.4.32 Kernel ).

All is well.

-- kjh

dugan · 11-19-2016, 04:17 PM

Well, if you have the latest -current update (Xorg 1.19), then you need to upgrade to 375.20. It's the first version to support Xorg 1.19.

Some notes:

1. I kept getting the "cannot create libEGL.so symlink; file exists" error when I tried to install the 32-bit compatibility layer. As far as I can tell, this is harmless.

2. If I log out of X, my console is blank and black. My workaround is to just start in runlevel 4 and stay in X all the time. Of course it's still an issue, but it's not a dealbreaker. Which kernel am I using? The stock generic 4.4.32 kernel. I'm also booting in UEFI mode, with rEFIND booting my kernel directly instead of going through any other boot loader. My google searches indicate that this may be a problem, although it hasn't been until now.

3. The workarounds for screen tearing are now checkboxes in NVidia Settings. Start by turning Vsync off in both the drivers and in your games. If you get screen tearing, turn ForceCompositionPipeline on in the driver. If you still get screen tearing, turn ForceFullCompositionPipeline on in the driver. If you still get screen tearing, turn "sync to vblank" on in the driver. You should never need to enable vsync in your games.

cwizardone · 11-20-2016, 08:27 AM

Regarding note 1: Yes, I've had the same problem with the new 375.20 driver and both the 4.4.29 and 4.4.32 kernels, but, as you said, it appears harmless, i.e., everything runs as it should.
I have not any of the problems described in notes 2 and 3.
Cheers.

kjhambrick · 11-20-2016, 08:50 AM

Yes.

Now that you mention it, I saw the same symlinking error while the 32-bit processes were running in the 375.20 NVidia Blob.

I checked the target and sources:

Code:

#
# are the files and SymLinks installed ?
#
# /bin/ls -la /usr/{lib,lib64}/libEGL.so*

lrwxrwxrwx 1 root root    11 Nov 19 06:28 /usr/lib/libEGL.so -> libEGL.so.1
-rwxr-xr-x 1 root root 71688 Nov 19 06:28 /usr/lib/libEGL.so.1
lrwxrwxrwx 1 root root    11 Nov 19 06:28 /usr/lib64/libEGL.so -> libEGL.so.1
-rwxr-xr-x 1 root root 77264 Nov 19 06:28 /usr/lib64/libEGL.so.1
#
# what are they ?
#
# file /usr/{lib,lib64}/libEGL.so*

/usr/lib/libEGL.so:     symbolic link to libEGL.so.1
/usr/lib/libEGL.so.1:   ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
/usr/lib64/libEGL.so:   symbolic link to libEGL.so.1
/usr/lib64/libEGL.so.1: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

They looked 'OK to me' ( the dates and `file` output looked OK ) so I assumed it was a bug in the binary nvidia-installer.

-- kjh

elcore · 11-20-2016, 11:48 PM

I've found out when removing binary driver 340.98 from slackware64 with kernel 4.4.32, reinstalling mesa and xorg-server may not be enough to bring back nouveau.
Seems like it's done something to hwdb, so I had to remove /etc/udev/hwdb.bin and let it recreate itself, otherwise it would cause a panic on boot.
Caught me by surprise though, as I haven't seen that before.

cwizardone · 12-14-2016, 07:53 PM

Quote:

Originally Posted by dugan

Well, if you have the latest -current update (Xorg 1.19), then you need to upgrade to 375.20. It's the first version to support Xorg 1.19.

Some notes:

1. I kept getting the "cannot create libEGL.so symlink; file exists" error when I tried to install the 32-bit compatibility layer. As far as I can tell, this is harmless....

This problem has been fixed in the new long term driver 375.26, released today, 14 December 2016.

https://www.nvidia.com/Download/driv...x/112992/en-us

ryanpcmcquen · 12-15-2016, 08:38 AM

Quote:

Originally Posted by cwizardone

This problem has been fixed in the new long term driver 375.26, released today, 14 December 2016.

https://www.nvidia.com/Download/driv...x/112992/en-us

I've updated the Bumblebee-SlackBuilds repo with that version:

https://github.com/WhiteWolf1776/Bumblebee-SlackBuilds

cwizardone · 02-14-2017, 11:27 AM

NIVIDA has released the 375.39 long term driver.

http://www.geforce.com/drivers/results/114708

Quote:

Release Highlights

Added support for the following GPU(s):
Quadro GP100
Quadro P4000
Quadro P2000
Quadro P1000
Quadro P600
Quadro P400
Quadro M1200
Quadro M2200
Fixed a bug that caused system hangs when resuming from suspend with some GPUs.
Fixed a regression that could cause corruption when hot-plugging displays.
Fixed a regression that prevented systems with multiple DisplayPort monitors from resuming correctly from suspend.

They have also updated two of their legacy drivers.

ryanpcmcquen · 02-14-2017, 11:29 AM

Anyone want to pull request the update? I am not using the proprietary driver at the moment.

kingbeowulf · 02-19-2017, 08:55 PM

I just posted nvidia-375.39 LLB to Slackbuilds.org. Sure, you can use the .run, but the SBo packages allow building on systems, and VMs, that do not have Nvidia GPU installed.

There were a lot of library changes again with GLVND/vulkan/wayland support. I'd like to switch to nvidia-installer, and almost have most of the 'out-of-tree' install to a $PKG directory figured out, but the nvidia-installer insists on (1) checking got an Nvidia GPU, and (2) deleting conflicting libs. Nvidia makes it extremely difficult to build a standalone redistributable package.

If anyone wants to assist in patching nvidia-installer to remove the backup and conflicting files code, ping me via email (see .info)