Nvidia-driver.SlackBuild from SBo (or: I am a bad and sloppy SBo maintainer)
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.
Nvidia-driver.SlackBuild from SBo (or: I am a bad and sloppy SBo maintainer)
With work, the excitment of the upcoming new release, I got all in a tither. Here and the SBo mailing list, some of you had issues with the SBo Nvidia-driver.SlackBuild and had to revert to running nvidia *.run installer. Most of those were sillyb mistakes. My apologies.
These are unofficial, of course, but will be merged into SBo when things settle down.
The current Nvidia-driver.SlackBuild on Sbo is still missing one symlink that, under some conditions, will result in a "libvdpau_nvpau.so missing" error. The fix is:
Code:
cd /usr/lib64
ln -sf libvdpau_nvidia.so.3042.17 libvdpau_nvidia.so
or you can edit the Nvidia-driver.SlackBuild to put
under "#symlinks" and "# symlinks for optional 32-bit support"
Also note, that the current SBo version still copies the various glx.h files from the nvidia package. This will cause errors with some compiles (Firefox
ESR). You can update to the new version (see above), manually revert the glx.h-xorg files, or stop X, login as root and:
With work, the excitment of the upcoming new release, I got all in a tither. Here and the SBo mailing list, some of you had issues with the SBo Nvidia-driver.SlackBuild and had to revert to running nvidia *.run installer. Most of those were sillyb mistakes. My apologies.
You have enormous respect from me for maintainng such a complex slackbuild with a moving target like the nVidia drivers .
Is anyone else having an issue with the /usr/include/GL/glx.h symlink? It's supposed to point to /usr/include/GL/glx.h-nvidia (which it does), but glx.h-nvidia doesn't exist. A file by the name of 'glx-nvidia' exists, and pointing glx.h to that makes OpenGL apps work correctly, but why is it doing this?
Is anyone else having this issue?
Code:
# grep include /var/log/packages/nvidia-driver-302.17-x86-2_SBo
usr/include/
usr/include/GL/
usr/include/GL/glext.h-nvidia
usr/include/GL/glxext.h-nvidia
usr/include/GL/glx-nvidia
usr/include/GL/gl.h-nvidia
# ls -l /usr/include/GL/glx.h
lrwxrwxrwx 1 root root 12 Aug 27 14:21 /usr/include/GL/glx.h -> glx.h-nvidia
With work, the excitment of the upcoming new release, I got all in a tither. Here and the SBo mailing list, some of you had issues with the SBo Nvidia-driver.SlackBuild and had to revert to running nvidia *.run installer. Most of those were sillyb mistakes. My apologies.
I got bitten - twice - by the recent NVidia driver updates. But you know what?
and is fixed for Slackware14. This was brought up in another LQ thread. If you go to the site listed in my OP, you can install the brand spanking new ones. In those, the headers aren't copied over (ie deprecated).
kikinovak, Danke schön. See the OP above for "fixed" version - you should be running that one anyway. Its been crazy juggling 4 -current installs (both arch), work, and this silly ass driver.
Not up on my Austrian lately, but I assume you mean:
Solange man nüchtern ist,
gefällt das Schlechte.
Wie man getrunken hat,
weiss man das Rechte. - J.W. Goethe
Last edited by kingbeowulf; 08-27-2012 at 07:41 PM.
Reason: no spell good.
The README is missing in the nvidia-driver directory which caused the build to fail at first but that won't be hard to fix
Maybe you could add a reminder in this README like "this package installs nvidia-installer, nvidia-xconfig and nvidia-settings, see the relevant manual pages" as some users could overlook that.
While you are at it, you could edit the README for nvidia-kernel as well, something like this:
Code:
sed -i s/edit the copy/edit the copy or run nvidia-xconfig/ README
as nvidia-xconfig provides many options specific to the nVidia driver which can be useful.
Huge thanks, keep up the good work.
Last edited by Didier Spaier; 08-29-2012 at 04:08 PM.
Reason: suggest to edit the README for nvidia-kernel
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.