cchtml.com - User contributions [en]

Fedora

2011-08-22T19:58:41Z

85.127.17.174: Undo revision 7177 by 146.243.4.157 (talk)

Fedora is a free GNU/Linux distribution sponsored by [http://www.redhat.com Red Hat]. It is not Red Hat, but has a similar history. Red Hat does use aspects of Fedora as an incubator for their Red Hat Enterprise Linux products. Please see the [[Red Hat Enterprise Linux]] distribution guide for more Red Hat specific information.

== General Status ==
* Repackaged by [http://rpm.livna.org/rlowiki/LivnaSwitcher Thorsten Leemhuis] and [http://freshrpms.net Matthias Saou].
* Official ATI binary package maintained by [http://www.phoronix.com Phoronix].

==Installation==

*[[Fedora Core 4 Installation Guide]]
*[[Fedora Core 5 Installation Guide]]
*[[Fedora Core 6 Installation Guide]]
*[[Fedora 7 Installation Guide]]
*[[Fedora 8 Installation Guide]]
*[[Fedora 9 Installation Guide]]
*[[Fedora 10 Installation Guide]]
*[[Fedora 11 Installation Guide]]
*[[Fedora 12 Installation Guide]]
*[[Fedora 13 Installation Guide]]
*[[Fedora 14 Installation Guide]]

==Related Resources==
*[http://rpmfusion.org/ RPMFusion RPM Repository] - Fedora RPM Builds
*[http://www.fedorafaq.org/#radeon Fedora FAQ] - Fedora FAQ

==References==
<references/>

{{VCT}}

[[Category: Distributions]]

Catalyst 9.4

2009-04-19T09:53:03Z

85.127.108.122:

ATI Catalyst Linux 9.4 driver 
Release date: April 17, 2009

The following products have been '''moved to the legacy software support structure''' (including Mobile and All-in-Wonder Variants):

* ATI Radeon 9500 Series
* ATI Radeon 9550 Series
* ATI Radeon 9600 Series
* ATI Radeon 9700 Series
* ATI Radeon 9800 Series
* ATI Radeon X300 Series
* ATI Radeon X550 Series
* ATI Radeon X600 Series
* ATI Radeon X700 Series
* ATI Radeon X800 Series
* ATI Radeon X850 Series
* ATI Radeon X1050 Series
* ATI Radeon X1300 Series
* ATI Radeon X1550 Series
* ATI Radeon X1600 Series
* ATI Radeon X1650 Series
* ATI Radeon X1800 Series
* ATI Radeon X1900 Series
* ATI Radeon Xpress Series
* ATI Radeon X1200 Series
* ATI Radeon X1250 Series
* ATI Radeon X2100 Series

== External Links ==
* [https://www2.ati.com/drivers/linux/ati-driver-installer-9-4-x86.x86_64.run Installer]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_94_linux.pdf Release notes]
* [http://www2.ati.com/drivers/linux/linux_cat92-inst.pdf Installer instructions]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]

[[Category:Releases]]

Catalyst 9.4

2009-04-19T09:47:34Z

85.127.108.122:

'''From the Release Notes:'''

AMD has moved a number of DX9 ATI Radeon™ graphics accelerators products to a legacy driver support structure. This change impacts Windows XP, Windows Vista, and Linux distributions. AMD has moved to a legacy software support structure for these graphics accelerator products in an effort to better focus development resources on future products.

The following products have been moved to the legacy software support structure (including Mobile and All-in-Wonder Variants):

* ATI Radeon 9500 Series
* ATI Radeon 9550 Series
* ATI Radeon 9600 Series
* ATI Radeon 9700 Series
* ATI Radeon 9800 Series
* ATI Radeon X300 Series
* ATI Radeon X550 Series
* ATI Radeon X600 Series
* ATI Radeon X700 Series
* ATI Radeon X800 Series
* ATI Radeon X850 Series
* ATI Radeon X1050 Series
* ATI Radeon X1300 Series
* ATI Radeon X1550 Series
* ATI Radeon X1600 Series
* ATI Radeon X1650 Series
* ATI Radeon X1800 Series
* ATI Radeon X1900 Series
* ATI Radeon Xpress Series
* ATI Radeon X1200 Series
* ATI Radeon X1250 Series
* ATI Radeon X2100 Series

AMD may periodically provide Windows XP and Windows Vista driver updates (for the products listed above) for critical fixes only. No new features will be provided in future driver updates. The Linux ATI Catalyst™ driver will only be supported in Linux distributions prior to February 2009 for the legacy products listed above.

Any customers using a combination of a ATI Radeon™ HD 2000 Series, ATI Radeon™ HD 3000 Series, or ATI Radeon™ HD 4000 Series product with any of the legacy products listed above in a single PC system must use the ATI Catalyst 9.3 or earlier driver. All future ATI Catalyst™ releases made available past the ATI Catalyst™ 9.3 release will not include support for the legacy products listed above or any of the features associated with those legacy products.

Catalyst 9.4

2009-04-19T09:47:06Z

85.127.108.122: New page: From the Release Notes: AMD has moved a number of DX9 ATI Radeon™ graphics accelerators products to a legacy driver support structure. This change impacts Windows XP, Windows Vista, an...

From the Release Notes:

AMD has moved a number of DX9 ATI Radeon™ graphics accelerators products to a legacy driver support structure. This change impacts Windows XP, Windows Vista, and Linux distributions. AMD has moved to a legacy software support structure for these graphics accelerator products in an effort to better focus development resources on future products.

The following products have been moved to the legacy software support structure (including Mobile and All-in-Wonder Variants):

* ATI Radeon 9500 Series
* ATI Radeon 9550 Series
* ATI Radeon 9600 Series
* ATI Radeon 9700 Series
* ATI Radeon 9800 Series
* ATI Radeon X300 Series
* ATI Radeon X550 Series
* ATI Radeon X600 Series
* ATI Radeon X700 Series
* ATI Radeon X800 Series
* ATI Radeon X850 Series
* ATI Radeon X1050 Series
* ATI Radeon X1300 Series
* ATI Radeon X1550 Series
* ATI Radeon X1600 Series
* ATI Radeon X1650 Series
* ATI Radeon X1800 Series
* ATI Radeon X1900 Series
* ATI Radeon Xpress Series
* ATI Radeon X1200 Series
* ATI Radeon X1250 Series
* ATI Radeon X2100 Series

AMD may periodically provide Windows XP and Windows Vista driver updates (for the products listed above) for critical fixes only. No new features will be provided in future driver updates. The Linux ATI Catalyst™ driver will only be supported in Linux distributions prior to February 2009 for the legacy products listed above.

Any customers using a combination of a ATI Radeon™ HD 2000 Series, ATI Radeon™ HD 3000 Series, or ATI Radeon™ HD 4000 Series product with any of the legacy products listed above in a single PC system must use the ATI Catalyst 9.3 or earlier driver. All future ATI Catalyst™ releases made available past the ATI Catalyst™ 9.3 release will not include support for the legacy products listed above or any of the features associated with those legacy products.

Template:Catalystfilename

2009-04-19T09:26:27Z

85.127.108.122:

ati-driver-installer-9-4-x86.x86_64.run<noinclude>
== Usage ==

<pre>{{catalystfilename}}</pre>
[[Category:Catalyst Templates]]
</noinclude>

Ubuntu Jaunty Installation Guide

2009-04-01T13:11:21Z

85.127.102.1: /* The three alternatives */

= Installation Guide for Ubuntu Jaunty (v 9.04) =

== The three alternatives ==
Users with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently have poor 3D performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jockey/"restricted" packages).
# Install the drivers manually. This should be your last resort, and '''may not even work'''. '''

= The open source drivers =
By default, one of the open source drivers are used. If this works for you, you don't need to change anything.

These come with the X.org X server:
* '''vesa''' (should work everywhere)
* '''ati''' (will select the "radeon" driver automatically, if needed)
* '''radeon'''
* '''radeonhd'''

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.
There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
'''This doesn't work for all ATI cards just yet. In the near future you should be able to have this smooth experience:'''
* 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

== Post-Installation Tweaks ==
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''

<pre>
Section "Device"
[...]
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
[...]
EndSection
</pre>

Note that when Visual Effects (Compiz) are active, flickering and artifacts may occur in OpenGL applications and hardware accelerated video windows (particularly with R300 chipset). To prevent this, disable Visual Effects.

= Installing the restricted drivers manually =
''If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!''

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

===''Before you start''===
Install the necessary programs
{{Box Terminal|
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms
}}

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

Download page: Catalyst {{catalystversion}}. 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

===''2. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/jaunty
}}

===''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 doesen'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 rembember the keypresses, remember this nonsensical phrase: "Raising Skinny Elefants Is Never Utterly Boring"

===''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 dpmk. If so install this first. Also check the version numbers (8.561) 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.''
[http://www.example.com link title]

== Additional 64-bit instructions ==

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 install -f
}}

Catalyst {{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
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Finishing the Install: Configuration ==

'' Note: try auto config first, and follow the question guide, reboot; if no effect observed, restore ''xorg.conf-bkp'' ''
{{Box Terminal|
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf-bkp 
sudo dpkg-reconfigure xserver-xorg
}}

'''If you've used fglrx previously, you will not need to do this.'''

Now you'll have to edit your xorg.conf

For Ubuntu:
{{Box Terminal|
sudo gedit /etc/X11/xorg.conf
}}

For Kubuntu:
{{Box Terminal|
sudo kate /etc/X11/xorg.conf
}}

and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it doesn't give an error you should be good.

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:

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

Finally, reboot the computer and type
{{Box Terminal|
fglrxinfo
}}
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.12 looks like:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 3850
OpenGL version string: 2.1.8304 Release
</pre>

Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.

== Finally ==
# 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, warsow etc :)

= Issues =

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

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

Ubuntu Jaunty Installation Guide

2009-04-01T13:10:47Z

85.127.102.1: /* Restricted Drivers Manager */

= Installation Guide for Ubuntu Jaunty (v 9.04) =

== The three alternatives ==
Users with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently have poor 3D performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jockey/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work. '''

= The open source drivers =
By default, one of the open source drivers are used. If this works for you, you don't need to change anything.

These come with the X.org X server:
* '''vesa''' (should work everywhere)
* '''ati''' (will select the "radeon" driver automatically, if needed)
* '''radeon'''
* '''radeonhd'''

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.
There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
'''This doesn't work for all ATI cards just yet. In the near future you should be able to have this smooth experience:'''
* 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

== Post-Installation Tweaks ==
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''

<pre>
Section "Device"
[...]
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
[...]
EndSection
</pre>

Note that when Visual Effects (Compiz) are active, flickering and artifacts may occur in OpenGL applications and hardware accelerated video windows (particularly with R300 chipset). To prevent this, disable Visual Effects.

= Installing the restricted drivers manually =
''If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!''

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

===''Before you start''===
Install the necessary programs
{{Box Terminal|
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms
}}

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

Download page: Catalyst {{catalystversion}}. 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

===''2. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/jaunty
}}

===''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 doesen'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 rembember the keypresses, remember this nonsensical phrase: "Raising Skinny Elefants Is Never Utterly Boring"

===''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 dpmk. If so install this first. Also check the version numbers (8.561) 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.''
[http://www.example.com link title]

== Additional 64-bit instructions ==

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 install -f
}}

Catalyst {{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
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Finishing the Install: Configuration ==

'' Note: try auto config first, and follow the question guide, reboot; if no effect observed, restore ''xorg.conf-bkp'' ''
{{Box Terminal|
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf-bkp 
sudo dpkg-reconfigure xserver-xorg
}}

'''If you've used fglrx previously, you will not need to do this.'''

Now you'll have to edit your xorg.conf

For Ubuntu:
{{Box Terminal|
sudo gedit /etc/X11/xorg.conf
}}

For Kubuntu:
{{Box Terminal|
sudo kate /etc/X11/xorg.conf
}}

and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it doesn't give an error you should be good.

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:

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

Finally, reboot the computer and type
{{Box Terminal|
fglrxinfo
}}
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.12 looks like:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 3850
OpenGL version string: 2.1.8304 Release
</pre>

Please note: Depending on the particular ATI card that you own, you may or may not automatically have all of the relevant driver features enabled. R500 and R600 cards (X1xxx, HD series, and newer) in particular will need TexturedVideo enabled in Xorg.conf (rather than the traditional VideoOverlay) in order to support Xv accelerated video playback.

== Finally ==
# 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, warsow etc :)

= Issues =

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

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

Template:Catalystfilename

2009-04-01T10:11:48Z

85.127.102.1:

ati-driver-installer-9-3-x86.x86_64.run<noinclude>
== Usage ==

<pre>{{catalystfilename}}</pre>
[[Category:Catalyst Templates]]
</noinclude>

Catalyst 7.12

2008-01-05T14:45:08Z

85.127.233.221:

ATI Catalyst Linux 7.12 driver

Release date: 20 December, 2007

The driver contains lots of bugfixes. Finally suspend/hibernate works with SLUB.

==New Features (according to the release notes)==
*This release of the ATI Catalyst™ Linux driver introduces support for the following new operating systems:

* Red Flag DT 6.0 Support
* OpenSUSE 10.3 Support

==Resolved Issues (according to the release notes)==
* A memory leak is no longer noticed when running OpenGL applications
* Running X -configure no longer results in a segmentation fault in the fglrx driver
* fglrxinfo no longer reports OpenGL Render string: as Mesa GLX Indirect on systems containing an ATI Rialto AGP series of product

==Known Issues (according to the release notes)==
* There is no support for video playback on the second head in dual head mode. Further details can be found in topic number 737-26985
* Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
* A black screen may be observed on some hardware when switching to the console or leaving the X window system when a Vesa framebuffer console driver is used. Further details can be found in topic number 737-30687
* Corruption may be noticed in the lower right corner of the display after the system is running for a long period of time
* Display flicker may be noticed when the gnome screen-saver starts
* Diagonal tearing may be noticed when playing a video file using a video player that utilizes the XVideo extension
* Video playback may look blocky when playing a video file using a video player that utilizes the XVideo extension
* Video Playback may display wrong colors and additional shadow images when cropping or expanding a video file using a video player that utilizes the XVideo extension
* Connecting a display device that supports 1680x1050 to a system running Linux may result in a maximum display resolution of 1280x1024 only being available
* Custom mode lines in xorg.conf may be ignored by the fglrx driver
* Building RPM packages for Mandriva may fail

Some of the issues are the same issues that have been plaguing the driver, just finally acknowledged. The one about the 1680x1050 resolution is true, accept when I tried the driver I could only get 1024x768.

Similar issues have also been observed with a Thinkpad T43 and HP 8510p; the native resolution of 1400x1050 cannot be used, and even if it is the only mode defined in xorg.conf, the display starts up with 1280x1024. ([[User:Akhuettel|Akhuettel]])

Same on a MacBook Pro (maximum is 1152x864, should be 1400x900)

==External links==

* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run Installer]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_712_linux.html Release notes]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat712-inst.html Installer Instructions]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]
[[Category:Releases]]