DRI User Guide : Hardware-Specific Information and Troubleshooting
Previous: General Trouble Shooting
Next: General Limitations and Known Bugs

10. Hardware-Specific Information and Troubleshooting

This section presents hardware-specific information for normal use and troubleshooting.

10.1. 3dfx Voodoo3 Series

10.1.1. Dependencies

The Voodoo3 DRI driver requires a special versions of the 3dfx Glide library. It can be downloaded from the DRI website.

10.1.2. Configuration

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/2.4.x/kernel/driver/char/drm/. 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.

10.1.3. Troubleshooting

10.1.4. Performance

10.1.5. Known Problems

10.2. 3dfx Voodoo5 Series

10.2.1. Dependencies

The Voodoo5 DRI driver requires a special versions of the 3dfx Glide library, different than that used for Voodoo3 hardware. It can be downloaded from the DRI website.

10.2.2. Configuration

Your XF86Config file's device section must specify the tdfx device:

        Section "Device"
            Identifier  "Voodoo5"
            VendorName  "3dfx"
            Driver      "tdfx"
        EndSection
            
The Screen section should then reference the Voodoo3 device:
	Section "Screen"
	    Identifier  "Screen 1"
	    Device      "Voodoo5"
	    Monitor     "High Res Monitor"
	    DefaultDepth 24
	    Subsection "Display"
		Depth       16
		Modes       "1280x1024" "1024x768" "800x600" "640x480"
		ViewPort    0 0
	    EndSubsection
	    Subsection "Display"
		Depth       24
		Modes       "1280x1024" "1024x768" "800x600" "640x480"
		ViewPort    0 0
	    EndSubsection
        EndSection
            

The kernel module for the Voodoo5 is named tdfx.o and should be installed in /lib/modules/2.4.x/kernel/driver/char/drm/. It will be automatically loaded by the Xserver if needed.

The DRI 3D driver for the Voodoo5 should be in /usr/X11R6/lib/modules/dri/tdfx_dri.so. This will be automatically loaded by libGL.so.

The Voodoo5 supports 3D rendering in 16 and 32 bpp modes. When running in 32bpp mode an 8-bit stencil buffer and 24-bit Z (depth) buffer are offered. When running in 16bpp mode only a 16-bit Z (depth) buffer is offered and stencil is implemented in software.

A software-based accumulation buffer is available in both 16 and 32bpp modes.

10.2.3. Troubleshooting

10.2.4. Performance

10.2.5. Known Problems

10.3. Intel i810

10.3.1. Dependencies

A Linux kernel with AGP GART support is required. The 2.2.x kernel series does not have AGP GART support. The 2.4.x test kernels have AGP GART and have been tested with the i810.

10.3.2. Configuration

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/2.4.x/kernel/driver/char/drm/. 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.

10.3.3. Troubleshooting

10.4. Matrox G200 and G400

10.4.1. Dependencies

A Linux kernel with AGP GART support (such as the 2.4.x test kernels) is needed.

10.4.2. Configuration

Your XF86Config file's device section must specify the mga device:

        Section "Device"
            Identifier  "MGA"
            VendorName  "Matrox"
            Driver      "mga"
	    VideoRam    32768
        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
            
To use a 32bpp screen mode, use this Screen section instead:
	Section "Screen"
	    Identifier  "Screen 1"
	    Device      "MGA"
	    Monitor     "High Res Monitor"
	    DefaultDepth 24
            DefaultFbBpp 32
	    Subsection "Display"
		Depth       24
		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/2.4.x/kernel/driver/char/drm/. 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.

10.4.3. Performance

Software rendering will be used under any of the following conditions:

10.4.4. IRQ Assignment

There have been problems in the past with the MGA driver being very sluggish when the DRI is enabled (to the point of being unusable.) This is caused by the graphics card not having an interrupt assigned to it. The current DRI trunk will attempt to detect this condition and bail out gracefully.

The solution to the above problem is to assign an interrupt to your graphics card. This is something you must turn on in your system BIOS configuration. Please consult your system BIOS manual for instructions on how to enable an interrupt for your graphics card.

10.4.5. MGA HAL lib

MGAHALlib.a is a binary library Matrox has provided for use under Linux to expose functionality for which they can not provide documentation. (For example TV-Out requires MacroVision be enabled on the output.) This binary library also sets the pixel/memory clocks to the optimal settings for your Matrox card.

Currently the MGAHAL library is required for the G450 to work. You can download this from the driver section on Matrox's website: www.matrox.com/mga

Here modifications to the DRI build instructions which make the mga ddx driver use the MGAHAL library:

	  1.Put the following define in your host.def file
		  #define UseMatroxHal YES
	  2. Place mgaHALlib.a in the following directory
		  xc/programs/Xserver/hw/xfree86/drivers/mga/HALlib/
          

You can use DualHead on the G400/G450 DH cards by creating two device sections which both point to the same BusID. For most AGP devices the BusID will be "PCI:1:0:0". Configure your screen section as you would normally configure XFree86 4.x Multihead. It should be noted that currently the second head does not support direct rendering.

10.4.6. Known Problems

None.

10.5. ATI Rage 128

10.5.1. Dependencies

A Linux kernel with AGP GART support (such as the 2.4.x test kernels) is needed.

10.5.2. Configuration

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/2.4.x/kernel/driver/char/drm/. 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.

10.5.3. Performance

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.

10.5.4. Known Problems

DGA is not yet supported in the ATI Rage 128 X server. This feature will be added in a future release.

10.6. 3DLabs Oxygen GMX 2000

The driver for this hardware was experimental and is no longer being developed or supported.


DRI User Guide : Hardware-Specific Information and Troubleshooting
Previous: General Trouble Shooting
Next: General Limitations and Known Bugs