Provided by: xserver-xorg-video-radeonhd_1.2.4-2_i386
radeonhd - AMD GPG (ATI) R5xx/R6xx video driver
radeonhd is an Xorg driver for AMD GPG (ATI) R5xx/R6xx/R7xx based video
At the time of this writing, radeonhd has the following limitations:
· On R6xx and R7xx based cards: NO support for hardware-based 2D & 3D
acceleration, no support for Xvideo.
· No TV and Component connector support so far.
· After using the fglrx driver, radeonhd might fail to work properly.
This combination is not and probably will never be supported. A
reboot fixes problems in most cases, sometimes a powercycle is
necessary. Unloading the kernel module is typically not enough.
A more up-to-date list can be found on the wiki page.
The radeonhd driver supports video cards based on the following ATI
RV505 Radeon X1550, X1550 64bit
RV515 Radeon X1300, X1550, X1600; FireGL V3300, V3350
RV516 Radeon X1300, X1550, X1550 64-bit, X1600; FireMV 2250
R520 Radeon X1800; FireGL V5300, V7200, V7300, V7350
RV530 Radeon X1300 XT, X1600, X1600 Pro, X1650; FireGL V3400, V5200
RV535 Radeon X1300, X1650
RV550 Radeon X2300 HD
RV560 Radeon X1650
RV570 Radeon X1950, X1950 GT; FireGL V7400
R580 Radeon X1900, X1950; AMD Stream Processor
R600 Radeon HD 2900 GT/Pro/XT; FireGL V7600/V8600/V8650
RV610 Radeon HD 2350, HD 2400 Pro/XT, HD 2400 Pro AGP; FireGL V4000
RV620 Radeon HD 3450, HD 3470
RV630 Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630;
RV635 Radeon HD 3650, HD 3670
RV670 Radeon HD 3690, 3850, HD 3870, FireGL V7700, FireStream 9170
R680 Radeon HD 3870 X2
M52 Mobility Radeon X1300
M54 Mobility Radeon X1400; M54-GL
M56 Mobility Radeon X1600; Mobility FireGL V5200
M58 Mobility Radeon X1800, X1800 XT; Mobility FireGL V7100, V7200
M62 Mobility Radeon X1350
M64 Mobility Radeon X1450, X2300
M66 Mobility Radeon X1700, X1700 XT; FireGL V5250
M68 Mobility Radeon X1900
M71 Mobility Radeon HD 2300
M72 Mobility Radeon HD 2400; Radeon E2400
M74 Mobility Radeon HD 2400 XT
M76 Mobility Radeon HD 2600; (Gemini ATI) Mobility Radeon HD 2600
M82 Mobility Radeon HD 3400
M86 Mobility Radeon HD 3650, HD 3670, Mobility FireGL V5700
M88 Mobility Radeon HD 3850, HD 3850 X2, HD 3870, HD3870 X2
RS600 Radeon Xpress 1200, Xpress 1250
RS690 Radeon X1200, X1250, X1270
RS740 RS740, RS740M
RS780 Radeon HD 3100/3200/3300 Series
RV770 Radeon HD 4800 Series; Everest, K2, Denali ATI FirePro
R700 Radeon R700
M98 Radeon M98 Mobility
RV730 Radeon HD4670, HD4650
M96 Radeon M96 Mobility
RV710 Radeon HD4570, HD4350
Please refer to xorg.conf(5) for general configuration details.
This section only covers configuration options specific to this driver,
for Section "Device". Some options may be deprecated and considered to
be removed or replaced by better implementations soon.
Option "AccelMethod" "none|default|shadowfb|xaa|exa"
Use the indicated accleration method.
none does not accelerate anything at all. Discouraged.
shadowfb is a software-only acceleration technique. Does not
work together with DRI at the moment.
xaa is the older but stable hardware-based acceleration
exa is the newer but more experimental hardware-based
The default is depending on the chipset, driver version, and
state of acceleration techniques and tries to give the best user
Rotation isn’t supported for the AccelMethods "none" and
Use this option to enable 3D and Xv acceleration using DRI (R5xx
and RS6xx chips only for the moment). Currently, the default is
Option "OffscreenSize" "<integer>M|<integer>%"
Specify the amount of framebuffer memory used for offscreen
pixmaps, in megabytes or percent of available memory. This
amount of memory is not available for DRI. Certain hardware and
software limits apply. The default is 10%.
Option "ScaleType" "none|center|scale|scale_keep_aspect_ratio|default"
Sets the scaling mode for laptop flat panels when used together
with an external screen. The scaling engine is capable of
scaling both up and down.i
none means to not scale at all, i.e. the image will be
displayed in the top left corner of the panel if the
resolution of the external display is lower than the
center means not to scale but center the image on the panel
i.e. apply a black frame around the image on the panel
in case the panel resolution is lower than the one of
the external display.
scale means to always scale to the resolution of the external
display filling the entire panel.
scales the panel display but keeps the aspect ratio of
the external display, which means if the external
display has a different aspect ratio than the panel it
black borders will be added to the top and bottom or
left and right.
default keeps the aspect ratio, but does not to scale
The default is to keep the aspect ratio.
Disable RandR 1.2 support. This turns the driver back to use
standard modesetting behavior. The default is to enable RandR
Option "SWcursor" "boolean"
Enable or disable the software cursor. The hardware cursor is
inactive when the software cursor is enabled. The default is
Option "ForceReduced" "boolean"
Force the use of reduced blanking modes. Use this if your LCD
monitor does not provide correct EDID data and you need a
reduced blanking mode to drive a high resolution mode over a
single link DVI connection. The default is off.
Option "UnverifiedFeatures" "boolean"
The radeonhd driver sometimes relies on unverified graphics card
features. You can add Option "UnverifiedFeatures" "off" to
disable those when you run into difficulties.
Option "RROutputOrder" "list-of-outputs"
RandR modesetting only.
Several legacy application rely on the Xinerama extension to
determine the primary screen. RandR returns the viewport
displayed on the first attached output of the internal table as
the first Xinerama screen. If your outputs are ordered in the
wrong way, you can reorder them by adding their names (separated
by spaces or commas) to the list-of-outputs. Typically only the
first (primary) output has to be listed, remaining outputs are
added automatically. The default is none.
Option "IgnoreConnector" "string"
Standard (non-RandR) modesetting only.
Connector to be ignored during non-RandR modesetting. The
default is none.
Option "UseConfiguredMonitor" "boolean"
Standard (non-RandR) modesetting only.
Use or ignore the monitor section in xorg.conf. In standard
modesetting radeonhd ignores the EDID data if a monitor section
is configured. This is different to what most drivers behave
like and a common source of configuration problems. Thus the
default is off (i.e. ignore).
Disable all hardware acceleration. The default is to enable
NOTE: Use of this option is considered deprecated. The
AccelMethod option is considered to be more flexible.
Option "HPD" "auto|off|normal|swap"
Change the use of the hot plug detection (HPD) pins. On R5xx the
according connector tables are often broken and have to be
Auto Select method depending on chipset and board
Off Don’t use HPD pins. Some connectors might not be able to
detect connections at all
Normal Use connector table information as-is
Swap Swap HPD pin 1 and 2 in connector table
NOTE: Use of this option is discouraged. Whenever this option is
needed to detect connected monitors correctly, please report to
the mailing list. The default is Auto.
Option "ForceDPI" "integer"
Force the use of the specified pixel density in Dots Per Inch.
The default is to use the monitor supplied values.
NOTE: Use of this option is discouraged. Monitors should return
valid DPI values, and the Xserver should honour them correctly.
Option "UseAtomBIOS" "boolean"
Selects the mode setting path. The default is chipset dependent.
NOTE: Use of this option is discouraged. The driver should
select the right path. If this option is needed to get your card
working correctly, please report to the mailing list.
Option "Audio" "boolean"
This option enables the audio hardware, wich is responsible for
delivering audio data to the different HDMI capable conntectors
and used to communicate with the audio driver of the operation
system. The default is off.
Option "HDMI" "boolean"
Possible values are "DVI-I 0", "DVI-I 1"..,"DVI-D 0","DVI-I
1",.., "all". This option enables HDMI-Audio and HDMI-Info
packets on the specified connector. This is the only way
enabling HDMI at the moment, since decoding E-EDID data to check
if monitor supports HDMI is not implemented (yet).
Option "Coherent" "string"
There are two different ways to program the TMDS encoder in an
output for best signal quality for the transmitter chip used
inside a digital monitor. This option may be used to set the
programming for each output individually. The string is a space
separated list of <output_transmitter>=on|off. Possible values
for <output_transmitter> are: TMDS_A, TMDS_B, UNIPHY_A,
UNIPHY_B, AtomOutputTMDSA, AtomOutputLVTMA,
AtomOutputKldskpLvtma, AtomOutputUniphyA, AtomOutputUniphyB.
The log file should be consulted on which ones to use. The line:
Option "Coherent" "TMDS_A=off TMDS_B=on" will set coherent mode
to off for TMDS A and to on for TMDS B. The default for all
outputs is off.
Option "TVMode" "tv-mode"
The TV standard to use on the TV output.
CV Composite Video
NOTE: This option isn’t implemented yet and has no effect.
RANDR OUTPUT PROPERTIES
The following properties can be queried with xrandr --prop and some of
them can be set with xrandr --output <output> --set <property> <value>
. Those marked with RR13 will be merged into a RandR 1.3 standard,
though substantially changed. Properties marked Read-Only are provided
by the driver for informational purpose only, those marked Static won’t
change during runtime.
RANDR_SIGNAL_FORMAT Read-Only RR13
Range/List: unknown VGA TMDS LVDS FBAS FBAS-PAL FBAS-NTSC
FBAS-SECAM SVideo YPbPr DisplayPort
Signal format / physical protocol format that is used for the
A driver MAY change this property of an output if the underlying
hardware indicates a protocol change (e.g. TV formats). Values
with dashes (FBAS-PAL) describe more specific versions of the
base values (FBAS) and SHOULD be used if known to the driver.
RANDR_CONNECTOR_TYPE Read-Only Static RR13
Range/List: unknown VGA DVI DVI-I DVI-A DVI-D HDMI PANEL TV
TV-FBAS TV-SVideo TV-YPbPr TV-SCART TV-C4
Connector type, as far as known to the driver.
Values with dashes (TV-FBAS) describe more specific versions of
the base values (TV). The former SHOULD be used if the
connector is not capable of producing other signal formats. The
later SHOULD be used if the exact connector is unknown, or the
connector is a multi-format connector that is not described
otherwise. DVI, for instance, SHOULD be handled like a DVI-I
connector, unless additional information is available to the
user agent. PANEL describes laptop-internal (normally LVDS)
displays. TV, TV-SCART, TV-YPbPr, and TV-C4 with signal format
VGA are valid combinations and describe RGB TV signals.
RANDR_CONNECTOR_NUMBER Read-Only Static RR13
Outputs that route their signal to the same connector MUST have
the same connector number. Outputs with the same connector
number MUST route their signal to the same connector, except if
it is 0, which indicates unknown connectivity. 1 is called the
primary connector, 2 the secondary. 3 is often a TV connector,
but that is completely driver / hardware dependent.
Outputs with the same connector number SHOULD have the same
connector type. Meaning and client behavior for mismatching
connector types is undefined at the moment.
RANDR_OUTPUT_NUMBER Read-Only Static RR13
A card may route one internal output to several connectors.
Connectors that are driven by the same output cannot be driven
by different Crtcs and are thus only allowed to be used in clone
mode. The driver SHOULD emit an error message and continue as
gracefully as possible if using different Crtcs for the same
internal output is requested.
Internal outputs are numbered from 1, 0 indicates that output
routing is unknown.
Specifies the panning area in RandR mode per output.
It actually is a Crtc-specific property, but RandR doesn’t
support that yet. As the xrandr application typically always
resets the framebuffer size with every action, --fb
<width>x<height> has to be added on every invocation, unless
there is an additional output configured that is using this size
as its resolution.
This property cannot be changed when in a rotated mode.
NOTE: Use of this option is considered deprecated. The driver
supports RandR 1.3 panning, which is included in Xserver 1.6.
It is considerable more flexible, and should support rotated
As the radeonhd driver is still in development, some non-obvious things
might not work yet. A list of major known bugs is maintained on the
wiki. Other places to check for known bugs and solutions are the
and the mailing list archives at http://lists.opensuse.org/radeonhd/
radeonhd development caused a few bugs in Xorg and a number of bugs in
xrandr(1) to be discovered. If you are using xrandr(1) versions older
than 2007-11-10, you should try updating xrandr(1).
Alternatively, you can try to always specify different CRTCs for all
monitors by explicitly selecting them with --crtc [0|1] on the
xrandr(1) command line.
Xorg(1), xorg.conf(5), xorgconfig(1), Xserver(1), X(7)
1. The official radeonhd wiki
2. The radeonhd mailing list
3. Overview about radeonhd development code
4. Query the bugtracker for radeonhd bugs
Egbert Eich, Luc Verhaegen, Matthias Hopf, Hans Ulrich Niedermann,
Christian Koenig, Alexander Deucher, and others.