LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-06-2009, 10:09 AM   #1
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Rep: Reputation: 54
Slackware 64 or SlamD64?


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?

Thanks in Advance for the help.
Ace
 
Old 12-06-2009, 10:42 AM   #2
manwichmakesameal
Member
 
Registered: Aug 2006
Distribution: Slackware
Posts: 804

Rep: Reputation: 110Reputation: 110
Have you tried packages for Slack64 instead of Slamd64? It's possible that they are linked to files that are in a different place.
 
Old 12-06-2009, 10:53 AM   #3
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
You must have done something wrong because you shouldn't use the slamd64 compat libs.

1) Download all packages seen here:
http://connie.slackware.com/~alien/multilib/
also download all packages in the subdirectories here:
http://connie.slackware.com/~alien/m...re64-compat32/
maintain the directory structure.

2) Run:
Code:
upgradepkg --reinstall --install-new *.t?z
installpkg *-compat32/*.t?z
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.
 
Old 12-07-2009, 04:11 PM   #4
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
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.

Thanks H_Tex. I appreciate it.

Ace
 
Old 12-08-2009, 05:21 PM   #5
jnsg
Member
 
Registered: Jan 2005
Location: Kentucky, USA
Distribution: Slackware 13
Posts: 125

Rep: Reputation: 15
Quote:
Originally Posted by H_TeXMeX_H View Post
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?
 
Old 12-08-2009, 07:03 PM   #6
nick_th_fury
Member
 
Registered: Jun 2003
Location: Texas
Distribution: Slackware, NetBSD
Posts: 151

Rep: Reputation: 23
Quote:
Originally Posted by jnsg View Post
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.

As to adding the 32bit compatibilty for userland apps, I think you should read this:
http://connie.slackware.com/~alien/multilib/README
That does a good job of explaining what to do.

Last edited by nick_th_fury; 12-08-2009 at 07:09 PM. Reason: Adding
 
Old 12-08-2009, 08:30 PM   #7
jnsg
Member
 
Registered: Jan 2005
Location: Kentucky, USA
Distribution: Slackware 13
Posts: 125

Rep: Reputation: 15
Quote:
Originally Posted by nick_th_fury View Post
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.

As to adding the 32bit compatibilty for userland apps, I think you should read this:
http://connie.slackware.com/~alien/multilib/README
That does a good job of explaining what to do.
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.

Last edited by jnsg; 12-08-2009 at 08:33 PM.
 
Old 12-08-2009, 10:17 PM   #8
kingbeowulf
Senior Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware
Posts: 1,266
Blog Entries: 11

Rep: Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744
re: Slackware 54 or SlamD64

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?
 
Old 12-09-2009, 02:30 AM   #9
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Quote:
Originally Posted by beowulf999 View Post
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.
 
Old 12-09-2009, 03:07 AM   #10
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by H_TeXMeX_H View Post
Same here, I don't use the slackbuild for this. I also don't see any CLI options to enable this.
Yup,same here as well. At the very final step the setup asks you if you would like to install 32bit-compat packages. Maybe you could try that?
 
Old 12-09-2009, 03:14 AM   #11
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Quote:
Originally Posted by ~sHyLoCk~ View Post
Yup,same here as well. At the very final step the setup asks you if you would like to install 32bit-compat packages. Maybe you could try that?
yes, but that's via the curses interface, would that work as a slackbuild ?
 
Old 12-09-2009, 06:54 AM   #12
imitheos
Member
 
Registered: May 2005
Location: Greece
Posts: 441

Rep: Reputation: 141Reputation: 141
Quote:
Originally Posted by jnsg View Post
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.
 
Old 12-09-2009, 07:32 AM   #13
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
jnsg

I'm not sure how to do it with slackbuild, but I use the binary from nvidia website and then do:

Code:
sh NVIDIA-* -qa --kernel-source-path=/usr/src/linux
 
Old 12-09-2009, 08:50 AM   #14
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
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)

Thanks
Ace
 
Old 12-09-2009, 08:59 AM   #15
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled
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.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
The future of Slamd64 now that Slackware 13.0 has been released ??? tallship Slackware 22 10-03-2009 01:30 PM
slamd64-12.2 to slackware-13.0 leftty Slackware 2 09-14-2009 02:39 PM
lilo + Slackware + Slamd64 Daedra Slackware 3 02-20-2009 12:36 AM
Slackware vs Slamd64 tdos20 Slackware 6 02-23-2007 01:33 AM
Is slamd64 worth removing slackware current? cheater1034 Slackware 4 06-13-2005 05:50 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration