What's new:

NOTE: These drivers are intended only for Voodoo3 or Voodoo Banshee based cards they will NOT work on Voodoo Graphics, Voodoo2, or Voodoo Rush based cards.

System Requirements:

• A working install of Linux based on the 2.2.x
• Your Linux kernel must support loadable modules in order to make use of the 3dfx Device Driver.
• A Voodoo Banshee or Voodoo3 PCI or AGP accelerator.

What's Included:

• 3dfx Device Driver
• The 3dfx device driver for /dev/3dfx allows Glide applications to run without root privileges. This package is distributed as a source RPM only, as it must be compiled for your specific kernel version. You must have development tools installed on your system to create the module. Note that no changes to existing applications are required to use this driver.
• Glide2x and Glide3x
• Glide is 3dfx's low level rasterization API. Mesa3D makes use of Glide2x in order to accelerate rendering in OpenGL API programs.
• Glide3x is a newer release of the Glide API with enhancements for newer hardware features. It is not source compatible with Glide2x. However, there are almost no applications that make use of the Glide3x API. In most circumstances you do not need Glide3x, its is provided for reference value.
• An X Server for XFree86 3.3.5
• The X Server is the 2D graphics driver.
• XF86Setup
• XF86Setup is a GUI configuration tool for X. It will help you to configure X with your new drivers for 3dfx. It is recommended that you use this if this is your first time installing 3dfx drivers, especially if you are new to Linux.
• Source for Glide is available on the Glide source page.
  • This is the source code to everything listed above. Do you want to hack Glide to make it faster, or add more features? Do you want to port Glide to Alpha or Sparc Linux, or to BSD? Do you want to know how it all works? Then download the source and hack away. And if you're serious about contributing changes and improvements to Glide visit the Developer Page for more information about the CVS tree and mailing list.

• You'll need to know a few things about your system in order to choose the right driver packages.
• Glibc version
• execute the following command and see what version you have
  ls /lib/ld*
  and read the version number from the file listed.
• If you've installed your own version of glibc then you should know what version it is.
• Unfortunately there are no binary Glide packages for libc5x at this time. If you are using libc5x you may consider building the drivers from source or you may consider upgrading you C library.
• XFree86 Version
• If you are running X, execute this command:
  xdpyinfo | grep vendor
• Look at the line that says "vendor release number: XXXX" The more traditional form of the number has decimal points so think of the number as something like 3.3.3 or 3.3.5

• It's recommended that you run with the 3DFX X server. Other X servers may work, but there is no guarantee.
• All 3D applications must be run from within X.
• For each full screen 3D resolution you want to use, you must define an X resolution of the same size. We recommend defining at least 640x480 and 800x600 modes. You can use XF86Setup to do this by selecting multiple resolutions in the mode section.
• The 2D X server may be run at any depth.
• Full screen 3D resolutions always run in 16 bits per pixel.

Installation with RPM:

1. Become root
2. Configure the 2D X Server:
1. Choose and download the appropriate packages based on your current version of XFree86 from this table.

   XFree86 Version	XFree86 3.3.3	XFree86 3.3.5
   X_Package	XFree86_3DFX-SVGA-3.3.3-5.i386.rpm	XFree86-SVGA-3.3.5-4.i386.rpm
   XF86Setup_Package	XFree86_3DFX-XF86Setup-3.3.3-5.i386.rpm	XFree86-XF86Setup-3.3.5-4.i386.rpm

   Install the packages you chose with the following command(s) using the names of the packages you downloaded in the previous step:
   rpm -Uvh X_Package
   rpm -Uvh XF86_Setup_Package
   

2. Use XF86Setup to assist with setting up the X Server execute the following command:
   XF86Setup
   Remember to select all resolutions that you want to use for 3D as well as your desired desktop resolution.
3. If you don't want to use XF86Setup then you will need to create and XF86Config file via some other means.
3. This concludes the installation of the 2D display drivers. Do not continue with the 3D driver installation until the 2D driver is properly configured.
4. To configure the fullscreen 3D driver
   1. Choose the appropriate packages based on you system's C library.

      Glibc Version	Glibc2.1	Glibc2.0	libc5
      Device_Driver	Device3Dfx-2.3-5.src.rpm	Device3Dfx-2.3-5.src.rpm	Device3Dfx-2.3-5.src.rpm
      Glide2x3x_Package	Glide_V3-2.60-16.i386.rpm	Glide_V3-2.60-16.i386.glibc2.0.rpm	Not Available
      Glide_SDK	Glide_SDK-2.2-16.i386.rpm	Glide_SDK-2.2-16.i386.rpm	Glide_SDK-2.2-16.i386.rpm

   2. Execute this command to build the 3dfx device driver:
      rpm --rebuild Device3Dfx-2.3-4.src.rpm
      
   3. RPM will place the resulting binary package in your RPM tree. 
5. Install the resulting binary package using the location of your RPM tree found in the previous step:
   rpm -Uvh RPM_PATH/RPMS/i386/Device3Dfx-2.3-4.i386.rpm
   
6. Install the Glide package.
   • The new combined Glide package doesn't have a clean upgrade path from the old separate packages. If you had installed any of the previous Glide_V3-2.60-xx or Glide_V3-3.10-xx packages you should uninstall them now. To uninstall the old Glide packages execute this command:
     rpm -e Glide_V3
     rpm -e Glide_V2
     If you get errors indicating that no Glide_V3 or Glide_V2 package is installed that is ok.
   Now install the new Glide package by substituting the name of the package you downloaded intp the following command:
   rpm -Uvh Glide2x3x_Package
   
7. You should also install the SDK, or Software Development Kit. It includes header files used to compile Glide programs. Even if you don't plan on writing any of your own Glide programs these headers are required for compiling software like Mesa. To install the SDK execute the following command:
   rpm -Uvh Glide_SDK
   
8. If you had previously installed an older version of the Device3Dfx module you will need to unload it or reboot. If you are unsure of what to do then reboot your system with the following command:
   shutdown -r now
9. Now you need to test the configuration. Do not skip this step If you can't run this simple test, no games will function.
   Execute the following commands:
1. /usr/local/glide/bin/testGlide2x
   You should see a soothing blue screen with the text "press a key to quit" in the upper left.
2. /usr/local/glide/bin/testGlide3x
   You should see the same soothing blue screen with the text "press a key to quit" in the upper left.
3. You should consider running these tests as a non-root user as well.