This Step by Step is based on the original posted by Bruce A. Leggett, <email@example.com>, and is intended to clarify a couple of points I found when I used Bruce's SxS, primarily figuring out which file to get from the nvidia.com ftp site, then some warnings when switching from a different video card.
I started on a Caldera eDesktop 2.4 system with XFree86-3.3.6 already installed from the updates on ftp.calderasystems.com. According to the documentation with from the nvidia.com site, their routines should also work with XFree86-3.3.5 as well.
I didn't run XF86Setup or xF86Setup prior to installing the updates from the nvidia.com ftp site because I had been running an ATI Xpert98 card which didn't have enough RAM to support 32-bit 1600x1200. This was using the Mach64 drives, not the SVGA so it wouldn't have done any good at this time.
Get the software from ftp1.detonator.nvidia.com or from our site where I have it mirrored. This shell script should do the trick. I've used a couple of variable names to keep the line lengths reasonable and make it easier to type if you should be so silly as to want to do it manually.
#!/bin/sh dir=/pub/drivers/english/riva128-riva128zx/linux file=nvidia-X-GLX-335-i386-dyn_tar.gz ncftp ftp1.detonator.nvidia.com:$dir/$file # OR if this is unreachable, uncomment this # ncftp ftp.celestial.com:/mirrors/ftp1.detonator.nvidia.com$dir/$file tar -xvzf $file cd nvidia-X-GLX-335-i386-dyn ./riva_install # this saves the modified XF86Config file as you will need it later cp /etc/XF86Config /etc/XF86Config.save_geforce
You should now be able to run XF86Config or xF86Config, in the normal manner telling it not to use the existing XF86Config file. This will leave modules added by the riva_install script out of the /etc/XF86Config file.
Execute the following command or script to add the module to the end of the /etc/XF86Config file.
#!/bin/sh cp -a /etc/XF86Config /etc/XF86Config.save_update cat >> /etc/XF86Config <<DONE # Added by riva_install script Section "Module" Load "glx.so" EndSection DONE
You should now be able to run ``kde'', ``startx'' or whatever now.
Bill Campbell, <firstname.lastname@example.org>