With hardware 3D acceleration, three-dimensional rendering uses the graphics processor on your video card instead of taking up valuable CPU resources drawing 3D images. It's also referred to as "hardware acceleration" instead of "software acceleration" because without this 3D acceleration your CPU is forced to draw everything itself using the Mesa software rendering libraries, which takes up quite a bit of processing power. While Xorg typically supports 2D hardware acceleration, it often lacks hardware 3D acceleration. Three-dimensional hardware acceleration is valuable in situations requiring rendering of 3D objects such as games, 3D CAD and modeling.

In many cases, both binary and open-source drivers exist. Open source drivers are preferable since we're using Linux and open source is one of its underlying principles. Sometimes, binary drivers are the only option, especially if your graphics card is so new that open source drivers have not yet been written to support its features. Binary drivers include x11-drivers/nvidia-drivers for nVidia cards and x11-drivers/ati-drivers for AMD/ATI cards.

The Direct Rendering Infrastructure, also known as the DRI, is a framework for allowing direct access to graphics hardware in a safe and efficient manner. It includes changes to the X server, to several client libraries and to the kernel. The first major use for the DRI is to create fast OpenGL implementations.

The DRM (Direct Rendering Manager) is an enhancement to Xorg that adds 3D acceleration for cards by adding the kernel module necessary for direct rendering.

This guide is for people who can't get direct rendering working with just Xorg. The DRM works for the following drivers:

• 3dfx
• intel
• matrox
• nouveau
• rage128
• radeon
• mach64
• sis300
• via

See the DRI homepage for more info and documentation.

Please read our Xorg Configuration Guide to get Xorg up and running.

Probe for your chipset and enable just that one.

# emerge pciutils; lspci | grep AGP
# 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
(Your output may not match the above due to different hardware.)

If your chipset is not supported by the kernel you might have some succes by passing agp=try_unsupported as a kernel parameter. This will use Intel's generic routines for AGP support. To add this parameter, edit your bootloader configuration file!

Most, if not all, kernels should have these options. This was configured using a standard gentoo-sources kernel.

# ls -l /usr/src/linux 
lrwxrwxrwx 1 root root 22 2007-02-14 20:12 /usr/src/linux -> linux-2.6.18-gentoo-r4
(Make sure /usr/src/linux links to your current kernel.)
# cd /usr/src/linux
# make menuconfig

Processor type and features --->
<*> MTRR (Memory Type Range Register) support
Device drivers --->
   Graphics support --->
   <M> /dev/agpgart (AGP Support) --->
      (The agpgart option is not present on 64-bit kernels; just choose your chipset support.)
      <M> Intel 440LX/BX/GX, I8xx and E7x05 support
      (Enable your chipset instead of the above.)
   <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
      <M> (Select your graphics card from the list)

# make && make modules_install

Don't forget to set up grub.conf or lilo.conf and run /sbin/lilo if you use LILO.

Next, add your user(s) to the video group, as explained in the handbook:

# gpasswd -a username video

Hopefully just adding your user to the video group is sufficient to enable direct rendering. However, you may also need to create a file in /etc/X11/xorg.conf.d/. You can name it anything you like; just make sure it ends in .conf. Open up your favorite text editor and create a file with this inside it:

Section "Device"
  Driver "radeon"
  (Replace radeon with the name of your driver.)
EndSection
Section "dri"
  Mode 0666
EndSection

You will need to add the module name that your card uses to /etc/modules.autoload.d/kernel-2.6 to ensure that the module is loaded automatically when the system starts up.

(Change module name as required.)
intel-agp

Reboot your computer to your new kernel and login as a normal user. It's time to see if you have direct rendering and how good it is. glxinfo and glxgears are part of the mesa-progs package, so make sure it is installed before you attempt to run these commands.

$ startx
(No need to load modules for your driver or agpgart, even if you compiled them as a module.)
(They will be loaded automatically.)
$ glxinfo | grep rendering
direct rendering: Yes
(If it says "No", you don't have 3D acceleration.)
$ glxgears
(Test your frames per second (FPS) at the default size. The number should be
significantly higher than before configuring DRM. Do this while the CPU is as idle as
possible.)

If you want to set more features, for performance or other reasons, check out the feature matrix on the DRI web site or the features listing on Sourceforge.

Try modprobe radeon before you start the X server (replace radeon with the name of your driver). Also, try building agpgart into the kernel instead of as a module.

That's because you compiled agpgart into the kernel instead of as a module. Ignore it unless you're having problems.

The drivers originally developed by the GATOS project have been merged into Xorg's codebase. You don't need anything special for TV-Out; x11-drivers/xf86-video-ati will work just fine.

Try out the binary drivers. For AMD cards, use ati-drivers; a listing is at http://support.amd.com/us/gpudownload/Pages/index.aspx. If those don't support it, use fbdev. It's slow, but it works.

Edit /etc/X11/xorg.conf. In section "Device" enable ForcePCIMode.

Option "ForcePCIMode" "True"

1. http://forums.gentoo.org/viewtopic.php?t=46681
2. http://forums.gentoo.org/viewtopic.php?t=29264
3. http://dri.freedesktop.org/
4. http://www.retinalburn.net/linux/dri_status.html

With suggestions, questions, etc., e-mail .