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

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - NVidia's Latest Long Term Driver, 361.28. Please see correction in post #7. (https://www.linuxquestions.org/questions/slackware-14/nvidias-latest-long-term-driver-361-28-please-see-correction-in-post-7-a-4175572087/)

cwizardone

02-12-2016 08:56 AM

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

Edit in: Please see correction in post #7.

Has anyone installed NVidia's latest long term driver, 361.28?

Under release highlights they say,

Quote:

Removed the VDPAU wrapper and trace libraries libvdpau.so.1 and libvdpau_trace.so.1 from the driver package. These libraries may be available via your distribution's package management system, or can be compiled from the sources available at:

Sorry to be so vague, but the install log was overwritten when I re-installed the previous version.
When installing 361.28, it comes up with a message that it can't find or create two or three symbolic links related to libvdpau, but other than that it appears to work OK, except it did cause a small, but not serious problem running a ms-windows application under WINE.
Anyone else had similar experiences?
Thanks.

bassmadrigal

02-12-2016 09:24 AM

Maybe the driver overwrote a few of the stock files for vdpau. Have you tried reinstalling libvdpau?

orbea

02-12-2016 09:31 AM

nvidia like to delete libraries and replace them with symlinks to their own crap, make sure you they didn't leave any old symlinks behind from the previous versions.

ryanpcmcquen

02-12-2016 12:26 PM

I am staying on 352.x until I have more time to research the new branch. The entire build system changed at 355.x.

elcore

02-13-2016 05:18 AM

I've installed it on 14.1 with custom kernel 4.1.17-smp

There was something with old modeline that no longer works, just needed to replace it with "CRT-1:nvidia-auto-select +0+0"
Traditionally, this would reduce my resolution to 1024x768 but it seems external EDID is now supported and working fine so I just include these in xorg.conf

Code:

  Option              "CustomEDID"          "CRT-1:/lib/firmware/1680x1050.bin"

  Option              "IgnoreEDIDChecksum"  "CRT-1"

And it seems the driver reporting normal resolution for vga connector and displaying skewed with black border problem (from 358.x series) has been fixed..
From what I can tell, vdpau (from SBo) works, opengl in wine works too, can't say I've had any problems with it.

1337_powerslacker

02-13-2016 10:38 AM

Quote:

Originally Posted by ryanpcmcquen (Post 5499245)

I am staying on 352.x until I have more time to research the new branch. The entire build system changed at 355.x.

I also have run into undesirable effects with the 361.x series, such as my computer not transitioning into console mode to initiate the shutdown sequence after I hit the shutdown button in KDE; my computer stays running unless I hold down the power button until my computer shuts off. Not desirable, as it potentially puts my computer's data at risk if done constantly. Hence my regression to the 352.x series.

cwizardone

02-13-2016 12:40 PM

Boy, was I wrong! That's what I get for not writing things down.
For a second time I installed the 361.28 and here are the errors.
They all start with

Quote:

The installer has encountered the following error during installation: 'Cannot create symlink......

and here are the three errors,

Quote:

/usr/lib/libGL.so.1

/usr/lib/libGL.so

libGLX_nvidia.so.0

and they all end with

Quote:

(File exists)'. Would you like to continue with the installation?

The NVidia has this to say,

Quote:

The OpenGL Vendor-Neutral Driver (GLVND) infrastructure is now included and supported by the NVIDIA GLX and OpenGL drivers. This should not cause any visible changes in behavior for end users, but some internal driver component libraries have been renamed and/or moved as a result. These changes may affect scripts that rely on the presence of NVIDIA OpenGL driver components other than those specified in the Linux OpenGL ABI version 1.0, maintainers of alternative NVIDIA driver installation packages, and applications which rely on the presence of any non- OpenGL/GLX symbols in the libGL.so.1 library and its dependencies in any way.

Please see:

https://github.com/NVIDIA/libglvnd

For more information on the GLVND project.

The Linux OpenGL ABI version 1.0 specification is available at:

https://www.opengl.org/registry/ABI

Drakeo

02-13-2016 04:55 PM

That pretty much tells me you did not reinstall mesa after uninstalling Nvidia. and during the time after you installed that driver you did some upgrades that where part of the xorg. remember anytime any part of the xorg build of slackware is updated. you need to uninstall the nvidia driver first then upgrade. or you will get them warnings.
In slackware 14.1 Pat did one or 2 xorg changes. In current we had had so many it hard to keep up with.
go to the source folder of the xorg in slackware look at the different libraries that may affect your driver.

as for libvdpau we have had that warning in nvidia for over 5 years. that's why that build is part of slackbuilds and is now default in current 14.2 beta.
You should always uninstall the nvidia before installing a new.

kingbeowulf

02-13-2016 05:23 PM

libvdpau is know included in Slackware-Current (14.2 Beta); the SBo verson is no longer needed. Nvidia stated years ago that the libvdpau wrapper will be removed from their driver package. If you installed an older driver then you may over wite libvdpau (SBo's version won't do that).
SBo nvidia scripts are "frozen" at 352.63 while I wait for RC1
You have to be very careful when removing Nvdia drivers, whether via SBo package 'nvdia-switch --remove' or Nvidia's remove script. Sometimes libGL etc s not restored correctly. Reinstalling Mesa and xorg-server restores the correct files and symlinks.
Just noticed Drakeo's post. So yeah, "ditto".

cwizardone

02-13-2016 07:01 PM

Quote:

Originally Posted by Drakeo (Post 5499785)

......remember anytime any part of the xorg build of slackware is updated. you need to uninstall the nvidia driver first then upgrade. or you will get them warnings............

Yes, I'm well aware of that and it is the procedure I follow, but the errors as reported above, still occur.

Drakeo

02-14-2016 06:40 AM

Ok I am using the latest that has warnings for the /usr/lib32 people and the /usr/lib people that do not go the /usr/lib64 way.
and since I run multi-lib I tested it in my 32 bit games it works fine.
So the warnings are just that.
Seems to be a nice driver so far for my gtx 960 .
you must build it with --glvnd-glx-client option to get the glvnd-glx client if not it defaults to the legacy way.

Code:

+------------------------------------------------------+                      

| NVIDIA-SMI 361.28    Driver Version: 361.28        |                      

|-------------------------------+----------------------+----------------------+

| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |

| Fan  Temp  Perf  Pwr:Usage/Cap|        Memory-Usage | GPU-Util  Compute M. |

|===============================+======================+======================|

|  0  GeForce GTX 960    Off  | 0000:01:00.0      On |                  N/A |

|  0%  28C    P0    26W / 160W |    107MiB /  2046MiB |      0%      Default |

+-------------------------------+----------------------+----------------------+

                                                                              

+-----------------------------------------------------------------------------+

| Processes:                                                      GPU Memory |

|  GPU      PID  Type  Process name                              Usage      |

|=============================================================================|

|    0    15839    G  /usr/libexec/Xorg                              93MiB |

+-----------------------------------------------------------------------------+

elcore

02-14-2016 11:41 AM

Quote:

Originally Posted by cwizardone (Post 5499662)

(File exists)'. Would you like to continue with the installation?

There was always leftovers from previous driver if you had not uninstalled it first, that is normal.
If you're using the .run installer, you will run into this every time there's a kernel/xorg/mesa upgrade, I have dealt with it like this:

Code:

#!/bin/bash

sh /root/NV*.run --ui=none -s -N --uninstall && sh /root/NV*.run --ui=none -a -s -N --no-nvidia-modprobe --no-rpms --no-unified-memory

Got this in /usr/local/bin/nvx so everytime the update is needed I just replace the latest .run in /root and do "init 3 && nvx"
Note the NV*.run -A output in case you want other options.

cwizardone

02-14-2016 08:30 PM

Quote:

Originally Posted by elcore (Post 5500102)

Thanks for the reply, but, no, this has not happened in the past.
Just for chuckles, I did a fresh install of Slackware64-current this afternoon and the same errors popped up with the 361.28 version of the driver. This has never happened with previous versions.

elcore

02-15-2016 02:58 PM

You're right, I checked on -current64 (without multilib) and could replicate the same error if 32 bit compatibility libs are chosen for install.
As I don't normally use multilib or these compatibility libs, I've had no such error in my logs.
Could be a bug with the install script for 64 bit, since it doesn't happen at all on pure 32 bit system.

cwizardone

03-22-2016 10:20 AM

Stumbled across the new 364.12-Beta driver yesterday and it installed and has been running flawlessly, unlike 361.28.

http://www.nvidia.com/download/drive...x/100577/en-us

fogpipe

03-22-2016 05:23 PM

Quote:

Originally Posted by cwizardone (Post 5519751)

Stumbled across the new 364.12-Beta driver yesterday and it installed and has been running flawlessly, unlike 361.28.

http://www.nvidia.com/download/drive...x/100577/en-us

Ty for linking that, im a sucker for a beta driver :)
Seems to be working fine here too with the latest current. In fact it seems a bit faster than the 3.52 it replaced.

Drakeo

03-22-2016 06:08 PM

yes your correct like I posted earlier it was 32 bit problem this is from the change log for the 364.12

Quote:

Fixed a bug that caused installer manifest entries for some 32-bit compatibility libraries to be duplicated in the installer package.

kingbeowulf

03-23-2016 05:10 PM

The 361.xx drivers are tricky, whether via SBo or running Nvidia'a install script. There are 2 sets of libraries: GLVND (new hotness) and non-GLVND (old and busted) and there can only be one set installed. This can also result in more conflicts with Mesa, as well as issues with EGL and GLES. Be aware that 364.xx installs GLVND GLX client libraries by default. Although this fixed some lib conflicts, it can also result in incompatibilities with older OpenGL software.

See also: https://devtalk.nvidia.com/default/topic/915640

Edit: Note that the SBo packages are hand-crafted to avoid Nvidia installer compatibility issues for both pure and multilib Slackware.

cwizardone

03-30-2016 01:01 PM

NVidia's new long term driver 361.42, fixes the problem with the 361.28 driver.

The problem with the 361.28 NVidia driver has been fixed with the release of their new long term driver version 361.42.
Among the "fixes" are, as Drakeo pointed out in post #17,

Quote:

Fixed a bug that caused installer manifest entries for some 32-bit compatibility libraries to be duplicated in the installer package.

http://www.nvidia.com/Download/drive...x/101423/en-us

przemo

03-30-2016 04:20 PM

will the nvidia-switch script work with driver installed from NVIDIA.run installer????

kingbeowulf

04-02-2016 05:13 PM

Quote:

Originally Posted by przemo (Post 5523747)

will the nvidia-switch script work with driver installed from NVIDIA.run installer????

No.

fogpipe

04-02-2016 10:16 PM

Just wanted those interested to know that using the 364.12-Beta i have been experiencing crashes and one hard freeze in quake2 (the jdolan improved aprq2 executable) going back to the 3.52.63 seems to have fixed the problem.

cwizardone

04-06-2016 11:44 AM

NVidia has released the 364.15-beta driver.

Among other things it,

Quote:

Added support for the following GPUs:
Quadro M6000 24GB
Fixed several EGL driver interaction problems with resizing windows in Wayland.
Fixed a bug that caused some DRM PRIME configurations to fail when DRM KMS was enabled (i.e., nvidia-drm.ko's modeset kernel module parameter was set to "1").
Fixed a bug that could cause a kernel crash when VDPAU was used while DRM KMS was enabled.
Updated the libglvnd snapshot included in the NVIDIA driver package to libglvnd commit b7d75429677eecc00c3701aaa4deac1304bc51ff. This contains a new revision of the libglvnd ABI. The driver is not compatible with a libglvnd older than commit c5bcda3b848fe52d6ae6ef25c917431c06d62d27.
Limited the default concurrency level in nvidia-settings to 32, to avoid hitting the maximum tasks limit on systems with many CPUs.

http://www.nvidia.com/download/drive...x/101704/en-us

cwizardone

04-09-2016 10:37 AM

Improved Vulkan Driver Support in Nvidia's new 364.16 driver.

Improved Vulkan Driver Support in Nvidia's new 364.16 driver.
The list of supported GPUs and download links can be found here,

https://developer.nvidia.com/vulkan-driver

Improvements are listed in this article,

https://www.phoronix.com/scan.php?pa...6-Linux-Vulkan

cwizardone

04-11-2016 01:32 PM

Just FYI, google-earth will not work with the 364.16 driver (at least not on this box).
:scratch:

cwizardone

04-22-2016 01:02 PM

The Nvidia 364.19 driver has been released.

The production version of the Nvidia 364.19 driver has been released.

Quote:

Added support for the following GPUs:
Quadro M6000 24GB
Quadro M5500
Fixed some locking issues in libnvidia-egl-wayland.so.
Fixed several libnvidia-egl-wayland.so interaction problems with buffer management Wayland protocols.
Fixed several EGL driver interaction problems with resizing windows in Wayland.
Fixed a bug that caused some DRM PRIME configurations to fail when DRM KMS was enabled (i.e., nvidia-drm.ko's modeset kernel module parameter was set to "1").
Fixed a bug that could cause a kernel crash when VDPAU was used while DRM KMS was enabled.
Changed the default OpenGL installation type to use the GLVND GLX client libraries rather than the legacy non-GLVND libraries.
Added initial support for Direct Rendering Manager Kernel Modesetting (DRM KMS).See the DRM KMS section of the README for details.
Added a new kernel module, nvidia-drm.ko, which registers as a DRM driver with both PRIME and DRM KMS support.
Added support for the following EGL extensions:

EGL_EXT_platform_wayland

to enable Wayland applications to run on NVIDIA's EGL implementation,

EGL_WL_bind_wayland_display

to enable Wayland compositors to run on NVIDIA's EGL implementation, and

EGL_EXT_device_drm
EGL_EXT_output_drm
EGL_EXT_stream_consumer_egloutput

to enable Mir and Wayland compositors to display their content through EGLDevice, EGLOutput, and EGLstreams.

Added a Wayland platform library, libnvidia-egl-wayland.so, to allow Wayland compositors that support EGLDevice, EGLOutput, and EGLstreams to share EGL buffers with Wayland applications.
Fixed a bug that could cause incorrect frame rate reporting on Quadro Sync configurations with multiple GPUs.
Added support for the Vulkan API version 1.0.
Improved X colormap precision from 8 significant bits to 11 on GeForce GPUs.Quadro GPUs already used 11 bits of precision.
Added a new RandR property, CscMatrix, which specifies a 3x4 color-space conversion matrix.The matrix is applied after the X colormap and before the gamma ramp.This property is available on GF119 and newer GPUs.
Improved handling of the X gamma ramp on GF119 and newer GPUs.On these GPUs, the RandR gamma ramp is always 1024 entries and now applies to the cursor and VDPAU or workstation overlays in addition to the X root window.
Reworked how the NVIDIA driver registers with the Linux kernel's DRM subsystem for PRIME support.As a result, PRIME support requires Linux kernel version 3.13 or newer (previously, PRIME support required Linux kernel version 3.10 or newer).
Improved the interactivity of applications that use a hardware cursor while G-SYNC is active.

http://www.nvidia.com/download/drive...x/101818/en-us

This one works with google-earth.

kjhambrick

04-22-2016 01:51 PM

Thanks cwizardone !

Just in time for tomorrow's upgrades !

-- kjh

Code:

# cat updates-B60420-042013.lst-not-installed-yet

Code:

slackware64/a/coreutils-8.25-x86_64-2.txz

slackware64/a/glibc-zoneinfo-2016d-noarch-1.txz

slackware64/ap/vim-7.4.1752-x86_64-1.txz

slackware64/d/cmake-3.5.2-x86_64-1.txz

slackware64/d/perl-5.22.1-x86_64-2.txz

slackware64/n/bluez-5.39-x86_64-2.txz

slackware64/n/libgcrypt-1.7.0-x86_64-1.txz

slackware64/x/mesa-11.2.1-x86_64-1.txz

slackware64/x/xf86-video-intel-git_20160418_562ae1f-x86_64-1.txz

slackware64/xap/imagemagick-6.9.3_8-x86_64-1.txz

slackware64/xap/vim-gvim-7.4.1752-x86_64-1.txz

cwizardone

05-20-2016 08:40 AM

The Nvidia 367.18-*Beta* Driver has been released.

The latest Driver from Nvidia, the 3667.18-Beta, has been released with the following fixes and updates:

Quote:

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 sometimes prevented flipping from being enabled on systems with multiple displays.
Fixed a bug that could cause applications to crash when using the EGL_EXT_platform_device extension on a system with multiple GPUs.
Fixed a bug that could cause nvidia-installer's runtime loader test to fail spuriously on some systems.
The NVIDIA Unified Virtual Memory kernel module, nvidia-uvm.ko, now has a minimum kernel requirement of Linux 2.6.32. On older kernel versions, nvidia-uvm.ko will be compiled as a stub kernel module which does not provide any functionality.
Updated the libglvnd snapshot included in the NVIDIA driver package to libglvnd commit b7d75429677eecc00c3701aaa4deac1304bc51ff. This contains a new revision of the libglvnd ABI. The driver is not compatible with a libglvnd older than commit c5bcda3b848fe52d6ae6ef25c917431c06d62d27....

Edit in: Working perfectly on this box. <--strke that.

cwizardone

05-21-2016 03:47 PM

Well, I've had some trouble with the desktop wallpaper suddenly disappearing, so the 367.18-Beta driver has been removed, the short term 364.19 driver re-installed, and all has returned to what passes for "normal."
:)

Drakeo

05-21-2016 08:25 PM

Quote:

Originally Posted by cwizardone (Post 5548876)

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

cwizardone

05-21-2016 08:53 PM

Quote:

Originally Posted by Drakeo (Post 5548985)

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?
:scratch:

cwizardone

06-13-2016 05:53 PM

Linux x64 (AMD64/EM64T) Display Driver 367.27.

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 (Post 5560406)

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 (Post 5560411)

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 (Post 5632462)

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 (Post 5642236)

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)

kingbeowulf

02-26-2017 05:15 PM

Quote:

Originally Posted by kingbeowulf (Post 5673292)

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

woot. I was able to figure out how to patch nvidia-installer to remove GPU check and prevent conflicting file deletion. Good Grief, it's been a long time since I looked at this much code. Just a few more clean-ups and a new nvidia-switch

Using nvidia-installer will help with

Allow simple version bumps (hopefully)
Better tracking of added/changed libs

cwizardone

05-04-2017 04:57 PM

New Long Term Nvidva Driver ver. 375.66 Released.

NVIDIA has released it latest "Long Lived Branch" driver, version 375.66.

http://www.nvidia.com/Download/drive...x/118290/en-us

sramov

05-06-2017 03:45 AM

Quote:

Originally Posted by cwizardone (Post 5706345)

NVIDIA has released it latest "Long Lived Branch" driver, version 375.66.

http://www.nvidia.com/Download/drive...x/118290/en-us

Works fine here on 4.4 and 4.9 LTS kernels.

All times are GMT -5. The time now is 06:37 PM.