Manpages

NAME

fglrx − proprietary ATI RADEON and FireGL display driver

SYNOPSIS

Section "Device"
Identifier
"devname"
Driver "fglrx"
...
EndSection

DESCRIPTION

fglrx is a X.org(7x) driver for ATI (Mobility(TM)) RADEON® and (Mobility(TM)) FireGL(TM) based video cards. The driver provides hardware acceleration for 3D graphics and video playback. It includes support for dual displays, TV Output and as of version 8.21.7 also OpenGL 2.0 (GLSL).

SUPPORTED HARDWARE

The driver supports the following chipsets and graphics cards:

R200

RADEON 8500 (AIW) / 9100

R200W

FireGL 8700 / 8800

RV250

RADEON 9000 (LE / PRO)

D9

RADEON 9000

M9

Mobility RADEON 9000, Mobility FireGL 9000

RV280

RADEON 9200 (SE) / 9250

M9+

Mobility RADEON 9200

R300

RADEON 9500 (PRO) / 9600 TX / 9700 (PRO)

R300W

FireGL X1 / Z1

RS300

RADEON 9100 IGP (2D only)

RS300M

Mobility RADEON 9000 / 9100 IGP (2D only)

R350

RADEON 9500 / 9800 (PRO / SE)

R350W

FireGL X2−256 / X2−256t

RS350

RADEON 9000 PRO / 9100 PRO IGP

RV350

RADEON 9550 / 9600 (SE)

RV350W

FireGL T2

R351

RADEON 9600

R360

RADEON 9800 XT

RV360

RADEON 9600 PRO

M10/M11

Mobility RADEON 9500 / 9600 / 9700, Mobility FireGL T2 / T2e

M12

Mobility RADEON 9550

M18

Mobility RADEON 9800

RV370

RADEON X300 / X550

RV370W

FireGL V3100

M22

Mobility RADEON X300, Mobility FireGL V3100

RV380

RADEON X600

RV380W

FireGL V3200

M24

Mobility RADEON X600, Mobility FireGL V3200

RS400, RS480, RS482, RC410

RADEON XPRESS 200/200M

RV410

RADEON X700 (PRO / SE / XT)

RV410W

FireGL V3300 / V5000

M26

Mobility RADEON X700 (XL), Mobility FireGL V5000

R420

RADEON X800 (PRO / SE / XT / XT PE)

R420W

FireGL X3−256

M28

Mobility RADEON X800 XT, Mobility FireGL V5100

R423

RADEON X800 (GT / PRO / SE / XT / XT PE)

R423W

FireGL V5100 / V7100

R430

RADEON X800 (GT / GTO / XL)

R480

RADEON X800 GTO, RADEON X850 (PRO / XT / XT PE)

R481

RADEON X850 (PRO / SE / XT / XT PE)

RV515

RADEON X1300 (LE / PRO / SE / VE / XT)

M52

Mobility RADEON X1300

M54

Mobility RADEON X1400

R520

RADEON X1800 (PRO / SE / XT)

M58

Mobility RADEON X1800

RV530

RADEON X1600 (PRO / XT)

M56

Mobility RADEON X1600

R580

RADEON X1900

CONFIGURATION DETAILS

Please refer to xorg.conf(5x) for general configuration details. This section only covers configuration details specific to this driver. The driver auto−detects a lot of device information necessary to initialize the card. However, if you have problems with auto−detection, you can specify:

See xorg.conf(5x) for more information about these options. With the ChipID option, you can force the driver to recognize your model as a different one by overriding the Chip−ID. This could be useful, if your card is not supported by default. Look up the PCI ID of your card with lspci −n (see lspci(8)) and then search for the ID of a similar but supported model in the file pci.ids (update−pciids(8)), which is also available online at http://pciids.sourceforge.net/pci.ids.

In addition, the following driver options are supported:

Option "AGPMask" "integer"

This option applies to AGPv1/2. To handle an AGPv3 interface, you will additionally need Option "AGPv3Mask".

To combine several settings, only add the values. Let me show an example: "0x00000216" means: force AGP 1x (disable AGP 2x and 4x), disable fast−writes and sidebanding.

You can check, if fast−writes has been disabled by searching your kernel log for ’AgpCommand = hex−integer’. The second last hex digit should be 0 (zero) if fast−writes is off, or 1 (one) if it is on.

Option "AGPv3Mask" "integer"

This option only applies to AGPv3.

Important: It is used in addition to Option "AGPMask". That means, that you turn off fast−writes or sidebanding with Option "AGPMask".

Option "BlockSignalsOnLock" "boolean"

To allow the debugging (using gdb(1), totalview(1) and others) of multi−threaded OpenGL applications it can become necessary to disable the blocking of task interruption signals. The default is: "on".

"off"

The driver will not use signal blocking. This introduces the risk of suffering memory leaks in combination with specific user activity.

Caution: Only use it, if you really know what you are doing.

"on"

The default value. The driver does not block signals for locking.

As of now it is uncertain which is the real origin of the problem. As of now it does look like the debugger application is getting in some trouble because of not getting back the debugging control after the lock condition was removed by the driver. This might be further investigated.

Option "BufferTiling" "boolean"

Option "Capabilities" "integer"

Option "CenterMode" "boolean"

The Center−Mode allows "real" screen display in non−"panel native modes" (e.g. a resolution of 1280x1024 on a 1600x1200 LCD): one pixel of the frame buffer is one pixel on the screen. The display is centered on the screen and the surrounding screen area remains black. Note that some panels may not work in Center−Mode, so the screen remains black then. The default is: "off".

Option "DesktopSetup" "integer"
Option "DesktopSetup" "
string"

This option defines the desktop setup. The driver can work with the following modes:

The modes are:

Single head mode:

Single monitor operation only. If a second monitor is connected, it remains dark. Only in this mode a full overlay functionality is available.

Clone mode:

The contents of the primary monitor are duplicated on the second monitor. If one monitor cannot display the selected resolution, a lower resolution is automatically selected for this monitor. The original resolution is used then as it was specified as the virtual resolution. This means the second screen will do panning when the mouse moves ahead.

Mirror mode:

The contents of the primary monitor are duplicated on the second monitor. Both monitors have an identical refresh rate and resolution.

Important: This mode is not supported on RADEON X1x00 products.

Big Desktop mode(s):

There is a single big frame buffer that gets split either horizontally or vertically and each half is sent to a single monitor. Both monitors have to operate with the same video mode settings and only one windows manager can be used. The orientation is set with:

Dual head mode:

A dual head setup uses separate frame buffers, independent displays and video modes for each monitor. Two window managers can be used.

Note: A connected digital display is always the primary display. If two display devices are connected, the primary head is: the bottom DVI port on FireGL X1, LCD output on Mobility RADEON M9 and the only DVI port on other cards. The secondary head is: the top DVI port on FireGL X1 and the VGA port on all other cards.

Option "EnableDepthMoves" "boolean"

Option "EnableHPV" "boolean"

Option "EnablePageFlip" "boolean"

Enable page flipping for 3D acceleration. This will increase performance but not work correctly in some rare cases. The default is "off".

Option "EnablePrivateBackZ" "boolean"

Option "ForceGenericCPU" "boolean"

Option "ForceMonitors" "string[,string,...]"

crt1, crt2, lvds, tv, tmds1, tmds2, tmds2i, nocrt1, nocrt2, nolvds, notv, notmds1, notmds2, notmds2i.

Option "FSAAEnable" "boolean"

Option "FSAADisableGamma" "boolean"

By default the Full scene Anti Aliasing (FSAA) gamma is set to 2.2, which is typical for CRT displays. Use this option to disable FSAA gamma. The default is: "no".

Option "FSAACustomizeMSPos" "boolean"

Use this option, if you want to customize the sample points, set with Option "FSAAScale". The default is: "no".

Option "FSAAMSPosX0" "real"
Option "FSAAMSPosY0" "
real"
Option "FSAAMSPosX1" "
real"
Option "FSAAMSPosY1" "
real"
Option "FSAAMSPosX2" "
real"
Option "FSAAMSPosY2" "
real"
Option "FSAAMSPosX3" "
real"
Option "FSAAMSPosY3" "
real"
Option "FSAAMSPosX4" "
real"
Option "FSAAMSPosY4" "
real"
Option "FSAAMSPosX5" "
real"
Option "FSAAMSPosY5" "
real"

Use this to customize the 1st, 2nd, ... 6th sample point. Depending on your setting for Option "FSAAScale", you have to set 2, 4 or all 6 points. The pixel size is 1x1, so the range for these values is "0..1".

Note: These options are only relevant, if Option "FSAACustomizeMSPos" is enabled.

Option "FSAAScale" "integer"

Set, enable or disable Full Scene Anti Aliasing (FSAA) for cards using a multi−sampling technique to implement anti−aliasing. Possible values are:

Option "GammaCorrectionI" "integer"
Option "GammaCorrectionII" "
integer"

Adjust the gamma correction factor. This setting can be made individual for each monitor. Normally the first is for the VGA device and the second is for the DVI device.

Option "HSync2" "frequency"

Horizontal sync range of the second monitor in e.g. big desktop mode.

Note: You can skip this value, if you define an appropriate HorizSync line in the related Section "Monitor".

Option "IgnoreEDID" "boolean"

Do not use EDID data for mode validation, but DDC is still used for monitor detection. This is different from Option "NoDDC". The default is: "off".

If the server is ignoring your modlines, set this option to "on" and try again.

Option "KernelModuleParm" "string"

If you change this option during runtime, you have to remove and reload the fglrx kernel module with rmmod fglrx && modprobe fglrx (see modprobe(8), rmmod(8)). Possible values you can provide with this option are (separate them by semicolon):

Note: If neither the built−in nor the kernel AGPGart support work, you can use [1] as a fallback.

Option "Mode2" "resolution1" "resolution2" "..."

Option "mtrr" "boolean"

Enable or disable DRI Memory Type Range Registers (MTRR) mapper. Be aware, that the driver has its own code for MTRR. The default is: "off".

Option "no_accel" "boolean"

Enables or disables all hardware acceleration (XAA). The default is: "off".

Option "no_dri" "boolean"

Enables or disables DRI extension. The default is: "off".

Option "NoDDC" "boolean"

Disable probing of DDC−information from your monitor. The default is: "off".

Option "NoTV" "boolean"

Enable or disable TV−Out for a monitor.

Option "OpenGLOverlay" "boolean"

If you enable this option, Option "VideoOverlay" will be disabled automatically.

Option "PBuffer" "integer"

Option "PowerState" "integer"

Option "PseudoColorVisuals" "boolean"

Enabling this options allows the usage of pseudo color visuals at the same time with true color visuals using the overlay technique. The default is: "off".

Option "RingSize" "integer"

Option "ScreenOverlap" "integer"

This option is intended to allow image overlapping with e.g. two video projectors. It only applies to big desktops (see Option "DesktopSetup").

Option "Stereo" "boolean"

To enable Stereo mode of Quad Buffer Stereo ("Active Stereo") capable cards, set this value to "on" and disable Option "VideoOverlay" and Option "OpenGLOverlay". The default is: "off".

If you enable Stereo Quad Buffering then you should not use virtual desktops bigger than the selected resolution. Further the stereo feature will only initialize if your adapter is in text−mode when launching X and the respective display mode. The adapter can not switch between multiple resolutions while keeping the stereo setup. For that reason it is highly recommended that you have only one single modes in your config file at Section "Screen" −> SubSection "Display".

Option "StereoSyncEnable" "integer"

Option "SWCursor" "boolean"

Disable or enable the use of a software cursor. The default is: "off".

Option "TMDSCoherentMode" "boolean"

Internal TMDS transmitter can be programmed in 2 different ways to get best signal qualities depending on connected transmitter chips in the panel. The noise must appear in 1600x1200 mode, but can also come up in 1280x1024x75Hz. You can enable or disable the coherent mode using this option. The default is: "on".

Option "TVFormat" "string"

Choose the TV format. Available values are: NTSC−JPN, NTSC−M, NTSC−N, PAL−B, PAL−CN, PAL−D, PAL−G, PAL−H, PAL−I, PAL−K, PAL−K1, PAL−L, PAL−N, PAL−M, PAL−SCART

Option "TVStandard" "string"

Choose the TV standard. Available values are: VIDEO, SCART, YUF

Option "TVColorAdj" "integer"

Option "TVHPosAdj" "integer"

Option "TVVPosAdj" "integer"

Option "TVHSizeAdj" "integer"

Option "TVVSizeAdj" "integer"

Option "TVHStartAdj" "integer"

Option "UseFastTLS" "integer"

Use this option to set the method to maintain the so called Thread Local Storage (TLS) locations. The default is: "0".

"0"

Fast operations. Provides the highest possible OpenGL performance. The method makes use of a quite limited resource. This is the default.

"1"

Fast operations.

"2"

Compatible mode. Fast operations are turned off. This method is some 10% slower and uses a less limited resource. Preferred for Wine(X), emulators and other VM manipulating programs.

If you do spot an immediate segmentation fault after launching a program that makes use of OpenGL and further when the fault can be traced down to the OpenGL implementation of the graphics driver, then you should try to tune the TLS settings.

Option "UseInternalAGPGART" "boolean"

Enable or disable the usage of an internal agpgart module. If you set this option to "yes", the driver will not use the kernel’s AGPGart module. Instead it will make use of the "built−in" AGP support. The default is "no", as long as the graphics driver’s kernel module detects the presence of an agpgart kernel module.

Warning: If you set this option to "yes" you must ensure, that you don’t have the kernel AGP support compiled in. Instead compile it as modules.

The AGP support in the driver may not always work, depending on the type of motherboard and/or card that you have. But there is a possibility, which maybe still works. Refer to the "agp_try_unsupported=1" value for Option "KernelModuleParm".

Option "VideoOverlay" "boolean"

Option "OpenGLOverlay" must not be enabled.

Option "VRefresh2" "frequency"

Vertical refresh rate range for the second monitor in e.g. big desktop mode.

Note: You can skip this value, if you define an appropriate VertRefresh line in the related Section "Monitor".

DIAGNOSTICS

The following diagnostics may be issued in Xorg.0.log:

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

At the moment, the driver will automatically disable direct rendering if you enable the Composite extension. To get 3D acceleration back, simply comment or remove the line in your xorg.conf(5x) that loads the Composite extension..

(WW) fglrx: No matching Device section for instance (BusID PCI:x:x:x) found

You may see this message if you aren’t using the secondary monitor connector on your card. X is just saying that you haven’t given any configuration details for it, but this doesn’t matter if you only have a single monitor in use. Note that the number represented by the "x" will vary depending on your system.

(WW) fglrx(0): board is an unknown third party board, chipset is supported

Don’t care. The driver detected, that you have a "Power−by−ATI" and not a "Built−by−ATI" board.

(WW) fglrx(0): Direct rendering is not supported when Xinerama is enabled

(WW) fglrx(0): Only single display is connected, DesktopOption will be ignored

(WW) fglrx(0): Option "..." is not used

Don’t care. Some options became obsolete over time. Others are maybe not supported by your hardware.

(WW) fglrx(0): Specified desktop setup not supported: 8

(WW) fglrx(0): * DRI initialization failed!

(EE) fglrx(0): Failed to initialize UMM driver.

(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP

This error can have many causes, but the most common is, that AGP support was not compiled into the kernel or it was compiled as module bot not loaded. On 2.6 kernels make sure you’ve loaded the generic and the specific AGPGart module (see modprobe(8)). For example: If you have a VIA motherboard, load the "agpgart" and "via−agp" modules. If you have a nForce board, you would load "agpgart" and "nvidia−agp" ... and so on for the other chipset types.

(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM"
(EE) fglrx(0): cannot init AGP

This error is generally more difficult to diagnose and fix. A few things you could try:

If you are using the kernel AGP support (Option "UseInternalAGPGART" is set to "no"), ensure that you have the necessary modules loaded (see also the error message above). If you are not using the kernel AGP support (Option "UseInternalAGPGART" is set to "yes"), ensure that you don’t have your kernel AGP settings compiled in.

Set Option "UseFastTLS" to "2" in your xorg.conf(5x).

Try Option "KernelModuleParm" with "agplock=0" in your xorg.conf(5x).

Increase your AGP aperture size in the BIOS (particularly for nForce2 boards).

Users of nForce2 boards can also try disabling the AGP 8x support in the BIOS.

If that all didn’t work, check the output of dmesg(8). Verify, that your kernel configuration is correct and if so, try a newer kernel.

(EE) fglrx(0): incompatible kernel module detected [..]

The version of the fglrx kernel module you have loaded does not match the version of the driver you have installed. This can happen if you change the driver version without unloading and reloading the fglrx module (or rebooting). To fix this error, you can simply reboot or unload the old module and load the new one: rmmod fglrx && modprobe fglrx (see modprobe(8), rmmod(8)).

BUGS

Report any issues with the fglrx driver to http://support.ati.com. There is also an unofficial BTS at http://ati.cchtml.com, which is also known by the ATI driver team.

SEE ALSO

aticonfig(1x), xorgconfig(1x), Xorg(1x), Xserver(1x), xorg.conf(5x), X(7x)

AUTHORS

Daniel Leidert <daniel.leidert [AT] wgdd.de>

Author.

Flavio Stanchina <flavio [AT] stanchina.net>

Author and Debian package maintainer.

Mathieu Malaterre <mathieu [AT] malaterre.com>

Author.

Matthijs Kooijman <m.kooijman [AT] student.nl>

Debian Bug report #360819.

Gentoo ATI Radeon FAQ

Many things in DIAGNOSTICS. Information about several options.