cchtml.com - User contributions [en]

Ubuntu Oneiric Installation Guide

2012-08-26T13:18:03Z

174.55.160.197: Undo revision 8924 by 85.25.140.166 (Either ignorance or a prank)

__TOC__

= The Options =
Users with ATI cards have the following driver options:
* '''vesa''' - very basic, lacks 2D/3D acceleration, and focuses on compatibility with all VESA-compliant graphics cards. It is good for starting the GUI environment when no accelerated driver is available/working, and little else.
* '''ati''' - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' - open source driver supporting all Radeon cards. This driver has excellent 2D acceleration and compatibility with the Linux graphics stack. 3D acceleration is sufficient for desktop effects and a nice set of native Linux games. Power management is now comparable to the Catalyst driver.
* '''radeonhd''' - an alternate driver supporting R520-R7x0 hardware. This driver is now officially deprecated in favor of radeon. If you still want to try it, see: https://help.ubuntu.com/community/RadeonHD
* '''Catalyst (a.k.a fglrx)''' a proprietary "blob" (closed source binary) driver designed by ATI, with 3D code based off of their Windows driver. Only RadeonHD chips are supported on recent Linux distros.

= Updated Open Source Driver PPA's =
* '''"Ubuntu-X"''' : This PPA offers the latest stable releases of video driver-related components. Follow the instructions at: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
* '''Xorg-edgers''': This bleeding-edge PPA offers video driver-related components straight from their code (git) repositories. Follow the instructions at: https://launchpad.net/~xorg-edgers/+archive/ppa

= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards are no longer supported by ATI?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid/10.04 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Oneiric (or anything later than Lucid/10,04)! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Using Ubuntu-supplied fglrx/Catalyst ==

This may not give you the latest drivers, but should be safest. On Ubuntu Oneiric, this will install Catalyst 8.881, which is roughly equivalent to Catalyst 11-8. NOTE: You must have the restricted repository enabled in Applications -> Ubuntu Software Center -> Edit -> Software Sources... for this to work. After you complete the install, skip to [[Ubuntu_Oneiric_Installation_Guide#Generate_a_new_.2Fetc.2FX11.2Fxorg.conf_file|Generate a new /etc/X11/xorg.conf file]].

=== Command line ===

sudo apt-get install fglrx fglrx-amdcccle

=== GUI ===

You must have jockey-common and jockey-gtk (or jockey-kde for Kubuntu) packages installed. Go to the Additional Drivers Manager (System -> Administration -> Additional Drivers) and activate the "ATI/AMD proprietary FGLRX graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you. For ocelot, go to the dashboard home and search for "Additional Drivers" in the applications search field.

== Installing Catalyst Manually (from AMD/ATI's site) ==
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).
or Applications->Ubuntu Software Center->Edit->Software sources->Other software: check canonical partners.

Install the prerequisite packages:
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases linux-headers-generic

''If you are using the x86_64 architecture (64 bit)'':
1. Install "ia32-libs" before proceeding!''
sudo apt-get install ia32-libs
2. Create a symlink from /usr/lib64 to /usr/lib<ref>[http://ubuntucomputing.blogspot.com/2012/01/amd-catalyst-121-driver-on-hp-pavilion.html AMD Catalyst 12.1 Driver on HP Pavilion dv6t Quad Hybrid Radeon with Linux Mint 12 / Ubuntu 11.10 Oneiric - Ubuntu Computing]</ref> :
cd /usr ; sudo ln -svT lib /usr/lib64
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run

===''Create .deb packages.''===
sudo sh ./amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --buildpkg Ubuntu/oneiric
It may take a while...

===''Install .debs.''===
sudo dpkg -i fglrx*.deb

==''Generate a new /etc/X11/xorg.conf file''==

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

=== Generic Config ===
This will work for most people:
sudo aticonfig --initial -f

=== Minimal Config ===
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by aticonfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:

Section "Device"
Identifier "ATI radeon 6870"
Driver "fglrx"
EndSection

=== X2/Dual GPU Cards ===
If you have an X2 card (e.g. 4870X2 or 5970), use... '''!!Do not use for two separate cards in crossfire!!'''
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all

=== Dual/Multi Monitors ===
If you have a dual monitor display (also known as "Big Desktop"), use:
sudo aticonfig --initial -f
sudo aticonfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553. Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.

==''Force use of the new xorg.conf (if necessary)''==
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:

sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

==''Test your installation''==
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 11-8 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.11005 Compatibility Profile Context (This line may be different depending on what graphics card and
Catalyst version you are using.)
</pre>
Now, try:
fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
sudo aticonfig --tls=0

===''Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".

An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

= Hardware Video Decode Acceleration (EXPERIMENTAL) =
This is confirmed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000-series or newer, you have UVD2. To see the complete list: http://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_enabled_GPUs

sudo apt-get install xvba-va-driver libva-glx1 vainfo
vainfo

vainfo should return something like the following (and no errors):
libva: libva version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/fglrx_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.32
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8
vainfo: Supported profile and entrypoints
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD

Once you've confirmed that vainfo is correct, you can test video playback. A good test player for xvba is VLC. You can enable xvba in Tools -> Preferences -> Input and Codecs. Check the box named "Use GPU acceleration (experimental)" and then restart VLC.

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the 'Removing Catalyst/fglrx' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing Catalyst/fglrx=
The uninstall script in the first command will only exist if you downloaded the drivers and installed them directly (rather than building packages as this guide does). Skip the first command if it does not exist.
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
sudo apt-get install xserver-xorg-video-ati
sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
sudo rm -rf /etc/ati

If you receive

$ E: Internal Error, No file name for libgl1-mesa-dri

Change the third command above to:

sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core

= Issues =

== XvBA Video Acceleration ==

If vainfo returns an error, you may need to create a symlink:

sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so

https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/821691

== Video Tearing ==

AMD/ATI claims that the "Tear Free Video" option is enabled by default, but that wasn't the case on the default Oneiric version of Catalyst (maybe Ubuntu disables it by default?).
If you're having issues with tearing, make sure that "Tear Free Video" is on. You can find this option in the Catalyst Control Center under 'Display Options' or you can use the following command:
sudo aticonfig --sync-video=on
The option will not take effect until you restart X.

If you're using compositing, you should also make sure that vsync is enabled in the compositor's settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.

=== kwin ===
You can enable vsync for kwin in System Settings -> Desktop Effects -> Advanced tab

=== Compiz (Unity/GNOME-Shell) ===
TODO: See if there's a friendlier way to make sure vsync is enabled without installing ccsm.

Install the compiz settings manager:
sudo apt-get install compizconfig-settings-manager
ccsm

The 'Sync to Vblank' is found in the 'OpenGL' subsection of the 'General' group

== Hybrid Graphics and Catalyst==

There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU's. Newer systems (those with PowerXpress >= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU's, and systems with older ATI GPU's have a mux, but don't quote that.

=== ATI/ATI Hybrids ===
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though I don't know if that applies to all ATI/ATI hybrids or only the muxless ones. One would use aticonfig's PowerXpress options to switch back and forth between the integrated and discrete cards, like so:

aticonfig --pxl # List current activated GPU
sudo aticonfig --px-dgpu # Activate discrete GPU (High-Performance mode), must re-start X to take effect
sudo aticonfig --px-igpu # Activate integrated GPU (Power-Saving mode), must re-start X to take effect

After switching, one would log out and back in to restart X.

=== Intel/ATI Hybrids ===

Use of Catalyst on older systems (those with a mux) is no longer supported. I have one report of switching success with Catalyst 11-6, but ATI has now disabled switching in Catalyst, even if it worked fine with older Catalyst versions. X will refuse to start and you will find this message in your Xorg log:
(WW) PowerXpress feature is not supported on A+I Mux platform. Please uninstall fglrx driver.
(EE) No devices detected.

Using open-source drivers and the vgaswitcheroo script may work better in this case.

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.841/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.5 in Ubuntu Natty). This should allow you to install fglrx:
sudo ln -sf /usr/bin/gcc-4.5 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
sudo dpkg -i --force-overwrite fglrx*.deb

== Problems Starting Xserver ==

If you get a black screen hang, the first thing to check is if xorg.conf is the problem.

You can disable the xorg.conf with:
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled

Reboot and check to see if things work now.

You can reinstate the file with:
sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf

Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

start on filesystem

script
chmod 0666 /dev/null
chmod 0666 /lib/udev/devices/null
end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
sudo aticonfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help.

If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a newer version of Catalyst than the one you're running.
cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run
sh amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --extract driver
sudo mv /etc/ati/control ~/control.bak
sudo cp driver/common/etc/ati/control /etc/ati

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorization files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server.

Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

cd ~/catalyst{{Catalystversion}}
sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
sudo chmod +x /etc/ati/authatieventsd.sh

This problem can be fixed permanently with:

sudo mkdir -p /var/lib/xdm/authdir
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles

If that doesn't work then you can disable atieventsd with this command:

sudo /usr/sbin/update-rc.d -f atieventsd remove

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
sudo dkms build -m fglrx -k `uname -r`
sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

== Aticonfig not found after installation & "module does not exist" after boot ==
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous fglrx installs, including those through Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig --initial after driver installation, you might end up not having the aticonfig available at all:
<pre>aticonfig: command not found</pre>
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do
ls /usr/lib/fglrx/bin
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do
update-alternatives --get-selections | grep gl_conf
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to
sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:
sudo update-alternatives --auto gl_conf
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.

== "update-alternatives: error" during install ==
During installation you may receive the following message:
<pre>update-alternatives: error: unable to make /usr/lib/xorg/modules/drivers/fglrx_drv.so.dpkg-tmp a symlink to /etc/alternatives/fglrx_drv: No such file or directory</pre>
This can be easily solved by creating directory "drivers" under /usr/lib/xorg/modules/
sudo mkdir /usr/lib/xorg/modules/drivers

== 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==
During installation you may receive the following message:
<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre>
This can happen when your /tmp folder is mounted with the option "noexec". The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]

== Black screen after uninstalling old amd drivers ==
Start you computer in recovery mode and exit to root shell.
Remount your partitions in rw mode:
mount -rw -o remount /
...
Go to your download directory and proceed with building and installing the drivers in recovery mode.
All should be fine after a reboot.

== References ==

<references/>

cchtml.com:Current events

2011-12-07T17:40:13Z

174.55.160.197: Undo revision 7724 by 94.122.66.247 (SPAM)

*Add pages for every distribution.
*Setup categories as we go along.
*Anything else I missed.

A spam filter is now in place, and I have customized it to better detect normal spammers. If you get blocked from the filter, please let [mailto:mike@cchtml.com me] know.

==Server News==
09-29-06
New 320gig perpendicular drive installed. Working great.
 
10-02-06
SpamBlacklist extension installed again to prevent weblink spam
 
08-17-07
All '''info''' domains are now blocked due to spammer abuse. If you need to post a '''info''' URL, post it on the discussion page.
 
09-10-07
Spammers have forced me to close anonymous editing. I may re-open it if a better spam filter becomes available.
 
09-11-07
I have enabled the simple captcha extension [http://www.mediawiki.org/wiki/Extension:ConfirmEdit ConfirmEdit] and re-enabled anonymous editing.
 
06-04-08
Doubled Internet connection thanks to advertising support. Spammers seem to have compromised the captcha, ugh.
 
10-17-09
Moved to new Nahalem-based server. Super-fast!
[http://www.italyavizesi.org İtalya Vizesi]

A Google Adsense bar has been added to help pay for hardware and bandwidth costs. Thanks to you guys, this wiki has become a hotspot for the ATI fglrx driver. Keep those hits coming!

Ubuntu Natty Installation Guide

2011-02-25T17:09:27Z

174.55.140.68: News Update

= Construction Notice =
Since Ubuntu Natty/11.04 is still under construction, so is this page. Until Natty is released, the Maverick guide ( http://wiki.cchtml.com/index.php/Ubuntu_Maverick_Installation_Guide ) will serve as the main source of info on ATI Catalyst. This page will only note items that are relevant to Natty, but not Maverick.

= Xserver 1.10 Incompatibility Warning =
(This section to be removed once Catalyst supports Xserver 1.10)
Hopefully, AMD will integrate support for the new Xserver before Natty's release. The Catalyst 11.3 beta is said to have it. --[[User:Dtl131|Dtl131]] 21:00, 29 January 2011 (UTC)

{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''Major Breakage'''
|-
| WARNING: At the end of January 2011, Ubuntu integrated Xserver 1.10 into Ubuntu Natty/11.04. Even the most current release of Catalyst, 11-2, is not compatible with it, so Catalyst will not work if you have already installed Xserver 1.10. If you have not yet installed it, and want to run Catalyst on your Natty/11.04 install, you can hold the Xserver packages (or "Lock Version" as Synaptic refers to it) and continue to run Catalyst 10-12. 
|}

= Patching Catalyst 10-12 Source =
(This section to be removed once Catalyst supports Xserver 1.10)
Catalyst 10-12 needs patched for compliance with kernel version 2.6.37 before you can install it.

$ cd ~/; mkdir catalyst10.12; cd catalyst10.12/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-12-x86.x86_64.run
$ chmod +x ati-driver-installer-10-12-x86.x86_64.run
$ ./ati-driver-installer-10-12-x86.x86_64.run --extract driver
$ cd driver
$ wget http://ubuntuone.com/p/WVN/firegl_public.c
$ wget http://ubuntuone.com/p/WVU/Makefile
$ mv firegl_public.c common/lib/modules/fglrx/build_mod/
$ mv Makefile common/lib/modules/fglrx/build_mod/2.6.x/
$ ./ati-installer.sh 8.801 --buildpkg Ubuntu/natty
$ cd ..
$ sudo dpkg -i fglrx*.deb

= Catalyst and Unity =
At this time, Catalyst doesn't work with the new Ubuntu desktop (Unity). You can still use the classic GNOME desktop (or another desktop environment).

Catalyst 10.10

2010-11-20T13:18:35Z

174.55.140.68: undo trolling

AMD Catalyst Linux 10.10 driver 
Revision Number: 10.10 (8.783) 
Release Date: 10/22/2010 
Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, or 7.6 

== External Links ==
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-10-10-x86.x86_64.run Installer]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_1010_linux.pdf Release Notes]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat1010-inst.pdf Installer instructions]
* [http://ati.amd.com/products/catalyst/linux.html AMD Proprietary Linux Driver FAQ]

[[Category:Releases]]

Ubuntu Lucid Installation Guide

2010-11-20T01:17:12Z

174.55.140.68: update for Catalyst 10.11

__TOC__

= The Options =
Users with ATI cards basically have these options:
# '''Standard Open Source Drivers''' Usually stable. These drivers currently have relatively poor 3D performance, but newer 3D drivers using the Gallium3D infrastructure are under development.
# '''Edge Open Source Drivers''' These drivers have improved 3D performance
# '''The Ubuntu Way''' Use the restricted-driver management system (a.k.a jockey) that comes with Ubuntu to install the proprietary drivers.
# '''Install the proprietary drivers manually''' Package-based install of a driver downloaded from AMD/ATI's site.

= Open Source Drivers =
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.
* '''ati''' Actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later. This driver is now all but officially deprecated in favor of radeon.

By default there is no configuration file (xorg.conf) for X anymore, so X will try to do the right thing.

If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ mainline-2.6.34-lucid] did the trick on a few machines.

= Installing Open Source Edge Drivers =

These packages are built regularly from the X.Org git repository, so they may not be fully stable. On Lucid, using this graphics stack now uses the r300g Gallium3D driver for 3D acceleration on Radeon R300-R500 (Radeon 9500 - Radeon X1950) class chips. It's probably a good idea to use the linux kernel provided by this repo if you go this route.

To install:
$ sudo add-apt-repository ppa:xorg-edgers/ppa
$ sudo apt-get update
Now you can update your packages using Synaptic or Update Manager.
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards do ATI no longer support?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid. If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Lucid! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Restricted Drivers Manager ==
NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

== Ubuntu X Team's PPA ==
This is an excellent PPA, frequently updated, and run by Ubuntu veterans.
$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
$ sudo apt-get update
At this point, you should install available updates and then you can install the driver:
$ sudo apt-get install fglrx

== Installing the drivers manually ==
I recommend copying and pasting the commands (do not include the leading '$') to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the "Removing the Driver" section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).

Install the prerequisite packages:
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''
$ sudo apt-get install ia32-libs

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-11-x86.x86_64.run

There is a new security hotfix need as of 9/28/2010, as a Linux kernel security update broke the driver:

http://support.amd.com/us/kbarticles/Pages/GPU83ATICatalystLinuxHotfix.aspx

'''Note''': this does not seem necessary anymore (12-nov-10) as the Release Notes for the Catalyst 10.10 states:

'''Resolved Known Issues'''
Kernel module build will now function on kernels with fix for security vulnerability CVE-2010-3081

===''Create .deb packages.''===
$ sh ati-driver-installer-10-11-x86.x86_64.run --buildpkg Ubuntu/lucid

===''Install .debs.''===
$ sudo dpkg -i fglrx*.deb

===''Generate a new /etc/X11/xorg.conf file''===

Before you do this, back up your current xorg.conf if you have one ('''Lucid does not have an xorg.conf by default''')

==== Back Up xorg.conf ====
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

==== Generic Config ====
This will work for most people:
$ sudo aticonfig --initial -f

==== X2 Cards ====
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
$ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all

==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
$ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.

===''Force use of the new xorg.conf (if necessary)''===
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

$ sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

===''Test your installation''===
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
$ fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 10-6 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4300/4500 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.9901 Compatibility Profile Context (This line may be different depending on what graphics card and Catalyst version you are using.)
</pre>
Now, try:
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig --tls=0
Another possibility may be to disable locked user pages with:
$ sudo aticonfig --locked-userpages=off
This option is even described in the help output of aticonfig.

===''Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".

An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

=Updating the Driver=

DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing the Driver=
The uninstall script in the first command will only exist if you downloaded the drivers and installed the directly (rather than building packages as this guide does). Skip the first command if it does not exist.
$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo dpkg-reconfigure xserver-xorg

= Issues =

== Build Fails and Log Shows "error: implicit declaration of function ‘compat_alloc_user_space’" ==

This issue occurs with more recent Lucid kernels (>= 2.6.32-25-generic). A workaround is proposed here: http://ubuntuforums.org/showpost.php?p=9877727&postcount=10

A slightly more detailed instructions (for newbies) are here: http://ubuntuforums.org/showthread.php?s=72306ca847141e035ce8bf9b28506c76&t=1576383

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.741/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
$ ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.4 in Ubuntu Lucid). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
$ sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

$ sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb

== Crashes in WINE ==
For more information, see [http://bugs.winehq.org/show_bug.cgi?id=4561#c6 this WINEHQ bug report]. This issue should be fixed in WINE 1.1.40, so you may want to get an updated version of WINE by using [https://launchpad.net/~vivnet/+archive/vivnet-wine this PPA]. If you prefer the Ubuntu version of WINE, then turn FastTLS off:
$ sudo aticonfig --tls=0

== Segfault Starting Xserver ==

After upgrading to Catalyst 10-6 the Xserver does not start. Xorg.0.log shows a segmentation fault. Adding
BusID "PCI:1:0:0"
to the fglrx Device section in xorg.conf helps. For more information, look at [http://ati.cchtml.com/show_bug.cgi?id=1836 bug #1836] in the bugtracker.

== Problems Starting Xserver ==
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

$ start on filesystem
$
$ script
$ chmod 0666 /dev/null
$ chmod 0666 /lib/udev/devices/null
$ end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo aticonfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. The new acceleration code was also available in Catalyst 10-2 through 10-5 (including the Catalyst that ships with Lucid), though it was not used by default. If you're using one of those versions, you can try the new acceleration code with the following command:
$ sudo aticonfig --set-pcs-str=DDX,Direct2DAccel,TRUE
Restart X (by logging out or rebooting) to apply the change. If you experience issues and want to return to the older, stable code:
$ sudo aticonfig --del-pcs-key=DDX,Direct2DAccel
If you're using Catalyst 10-6 or later, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE

In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a different version of Catalyst.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-11-x86.x86_64.run
$ chmod +x ati-driver-installer-10-11-x86.x86_64.run
$ sh ati-driver-installer-10-11-x86.x86_64.run --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati

If the above workaround causes issues, restore the original control file:

$ sudo mv ~/control.bak /etc/ati/control

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
$ sudo apt-get remove xserver-xgl
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
$ DISPLAY=:0 glxinfo | grep render
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart some others:
$ sudo modprobe -r i82875p_edac
$ sudo modprobe -r fglrx
$ sudo modprobe -r intel-agp
$ sudo modprobe -r agpgart
$ sudo modprobe agpgart
$ sudo modprobe intel-agp
$ sudo modprobe fglrx

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting
$ gksu gedit /etc/modprobe.d/blacklisti82875p_edac.conf
:add the following line to the blank text file:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you upgraded to your current Ubuntu install (rather than doing a clean install), you may still be using the old kernel without knowing it.
$ uname -r
:If your kernel version is less than 2.6.32, it is a kernel from a previous Ubuntu installation.

If this doesn't help, try other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:

$ sudo mkdir -p /var/lib/xdm/authdir
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre>

If that doesn't work then you can disable atieventsd with this command:

$ sudo /usr/sbin/update-rc.d -f atieventsd remove

Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

$ cd ~/catalyst{{Catalystversion}}
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
$ sudo chmod +x /etc/ati/authatieventsd.sh</pre>

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

$ sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
$ sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
$ sudo dkms build -m fglrx -k `uname -r`
$ sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

== Aticonfig not found after installation & "module does not exist" after boot ==
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig --initial after driver installation, you might end up not having the aticonfig available at all:
<pre>aticonfig: command not found</pre>
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do
$ ls /usr/lib/fglrx/bin
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do
$ update-alternatives --get-selections | grep gl_conf
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to
$ sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:
$ sudo update-alternatives --auto gl_conf
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.

Ubuntu Maverick Installation Guide

2010-11-20T01:15:46Z

174.55.140.68: update for Catalyst 10.11

__TOC__

= The Options =
Users with ATI cards have the following driver options:
* '''vesa''' - very basic, lacks 2D/3D acceleration, and focuses on compatibility with all VESA-compliant graphics cards. It is good for starting the GUI environment when no accelerated driver is available/working and little else.
* '''ati''' - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' - open source driver supporting all Radeon cards. This driver has excellent 2D acceleration and compatibility with the Linux graphics stack. 3D acceleration is sufficient for desktop effects and a nice set of native Linux games. Power management is now comparable to the Catalyst driver.
* '''radeonhd''' - an alternate driver supporting R520-R7x0 hardware. This driver is now officially deprecated in favor of radeon. If you still want to try it, see: https://help.ubuntu.com/community/RadeonHD
* '''Catalyst (a.k.a fglrx)''' a proprietary "blob" (closed source binary) driver designed by ATI, with 3D code based off of their Windows driver. Only RadeonHD chips are supported on recent Linux distros.

= Updated Open Source Driver PPA's =
* '''"Ubuntu-X"''' : This PPA offers the latest stable releases of video driver-related components. Follow the instructions at: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
* '''Xorg-edgers''': This bleeding-edge PPA offers video driver-related components straight from their code (git) repositories. Follow the instructions at: https://launchpad.net/~xorg-edgers/+archive/ppa

= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards do ATI no longer support?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid. If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Maverick! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Restricted Drivers Manager ==
NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Maverick, this will install Catalyst 8.780, which is roughly equivalent to Catalyst 10-10. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

== Installing the drivers manually ==
I recommend copying and pasting the commands (do not include the leading '$') to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the "Removing the Driver" section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).

Install the prerequisite packages:
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''
$ sudo apt-get install ia32-libs

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-11-x86.x86_64.run

===''Create .deb packages.''===
$ sh ati-driver-installer-10-11-x86.x86_64.run --buildpkg Ubuntu/maverick

===''Install .debs.''===
$ sudo dpkg -i fglrx*.deb

===''Generate a new /etc/X11/xorg.conf file''===

Before you do this, back up your current xorg.conf if you have one ('''Lucid does not have an xorg.conf by default''')

==== Back Up xorg.conf ====
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

==== Generic Config ====
This will work for most people:
$ sudo aticonfig --initial -f

==== X2 Cards ====
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
$ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all

==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
$ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.

===''Force use of the new xorg.conf (if necessary)''===
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

$ sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

===''Test your installation''===
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
$ fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 10-6 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4300/4500 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.9901 Compatibility Profile Context (This line may be different depending on what graphics card and Catalyst version you are using.)
</pre>
Now, try:
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig --tls=0

===''Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".

An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing Catalyst/fglrx=
The uninstall script in the first command will only exist if you downloaded the drivers and installed the directly (rather than building packages as this guide does). Skip the first command if it does not exist.
$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo dpkg-reconfigure xserver-xorg

= Issues =

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.780/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
$ ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.4 in Ubuntu Maverick). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
$ sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

$ sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb

== Problems Starting Xserver ==
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

$ start on filesystem
$
$ script
$ chmod 0666 /dev/null
$ chmod 0666 /lib/udev/devices/null
$ end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo aticonfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. If you're not running compositing/desktop effects, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE

In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a different version of Catalyst.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-11-x86.x86_64.run
$ chmod +x ati-driver-installer-10-11-x86.x86_64.run
$ sh ati-driver-installer-10-11-x86.x86_64.run --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati

If the above workaround causes issues, restore the original control file:

$ sudo mv ~/control.bak /etc/ati/control

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
$ sudo apt-get remove xserver-xgl
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
$ DISPLAY=:0 glxinfo | grep render
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:

$ sudo mkdir -p /var/lib/xdm/authdir
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre>

If that doesn't work then you can disable atieventsd with this command:

$ sudo /usr/sbin/update-rc.d -f atieventsd remove

Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

$ cd ~/catalyst{{Catalystversion}}
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
$ sudo chmod +x /etc/ati/authatieventsd.sh</pre>

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

$ sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
$ sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
$ sudo dkms build -m fglrx -k `uname -r`
$ sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

== Aticonfig not found after installation & "module does not exist" after boot ==
This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig --initial after driver installation, you might end up not having the aticonfig available at all:
<pre>aticonfig: command not found</pre>
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do
$ ls /usr/lib/fglrx/bin
and see if the command lists some Ati related programs. If they are listed but not found from /usr/bin, it is possible that the "update-alternatives" fglrx .deb installation does has been ignored. See man update-alternatives for more information about the concept and workings of alternatives. In practice, update-alternatives is supposed to create several symbolic links to the files in the fglrx directory, but it will be ignored if the alternatives for the very related gl_conf entry has been set to manual. Do
$ update-alternatives --get-selections | grep gl_conf
and see if the mode is manual instead of auto and if mesa is mentioned instead of fglrx in the path that is printed. In this case you need to
$ sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf
to set fglrx as the active alternative. You can alternatively (no pun intended) and additionally change the gl_conf into automatic mode before the installation this way:
$ sudo update-alternatives --auto gl_conf
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.

10.11

2010-11-20T01:13:27Z

174.55.140.68: yeah..

#Redirect [[Catalyst 10.11]]

10.11

2010-11-20T01:13:11Z

174.55.140.68: Initial page

#Redirect [[Catalyst 10.10]]

Template:Catalystversion

2010-11-20T01:08:34Z

174.55.140.68:

[[10.11]]<noinclude>
== Usage ==

<pre>{{catalystversion}}</pre>
'''This template is for the version number only.'''
[[Category:Catalyst Templates]]
</noinclude>

Catalyst 10.11

2010-11-20T01:07:16Z

174.55.140.68: Initial creation

AMD Catalyst Linux 10.11 driver 
Revision Number: 10.11 (8.791) 
Release Date: 11/17/2010 
Description: Automated installer and Display Drivers for X.Org 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, or 7.6 

== External Links ==
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-10-11-x86.x86_64.run Installer]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_1011_linux.pdf Release Notes]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat1011-inst.pdf Installer instructions]
* [http://ati.amd.com/products/catalyst/linux.html AMD Proprietary Linux Driver FAQ]

[[Category:Releases]]

Ubuntu Lucid Installation Guide

2010-09-30T07:31:01Z

174.55.140.68: Added compat_alloc_user_space issue

__TOC__

= The Options =
Users with ATI cards basically have these options:
# '''Standard Open Source Drivers''' Usually stable. These drivers currently have relatively poor 3D performance, but newer 3D drivers using the Gallium3D infrastructure are under development.
# '''Edge Open Source Drivers''' These drivers have improved 3D performance
# '''The Ubuntu Way''' Use the restricted-driver management system (a.k.a jockey) that comes with Ubuntu to install the proprietary drivers.
# '''Install the proprietary drivers manually''' Package-based install of a driver downloaded from AMD/ATI's site.

= Open Source Drivers =
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.
* '''ati''' Actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later. This driver is now all but officially deprecated in favor of radeon.

By default there is no configuration file (xorg.conf) for X anymore, so X will try to do the right thing.

If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ mainline-2.6.34-lucid] did the trick on a few machines.

= Installing Open Source Edge Drivers =

These packages are built regularly from the X.Org git repository, so they may not be fully stable. On Lucid, using this graphics stack now uses the r300g Gallium3D driver for 3D acceleration on Radeon R300-R500 (Radeon 9500 - Radeon X1950) class chips. It's probably a good idea to use the linux kernel provided by this repo if you go this route.

To install:
$ sudo add-apt-repository ppa:xorg-edgers/ppa
$ sudo apt-get update
Now you can update your packages using Synaptic or Update Manager.
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards do ATI no longer support?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid. If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Lucid! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Restricted Drivers Manager ==
NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

== Ubuntu X Team's PPA ==
This is an excellent PPA, frequently updated, and run by Ubuntu veterans.
$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
$ sudo apt-get update
At this point, you should install available updates and then you can install the driver:
$ sudo apt-get install fglrx

== Installing the drivers manually ==
I recommend copying and pasting the commands (do not include the leading '$') to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the "Removing the Driver" section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).

Install the prerequisite packages:
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''
$ sudo apt-get install ia32-libs

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-9-x86.x86_64.run

===''Create .deb packages.''===
$ sh ati-driver-installer-10-9-x86.x86_64.run --buildpkg Ubuntu/lucid

===''Install .debs.''===
$ sudo dpkg -i fglrx*.deb

===''Generate a new /etc/X11/xorg.conf file''===

Before you do this, back up your current xorg.conf if you have one ('''Lucid does not have an xorg.conf by default''')

==== Back Up xorg.conf ====
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

==== Generic Config ====
This will work for most people:
$ sudo aticonfig --initial -f

==== X2 Cards ====
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
$ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all

==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
$ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.

===''Force use of the new xorg.conf (if necessary)''===
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

$ sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

===''Test your installation''===
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
$ fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 10-6 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4300/4500 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.9901 Compatibility Profile Context (This line may be different depending on what graphics card and Catalyst version you are using.)
</pre>
Now, try:
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig --tls=0

===''Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".

An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

=Updating the Driver=

DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing the Driver=
The uninstall script in the first command will only exist if you downloaded the drivers and installed the directly (rather than building packages as this guide does). Skip the first command if it does not exist.
$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo dpkg-reconfigure xserver-xorg

= Issues =

== Build Fails and Log Shows "error: implicit declaration of function ‘compat_alloc_user_space’" ==

This issue occurs with more recent Lucid kernels (>= 2.6.32-25-generic). A workaround is proposed here: http://ubuntuforums.org/showpost.php?p=9877727&postcount=10

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.741/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
$ ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.4 in Ubuntu Lucid). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
$ sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

$ sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb

== Crashes in WINE ==
For more information, see [http://bugs.winehq.org/show_bug.cgi?id=4561#c6 this WINEHQ bug report]. This issue should be fixed in WINE 1.1.40, so you may want to get an updated version of WINE by using [https://launchpad.net/~vivnet/+archive/vivnet-wine this PPA]. If you prefer the Ubuntu version of WINE, then turn FastTLS off:
$ sudo aticonfig --tls=0

== Segfault Starting Xserver ==

After upgrading to Catalyst 10-6 the Xserver does not start. Xorg.0.log shows a segmentation fault. Adding
BusID "PCI:1:0:0"
to the fglrx Device section in xorg.conf helps. For more information, look at [http://ati.cchtml.com/show_bug.cgi?id=1836 bug #1836] in the bugtracker.

== Problems Starting Xserver ==
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

$ start on filesystem
$
$ script
$ chmod 0666 /dev/null
$ chmod 0666 /lib/udev/devices/null
$ end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo aticonfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. The new acceleration code was also available in Catalyst 10-2 through 10-5 (including the Catalyst that ships with Lucid), though it was not used by default. If you're using one of those versions, you can try the new acceleration code with the following command:
$ sudo aticonfig --set-pcs-str=DDX,Direct2DAccel,TRUE
Restart X (by logging out or rebooting) to apply the change. If you experience issues and want to return to the older, stable code:
$ sudo aticonfig --del-pcs-key=DDX,Direct2DAccel
If you're using Catalyst 10-6 or later, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE

In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a different version of Catalyst.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-9-x86.x86_64.run
$ chmod +x ati-driver-installer-10-9-x86.x86_64.run
$ sh ati-driver-installer-10-9-x86.x86_64.run --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati

If the above workaround causes issues, restore the original control file:

$ sudo mv ~/control.bak /etc/ati/control

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
$ sudo apt-get remove xserver-xgl
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
$ DISPLAY=:0 glxinfo | grep render
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart some others:
$ sudo modprobe -r i82875p_edac
$ sudo modprobe -r fglrx
$ sudo modprobe -r intel-agp
$ sudo modprobe -r agpgart
$ sudo modprobe agpgart
$ sudo modprobe intel-agp
$ sudo modprobe fglrx

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting
$ gksu gedit /etc/modprobe.d/blacklisti82875p_edac.conf
:add the following line to the blank text file:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you upgraded to your current Ubuntu install (rather than doing a clean install), you may still be using the old kernel without knowing it.
$ uname -r
:If your kernel version is less than 2.6.32, it is a kernel from a previous Ubuntu installation.

If this doesn't help, try other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:

$ sudo mkdir -p /var/lib/xdm/authdir
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre>

If that doesn't work then you can disable atieventsd with this command:

$ sudo /usr/sbin/update-rc.d -f atieventsd remove

Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

$ cd ~/catalyst{{Catalystversion}}
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
$ sudo chmod +x /etc/ati/authatieventsd.sh</pre>

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

$ sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
$ sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
$ sudo dkms build -m fglrx -k `uname -r`
$ sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

Ubuntu Lucid Installation Guide

2010-08-20T16:26:41Z

174.55.140.68: Clarify uninstall script

__TOC__

= The Options =
Users with ATI cards basically have these options:
# '''Standard Open Source Drivers''' Usually stable. These drivers currently have relatively poor 3D performance, but newer 3D drivers using the Gallium3D infrastructure are under development.
# '''Edge Open Source Drivers''' These drivers have improved 3D performance
# '''The Ubuntu Way''' Use the restricted-driver management system (a.k.a jockey) that comes with Ubuntu to install the proprietary drivers.
# '''Install the proprietary drivers manually''' Package-based install of a driver downloaded from AMD/ATI's site.

= Open Source Drivers =
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.
* '''ati''' Actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards).
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later. This driver is now all but officially deprecated in favor of radeon.

By default there is no configuration file (xorg.conf) for X anymore, so X will try to do the right thing.

If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ mainline-2.6.34-lucid] did the trick on a few machines.

= Installing Open Source Edge Drivers =

These packages are built regularly from the X.Org git repository, so they may not be fully stable. On Lucid, using this graphics stack now uses the r300g Gallium3D driver for 3D acceleration on Radeon R300-R500 (Radeon 9500 - Radeon X1950) class chips. It's probably a good idea to use the linux kernel provided by this repo if you go this route.

To install:
$ sudo add-apt-repository ppa:xorg-edgers/ppa
$ sudo apt-get update
Now you can update your packages using Synaptic or Update Manager.
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =
*PLEASE READ FIRST!
'''Which cards do ATI no longer support?'''
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid. If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION RADEON USERS'''
|-
| NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Lucid! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers. 
|}

== Restricted Drivers Manager ==
NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You must also have the fglrx-modaliases and jockey-gtk (or jockey-kde for Kubuntu) packages installed. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.

== Ubuntu X Team's PPA ==
This is an excellent PPA, frequently updated, and run by Ubuntu veterans.
$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
$ sudo apt-get update
At this point, you should install available updates and then you can install the driver:
$ sudo apt-get install fglrx-installer

== Installing the drivers manually ==
I recommend copying and pasting the commands (do not include the leading '$') to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl '''+ Shift''' + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).

===''Before you start''===
If you have previously attempted installing Catalyst, remove any leftover files by following the "Removing the Driver" section. Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).

Install the prerequisite packages:
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''
$ sudo apt-get install ia32-libs

===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-7-x86.x86_64.run

===''Create .deb packages.''===
$ sh ati-driver-installer-10-7-x86.x86_64.run --buildpkg Ubuntu/lucid

===''Install .debs.''===
$ sudo dpkg -i fglrx*.deb

===''Generate a new /etc/X11/xorg.conf file''===

Before you do this, back up your current xorg.conf if you have one (Lucid does not have an xorg.conf by default)

==== Back Up xorg.conf ====
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

==== Generic Config ====
This will work for most people:
$ sudo aticonfig --initial -f

==== X2 Cards ====
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
$ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all

==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
$ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.

===''Force use of the new xorg.conf (if necessary)''===
Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

$ sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

===''Test your installation''===
NOTE: if you don't reboot first, fglrxinfo gives an error message.
Reboot the computer and type
$ fglrxinfo
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 10-6 and a RadeonHD 4550 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4300/4500 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.9901 Compatibility Profile Context (This line may be different depending on what graphics card and Catalyst version you are using.)
</pre>
Now, try:
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig --tls=0

===''Just in case''===
Write down or remember this series of Alt+PrntScr key combinations, just in case your screen should go black and Ctrl+Alt+F1 and Ctrl+Alt+Backspace doesn't work.

Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b

These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".

An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

=Updating the Driver=

DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.

=Removing the Driver=
The uninstall script in the first command will only exist if you downloaded the drivers and installed the directly (rather than building packages as this guide does). Skip the first command if it does not exist.
$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo dpkg-reconfigure xserver-xorg

= Issues =

== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==

If the installation fails and you find the above message in /var/lib/dkms/fglrx/8.741/build/make.log, it may be because you're using a pentium-build wrapper around gcc. See what the following ls command returns:
$ ls -la /usr/bin/gcc
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.4 in Ubuntu Lucid). This should allow you to install fglrx:
$ sudo ln -sf /usr/bin/gcc-4.4 /usr/bin/gcc
When you're finished installing the driver, return the gcc link to its original value:
$ sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957

== "Errors were encountered while processing: fglrx-amdcccle" (on 64-bit systems) ==
Most likely, you probably did not have the "ia32-libs" package installed beforehand. If you have a 64 bit install, the above dpkg command may complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, use the following command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

$ sudo apt-get -f install

Catalyst {{Template:Catalystversion}} on 64-bit systems may require the ''--force-overwrite'' command in the above ''dpkg'' command:
$ sudo dpkg -i --force-overwrite fglrx*.deb

== Crashes in WINE ==
For more information, see [http://bugs.winehq.org/show_bug.cgi?id=4561#c6 this WINEHQ bug report]. This issue should be fixed in WINE 1.1.40, so you may want to get an updated version of WINE by using [https://launchpad.net/~vivnet/+archive/vivnet-wine this PPA]. If you prefer the Ubuntu version of WINE, then turn FastTLS off:
$ sudo aticonfig --tls=0

== Segfault Starting Xserver ==

After upgrading to Catalyst 10-6 the Xserver does not start. Xorg.0.log shows a segmentation fault. Adding
BusID "PCI:1:0:0"
to the fglrx Device section in xorg.conf helps. For more information, look at [http://ati.cchtml.com/show_bug.cgi?id=1836 bug #1836] in the bugtracker.

== Problems Starting Xserver ==
Before tweaking ACPI settings, try ensuring /dev/null is chmodded to 0666. This intermittently changes when using the nano (and possibly other) editors with sudo and the group/world permissions are unset. This leads to the ATI drivers hanging on boot or otherwise. A quick and dirty init script saved as /etc/init/chmodnull does the trick for me -

$ start on filesystem
$
$ script
$ chmod 0666 /dev/null
$ chmod 0666 /lib/udev/devices/null
$ end script

This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig --tls=0) to get things to stay stable!

If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo aticonfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.

== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. The new acceleration code was also available in Catalyst 10-2 through 10-5 (including the Catalyst that ships with Lucid), though it was not used by default. If you're using one of those versions, you can try the new acceleration code with the following command:
$ sudo aticonfig --set-pcs-str=DDX,Direct2DAccel,TRUE
Restart X (by logging out or rebooting) to apply the change. If you experience issues and want to return to the older, stable code:
$ sudo aticonfig --del-pcs-key=DDX,Direct2DAccel
If you're using Catalyst 10-6 or later, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE

In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start

== Unsupported Hardware Watermark ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help. If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a different version of Catalyst.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-{{Catalystversion}}-x86.x86_64.run
$ chmod +x ati-driver-installer-{{Catalystversion}}-x86.x86_64.run
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati

If the above workaround causes issues, restore the original control file:

$ sudo mv ~/control.bak /etc/ati

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
$ sudo apt-get remove xserver-xgl
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
$ DISPLAY=:0 glxinfo | grep render
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart some others:
$ sudo modprobe -r i82875p_edac
$ sudo modprobe -r fglrx
$ sudo modprobe -r intel-agp
$ sudo modprobe -r agpgart
$ sudo modprobe agpgart
$ sudo modprobe intel-agp
$ sudo modprobe fglrx

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting
$ gksu gedit /etc/modprobe.d/blacklisti82875p_edac.conf
:add the following line to the blank text file:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you upgraded to your current Ubuntu install (rather than doing a clean install), you may still be using the old kernel without knowing it.
$ uname -r
:If your kernel version is less than 2.6.32, it is a kernel from a previous Ubuntu installation.

If this doesn't help, try other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

If you experience hangs when logging out (of X) it is probably due to the /etc/ati/authatieventsd.sh script looking for X authorisation files in the wrong place when it starts up. You can kill the hanging authatieventsd.sh processes from a console tty to allow the shutdown of the X server. This can be fixed permanently with:

$ sudo mkdir -p /var/lib/xdm/authdir
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre>

If that doesn't work then you can disable atieventsd with this command:

$ sudo /usr/sbin/update-rc.d -f atieventsd remove

Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do:
(assuming that the installer is in the directory we used to install)

$ cd ~/catalyst{{Catalystversion}}
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh
$ sudo chmod +x /etc/ati/authatieventsd.sh</pre>

You'll have to restart for this to take effect.

== Suspend/Hibernation ==

Suspend hibernation '''works''' with the latest driver.

For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)

<pre>
Section "Extensions"
Option "Composite" "Disable"
EndSection

Section "ServerFlags"
Option "AIGLX" "off"
EndSection
</pre>

Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):

$ sudo apt-get install fusion-icon

After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.

When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)

KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.

Hopefully this helped some people, as it did for me!
Solution posted by zwyber@gmail.com

== Can't remove fglrx with dpkg (diversion issue) ==

If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:
<pre>dpkg-divert: mismatch on divert-to
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2

== This module/version combo is already installed ==

If you get this error-message, simply uninstall the previous version before installing the new one with:
$ sudo dkms remove -m fglrx --all

== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:
$ sudo dkms build -m fglrx -k `uname -r`
$ sudo dkms install -m fglrx -k `uname -r`

if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]

10.7

2010-07-26T18:36:16Z

174.55.164.6: Redirect page

#Redirect [[Catalyst 10.7]]

Template:Catalystversion

2010-07-26T18:34:38Z

174.55.164.6:

[[10.7]]<noinclude>
== Usage ==

<pre>{{catalystversion}}</pre>
'''This template is for the version number only.'''
[[Category:Catalyst Templates]]
</noinclude>

Catalyst 10.6

2010-07-26T18:32:47Z

174.55.164.6:

ATI Catalyst Linux 10.6 driver 
Revision Number: 10.6 (8.741) 
Release Date: 6/16/2010 
Description: Automated installer and Display Drivers for X.Org 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, or 7.5 

== External Links ==
* [http://www2.ati.com/drivers/linux/ati-driver-installer-10-6-x86.x86_64.run Installer]
* [http://www2.ati.com/drivers/linux/catalyst_106_linux.pdf Release notes]
* [http://www2.ati.com/drivers/linux/linux_cat106-inst.pdf Installer instructions]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]

[[Category:Releases]]

Catalyst 10.7

2010-07-26T18:31:41Z

174.55.164.6: Created page with 'ATI Catalyst Linux 10.7 driver Revision Number: 10.7 (8.753) Release Date: 7/26/2010 Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.…'

ATI Catalyst Linux 10.7 driver 
Revision Number: 10.7 (8.753) 
Release Date: 7/26/2010 
Description: Automated installer and Display Drivers for X.Org 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4, or 7.5 

== External Links ==
* [http://www2.ati.com/drivers/linux/ati-driver-installer-10-7-x86.x86_64.run Installer]
* [http://www2.ati.com/drivers/linux/catalyst_107_linux.pdf Release notes]
* [http://www2.ati.com/drivers/linux/linux_cat107-inst.pdf Installer instructions]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]

[[Category:Releases]]