[SOLVED] Slackware64 multi-lib and Nvidia graphics?

Lufbery · 08-13-2010, 08:26 AM

Hi all,

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:

Quote:

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).

So:

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?

Thanks,

Lufbery · 08-13-2010, 09:51 AM

Anyone? I can't be the only person wanting to use the multi-lib files with the Nvidia driver.

brianL · 08-13-2010, 09:59 AM

I've got multilib, but I installed the NVidia driver from their site, didn't use the SlackBuild.

business_kid · 08-13-2010, 10:03 AM

1. Try
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*
/usr/lib/libGL.la /usr/lib/libGLU.so.1.3.060502
/usr/lib/libGL.so /usr/lib/libGLcore.so.1
/usr/lib/libGL.so.1 /usr/lib/libGLcore.so.96.43.14
/usr/lib/libGL.so.96.43.14 /usr/lib/libGLw.so
/usr/lib/libGLU.so /usr/lib/libGLw.so.1
/usr/lib/libGLU.so.1 /usr/lib/libGLw.so.1.0.0

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
/home/declan/bin/NVIDIA-Linux-x86-96.43.14-pkg1.run
/usr/lib/xorg/modules/extensions/libglx.so.96.43.14
/usr/lib/libnvidia-cfg.so.96.43.14
/usr/lib/libnvidia-tls.so.96.43.14
/usr/lib/libGL.so.96.43.14
/usr/lib/libXvMCNVIDIA.so.96.43.14
/usr/lib/tls/libnvidia-tls.so.96.43.14
/usr/lib/libGLcore.so.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.

3. Yes, that command looks good.

Lufbery · 08-13-2010, 11:07 AM

Okay, I haven't got anything in /usr/lib because this is a 64-bit computer, but there's a bunch in /usr/lib64:

Code:

-rwxr-xr-x 1 root root  652 2010-08-02 23:51 /usr/lib64/libGL.la
lrwxrwxrwx 1 root root   10 2010-08-01 17:53 /usr/lib64/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root   18 2010-08-02 23:51 /usr/lib64/libGL.so.1 -> libGL.so.195.36.15
-rwxr-xr-x 1 root root 455K 2010-04-27 16:25 /usr/lib64/libGL.so.1.2-xorg
lrwxrwxrwx 1 root root   25 2010-08-02 23:51 /usr/lib64/libGL.so.195.36.15 -> libGL.so.195.36.15-nvidia
-rwxr-xr-x 1 root root 936K 2010-03-12 05:19 /usr/lib64/libGL.so.195.36.15-nvidia
-rw-r--r-- 1 root root 508K 2009-08-03 20:34 /usr/lib64/libGLEW.a
lrwxrwxrwx 1 root root   16 2010-08-01 17:53 /usr/lib64/libGLEW.so -> libGLEW.so.1.5.1
lrwxrwxrwx 1 root root   16 2010-08-01 17:53 /usr/lib64/libGLEW.so.1.5 -> libGLEW.so.1.5.1
-rw-r--r-- 1 root root 302K 2009-08-03 20:34 /usr/lib64/libGLEW.so.1.5.1
lrwxrwxrwx 1 root root   11 2010-08-01 17:53 /usr/lib64/libGLU.so -> libGLU.so.1
lrwxrwxrwx 1 root root   20 2010-08-01 17:53 /usr/lib64/libGLU.so.1 -> libGLU.so.1.3.070801
-rwxr-xr-x 1 root root 453K 2010-04-27 16:25 /usr/lib64/libGLU.so.1.3.070801
lrwxrwxrwx 1 root root   22 2010-08-02 23:51 /usr/lib64/libGLcore.so.1 -> libGLcore.so.195.36.15
lrwxrwxrwx 1 root root   29 2010-08-02 23:51 /usr/lib64/libGLcore.so.195.36.15 -> libGLcore.so.195.36.15-nvidia
-rwxr-xr-x 1 root root  28M 2010-03-12 05:19 /usr/lib64/libGLcore.so.195.36.15-nvidia
lrwxrwxrwx 1 root root   11 2010-08-01 17:53 /usr/lib64/libGLw.so -> libGLw.so.1
lrwxrwxrwx 1 root root   15 2010-08-01 17:53 /usr/lib64/libGLw.so.1 -> libGLw.so.1.0.0
-rwxr-xr-x 1 root root  17K 2010-04-27 16:25 /usr/lib64/libGLw.so.1.0.0

So it looks like the proper steps after installing the 32-bit compatibility stuff are to:

Reinstall the 64-bit binary driver from Slackbuilds.org
Download and build 32-bit packages from Slackbuilds.org of the Nvidia driver and deps, but using the convertpkg-compat32 script so that the 32-bit Nvidia drivers don't overwrite the 64-bit ones.

Am I on the right track?

Has anyone else installed both the Nvidia drivers from Slackbuilds.org and made Slackware64 multi-lib?

Thanks,

T3slider · 08-13-2010, 01:15 PM

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.

Lufbery · 08-13-2010, 01:42 PM

T3slider,

I think you're right with the regular Nvidia installer (according to this site), but the Slackbuild for the Nvidia driver seems to require separate 32-bit and 64-bit builds.

There are two downloads (one for 32- and one for 64-bit), and the Slackbuild script itself is set up to either put stuff in /usr/lib or /usr/lib64.

Still researching . . .

Lufbery · 08-13-2010, 01:44 PM

Ah ha! I think I was on the right track!

Ponce's Sbo-git repository has an nvidia-driver-compat32 build.

Regards,

lumak · 08-13-2010, 10:08 PM

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.

Lufbery · 08-14-2010, 09:25 AM

Lumak,

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.

Regards,

Daedra · 08-14-2010, 04:10 PM

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

./NVIDIA-Linux-x86_64-256.44.run --uninstall

Just use removepkg or pkgtools to remove your slackbuilds packages before you use the nvidia installer.

Lufbery · 08-14-2010, 06:31 PM

Well, Lumak's scripts worked well and I got Slackware64 running as a multi-lib installation with the proper 32-bit Nvidia driver installed too.

I may still switch to the regular Nvidia installer, but probably not until I upgrade to the next version of Slackware.

Regards,

Lufbery · 08-14-2010, 08:48 PM

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.

Thanks all!

Daedra · 08-15-2010, 12:47 AM

Just curious what glide wrapper do you use?

Lufbery · 08-15-2010, 03:47 PM

Quote:

Originally Posted by Daedra

Just curious what glide wrapper do you use?

This one: http://www.zeckensack.de/glide/

It comes as a .exe file that opens up and installs via Wine. It seems to work well.

I've got another one on my Windows partition that's simply a .dll that goes somewhere in the windows directory, but I can't remember where I got it.