EXAVSync 选项试图通过stalling the engine until the display controller has passed the destination region来避免撕裂。在开启了Xv overlay视频选项的3D加速桌面非常有用，使用KMS时则没有必要。

Option "EXAVSync" "yes"

下面是一个简单的配置文件示例： /etc/X11/xorg.conf.d/20-radeon.conf:

Section "Device"
Identifier "My Graphics Card"
Driver "radeon"
Option "SWcursor" "off" #software cursor might be necessary on some rare occasions, hence set off by default
Option "EnablePageFlip" "on" #supported on all R/RV/RS4xx and older hardware, and set on by default
Option "AccelMethod" "EXA" #valid options are XAA, EXA and Glamor. EXA is the default
Option "RenderAccel" "on" #enabled by default on all radeon hardware
Option "ColorTiling" "on" #enabled by default on RV300 and later radeon cards
Option "EXAVSync" "off" #default is off, otherwise on. Only works if EXA activated
Option "EXAPixmaps" "on" #when on icreases 2D performance, but may also cause artifacts on some old cards. Only works if EXA activated
Option "AccelDFS" "on" #default is off, read the radeon manpage for more information
EndSection

Hybrid graphics/AMD Dynamic Switchable Graphics

It is the technology used on recent laptops equiped with two GPUs, one power-efficent (generally Intel integrated card) and one more powerful and more power-hungry (generally Radeon or Nvidia). There are three ways to get it work:

If you do not need to run any GPU-hungry application, you can plainly disable the discrete card: echo OFF > /sys/kernel/debug/vgaswitcheroo/switch. You can do more things with vgaswitcheroo (see Ubuntu wiki for more information) but ultimately at best one card is bound to one graphic session, you cannot use both on one graphic session.

You can use PRIME. It is the proper way to use hybrid graphics on Linux but still requires a bit of manual intervention from the user.

节能

With kernel 3.11

With kernel prior to 3.11

With the radeon driver, power saving is disabled by default but the kernel provides a method to enable it using sysfs.

You can choose between two different methods. It's hard to say which is the best, you have to try it yourself.

Dynamic frequency switching

This method dynamically changes the frequency depending on GPU load, so performance is ramped up when running GPU intensive apps, and ramped down when the GPU is idle. The re-clocking is attempted during vertical blanking periods, but due to the timing of the re-clocking functions, does not always complete in the blanking period, which can lead to flicker in the display. Due to this, dynpm only works when a single head is active.

It can be activated by simply running the following command:

# echo dynpm > /sys/class/drm/card0/device/power_method

Profile-based frequency switching

This method will allow you to select one of the five profiles (described below). Different profiles, for the most part, end up changing the frequency/voltage of the GPU. This method is not as aggressive, but is more stable and flicker free and works with multiple heads active.

To activate the method, run the following command:

# echo profile > /sys/class/drm/card0/device/power_method

Select one of the available profiles:

default uses the default clocks and does not change the power state. This is the default behaviour.

auto selects between mid and high power states based on the whether the system is on battery power or not. The low power state is selected when the monitors are in the DPMS-off state.

low forces the gpu to be in the low power state all the time. Note that low can cause display problems on some laptops, which is why auto only uses low when monitors are off.

mid forces the gpu to be in the mid power state all the time. The low power state is selected when the monitors are in the DPMS-off state.

high forces the gpu to be in the high power state all the time. The low power state is selected when the monitors are in the DPMS-off state.

As an example, we will activate the low profile (replace low with any of the aforementioned profiles as necessary):

It depends on which GPU line yours is, however. Along with the radeon driver versions, kernel versions, etc. So it may not have much/any voltage regulation at all.

Thermal sensors are implemented via external i2c chips or via the internal thermal sensor (rv6xx-evergreen only). To get the temperature on asics that use i2c chips, you need to load the appropriate hwmon driver for the sensor used on your board (lm63, lm64, etc.). The drm will attempt to load the appropriate hwmon driver. On boards that use the internal thermal sensor, the drm will set up the hwmon interface automatically. When the appropriate driver is loaded, the temperatures can be accessed via lm_sensors tools or via sysfs in /sys/class/hwmon.

TV输出（TV out）

This article or section is out of date.

Reason:please use the first argument of the template to provide a brief explanation. (Discuss in Talk:ATI (简体中文)#)

HDMI audio

HDMI audio is supported in the xf86-video-ati video driver. By default HDMI audio is disabled in the driver kernel versions >=3.0 because it can be problematic. However, if your Radeon card is listed in the Radeon Feature Matrix it may work. To enable HDMI audio add radeon.audio=1 to the Kernel parameters. For example, for syslinux:

If the sound is distorted in PulseAudio try setting tsched=0 and make sure rtkit daemon is running.

Dual Head setup

Independent X screens

Independent dual-headed setups can be configured the usual way. However you might want to know that the radeon driver has a "ZaphodHeads" option which allows you to bind a specific device section to an output of your choice, for instance using:

This can be a life-saver, because some cards which have more than two outputs (for instance one HDMI out, one DVI, one VGA), will only select and use HDMI+DVI outputs for the dual-head setup, unless you explicitely specify "ZaphodHeads" "VGA-0".

Moreover, this option allows you to easily select the screen you want to mark as primary.