Have AMD Athlon900 PC133,30GB w/ NV6 Vanta LT and PIII600e PC100 w/ATI RagePro
1 Ques. is what ver of Slackware stops providing Legacy Video Drivers Support?

2 Ques. Which Slackware stops using xorgconfig? - Confused about this b/c i think I read a post that said xorgconfig is no longer used to configure X11?

3 Ques. I found the following post:
"downloaded slackbuilds for nvidia. Need help with xorg.conf"
but I need more,

a) basic instruction for downloading the nvida-legacy71-driver and nvida-legacy71-kernel *from cline b/c I am doing another fresh install of 12.2 so i won't setup X before installing driver.

b) I don't understand the kernel part. How do I actually unpack, install and to what location?

I have a few older computers and want to setup the AMD as a KDE Desktop all the yrs. I been trying to learn slackware I've only use XFCE and even in 12.2 i still get the screen saver errors when I shut down. I think I will use the PIII600e PC100 Slackware12.1 for server router it has 320gb.or do u think I shld setup the PIII as the desktop, Or shld I request support for this in another post?

c) I had successfully installed 12.2 and got X to work w/nv did not completely configure my monitor for X so I had a little flickering of thin white lines but I have a AGP4 ATI Card on 12.1 and after setting up modeline and all resolution settings in Xorg I don't have any issues. Going to switch card out with old geforce2 card.

I can help on Nvidia and since your post alludes to you may not know how to install from SlackBuilds I'll copy and paste a post an Admin made on how to install from Slackbuilds and an exerpt from a post I made on Setting Slack up.
Both were intended for 12.2 btw and this reply will be lengthy.

How to Utilize SlackBuilds <muaythaimaster74>

If you're using slackware, you'll find there are many packages not "included" with the base distribution. Slack tends to use vanilla packages with little or no patching from how the application was intended by the author upstream... so this means that you can build virtually anything you need with the excellent build tools.

Utilizing slackbuilds from slackbuilds.org is a good way to do this.

First, we need to su to root so that we can build and install the packages. so we open a terminal and type

then we need to create our build directory. this can be anywhere, but you may want to put it in your user's home directory. So we create the directory like so.. substitute your user name where "user" is listed.

then we'll change directory to our build directory

now we can begin building packages. navigate in your favorite web browser to http://slackbuilds.org/

On the right hand side of the screen you will find a search navigation tool, and the version number. So if you're using slackware 12.2, you select that and then search for the package you want to build. Let's try something simple like flash... which brings us to this page.
http://slackbuilds.org/result/?search=flash&sv=12.2

now at this point the different options available for building flash are listed. We'll simply go with flash-player-plugin so we can watch some videos on youtube.
http://slackbuilds.org/repository/12...player-plugin/

Now that we're on this page, we have access to the slackbuild tar ball and a link to the source required to compile it. It's a good idea to read the README file linked to at the bottom of the page and to peruse the slackbuild script.

Next we'll download the slackbuild in our terminal session using wget which is very reliable. Simply right click on the link to the slackbuild source under "Download slackbuild" and select "copy link location". Then type

then leave a space and right click in the terminal and select paste. this will paste the location of the source slackbuild for you to download. then hit enter. so in this case it would look like this.

now we need to untar the archive

now we need to see what directory has been created, and we can do this with ls

it will show the directory. in this case it's "flash-player-plugin". so we'll change to that directory.

now we'll download the source linked to on the slackbuild page under "Download Source"

we now want to make sure that our slackbuild is fine, so we can open a text editor and take a look to make sure everything seems fine. sometimes the slackbuild site doesn't link to the latest version available, so we can navigate to the homepage of the original author, download the source and edit the slackbuild. we'll cover that another time however and focus on installing this slackbuild.

next we have to ensure that the slackbuild is executable.

now we're ready to build the package.

the program will compile now, assuming we've met the needed dependencies. flash-player-plugin doesn't have any additional dependencies, so it should compile just fine on a stock slack install.

the created package is created and moved to /tmp, and the full file name is listed. we can either cd to the tmp directory and then use installpkg, or we can simply use the full path. so our next step is to install the package now.

congrats! you have just compiled your first slackware compliant package and installed it.




inittab and nvidia drivers.

2. To get a user/passwd login splash open a terminal and:
1. su to root
2. type- There is a section that will look like:


Just below it is the line which needs edited.

The default level is normally 3 by default, change it to 4 and you will have the graphic login as well as have the reboot, shutdown option from your menu.
Reboot directly after saving the edit.

3. It seems xorgconfig doesn't quite figure out the scroll wheel on the mouse for some reason.
It's an easy fix.
Open your terminal.
Su to root and type,,, Use your arrow keys and space bar to navigate to the section concerning the mouse.
You'll see an uncommented line that probably says"

Backspace the PS out and insert IMPS, don't just add IM to it.
Dunno what difference it makes but it hosed my entire X11 when I just added IM.

Make that line just like below as well as adding the next line:

Make sure there isn't a comment >#< at Options emulate 3 buttons as well.

Strike ctrl x,, select y and enter.
Close the terminal.
Restart X and your scroll should now function.

4. Nvidia driver

Edit: At this point in time the Nvidia driver and kernel module are outdated.
Your performance will be much better by installing the proprietary driver from Nvidia itself.
If you're already running the driver from slackbuilds, first remove it by following the switch instructions found on the driver page written and maintained by ppr-kut.
It's simple, run switch, then remove the driver, then proceed with below.

To install the proprietary driver:
1.] Download the driver to your desktop.
2.] open a terminal, su to root and do nano /etc/inittab, change the boot level back to 3. [see above], save and exit.
3.] reboot and log in as root
4.] cd to /home/user-name/Desktop
5.] type ls and a list of what is on your desktop will show including the driver.
6.] type sh NVIDIA-Linux-whatever the label of the driver states that you downloaded and press enter.
7.] accept the licensce and allow the installer to build the kernel module, also allow nvidia-xconfig.
8.] after the install, reboot and log in as user, then type startx to check that everything worked.
9.] You may want to check below and edit you xorg.conf as shown,,, that's your decision.
10,] If everything performs well and seem's ok, the change your inittab back to runlevel 4 and you're set to go.

Installing the driver from Slackbuilds:

You'll first need to install the kernel module from Slackbuilds.org per MT's tutorial and then the driver second.
Disregard the switch function mentioned in the section where the driver is downloaded.
You'll then need to open /etc/X11/xorg.conf as root.
Scroll down and edit the following:


Add this to the very bottom of the list after the last entry:

windtalker thanks, Haven't tried it yet, honestly I'm afraid to. Did not install kernel source trying to conserve hdd install space. Also currently i have no GUI installed so when u say "use your favorite browser to navigate to website.org"? Do u mean I can open a browser from command line without having installed any gui?

The RagePro is supported (with 2D acceleration) but Xorg. There are no extra drivers to install. Theoretically, X should just work with the correct driver if you run 'startx' from the command line. If that doesn't happen, we'd need to see your /var/log/Xorg.0.log file to tell you why.

Adam

Adam I have Nvida Geforce2 GTS/Pro on the AMD box in question bc it has more mb on card than the ati card.

Reinstalled slackware12.2 w/ kernel src and w/0 NV driver... downloaded proprietary legacy nvida driver for my card to desktop.

Install failed. nvidia-installer.log: nvidia: version magic '2.6.27.7-smp SMP mod_unload 686' should be huge-'2.6.27.7

I installed huge-2.6.27.7 apparently this is an issue? How do i fix this?

First attemp failed per previous post. Since I had other issues with the install - i dwnlded new install disk and installed fresh again. I have not initiated any desktops. So i will mkdir /home/me/build and download the driver there?

Installed nVidia proprietary legacy driver. Boot up screen reports the NVIDA Driver has tainted the huge.smp. I used the proprietary driver b/c of posts recommending this driver over the legacy SlackBuild version.
I am thinking of uninstalling the NVidia Proprietary Legacy pkg and using slackbuild ver. Question is this pc is AMD CPU and via chipset - hoow does this affect the install script and/or process. What instruction wld i have to change on install scripts?

I also got the notice that the nvidia driver "taints" the kernel in Slack 12.2. I'm on Slackware64 13.0 now. I don't recall seeing that message when the system boots up on Slack64, but I will check for it on the next reboot.
Anyway, the "taints kernel" message is nothing to worry about. If the driver is working ok then just ignore it. I did.
Also, you should be using the generic-smp kernel unless you have a specific reason not to.

thanks tommcd, for the info... I am removing Kde from that computer anyway.. its too much of a resource hog. Its kind of pretty and has the network and development apps i want to learn, am going to try it in a 3.2ghz pc someone was going to throwout.
Sometimes you want things to just be easy but I am already use to xfce and as i grow i can develop a desktop tailored for what i do. Thats the promise of slackware so I have put years into this learning process.lol
I think i want to install the slackbuild nvidia drivers b/c then i won't get that nvida logo poping up at startup in the bkground and I won't taint the kernel. video quality is probally not even neglagible. Now I have to install Geforce 6600 shows up with 256mb of its own ram is this a legacy 96.43.11 or 173.14.18?

Is Geforce 6600 a legacy card too?

Sorry I never replied to your question when you first asked it nightsky,,,, to many irons in the fire.
Anyway, a gui isn't necesary to download things, you can use wget to retrieve pretty much anything you want which is gone over in the tutorial I posted for you.
As for stopping the nvidia logo from popping up, reread the same tutorial where it concerns editing xorg.conf.

>>Option "NoLogo" "true"<<

thank you all; More questions i hav looked at other tutorials to fill-in my conceptual blanks about the intall process. windtalker10, I used your tut to also download icwm and it worked but where did all the files go afterwards? And I cldn't get wget to work.

1) What is the difference between doing mkdir /home/user/build and using it to build and install apps & drivers and using /usr/local/src as suggested in other tuts? The suggestion being to use /usr/local/src for third party software?

2) So once you build the pkg and install it, where do u save it? /usr/local/src?
Reason I ask is so I can store my favorite apps to re-use on my different computers minimizing reinstalls and facilitating updates. Do i move everything to /usr/local/scr for centralized keeping?

3) During my 1st install of legacy driver - Nvidia Installer had trouble finding my kernel source and I don't understand why bc I reinstalled on that machine the huge.smp kernel and src specifically so Nvidia cld use during 2nd legacy driver install attempt. As for xorg.conf I know howto do that for my monitor, etc.

4) With mainstream Drivers do we use slackbuild scripts like because i did not see anything referring to this geforce 6600 card on slackBuilds.org???
Sorry for all the ques. I just want to do it right on this last slack install. Tired of reinstalling. lol

Cldn't get wget or curl to download frm nvidia.com
All i got was: 301, 302, 404 error messages???

Wound up downloading w/ curl the following: Linux-x86-185.18.36-pkg1.run - shld i rename it? Sooo frustrating all the inconsistencies

is this right? Is it ok that it does not say Nvidia-Linux-x86-185.18.36-pkg1.run?

These files i downloaded were worthless text shells or something.

I need a link i cn put into wget and get a installable
Nvidia-Linux-x86-185.18.36-pkg1.run

Thank you