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.
I'm currently running Slackware 64 on a HP dv2500 with AMD Turion X2. I'm haven't trouble getting the 32 compatability to run. I've reinstalled and felt I followed Alien_Bob's directions and packages. It's not work like it seems to for most so I've missed something. I was hoping my process flow would show my error to someone that knew what the pitfalls were. Here they are
1) Reinstalled Slackware 13 (64)
2) Updated the graphics card so KDE will work
3) Updated my Broadcom driver so internet will work
4) Installed Wicd so I can get online and search for wireless access.
5) Installed the 32 compat gcc files (per Alien Bob)
6) Installed the 32compat packages (per Alien Bob) though they had SlamD titles
7) Installed Slack Package Manager (pretty sweet program BTW. Good One Mystic)
8) Installed DOSBox 72 (the one I used with Slam D)
9) Installed Wine (don't remember the version but the one I used with SlamD)
Tried to run both DOS and Wine programs. The task bar shows it tries to start but the HDD light flashes like crazy then the task bar clears and the programs never comes up. Anyone have any idea what I'm doing wrong?
Would it be easier to get some of the new packages (KDE4) to work with SlamD 12.2 or continue to attempt to get Slack64 to run 32bit programs?
the first command installs the gcc packages, the second installs all the compat32 (they should be in a directory structure much like on the site)
if the site were ftp you could easily mirror it, but as it is http, I'm not sure how to do it.
3) Reinstall your graphics driver, and include 32-bit compatibility. This step is important, or wine will not work properly. This is because when you install the compat32 libs, mesa overwrites your current GL libs, so you have to reinstall your graphics driver no matter what to fix that. Unless, you don't use a graphics driver that replaces mesa.
Well I now have D-Box working (sorta, the keys are acting funny but I'm thinking it's a configuration issue) And WINE works well. So 1 of 2 things was the issue.
1) Using SlamD 32compat files
or
2) Updating graphics before installing compat pkgs.
This time (for those interested )
1) Downloaded the gcc and compat32 pkgs from connie.slackware.com (Thanks Alien Bob)
2) I installed Slackware64.
3) copied the 32 compat files to home directory.
4) Updated the gcc files per Alien Bob's instructions
5) installed the compat pkgs per Alien Bob's instructions
6) updated video card driver
7) brought up KDE and installed DOSBox 0.72 and WINE from terminal window
8) open Dolphin and right clicked examples of each style program and they both worked.
3) Reinstall your graphics driver, and include 32-bit compatibility. This step is important, or wine will not work properly. This is because when you install the compat32 libs, mesa overwrites your current GL libs, so you have to reinstall your graphics driver no matter what to fix that. Unless, you don't use a graphics driver that replaces mesa.
Not to hijack the thread, but I have a question about this. I installed my Nvidia proprietary driver using the slackbuild from slackbuilds.org, which seems to build either a 32- or 64-bit package. How can I "include 32-bit compatibility"? I don't think I can just install the 32-bit version of the package on top of the 64-bit version, or can I?
Not to hijack the thread, but I have a question about this. I installed my Nvidia proprietary driver using the slackbuild from slackbuilds.org, which seems to build either a 32- or 64-bit package. How can I "include 32-bit compatibility"? I don't think I can just install the 32-bit version of the package on top of the 64-bit version, or can I?
Is your setup not working correctly after installing the 64bit driver? I usually just build the driver to match the kernel that I'm installing it into.
I don't think they'd even install to the same place, so I wouldn't install one without removing the other first. I'm guessing the 32bit would probably give you a 'No such file or directory error. I've never tried to install a 32bit driver on a 64 setup though, so I'm not positive.
Is your setup not working correctly after installing the 64bit driver? I usually just build the driver to match the kernel that I'm installing it into.
I don't think they'd even install to the same place, so I wouldn't install one without removing the other first. I'm guessing the 32bit would probably give you a 'No such file or directory error. I've never tried to install a 32bit driver on a 64 setup though, so I'm not positive.
I think you misunderstand. I have a working 64-bit system, including the 64-bit Nvidia driver. I have already followed Alien BOB's procedure for adding 32-bit compatibility, and I have successfully compiled 32-bit Wine on my 64-bit Slackware system.
What H_TeXMeX_H suggests is the same thing that Alien BOB's guide says here:
Quote:
Originally Posted by Alien BOB's guide
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.
My question is, how does one install both the 64- and 32-bit Nvidia packages? I don't know if I'm the only one running multilib and using the slackbuilds.org package of the driver or if others just haven't run into an issue yet, but I intend to run Wine (it's basically the sole reason for my setting up multilib) and it's been stated that Wine specifically needs the 32-bit video driver.
My guess is that the .run file for the driver gives you the option to install both, but the slackbuild doesn't support that. I just figured someone would have run into this issue by now, but I haven't seen it mentioned anywhere I've looked.
I have always used the NVIDIA-*.run packages to install the 64 and 32 bit drivers in both SLAMD64 and SLACKWARE64. Works well. The only reason to use the slackbuilds is if you suddenly have an urge to return to the open source nv driver (ad so have to restore not just it but mesa as well. The slackbuild package makes that easier. But until the Nouveau drivers are ready, why give up 3D accelleration?
I have always used the NVIDIA-*.run packages to install the 64 and 32 bit drivers in both SLAMD64 and SLACKWARE64. Works well. The only reason to use the slackbuilds is if you suddenly have an urge to return to the open source nv driver (ad so have to restore not just it but mesa as well. The slackbuild package makes that easier. But until the Nouveau drivers are ready, why give up 3D accelleration?
Same here, I don't use the slackbuild for this. I also don't see any CLI options to enable this.
Not to hijack the thread, but I have a question about this. I installed my Nvidia proprietary driver using the slackbuild from slackbuilds.org, which seems to build either a 32- or 64-bit package. How can I "include 32-bit compatibility"? I don't think I can just install the 32-bit version of the package on top of the 64-bit version, or can I?
I may be wrong but i see that the slackbuild mentions
NVIDIA-Linux-x86_64-190.42-pkg0.run. I have the impression
that 32bit compatibility libraries are shipped only in the pkg2.run
I think that nvidia packages go like this:
pkg0: only necessary libs and module source
pkg1: pkg0 + precompiled modules for some distros
pkg2: pkg1 + 32bit libs
If i remember correctly, installing the pkg2.run file will
install 32bit libs fine.
I downloaded the 64 bit from the NVIDIA website and just
./NVIDIA_64_blah-blah.run.txt
And it installed the driver. I did it after I upgraded the 32compat packages per Alien Bob.
I then, just to have both, down loaded the 32 bit driver but when I went to install from the prompt, it told me I didn't have a 32 bit machine and didn't install.
I didn't do any hacking or SlackPack type install just tried to run the
./NVIDIA_32_blah-blah.run
file.
Do you have to have the 32 file to run a 32 bit program? I've run my DOX Box and WINE stuff with no issue except for the Wizard 101 out of WINE (as seen on another thread)
I'm running Slack64 with multilib and only installed the 64 bit NVIDIA-*run , and everything's OK. I think I answered "yes" to all the questions during setup, about it compiling modules, writing an xorg.conf plus backup of the old one, etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.