cchtml.com - User contributions [en]

Debian

2012-10-09T13:23:33Z

94.40.24.73: /* Debian Squeeze x86_64 and AMD A Series (June 2012) */

= Read Me First =

'''Which cards are no longer supported by ATI Catalyst?'''
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 Debian Squeeze/6.0 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use Debian Lenny/5.0.x and install Catalyst 9-3.
{| 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 Debian versions later than Lenny/5.0.x! !!!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. 
|}

= Installation =

The open-source ati/radeon driver should already be installed and used as the default.
See [[Debian Open Source|Debian Open Source Drivers]].
This guide focuses on installing the proprietary ATI driver (fglrx/Catalyst).

==Before Starting==
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section.

== Installing from Debian Repository ==

NOTE: This no longer works on Wheezy/testing or Sid after upgrade to Xserver 1.12. Unfortunately fglrx/Catalyst trigger segfaults in Xorg newer than 1.11.x, and the driver was removed from Wheezy and Sid.

Fglrx is non-free software, so it is located in the non-free repository. If you do not have non-free enabled, you can do so like this: http://serverfault.com/questions/240920/how-do-i-enable-non-free-packages-on-debian

$ sudo apt-get remove --purge xserver-xorg-video-radeon
$ sudo apt-get install fglrx-driver fglrx-control fglrx-glx fglrx-atieventsd fglrx-modules-dkms

If you are using 64-bit Debian, install the 32-bit fglrx libraries for use with 32-bit programs.

$ sudo apt-get install fglrx-glx-ia32

The Debian community provides information on its wiki pages [http://wiki.debian.org/ATIProprietary here] and [http://wiki.debian.org/ATIStream here].

== Installing Manually ==
This [[can not]] work at all. please refer the Discussion for details....

This method uses the latest Catalyst driver downloaded from AMD/ATI's site.

===Prerequisite Packages===
Install the prerequisite packages (names are based on Debian sid, older Debians may be different):
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 module-assistant dh-modaliases
''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 <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

Interestingly enough, as I test this (October 6, 2012), it seems that AMD have started releasing the driver as a *.zip file. The current version can be found here :
$ http://www2.ati.com/drivers/linux/amd-driver-installer-12-8-x86.x86_64.zip

===Create .deb packages.===
You can run <code>./amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --listpkg</code> to get a list of all the potential packages

For Debian systems, <package> will be one of the following:
Debian/sid Debian/unstable Debian/etch Debian/stable Debian/lenny Debian/testing Debian/experimental
$ fakeroot sh amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --buildpkg <package>

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

== Wheezy Installation (current as of June 22, 2012) ==

Wheezy upgraded from xserver 1.11 to 1.12 on May 20, 2012. AMD has not updated their driver to work with this version of xserver. So, you have two options:

1) Downgrade from xserver 1.12 (Tested, and works on 6/22/12 on Debian Wheezy kernel 3.2.0-1-amd64)

Link to instructions (this should be copied over to this wiki for posterity):
https://www.linuxquestions.org/questions/linux-hardware-18/how-do-i-get-my-fglrx-driver-back-946102/#post4684285.

Notes:
In the linked directions they use fglrx version 12.4. At the time of making this edit beta version 12.6 also works just fine. If you want to run the bleeding edge, it can be found here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English
With the 12.6 beta version you will get a watermark in the lower right hand corner. After you have everything working properly run this script: http://www.areyoueye.net/scripts/watermark_nix.sh It will get rid of that water mark.

2) Patch libpciaccess (I have no first hand knowledge of this working but others swear by it)

This will get you the latest and greatest xserver and fglrx working together.

Read this: http://ati.cchtml.com/show_bug.cgi?id=522
Apply this patch: http://pastebin.com/swpDj4FD

= Post Install =

==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 amdconfig --initial -f

If you are using dual head, that is to say, two _different_ desktops on two monitors, do this:
$ sudo amdconfig --initial=dual-head -f

Most people with two or more monitors will want instead one large desktop; to do this you may
have to specify your monitors individually in the xorg.conf file and tell the driver to use a
larger desktop size (big enough to contain both monitors) then use xrandr to configure the
monitor arrangement.

=== 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 amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon 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 amdconfig --initial -f --adapter<nowiki>=</nowiki>all

=== Dual/Multi Monitors ===

A post at http://phoronix.com/forums/showthread.php?t=18553 suggested to do the following
to use a dual monitor display (also known as "Big Desktop"):
$ sudo amdconfig --initial -f
$ sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"

However the information is dated 2009 and now believed to be obsolete.

For multiple monitors, instead try specifying all monitors in your xorg.conf file.
Use the following as a starting point:

Section "ServerLayout"
Identifier "amdconfig Layout"
Screen 0 "amdconfig-Screen[0]-0" 0 0
EndSection

Section "Module"
EndSection

Section "Monitor"
Identifier "0-DFP6"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
EndSection

Section "Monitor"
Identifier "0-CRT1"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
EndSection

Section "Device"
Identifier "amdconfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
Option "Monitor-DFP6" "0-DFP6"
Option "Monitor-CRT1" "0-CRT1"
EndSection

Section "Screen"
Identifier "amdconfig-Screen[0]-0"
Device "amdconfig-Device[0]-0"
Monitor "0-DFP6"
DefaultDepth 24

SubSection "Display"
Viewport 0 0
Depth 24
# Big Desktop: 1920+1280=3200, max(1080,1024)=1080
Virtual 3200 1080
EndSubSection

EndSection

After starting X successfully, use <nowiki>xrandr</nowiki> to check the maximum screen size
is large enough for your combined desktop:

$ xrandr
Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 3200 x 1080

And positioning of connected monitors:

DFP1 disconnected (normal left inverted right x axis y axis)
DFP2 disconnected (normal left inverted right x axis y axis)
DFP3 disconnected (normal left inverted right x axis y axis)
DFP4 disconnected (normal left inverted right x axis y axis)
DFP5 disconnected (normal left inverted right x axis y axis)
DFP6 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
[modes elided]
CRT1 connected 1280x1024+1920+56 (normal left inverted right x axis y axis) 338mm x 270mm

Use xrandr (or in KDE, krandrtray) to reposition your monitors within your screen.

==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 amdconfig <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-4 and a RadeonHD 4250 returns:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4200 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.10665 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 amdconfig --tls=0

= 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
== Debian wheezy/7.0 and Later ==
$ sudo apt-get install xvba-va-driver

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section below to remove your existing driver.

=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* 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 mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

=Catalyst 11.9 and Debian Squeeze x86_64 (October 2011)=
Version 11.9 will not install on Debian Squeeze with Kernel >= 3.1. To fix and install proceed as follows.
First uninstall all versions of fglrx you can find, see above. (!!)

Download the driver and extract it thusly:
$ sudo ./ati-driver-installer-11-9-x86.x86_64.run --keep
Enter the newly created directory (will be named fglrx-install.XXXXXX).
Use a hexeditor to find bytes starting at A6B0 with the values <nowiki>e8 53 90 ff ff</nowiki> and replace them with <nowiki>90 90 90 90 90</nowiki>.
This replaces a faulty free-op with 5 no-ops and fixes the exception thrown by "setup.data/bin/x86_64/setup".
Read up on this at <nowiki>http://disbauxes.upc.es/?p=2964</nowiki> .

Now the kernel-build-environment for the 3.1 kernel is currently missing in the repositories. To get around that type:
$ sudo aptitude install linux-source-3.1.0-rc7
$ cd /usr/src;tar -xjf linux-source-3.1.0-rc7;ln -s linux-source-3.1.0-rc7 linux;cd linux;
You may need to append an "-amd64" (or similar) to the localversion of the source to have its version-string match the one of the running kernel.
To do so open .config in the current dir with an editor and search for "LOCALVERSION", set that var to "-amd64" or similar.
Configure the kernel using
$ sudo make oldconfig
and build it using
$ make-kpkg --initrd --append-to-version="-myversion" kernel_image kernel_headers modules_image
You may not need to rebuild the whole kernel, installing its headers may be enough,
but i wanted a fresh kernel with a few custom options.
Install your kernel (or just the headers) from the .deb-files that were created by make-kpkg in the directory above.

After this return to the directory where you extracted the driver to and type:
$ sudo ./amd-installer.sh 8.892 --install --force

To load the driver type:
$ sudo modprobe fglrx

=Debian Squeeze x86_64 and AMD A Series (June 2012)=

First install Kernel 3.2 from squeeze-backports.
Add backports to your sources.list
Add this line
deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free

to your sources.list (or add a new file to /etc/apt/sources.list.d/)
$ sudo apt-get update
$ sudo apt-get -t squeeze-backports install linux-image-3.2.0-0.bpo.2-amd64

$ sudo reboot

$ sudo apt-get remove --purge xserver-xorg-video-radeon
$ sudo apt-get -t squeeze-backports install fglrx-driver fglrx-control fglrx-glx fglrx-atieventsd fglrx-modules-dkms

If you are using 64-bit Debian, install the 32-bit fglrx libraries for use with 32-bit programs.

$ sudo apt-get -t squeeze-backports install fglrx-glx-ia32

[[Category:Distributions]]

Ubuntu Jaunty Installation Guide

2011-08-22T20:38:18Z

94.40.120.253: /* Finishing the Install: Configuration */

__TOC__

{| 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 UBUNTU JAUNTY USERS'''
|-
| Warning: Does not work for all system combinations at this time 
|}

= The Options =
Users with ATI cards basically have these options:
# '''Standard Open Source Drivers''' These are stable and nice, but currently have poor 3D performance, if any. If you have a Radeon X1k product or earlier, this is your only option.
# '''Edge Open Source Drivers''' These drivers have improved 3D performance
# '''The Ubuntu Way''' Use the restricted-driver management system that comes with Ubuntu to install the proprietary drivers.
# '''Third (Fourth?) Party Installer''' Use envy/jockey or other installer helper.
# '''Install the drivers manually''' Using the installer downloaded from AMD's site via either package based install or direct install.

= 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 facade that will invoke the radeon driver.
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later.

By default there is no configuration file 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.29.3/ mainline-2.6.29.3] did the trick on a few machines.

There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future. For more information, see http://wiki.x.org/wiki/RadeonFeature

= Installing Open Source Edge Drivers =

These drivers are built regularly from the X.Org git repository. So sometimes they work, sometimes they don't. However, they have been stable for me, and are the only drivers that work for me. The fglrx drivers hang my system, and the standard "radeon" driver does not support a 2560x1600 resolution.

To install:

First add the repository https://launchpad.net/~tormodvolden/+archive/ppa. Instructions on how to do that are on that page. Then update your packages using Update Manager, and then add the ''xserver-xorg-video-radeonhd'' package. When you log in, you may be using the new driver, but you will probably still be using the radeon driver. To switch to the radeonhd driver, add this to '''/etc/X11/xorg.conf''' :

<pre>Section "Device"
Identifier "Default Device"
Driver "radeonhd"
EndSection</pre>

= The Ubuntu way to install the Proprietary Drivers =

== Restricted Drivers Manager ==
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available
* Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"
* Ubuntu will then install and configure the driver for you

Note that you will be restricted to the drivers for you version of Ubuntu that Canonical deem as stable. This may not give you the latest drivers, but should be safest. The driver installed this way does not work with Radeon X1300.

= Installing the drivers manually =
*PLEASE READ FIRST!
This portion of the guide works, since I have used it myself. I guess the rest of the guide is broken or it may be because the new driver doesn't support any of the older ATI cards anymore.

'''Which cards does ATI no longer support?'''
The ATI Radeon 9500-9800, X300-X2100, Xpress. See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
If your card is on that list, you are restricted to the 9.3 driver - however since 9.3 driver doesn't support xorg-xserver 1.6, it will not work with Jaunty! This guide currently is for installing 9.10. !!!SO BE CAREFUL!!!

_______________________________________________

I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Ctrl + Shift + V or Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.

''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''

Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.

No complaints on this end, simlpy a good piece.

===''1. Download the latest Catalyst package.''===

Download page: Catalyst {{catalystversion}} -- File: {{catalystfilename}}. This package contains both the 32-bit and 64-bit driver.

Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)

Make sure your directory path does not contain spaces

(Errors may be experienced during the creation of the *.deb files for manual install for version 9.12. If so try 9.11 as I tested it myself and had no errors)

===''2. Create .deb packages.''===
{{Box Terminal|
sh {{Template:Catalystfilename}} --buildpkg Ubuntu/jaunty
}}
''note that if you are following these instructions for karmic to replace Ubuntu/jaunty with Ubuntu/karmic''

===''3. 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 keypresses will reboot the system safely. To remember the keypresses, 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 remebering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.

===''4. Install .debs.''===

Install the debs, depending on if you're on a 32-bit or 64-bit system:

* For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}

(This may fail due to a missing dkms. If so install this first. Also check the version numbers (8.632) against the created debs)

* For 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

=== ''5. Additional 64-bit instructions'' ===

--If you have installed the "ia32-libs" package most likely you will not need to do this step.--

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, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdcccle package:

{{Box Terminal|
sudo apt-get -f install
}}

Catalyst {{Template:Catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb fglrx-modaliases_*.deb libamdxvba1_*.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

I cannot tell a lie, that rlleay helped.

=HOW TO UPDATE DRIVER=

To update your driver to a new version (say 9.5 to 9.6) first disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal: {{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it doesn't give an error you should be good.

If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
{{Box Terminal|
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all
}}
instead in a terminal to generate the /etc/Xorg.conf file.

and

{{Box Terminal|
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>
}}

then reboot.

It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the old driver then installed the new one, it worked perfectly.

=HOW TO REMOVE DRIVER=

To completely remove the driver disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer.

Alternatively, use the following command from the terminal.

{{Box Terminal|
sudo apt-get remove --purge xorg-driver-fglrx
}}

=Tweaks=
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422
# Restart X, if it doesn't work, you can use the "vesa", "ati", "radeon" or "radeonhd" driver in the mean time, until you make it work.
# If you downgraded X to make fglrx work: enter synaptic, make sure all packages with "xorg" and "x11" are locked so that you can update and upgrade without worries.

Done! Now run amdcccle, glxgears, nexuiz, warsow etc :)

= Issues =

== Installation ==
There are some system configurations on which '''none''' of the installation alternatives work with the latest 9.5 driver (please add; also please add if you got it to work in one of the listed setups):
* Ubuntu 9.04 (x64 and i386) on x86_64 with Radeon HD4870X2 and 9.5 driver: Framebuffer error ("No valid linear framebuffer address"), garbled screen.
** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.4 driver: use 'aticonfig --initial -f --adapter=all'
** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.6 driver: use 'aticonfig --initial -f' (without adapter=all, if you only have one screen)
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD3870X2 and 9.5 driver: "No supported adapters detected."
* Ubuntu 9.04 (x64) on x86 and x86_64 with Radeon HD4850X2: Framebuffer error, garbled screen.
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4850: Framebuffer error, garbled screen (with automatic log-on, using the restricted drivers manager installation).
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.
**Working Radeon HD 3300 connected to an HDTV, I had a garbled screen before, I reinstalled Ubuntu, then follow manual steps closely. Reinstalled because I didn't know how to remove fglrx, but you may be able to avoid reinstalling by following fglrx complete removal in this guide.
**Working 790GX (A790GMH/128M) with 9.5 driver after manual install (following install with envyng, which might be older version as of 25/5/09). Able to change display resolution which before was not working.
**Working 790GX (MSI 790GX-G65): Now able to call System/Video Configuration which hang up. This driver also reduced the power consumption by 15 W (from 93 W down to 78 W). Thank you for that great installation guide.
** Working Radeon HD 3450 connected to an HDTV on Kubuntu 9.04. Followed manual install of latest drivers (9.6) to the letter, rebooted, and works fully.

== 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.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''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
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
: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 a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<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're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or 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:

<pre>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:

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

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 your home directory)

<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre>

<pre>sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre>

(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)

<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre>

just reboot login and ctrl+alt+backspace to try

== Suspend/Hibernation ==

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

For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

<blockquote>
Comment: This is a little surprising, since the comments at the beginning of /etc/default/acpi-support seem to make it quite clear that those settings are ignored unless you add "acpi-support" to SUSPEND_METHODS. --[[User:Bewst|Bewst]] 23:22, 19 December 2008 (UTC)
</blockquote>

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):

<code>
sudo apt-get install fusion-icon
</code>

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 ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.

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

If you get this error-message, simply uninstall the previous version before installing the new one with:
{{Box Terminal|
sudo dkms remove -m fglrx -v 8.522 --all
}}

== New kernel installed? ==
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.
You can do that by these simple steps:
{{Box Terminal|
sudo dkms build -m fglrx -v 8.552 -k `uname -r` 
sudo dkms install -m fglrx -v 8.552 -k `uname -r`
}}
[[Category:Installation Documentation]]
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf