[SOLVED] NVidia's Latest Long Term Driver, 361.28. Please see correction in post #7.
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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 8,666
Rep:
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.
Last edited by cwizardone; 02-13-2016 at 12:44 PM.
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.
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
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.
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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 8,666
Original Poster
Rep:
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.
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.
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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 8,666
Original Poster
Rep:
Quote:
Originally Posted by Drakeo
......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.
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 |
+-----------------------------------------------------------------------------+
(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.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 8,666
Original Poster
Rep:
Quote:
Originally Posted by elcore
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,....
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
