This section presents hardware-specific information for normal use and troubleshooting.
Your XF86Config file's device section must specify the
tdfx device:
Section "Device"
Identifier "Voodoo3"
VendorName "3dfx"
Driver "tdfx"
EndSection
The Screen section should then reference the Voodoo3 device:
Section "Screen"
Identifier "Screen 1"
Device "Voodoo3"
Monitor "High Res Monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
The kernel module for the Voodoo3 is named tdfx.o and
should be installed in /lib/modules/KERNEL-VERSION/misc/.
It will be automatically loaded by the Xserver if needed.
The DRI 3D driver for the Voodoo3 should be in
/usr/X11R6/lib/modules/dri/tdfx_dri.so.
This will be automatically loaded by libGL.so.
xdpyinfo to verify that all your visuals are depth 16.
Edit your XF86Config file if needed./dev/3dfx device is not used for DRI; it's only for
Glide on older 3dfx hardware.
FX_GLIDE_SWAPINTERNVAL
environment variable.
The value of this variable indicates the maximum number of
swap buffer commands can be buffered.
Zero allows maximum frame rate.glTexEnv mode GL_BLEND is not directly supported
by the 3dfx hardware.
It can be accomplished with a multipass algorithm but it's not
implemented at this time.
Applications which use that mode, such as the Performer Town
demo, may become sluggish when falling back to software
rendering to render in that mode.
Your XF86Config file's device section must specify the
i810 device, and specify a usable amount of video
ram to reserve.
Section "Device"
Identifier "i810"
VendorName "Intel"
Driver "i810"
VideoRam 10000
EndSection
The Screen section should then reference the i810 device:
Section "Screen"
Identifier "Screen 1"
Device "i810"
Monitor "High Res Monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
The kernel module for the i810 is named i810.o and
should be installed in /lib/modules/KERNEL-VERSION/misc/.
It will be automatically loaded by the Xserver if needed.
The DRI 3D driver for the i810 should be in
/usr/X11R6/lib/modules/dri/i810_dri.so.
This will be automatically loaded by libGL.so.
xdpyinfo to verify that all your visuals are depth 16.
Edit your XF86Config file if needed.Your XF86Config file's device section must specify the
mga device:
Section "Device"
Identifier "MGA"
VendorName "Matrox"
Driver "mga"
EndSection
The Screen section should then reference the MGA device:
Section "Screen"
Identifier "Screen 1"
Device "MGA"
Monitor "High Res Monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
The kernel module for the G200/G400 is named mga.o and
should be installed in /lib/modules/KERNEL-VERSION/misc/.
It will be automatically loaded by the Xserver if needed.
The DRI 3D driver for the G200/G400 should be in
/usr/X11R6/lib/modules/dri/mga_dri.so.
This will be automatically loaded by libGL.so.
xdpyinfo to verify that all your visuals are depth 16.
Edit your XF86Config file if needed.No data at this time.
Your XF86Config file's device section must specify the
r128 device:
Section "Device"
Identifier "Rage128"
VendorName "ATI"
Driver "r128"
EndSection
The Screen section should then reference the Rage 128 device:
Section "Screen"
Identifier "Screen 1"
Device "Rage128"
Monitor "High Res Monitor"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
The kernel module for the Rage 128 is named r128.o and
should be installed in /lib/modules/KERNEL-VERSION/misc/.
It will be automatically loaded by the Xserver if needed.
The DRI 3D driver for the Rage 128 should be in
/usr/X11R6/lib/modules/dri/r128_dri.so.
This will be automatically loaded by libGL.so.
You may also set your screen depth to 32 for 32bpp mode.
While PCI Rage 128 based cards are supported, they do not yet support PCI GART, so they will not perform as well as their AGP counterparts.
DGA is not yet supported in the ATI Rage 128 X server. This feature will be added in a future release.
The driver for this hardware was experimental and is no longer being developed or supported.