본 글은 http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html 에서 발췌하였음을 밝힙니다.

 

Gentoo ATI Radeon FAQ

Section 1 - Information about the drivers

Section 2 - Kernel configuration

Section 3 - Installing the drivers

Section 4 - Troubleshooting

Section 5 - Miscellaneous

• fgl_agp
• fglrx_binary_edit

Section 6 - Credits

Section 1 - Information about the drivers

   mkdir -p /etc/portage
   echo "x11-drivers/ati-drivers ~x86" >> /etc/portage/package.keywords

• Radeon 9500 series (including R9550)
• Radeon 9600 / 9700 / 9800 series
• Radeon X-series (X300 / X550 / X600 / X700 / X800 / X850)
• Radeon X1K-series (X1300 / X1600 / X1800 / X1900)
• Radeon Mobility X-series (X300 / X600 / X700 / X800)
• Radeon Mobility X1K-series (X1300 / X1400 / X1600 / X1800)
• Radeon Mobility models 9500 / 9550 / 9600 / 9800
• FireGL models (workstation cards): V7350 / V7300 / V7200 / V7100 / V5200 / V5100 / V5000 / V3400 / V3300 / V3200 / V3100 / X3-256 / X3 / X2-256 / Z1-128 / T2-128 / X1-128 / X1-256p / FireMV 2200 / Mobility FireGL V5000 / Mobility FireGL T2
• Radeon Xpress 200 / Radeon Xpress 1250 IGP

   x11-drivers/ati-drivers ~x86
   x11-drivers/ati-drivers-extra ~x86

Section 2 - Kernel configuration

• Loadable module support -> Enable loadable module support: ENABLED
  
• Loadable module support -> Module unloading: ENABLED
  
• Loadable module support -> Automatic kernel module loading: ENABLED
  The above 3 options will generally be enabled in most kernels anyway, but since it wouldn't be possible to load any modules without them, they are required to use the ATI drivers.
• Bus options (PCI, PCMCIA, EISA, MCA, ISA) -> PCI Express support: ENABLED (only if you have a PCIe card)
  
• File systems -> Pseudo filesystems -> Virtual memory file system support: ENABLED
  
• Processor type and features -> MTRR (Memory Type Range Register) support: ENABLED
  MTRR support should always be enabled - if not, the driver may run very slowly, if it runs at all
  NOTE: on some AMD64 chipsets, you may have to disable MTRR in order to enable AGP support, without which the driver will usually fail to compile. Known chipsets that have this issue so far: NVIDIA nForce3 Go150.
  
• Device drivers -> Character Devices -> /dev/agpgart (AGP Support): ENABLED OR MODULE (if you don't compile this as a module, you'll have to set "UseInternalAGPGART" to "no" in your XF86Config file)
  This option enables AGP support in the kernel, which is usually a good thing to have :)
• Device drivers -> Character Devices -> (pick the correct AGP chipset option from the list, depending on your motherboard): ENABLED OR MODULE
  Examples:
  Motherboard: nVidia nForce2 based ---- NVIDIA nForce/nForce2 chipset support
  Motherboard: VIA KT266/333/400 based ---- VIA chipset support
  NB: the ATI AGP option is NOT normally required in systems with a standard AGP card. See Q2.3.
  NB: compiling this option as a module is only possible in 2.6 kernels.
  
• Device drivers -> Character Devices -> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support): DISABLED
  This option is not required, and will almost certainly prevent the driver from working if enabled.

Section 3 - Installing the drivers

1. The first stage of installing the drivers is configuring your kernel properly. Q2.1 lists the relevant options and what they should be set to.
2. Next, check that the /usr/src/linux symlink is pointing to the directory containing the sources for your current kernel. If you're not sure which kernel version you're running, use the uname -r command to display it. As an example, if you're running kernel 2.6.1, then ls -l /usr/src/linux should show the following:
   lrwxrwxrwx 1 root root 26 Feb 6 14:19 /usr/src/linux -> /usr/src/linux-2.6.1. If the symlink is correct, move on to step 3. If it's not correct, run the command rm -f /usr/src/linux followed by ln -s /usr/src/linux-`uname -r` /usr/src/linux, which will recreate the symlink and point it to the correct kernel source directory.
3. If you had to change any kernel options in step 1, you should now recompile the kernel and reboot. To recompile the kernel run the following commands from the /usr/src/linux directory.
   For 2.4 kernels: make dep && make clean bzImage modules modules_install
   For 2.6 kernels: make && make modules_install
   
   If you have to mount your /boot partition, do so now (mount /boot), then copy your new bzImage over: cp /usr/src/linux/arch/i386/boot/bzImage /boot/<your kernel name>
   Remember to update your bootloaders configuration file if necessary, then reboot.
4. Now you should be ready to install the drivers, which you can do by running emerge ati-drivers. Pay attention to the output displayed by the ebuild - it will NOT abort if the fglrx kernel module fails to compile, and this is easy to miss. If you find that you get a "Module fglrx not found" error when trying to load the fglrx module at a later stage, this is often the cause.
5. When the emerge has completed, you should now configure your /etc/X11/xorg.conf file. If you're just upgrading from a previous driver version, it will usually be OK to continue using your existing configuration file. However, there may be occasions when a new driver introduces new settings that have to be configured in the /etc/X11/xorg.conf file.
   
   Configuring the /etc/X11/xorg.conf file was originally done using the fglrxconfig application (see Q3.3), but ATI now recommend using aticonfig, which was introduced in recent driver versions. aticonfig is designed to update your existing configuration rather than replace it with a new one, which is a bit more convenient. A basic configuration can be produced simply by running the command aticonfig --initial --input=/etc/X11/xorg.conf. Run the application without arguments for a listing of the various parameters and some examples. You can run aticonfig again in future to enable/disable any of the other various settings the driver supports.
   
   If you find that you get a "command not found" error when trying to run aticonfig, you may have to run env-update && source /etc/profile before it will work. This happens because aticonfig is installed into /opt/ati/bin, and this location won't normally be part of your $PATH environment variable ($PATH contains the directories where the shell looks for executables)
   
   
6. Run opengl-update ati to switch to the ATI OpenGL libraries. opengl-update is being deprecated in favour of eselect. You should already be able to use the replacement command eselect opengl set ati if your system is up to date.
7. If you're using the kernel AGP support (see step 4), and have it compiled as modules, load them now. For 2.4 kernels, you just need to load the agpgart module. For 2.6 kernels, you need to load agpgart and a second module, the name of which is dependent on your motherboard. nForce users should load nvidia_agp, VIA users via_agp, Intel users intel_agp, and so on. You should add the modules that you require to /etc/modules.autoload.d/kernel-2.4 or /etc/modules.autoload.d/kernel-2.6 to ensure they are loaded on every boot. You should also add the fglrx module to the list, after the kernel AGP modules.
8. Before starting X, ensure that you have all the necessary modules loaded and that your xorg.conf file is configured to your liking.
9. Once X is started, you can check if Direct Rendering (ie 3D acceleration) is working by running glxinfo | grep direct. This should display direct rendering: Yes if everything is working.
10. Finally, remember that you need to emerge the ati-drivers ebuild each time you change your kernel version. Remember to update the symlink as described above before doing so.

Section 4 - Troubleshooting

• You have no AGP support compiled into your kernel - see Q2.1
• You have AGP support compiled as modules but don't have the modules loaded. In a 2.4 kernel, you just need to load the "agpgart" module. However, in a 2.6 kernel, there are TWO modules which have to be loaded. The first is "agpgart", and the second depends on the AGP chipset option you selected in the kernel config (which depends on the type of motherboard you have). If you picked the nVidia option, load the module "nvidia_agp". If you picked the VIA option, load "via_agp". If you picked the SiS option, load "sis_agp" and so on.
• You have AGP support for the wrong chipset in the kernel - see Q2.1
• Some AMD motherboards can cause trouble setting up the AGP aperture when booting Linux, due to problems with the way the BIOS operates. In some cases, changing your BIOS version can fix this problem. There are also some kernel patches available to try and fix the problem, see this kernel bugzilla entry, and this Gentoo forums posting for more information and links to the patches.
• Try cleaning up your kernel source directory. You can do this in two main ways. First, by unmerging and remerging the kernel (assuming your current kernel is pointed to by /usr/src/linux):

     emerge -C development-sources OR vanilla-sources OR mm-sources etc
     cp /usr/src/linux/.config ~/config (make a copy of your kernel config)
     rm -fr /usr/src/linux-x.y.z (where x.y.z is the kernel version you just unmerged)
     emerge development-sources OR vanilla-sources OR mm-sources etc
     cp ~/config /usr/src/linux/.config
     cd /usr/src/linux
     make oldconfig

  or by the following method:

     cd /usr/src/linux
     cp .config ~/config (make a copy of your kernel config)
     make mrproper
     cp ~/config .config
     make oldconfig

  After you have done this, rebuild the kernel, then remerge the ati-drivers package and try again.

   opengl-update xfree / opengl-update xorg-x11
   emerge ati-drivers
   opengl-update ati

   cd /usr/src/linux
   patch -p1 < /path/to/nvidia-agp.diff

   SubSection  "extmod"
      Option    "omit xfree86-dga" 
   EndSubSection

   (II) fglrx(0): [drm] loaded kernel module for "fglrx" driver
   (II) fglrx(0): [drm] DRM interface version 1.0
   (II) fglrx(0): [drm] drmSetBusid failed (4, PCI:1:0:0), Inappropriate ioctl for device
   (EE) fglrx(0): DRIScreenInit failed!
   (WW) fglrx(0): ***********************************************
   (WW) fglrx(0): * DRI initialization failed! *
   (WW) fglrx(0): * (maybe driver kernel module missing or bad) *
   (WW) fglrx(0): * 2D acceleraton available (MMIO) *
   (WW) fglrx(0): * no 3D acceleration available *
   (WW) fglrx(0): ********************************************* *

   (II) fglrx(0): Composite extension enabled, disabling direct rendering

   Option "KernelModuleParm"  "agplock=0"

   Section "Device"
      Identifier "ATI Graphics Adapter"
      Driver "fglrx"
      Option "MonitorLayout" "NONE, AUTO"
      # === TV-out Management ===
      Option "NoTV" "no"
      Option "TVStandard" "NTSC-M"
      Option "TVHSizeAdj" "0"
      Option "TVVSizeAdj" "0"
      Option "TVHPosAdj" "0"
      Option "TVVPosAdj" "0"
      Option "TVHStartAdj" "0"
      Option "TVColorAdj" "0"
      Option "GammaCorrectionI" "0x00000000"
      Option "GammaCorrectionII" "0x00000000"
      ...
   EndSection

   Section "Screen"
      Identifier "Screen0"
      Device "ATI Graphics Adapter"
      Monitor "Monitor0"
      DefaultDepth 24

      Subsection "Display"
         Depth 24
         Modes "1024x768" "800x600"
         ViewPort 0 0 # initial origin if mode is smaller than desktop
      EndSubsection
   EndSection

• Some systems may require you to change the "MonitorLayout" setting from the default of "AUTO, AUTO" (which tries to autodetect your monitor config). If you have a laptop with a Mobility card and are seeing black screens, try changing "AUTO, AUTO" to "LVDS, AUTO". This problem particularly seems to be affecting laptops with X-series Mobilty chipsets (X300, X600 etc).
• If you have a large amount of RAM (more than 768MB), try limiting the amount used by Linux as described in this bug report.
• It may also be worth trying different values for the "MonitorLayout" setting for various other monitor layouts. The possible values for the two settings (the first is the primary monitor, the second is the secondary) appear to be:
  • NONE
  • TVDAC/ExtDAC
  • AUTO
  • TMDS
  • LVDS
• Try setting the NoDRI option in your /etc/X11/xorg.conf file to "on", starting X, exiting, setting NoDRI back to "off" (the default), then starting X again. If this succeeds, X will only keep working until you reboot. There is a bug report on this issue here.
• One user has reported that setting BlockSignalsOnLock to "off" can also help. However, according to a readme file from an old (very old) version of the drivers: Option "BlockSignalsOnLock" should always be set to "on" unless you are debugging a multithreaded OpenGL app. Turning it off can lead to memory leaks. I don't know if this is still the case for the newer drivers, but it's something to keep in mind if you need to change this setting to get things working.

Section 5 - Miscellaneous

• fgl_agp.tar.bz2: a (very) simplified version of ATI's fireglcontrol application. It's a console app (no QT libs required) that just tries to display the AGP mode the driver is running in. After unpacking the tarball, run make, then ./fgl_agp (X must be running for it to work). So far it's only been tested on x86 systems with AGP cards and on an AMD64 PCI-E system.
  
  
• fglrx_binary_edit.tar.bz2: if you find that the current versions of the ATI driver don't support your card (usually signalled by a "No device found" message when attempting to load the fglrx module), it's often possible to edit the binary part of the driver and insert the necessary PCI ID to let it recognise your card. See the links in Q4.41 for more details.
  fglrx_binary_edit is a little program that should do the work of editing the binary for you. I've now included a README in the tarball, so check that for instructions and more information.