[SOLVED] Slackware64 multi-lib and Nvidia graphics?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm just about to install Alien Bob's multi-lib packages for Slackware64. Everything looks easy, but I've got a question about this part of the instructions:
After installing the ”-compat32” packages, you may have to re-install your binary Nvidia or Ati video X.Org drivers. These driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. If you installed the driver files for both architectures, the ”mesa-compat32” package will overwrite some of the 32bit library files.
On the other hand, if you originally only installed the 64bit driver libraries for your Nvidia/Ati card, it is recommended after installation of the multilib packages, to re-install the binary driver package. This time, choose to install the 32bit driver files as well.
The graphical 32bit applications that you are going to run on your multilib installation will require these 32bit driver libraries. Crashes are likely to occur if you fail to install the correct files.
Right now, I'm on pure 64-bit Slackware64-13.1, and I'm using the Nvidia driver from Slackbuilds.org (along with the nvidia-kernel and libvdpau packages from there too).
Do I have both 32- and 64- bit bindary drivers installed as part of the package from Slackbuilds.org?
Could I avoid all this hassle by simply not installing the mesa-compat32 package?
If I do need to reinstall the Nvidia binary driver, do I just upgradepkg --reinstall nvidia-driver-195.36.15-x86_64-1_SBo.tgz?
ls -l /usr/lib/libGL* for the 32 bit ones
ls -l /usr/lib64/libGL* for the 64 bit ones
Here's the showing from this (32 bit) box
bash-3.1$ ls /usr/lib/libGL*
The 96.43.14 files are nvidia's proprietary files, and the symlinks point to them. Here's a complete list
bash-3.1$ locate *96.43.14
Now you can go back in, I imagine, and fix the symlinks after installing mesa-compat32 or reinstall
2. Not really. 32 bit packages simply may not run.
I run pure64 so take this with a grain of salt, but I think you are confused -- the nVidia proprietary drivers should install *both* 64-bit and 32-bit drivers when compiling on a multilib-capable system (there may be a configuration option in the SlackBuild or a question asked in the installer that asks you if you want to build for 32-bit as well as 64-bit, but I'm not sure). You should *not* install two separate nVidia packages for each architecture AFAIK -- just install the proper multilib packages and rebuild the nVidia driver on your now-multilib system and verify that the package contains both 32-bit and 64-bit libraries.
Personally, I make packages of the 32bit compatibility drivers from nvidia. Here is my blog article and some EXAMPLE Scripts. They are really just hacks of the slackbuilds script and the accompanying nvidia-switch utility... I'm not sure if the main nvidia-switch utility has multilib support for switching. That's the only reason I hacked a year ago. slackware64-nvidia-driver-compat32
I try to keep it reasonably updated... at least each time I install a new version of the drivers.
Really though, if you don't intend on ever using mesa or the open source drivers, it's just easier to use the nvidia installer as is and not think about it.
Thanks for the heads up and the link to your blog post.
It looks as though you're the source of the files in Ponce's Sbo-git repository. In any event, I'll be building it soon. Thank you.
Is the libvdpau-compat32 really needed?
It does sound, however, like simply using the Nvidia installer is easier than making packages, and that seems to be what most people here do. How easy is it to switch from the Slackbuild to the Nvidia installer?
I'm torn. I'm more comfortable with a Slackbuild package, but people seem to have great success with the standard Nvidia installer. It would be nice if the compat32 stuff could get a little more attention.
I agree with the lumak. The only benefit of using the slack packages is the ability to switch between the nvidia binary driver and the open source driver. I make packages out of everything (even my kernels) except for the nivida driver. Just use the nivida installer since it will install both 64bit and 32bit libraries for you. Plus the installer can also uninstall the drivers for you, just run the script like this
Just use removepkg or pkgtools to remove your slackbuilds packages before you use the nvidia installer.
A further update: I've now got Alien Bob's WINE package installed on Slackware64_13.1 multi-lib with my Nvidia driver and the best part is: I'm running Red Baron 3D in WINE, in all its Glide wrapped glory!
So the Nvidia-compat32 and libvdpau-compat32 libraries work.