Provided by: xserver-xorg-video-radeonhd_1.1.0-1_i386
radeonhd - AMD GPG (ATI) R5xx/R6xx video driver
radeonhd is an Xorg driver for AMD GPG (ATI) R5xx/R6xx based video
RADEONHD is still very much work in progress.
At the time of this writing, radeonhd has the following major
· NO support for 2D & 3D acceleration, no support for Xvideo.
· No TV, Component, and HDMI connector support so far.
· Suspend & Resume is pretty much untested. Often it just works, but
your milage may vary.
· After using the fglrx driver, the display can get very jittery with
radeonhd. Also suspend & resume will probably fail. A reboot fixes
this problem 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
RV630 Radeon HD 2600 LE/Pro/XT, HD 2600 Pro/XT AGP; Gemini RV630;
RV670 Radeon HD 3850, HD 3870, FireGL V7700
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
RS600 Radeon Xpress 1200, Xpress 1250
RS690 Radeon X1200, X1250, X1270
Please refer to xorg.conf(5) for general configuration details. This
section only covers configuration options specific to this driver. Some
options may be deprecated and considered to be removed or replaced by
better implementations soon.
Option "SWcursor" "boolean"
Enable or disable the software cursor. The hardware cursor is
inactive when the software cursor is enabled. The default is
Disable all hardware accleration. The default is to enable
Acceleration is not implemented yet, so this option is ignored
for the moment.
Option "ShadowFB" "boolean"
Enable or disable shadow framebuffer support. This greatly
improves the speed of unaccelerated drivers. The default is on
as long as acceleration is not supported.
Disable RandR 1.2 support. This turns the driver back to use
standard modesetting behavior. The default is to enable RandR
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 "HPD" "hpd-mode"
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 "RRUseXF86Edid" "boolean"
RandR modesetting only.
Enable or disable the use of xf86OutputGetEDID() and
xf86OutputGetEDIDModes() instead of the default routines from
radeonhd, which are better adapted to the chipset. Panels will
often fail to work with these calls. The default is off.
NOTE: Use of this option is considered deprecated. Report to the
mailing list if this is needed for your configuration.
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).
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 are probably merged into a RandR 1.3
standard. Properties marked Read-Only are provided by the driver for
informational purpose only, those marked Static won’t change during
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.
As the radeonhd driver is still in an early stage of development, many
non-obvious things do 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 bugtracker at
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
Driver written by Egbert Eich, Luc Verhaegen, Matthias Hopf, and
Man page written by Hans Ulrich Niedermann, Matthias Hopf, and others.