Installation

Catalyst was once a precompiled package offered by Arch in the [extra] repository, but as of March 2009, official support has been dropped because of dissatisfaction with the quality and speed of development of the proprietary driver.

[*]catalyst-total is available only on AUR, as it was designed to be the fastest way of building catalyst drivers for AUR users

If you are using x86_64 architecture and want 32-bit OpenGL support - install lib32-catalyst-utils, just make sure that you did uncomment [multilib] repository in /etc/pacman.conf before installing this package - note: if you are using catalyst-total then you do not need this package.

Please note that there are some additional packages which can be usefull, every one of them can replace catalyst package and provide fglrx modules for multiple kernels installed on your system, these packages are:

- catalyst-generator - able to generate fglrx modules packed into pacman's packages - most secure and KISS-compatible package in this side-note, althought it has to be operated manually;

If you are using x86_64 architecture and want 32-bit OpenGL support - install AUR's lib32-catalyst-utils, just make sure that you have uncommented [multilib] repository in /etc/pacman.conf. Note: if you are using catalyst-total then you do not need this package.

Note: With every Catalyst update you should remove amdpcsdb file in this way: stop your X/DE, remove /etc/ati/amdpcsdb, start your X/DE, and then run amdcccle - otherwise you may experience bad catalyst's versioning in amdcccle.

Warning:

Make sure that you own a R6xx (HD2xxx) or newer card or the driver won't be enabled. You will encounter an error if you try to enable your display using Catalyst and a card older than the R6xx series.

It appears that Catalyst 9.10-10.11 does not support nForce4 motherboard chipsets.

Warning: Whether or not you install catalyst package from AUR, you will have to reinstall/update fglrx every time the kernel is updated. Otherwise, X will fail to start. Please remember that you can alway use catalyst-hook or catalyst-daemon package which will perform automatic fglrx update - read this section for more details

Custom Kernels

Note: catalyst-generator is able to build catalyst-{kernver} packages for you so you do not actually need to perform all those steps manually, although this section should stay because it can be usefull

To install catalyst for a custom kernel, you'll need to build your own catalyst-$kernel package.

If you are at all uncomfortable or inexperienced making packages, read up the ABS wiki page first so things go smoothly.

Three changes need to be made here:
1. Change:pkgname=catalyst to pkgname=catalyst-KERNEL_NAME
where KERNEL_NAME is whatever you want (e.g. custom, mm, themostawesomekernelever)

2. Remove linux from the dependencies list.

3. Build and install the package. (makepkg -i or makepkg followed by pacman -U pkgname.pkg.tar.gz)

Note: If you run multiple kernels, then install catalyst module packages for all kernels. They won't conflict with one another.

Unofficial repositories

There are some unofficial repositories containing the newest (or older) catalyst packages along with the appropriate libs and software in order to use the driver.
If you want to know what packages are inside any given repository you need to first add repository to pacman.conf, perform pacman -Sy command and then list repository with pacman -Sl command:

# pacman -Sl catalyst

[catalyst] repository

It contains newest stable catalyst driver and some additional packages.
This repository should always work with the stock kernel from [core] and it is updated most frequently. The catalyst driver currently requires xorg-server<1.11.0 though.

To use it you need:

1.) Edit /etc/pacman.conf and add those lines above all other repositories (so also above [core] and [extra]):

[catalyst-11.9] repository

The catalyst driver is now up to 11.9, but it is not easily compatible with xorg 1.11. For this reason, the current stable catalyst version is 11.8; however, you can enable 11.9 with the catalyst-11.9 repository:

Simply follow the same steps above after enabling this repository. You will also need to enable the xorg110 repository. See the xorg section below.

Archived repositories

There are some archived repositories placed in http://catalyst.apocalypsus.net/repo, please browse this site and look for files with *.db extension, if you have found interesting catalyst repository tell pacman to use it.
For catalyst-10.9.db pacman.conf entry looks like:

To use it you need edit /etc/pacman.conf and add those lines above all other repositories:

[xorg19]
Server = http://catalyst.apocalypsus.net/repo/xorg19/$arch

[xorg18]

Catalyst < 10.10 isn't working with xorg-server >= 1.9 (checked also with IgnoreAbi flag).
To use it you need edit /etc/pacman.conf and add those lines above all other repositories:

[xorg18]
Server = http://catalyst.apocalypsus.net/repo/xorg18/$arch

[xorg17]

Supported since catalyst 10.4

[xorg17] repository contains xserver 1.7 packages, use it only if you are experiencing problems with newer xservers.

Repository contains xorg-server-backclear (patched with backclear patch) and xorg-server-1.7-catalyst-maximize-fix (patched with fedora patch) packages. Both this patches fix problems with maximizing/resizing but they are doing it in different way - you may choose which patched xserver is best for you. To remove xorg-server and install xorg-server-backclear just type:

# pacman -Rdd xorg-server
# pacman -S xorg-server-backclear

Similar with xorg-server-1.7-catalyst-maximize-fix

To use [xorg17] repo please put those lines at the top of all other repositories in /etc/pacman.conf:

[xorg17]
Server = http://catalyst.apocalypsus.net/repo/xorg17/$arch

[xorg16]

[xorg16] repository contains xserver 1.6 packages, use it only if you are experiencing problems with newer xservers.

[xorg16]
Server = http://catalyst.apocalypsus.net/repo/xorg16/$arch

Official ATI/AMD Installer

Warning: Using the installer from ati.com/amd.com is NOT recommended for inexperienced users! It may cause file conflicts and X failures. You must be familiar with booting to the command-line if you wish to attempt this.

Note: If you have attempted a manual install from the official installer, and cannot recover your desktop:
# /usr/share/ati/fglrx-uninstall.sh

1.) Download the installer from AMD or elsewhere (whereas *-* will be the version): ati-driver-installer-*-*-x86.x86_64.run

2.) Make sure it's executable: # chmod +x ati-driver*

3.) Ensure you're using a basic video driver like vesa, and remove conflicting drivers (i.e. xf86-video-ati, radeon) with pacman and from /etc/rc.conf

5.) As root: # ./ati-driver-installer-*-*-x86.86_64.run (Files will extract to a temporary folder and scripts will run...)

Assuming nothing went horribly wrong...

6.) Check /usr/share/ati/fglrx-install.log for issues. There should also be a /lib/modules/fglrx/make.{ker_version}.log

Note: If you modify the make scripts, save to a different filename. Otherwise uninstall will not complete successfully.

7.) Finally, try # aticonfig As of Catalyst 11.7, it still assumes /etc/X11/xorg.conf should exist.

Note: If you want to adhere to the new xorg.conf.d: Append your aticonfig string with --output so that you can adapt the Device section to /etc/X11/xorg.conf.d/20-radeon.conf The drawback of this is that many aticonfig options rely on an xorg.conf, and thus will be unavailable.

Tools

catalyst-generator

catalyst-generator is a package able to build and install fglrx modules packed into nice catalyst-{kernver} pacman's packages.

It creates catalyst-{kernver} packages using makepkg and installs them with pacman. {kernver} is the kernel version for which each package was built (e.g. catalyst-2.6.35-ARCH package was built for 2.6.35-ARCH kernel).

To build and install catalyst-{kernver} package for booted kernel as an unprivileged user (safer way) type this:
catalyst_build_module
You will be asked for root's password to proceed to package installation.
It is important to run this command after installing catalyst-generator.

This package doesn't support auto re-compilation functionality so after kernel updates you will have to manually update catalyst-{kernver} package. Do it in this way (without rebooting):

1.) As root:

# catalyst_build_module remove

This will remove all unused catalyst-{kernver} packages

2.) As unprivileged user:

# catalyst_build_module new_kernel_version

Where new_kernel_version is a version of kernel which you just updated/installed. e.g.:

catalyst_build_module 2.6.36-ARCH

or:

catalyst_build_module all

which will built catalyst-{kernver} packages for all kernels.

If you want to remove catalyst-generator - it's best to run this as root before removing catalyst-generator:

catalyst_build_module remove_all

(This will remove all catalyst-{kernver} packages from the system.)

catalyst-generator isn't able to remove all those catalyst-{kernver} packages automatically while being removed because there can not be more than one instance of pacman running. If you forget to type `catalyst_build_module remove_all` before typing `pacman -R catalyst-generator` - catalyst-generator will tell you which catalyst-{kernver} packages you will have to remove after removing catalyst-generator.

Note: If you see those warnings:

WARNING: Package contains reference to $srcdir

WARNING: '.pkg' is not a valid archive extension.

while building catalyst-{kernver} package - do not be concerned, it's normal.

Automatic re-compilation of fglrx module with every kernel update

Note: Here catalyst_build_module script is working on fglrx modules files, not on pacman's packages.

Most of catalyst_build_module script options mentioned in catalyst-generator section is supported, type catalyst_build_module help to check which ones exactly.

Since catalyst 10.9 that funcionality has been removed from catalyst package mainly because of this and that.

Still it can be very usefull if you are using more than one stock kernel, or you do not like to rebuild catalyst package with every kernel update.
Known mkinitcpio's hook functionality has been moved to AUR's catalyst-hook.

Also there is a new package able to provide similar functionality called catalyst-daemon.

Please note that those packages provides only re-building scripts and source files needed to build fglrx module, and they depend on catalyst-utils package.

Auto re-compilation is enabled by default after installing selected package, if you want to turn it off just run this command as root:

# catalyst_build_module autooff

You can also turn it on with:

# catalyst_build_module auto

catalyst_build_module is storing all informations about compilling/installig fglrx module in log file placed in /var/log/catalys-install.log. But you do not need to remember it, you will be informed about that fact whenever installation fails.

catalyst-hook

In catalyst-hook 'automatic re-compilation' functionality is done by a fglrx hook on mkinitcpio with combination of forcing to update package linux-headers in first place.

The hook will call catalyst_build_module command to update fglrx module for the version of your new kernel, and additionally it will call catalyst_build_module remove command to remove unneeded flgrx module(s).

Note: If you are using this functionality it's important to look at the installation process of linux (or any other kernel) package. fglrx hook will tell you is everything all right.

Note: If your custom kernel is using some non-standard mkinitcpio configuration file (ie. linux-zen is using /etc/mkinitcpio-zen.conf) you'll have to manually add fglrx to HOOKS array so it can be auto-recompiled with kernel's update.

Note: If you aren't using stock linux at all and still wanna use auto recompilation you should remove linux-headers from SyncFirst list of /etc/pacman.conf after running 'catalyst_build_module auto'.

catalyst-daemon

In catalyst-daemon 'automatic re-compilation' functionality is done by init script called autofglrx which runs with every system boot and checks if kernel was updated. If kernel was updated - it's rebuilding fglrx module. If kernel wasn't updated - it's loading previously built fglrx module (this whole operation is taking only 20ms on 2.4 GHz CPU).

Autofglrx's check function is comparing built time of just booted kernel (provided by `uname -v`) with built time of a kernel for which fglrx module was built.
It's able to do such a comparison because it adds `uname -v` information to the fglrx module's description while module's compilation.

While rebuilding autofglrx will call 'catalyst_build_module' to build a module and 'catalyst_build_module remove' to remove unneeded, older fglrx module.

It doesn't remain in memory.

Note: While installation autofglrx is added into beginning of DAEMONS array of /etc/rc.conf file. You may replace it, but be sure to add it before your DM/X, and do NOT add monkey (@) to it because it must NOT be started in background.

Note: If you are using own compilation flags and got problems with a daemon - please add those flags into /usr/bin/catalyst_build_module file.

Configuration

Three things to check in Arch before rebooting, otherwise X can break:

/etc/X11/xorg.conf

/etc/rc.conf

/boot/grub/menu.lst

First, xorg.conf:
AMD provides the aticonfig tool to create/modify xorg.conf file. It also can configure virtually every aspect of the card for it also accesses the amdpcsdb file. For a complete list of aticonfig options, run:

# aticonfig --help | less

Warning: Use the --output option before committing to /etc/X11 as an xorg.conf file will override anything in /etc/X11/xorg.conf.d

Simple examples from aticonfig:

1. Setting up fglrx for the first time.
Single head : aticonfig --initial --input=/etc/X11/xorg.conf
Dual head : aticonfig --initial=dual-head --screen-layout=above
This command will generate a dual head configuration
file with the second screen located above the first
screen.

If you do not already have an xorg.conf file, you can compare the generated file to one of the Sample Xorg.conf examples listed on the Xorg page.

Although most options are now automatically detected in current Xorg, you may want to specify some in case the defaults change between versions.

Here is an example(with notes) for reference. Entries with '#' should be required, add entries with '##' as needed:

Remove radeon from MODULES and blacklist it in /etc/modprobe.d/modprobe.conf if blacklist-fglrx.conf does not exist.

Adding fglrx to MODULES appears to be optional if added instead to /etc/mkinitcpio.conf (boot image would be rebuilt before reboot).

Note: If you are using an AGP card instead of PCI Express add the agp module as well

Finally, menu.lst:

Clear modesetting options as the driver doesn't appear to take advantage of KMS yet. Add nomodeset.

For example: kernel /boot/vmlinuz26 root=/dev/sda1 ro nomodeset

Reboot!

Checking operation

Assuming reboot to your login was successful, otherwise #Troubleshooting.
Commands to check that fglrx is up and running:

lsmod | grep fglrx
fglrxinfo

Finally, run Xorg with startx or by using GDM/KDM and verify that direct rendering is enabled by running the following command in a terminal:

$ glxinfo | grep direct

If it says "direct rendering: yes" then you're good to go! If the glxinfo command is not found, you may need to install the mesa-demos package as well.

Warning: In recent versions of Xorg, the paths of libs are changed. So, sometimes libGL.so cannot be correctly loaded even if it's installed. Check this if your GL is not working. Please read "Troubleshooting" section for details.

Double Screen (Dual Head / Dual Screen / Xinerama)

Introduction

First of all: you have to know, it does not exist one single solution because each needs and configurations are different. That's why you have to adapt the step below to your own needs. It is possible that you have to try more than once. Therefore, you MUST save your working /etc/X11/xorg.conf BEFORE you start any change and you must be able to recover from tty.

In this part, we will describe the installation of 2 differend sized screens on only one graphic cad with 2 different output ports (DVI + HDMI) using a "BIG Desktop" configuration.

The Xinerama solution has some inconveniences, especially because it is not compatible with XrandR. For that very reason, you should not use this solution, because XrandR is just a must for our later configuration.

The Dual Head solution would allow you to have 2 different sessions (one for each screen). It could be your wish but you will not be able to move windows from one screen to another. If you have only one screen, you will have to define the mouse inside your xorg for the 2 sessions inside the Server Layout section.

ATI Catalyst Control Center

The GUI tool shiped by ATI is very useful and we will try to use it as much as we can. To launch it, open a terminal and use the following command line:

kdesu amdcccle

Note: Of course, you have to adapt if you are using GNOME or any other DM.

Warning: Do NOT use sudo directly with a gui. Sudo gives you admin rights with user account information. Kdesu gives you admin rights with root privileges & variables.

Installation

Here, it is easy but important : make sure that your hardware is pluged correctly, power is on, and that you know your hardware caracteristics (screen dimensions, sizes, refresment rates ...) Normally, both screens are recognize during boot time but not necessarly identified properly, especially if you are not using any xorg base configuration file but instead relying on the hot-plugging feature.

The first step is to make sure they will be recognized by your DE / xorg. For this, you need to generate a basic xorg file for your 2 screens :

aticonfig --initial --desktop-setup=horizontal --overlay-on=1

or

aticonfig --initial=dual-head --screen-layout=left

Note: overlay is important because it allows you to have 1 pixel (or more) shared between the 2 screens.

Tip: For the different possible & available options, do not hesitate to type aticonfig inside a terminal to display all available command lines.

Normally, you have now a basic file that you can now edit to add your screen resolutions. It is important to precise the working resolution especially if you have screens of different sizes. To be added insithe the "Screen" section:

SubSection "Display"
Depth 24
Modes "1200x800"
EndSubSection

Well, from now on, instead of editing the xorg.conf file manually, let us use the ATI gui tool. Reboot X to be sure that your 2 screens are well supported and that the resolution are well recognized. (Screens must be independant).

Configuration

Here, you only have to launch the ATI control center with root privileges, go inside the display menu and choose how you would like to set your configuration (small arrow of the drop down menu). A last reboot of X and you will be done !

Before you reboot, do not hesitate to verify your new xorg.conf file. At this stage, inside the "Display" sub-section of the "Screen" section, you should see a "Virtual" command line, of which the resolution should be the sum of both screens. The "Server Layout" section says all the rest.

Features

Video acceleration

Video Acceleration API (VA API) is an open source software library ("libVA") and API specification which enables and provides access to graphics hardware (GPU) acceleration for video processing on Linux and UNIX based operating systems.
The main motivation for VA API is to enable hardware accelerated video decode at various entry-points (VLD, IDCT, Motion Compensation, deblocking) for the prevailing coding standards today (MPEG-2, MPEG-4 ASP/H.263, MPEG-4 AVC/H.264, and VC-1/WMV3).

XvBA support and xvba-video is still under development, however in nowadays it is working very well in most cases and with mplayer (and mplayer front-ends), so feel free to check it. You have to build xvba-video package and install mplayer-vaapi (available in community repository) & libva (available in extra repository) packages.
Then just set your video player to use vaapi:gl as video output.

KWin and composite

You may use XRender if the rendering with OpenGL is slow. However, XRender might also be slower than OpenGL depending on your card.
XRender also solves artifact issues in some cases.

Black screen with complete lockups / hangs after reboot or startx

Faulty ACPI hardware calls

It is possible that fglrx doesn't cooperate well with the system's ACPI hardware calls, so it autodisables itself and there is no screen output.

So try to run this:

aticonfig --acpi-services=off

KDM disappears after logout

If you are running Catalyst proprietary driver and you get a console (tty1) instead of the expected KDM greeting when you log out, you must instruct KDM to restart the X server after each logout:

$ sudo nano /usr/share/config/kdm/kdmrc

Uncomment the following line under the section titled [X-:*-Core]:

TerminateServer=True

KDM should now appear when you log out of KDE.

Direct Rendering does not work

This problem may occur when using the proprietary catalyst driver.

Warning: This error would also appear if you have not rebooted your system after the installation or upgrade of catalyst. The system needs to load the fglrx.ko module in order to make the driver work.

If you have problem with direct rendering, run:

$ LIBGL_DEBUG=verbose glxinfo > /dev/null

at the command prompt. At the very start of the output, it'll usually give you a nice error message saying why you do not have direct rendering.

Common errors, and their solutions, are:

libGL error: XF86DRIQueryDirectRenderingCapable returned false

Ensure that you are loading the correct agp modules for your AGP chipset before you load the fglrx kernel module. To determine which agp modules you'll need, run hwdetect --show-agp, then ensure that all modules listed from that command are in the MODULES= array in rc.conf, before fglrx.

Something has not been installed correctly. If the paths in the error message are /usr/X11R6/lib/modules/dri/fglrx_dri.so, then ensure you've logged completely out of your system, then back in. If you're using a graphical login manager (gdm, kdm, xdm), ensure that /etc/profile is sourced every time you log in. This is usually accomplished by adding source /etc/profile into ~/.xsession or ~/.xinitrc, but may vary between login managers.

If the paths above in your error message are/usr/lib/xorg/modules/dri/fglrx_dri.so, then something has not been correctly installed. Try reinstalling the catalyst package.

These are the only three libGL.so files you should have on your system. If you have any more (e.g. /usr/X11R6/lib/libGL.so.1.2), then remove them. This should fix your problem.

You might not get any error to indicate that this is a problem. If you are using X11R7, make sure you do not have these files on your system:

/usr/X11R6/lib/libGL.so.1.2
/usr/X11R6/lib/libGL.so.1

Hibernate/Sleep Issues

Video fails to resume from suspend2ram

ATI's proprietary Template:Codeline driver cannot resume from suspend if the framebuffer is enabled. To disable the framebuffer, add vga=0 to your kernel options in /boot/grub/menu.lst, for example:

kernel /vmlinuz-linux root=/dev/sda3 resume=/dev/sda2 ro quiet vga=0

System Freezes/Hard locks

The radeonfb framebuffer drivers have been known in the past to cause problems of this nature. If your kernel has radeonfb support compiled in, you may want to try a different kernel and see if this helps.

Hardware Conflicts

Radeon cards used in conjunction with some versions of the nForce3 chipset (e.g. nForce 3 250Gb) won't have 3D acceleration. Currently the cause of this issue is unknown, but some sources indicate that it may be possible to get acceleration with this combination of hardware by booting Windows with the drivers from nVIDIA and then rebooting the system. This can be verified by issuing in a root console the following command:

Some sources indicate that in some situations, downgrading the motherboard BIOS may help, but this cannot be verified in all cases. Also, a bad BIOS downgrade can render your hardware useless, so beware.

With catalyst 10.6 AMD/ATi announce new method of 2D acceleration for radeons, unfortunately this step causes bugs for some users. To turn on old (slower xaa) method of 2d rendering please kill your desktop environment and Xserver and type this command as root: