<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.cchtml.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=24.84.0.0%2F16</id>
	<title>cchtml.com - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.cchtml.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=24.84.0.0%2F16"/>
	<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Special:Contributions/24.84.0.0/16"/>
	<updated>2026-11-18T15:35:14Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=AMDGPU-PRO_17.30_(August_14)&amp;diff=11153</id>
		<title>AMDGPU-PRO 17.30 (August 14)</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=AMDGPU-PRO_17.30_(August_14)&amp;diff=11153"/>
		<updated>2017-09-18T19:42:47Z</updated>

		<summary type="html">&lt;p&gt;24.84.37.19: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;AMD released an &amp;quot;updated&amp;quot; version 17.30 driver ([[AMDGPU-PRO 17.30|originally released July 27, 2017]]).&lt;br /&gt;
&lt;br /&gt;
Version: 17.30&lt;br /&gt;
&lt;br /&gt;
Release Date: August 14, 2017&lt;br /&gt;
&lt;br /&gt;
==New in This Version==&lt;br /&gt;
* Provides support for the Radeon RX Vega series of graphics cards&lt;br /&gt;
* Provides support for RHEL 6.9 and CentOS 6.9&lt;br /&gt;
* Provides support for Ubuntu 16.04.3 (kernel 4.10/X.Org 1.19)&lt;br /&gt;
&lt;br /&gt;
==Fixed Issues==&lt;br /&gt;
* Display goes into sleep mode while installing the Driver on RHEL7.3&lt;br /&gt;
* Application crashes while swapping rendering engine settings from &amp;quot;OpenGL&amp;quot; to &amp;quot;OpenGL Core profile&amp;quot; on Maya 2016&lt;br /&gt;
* Fatal error observed while Exit/Close of Houdini v16&lt;br /&gt;
* Unable to get to Desktop after driver install the driver on RHEL7.3&lt;br /&gt;
* Performance score fluctuation while running Unigine Heaven with a 4K display, under 8x mode.&lt;br /&gt;
* Failure observed while running Specviewperf10 ensight test under Ubuntu&lt;br /&gt;
* Occasional hang observed while playing Hitman and Rust&lt;br /&gt;
&lt;br /&gt;
==Known Issues==&lt;br /&gt;
* System hangs are observed sometimes during wake on performing S3 on Vega-based cards&lt;br /&gt;
* Corruption observed in F1 2015 on Vega-based cards&lt;br /&gt;
* A display hang may be observed when launching CounterStrike: Global Offensive in low settings on Vega-based cards.&lt;br /&gt;
* Booth Demo Sample is not as expected in Radeon ProRender&lt;br /&gt;
* Application crashes may occur while setting the Dragon Sample in Radeon ProRender&lt;br /&gt;
* Blender rendering has issues with this driver&lt;br /&gt;
* Indigo-Bench hangs system on 2nd scene render&lt;br /&gt;
* Sometimes failures are observed with the latest version of FireRender&lt;br /&gt;
* No OpenCL support for RX550 based cards. &lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
* [http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-GPU-PRO-Linux-Beta-Driver%E2%80%93Release-Notes.aspx Release Notes]&lt;br /&gt;
* [https://www2.ati.com/drivers/linux/rhel7/amdgpu-pro-17.30-465504.tar.xz AMDGPU-Pro Driver Version 17.30 for RHEL 7.3/CentOS 7.3]&lt;br /&gt;
* [https://www2.ati.com/drivers/linux/rhel6/amdgpu-pro-17.30-465504.tar.xz AMDGPU-Pro Driver Version 17.30 for RHEL/CentOS 6.9]&lt;br /&gt;
* [https://www2.ati.com/drivers/linux/ubuntu/amdgpu-pro-17.30-465504.tar.xz AMDGPU-Pro Driver Version 17.30 for Ubuntu 16.04.2]&lt;br /&gt;
* [https://www2.ati.com/drivers/linux/sled-sles/amdgpu-pro-17.30-465504.tar.xz AMDGPU-Pro Driver Version 17.30 for SLED/SLES 12 SP2]&lt;br /&gt;
&lt;br /&gt;
[[Category:AMDGPU-PRO Releases]]&lt;/div&gt;</summary>
		<author><name>24.84.37.19</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10466</id>
		<title>Ubuntu Saucy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10466"/>
		<updated>2014-04-27T02:09:30Z</updated>

		<summary type="html">&lt;p&gt;24.84.213.185: added link wiki document with instructions with working URLs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; __TOC__&lt;br /&gt;
&lt;br /&gt;
= The Options =&lt;br /&gt;
Users with ATI cards have the following driver options:&lt;br /&gt;
* &#039;&#039;&#039;vesa&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;ati&#039;&#039;&#039; - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). &lt;br /&gt;
* &#039;&#039;&#039;radeon&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;Catalyst (a.k.a fglrx)&#039;&#039;&#039; a proprietary &amp;quot;blob&amp;quot; (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. You may want to use this driver for longer battery life on a laptop or for more demanding 3D applications.&lt;br /&gt;
&lt;br /&gt;
= Updated Open Source Driver PPA&#039;s =&lt;br /&gt;
* &#039;&#039;&#039;&amp;quot;Ubuntu-X&amp;quot;&#039;&#039;&#039; : 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&lt;br /&gt;
* &#039;&#039;&#039;Xorg-edgers&#039;&#039;&#039;: 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&lt;br /&gt;
&lt;br /&gt;
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =&lt;br /&gt;
&lt;br /&gt;
{| WIDTH=&amp;quot;650&amp;quot; cellpadding=0 cellspacing=0 style=&amp;quot;background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;&amp;quot; &lt;br /&gt;
| style=&amp;quot;background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;&amp;quot; | &amp;lt;font size=&amp;quot;-1&amp;quot;&amp;gt;&#039;&#039;&#039;ATTENTION RADEON USERS&#039;&#039;&#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
|- &lt;br /&gt;
| &amp;lt;br /&amp;gt;*PLEASE READ FIRST!&lt;br /&gt;
&#039;&#039;&#039;Which Radeon cards are no longer supported by ATI&#039;s Catalyst?&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300&#039;&#039;&#039;&lt;br /&gt;
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.&lt;br /&gt;
NOTE: If you enter your card information on AMD/ATI&#039;s driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn&#039;t support X servers past 1.5, and it will not work with Precise (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 &#039;Removing the Driver&#039; section to restore the default/pre-installed drivers.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI RadeonHD 2x00 - 4xx0 cards&#039;&#039;&#039;&lt;br /&gt;
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).&lt;br /&gt;
This can be done really easily and automaticly (downgrading &amp;amp; installing) by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.&lt;br /&gt;
&lt;br /&gt;
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl &#039;&#039;&#039;+ Shift&#039;&#039;&#039; + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).&lt;br /&gt;
&lt;br /&gt;
== Before you start ==&lt;br /&gt;
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources (System -&amp;gt; Administration -&amp;gt; Software Sources).&lt;br /&gt;
or Applications-&amp;gt;Ubuntu Software Center-&amp;gt;Edit-&amp;gt;Software sources-&amp;gt;Other software: check canonical partners.&lt;br /&gt;
&lt;br /&gt;
Install the prerequisite packages:&lt;br /&gt;
 sudo apt-get install cdbs dh-make dkms execstack dh-modaliases linux-headers-generic libqtgui4&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you are using the x86_64 architecture (64 bit)&#039;&#039;:&lt;br /&gt;
 sudo apt-get install lib32gcc1&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;STABLE&#039;&#039; ==&lt;br /&gt;
[http://wiki.cchtml.com/index.php/Ubuntu_Saucy_Installation_Guide#Working_Method_for_Installing_Catalyst_14-4_Manually_.28from_AMD.2FATI.27s_site.29 Instructions with working URLs. ]&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
 mkdir catalyst{{Catalystversion}} &amp;amp;&amp;amp; cd catalyst{{Catalystversion}}&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 unzip amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ./amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails (since Ubuntu/saucy is currently not supported in the rev. 13.12 release from 19 December, 2013) you can apply a patch folowing [https://gist.github.com/moldcraft/8116528 This instructions] (recommended as you create deb packages) or you can try an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation] which does NOT create deb packages and might cause some trouble when trying to uninstall.&lt;br /&gt;
&lt;br /&gt;
== Working Method for Installing Catalyst 14-4 Manually (from AMD/ATI&#039;s site)   ==&lt;br /&gt;
Above method is broken and doesn&#039;t work, this will.&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
 mkdir ~/catalyst14-4 &amp;amp;&amp;amp; cd ~/catalyst14-4&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;14-4-linux-x86-x86-64.zip&lt;br /&gt;
 unzip amd-catalyst-14-4-linux-x86-x86-64.zip&lt;br /&gt;
 chmod +x ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Install additional dependencies ===&lt;br /&gt;
 sudo apt-get install -y xorg-xserver-dev&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;BETA/EXPERIMENTAL&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
 mkdir catalyst-14.3beta1.0 &amp;amp;&amp;amp; cd catalyst-14.3beta1.0&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/beta/Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 unzip Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&lt;br /&gt;
 cd fglrx-13.35.1005&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
&lt;br /&gt;
 sudo ./amd-driver-installer-13.35.1005-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]&lt;br /&gt;
&lt;br /&gt;
== In case of failure ==&lt;br /&gt;
Remember these steps before you reboot your computer.&lt;br /&gt;
&lt;br /&gt;
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.&lt;br /&gt;
&lt;br /&gt;
 sudo startx&lt;br /&gt;
&lt;br /&gt;
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of &amp;quot;Could not stat /usr/lib64/fglrx/switchlibGL&amp;quot; which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. &lt;br /&gt;
&lt;br /&gt;
If all else fails, revert your xorg.conf and reboot.&lt;br /&gt;
&lt;br /&gt;
 sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
This should return your original display.&lt;br /&gt;
&lt;br /&gt;
== Generate a new /etc/X11/xorg.conf file ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Generic Config ===&lt;br /&gt;
This will work for most people:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
&lt;br /&gt;
=== Minimal Config ===&lt;br /&gt;
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that&#039;s not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
  Identifier &amp;quot;ATI radeon 6870&amp;quot;&lt;br /&gt;
  Driver &amp;quot;fglrx&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
=== X2/Dual GPU Cards ===&lt;br /&gt;
If you have an X2 card (e.g. 5970), use... &#039;&#039;&#039;!!Do not use for two separate cards in crossfire!!&#039;&#039;&#039;&lt;br /&gt;
 sudo amdconfig --initial -f --adapter&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;all&lt;br /&gt;
&lt;br /&gt;
=== Dual/Multi Monitors ===&lt;br /&gt;
If you have a dual monitor display (also known as &amp;quot;Big Desktop&amp;quot;), use:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
 sudo amdconfig --set-pcs-str&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;&amp;quot;DDX,EnableRandR12,FALSE&amp;quot;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Force use of the new xorg.conf &#039;&#039;(if necessary)&#039;&#039;==&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test your installation ==&lt;br /&gt;
NOTE: if you don&#039;t reboot first, fglrxinfo gives an error message.&lt;br /&gt;
Reboot the computer and type&lt;br /&gt;
 fglrxinfo&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)&lt;br /&gt;
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and &lt;br /&gt;
Catalyst version you are using.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Now, try:&lt;br /&gt;
 fgl_glxgears&lt;br /&gt;
If you experience issues or a hang, you may need to disable fast TLS.&lt;br /&gt;
 sudo amdconfig --tls=0&lt;br /&gt;
&lt;br /&gt;
=== Just in case ===&lt;br /&gt;
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&#039;t work.&lt;br /&gt;
&lt;br /&gt;
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b&lt;br /&gt;
&lt;br /&gt;
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: &amp;quot;Raising Skinny Elephants Is Never Utterly Boring&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
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: &amp;quot;BUSIER&amp;quot; or remembering a phrase: &amp;quot;Restart Even If System Utterly Broken&amp;quot;. This would also safely shutdown the system.&lt;br /&gt;
&lt;br /&gt;
= Hardware Video Decode Acceleration (EXPERIMENTAL) =&lt;br /&gt;
&lt;br /&gt;
== Using XBMC player (XvBA) ==&lt;br /&gt;
&lt;br /&gt;
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu&#039;s repositories. To install the XvBA-enabled version of xbmc:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-add-repository ppa:wsnipex/xbmc-xvba&lt;br /&gt;
 sudo apt-get update&lt;br /&gt;
 sudo apt-get install xbmc&lt;br /&gt;
&lt;br /&gt;
NOTE: deprecated as of october 2013. Moved to ppa:wsnipex/xbmc-fernetmenta-master&lt;br /&gt;
&lt;br /&gt;
== Using the xvba-va driver (VA-API) ==&lt;br /&gt;
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.&lt;br /&gt;
&lt;br /&gt;
This is confirmed to work for newer RadeonHD GPU&#039;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&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install xvba-va-driver&lt;br /&gt;
&lt;br /&gt;
A good player the utilizes va-api is VLC. You can enable va-api in Tools -&amp;gt; Preferences -&amp;gt; Input and Codecs. Check the box named &amp;quot;Use GPU accelerated decoding&amp;quot; and then restart VLC.&lt;br /&gt;
&lt;br /&gt;
=== Test the xvba-va driver (VA-API) ===&lt;br /&gt;
The tool &#039;&#039;&amp;quot;vainfo&amp;quot;&#039;&#039; allows you to test the proper functioning of the xvba-va driver.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libva-glx1 libva-x11-1 vainfo&lt;br /&gt;
 vainfo&lt;br /&gt;
&lt;br /&gt;
vainfo should return something like the following (and no errors):&lt;br /&gt;
      libva: libva version 0.32.0&lt;br /&gt;
      Xlib:  extension &amp;quot;XFree86-DRI&amp;quot; missing on display &amp;quot;:0.0&amp;quot;.&lt;br /&gt;
      libva: va_getDriverName() returns 0&lt;br /&gt;
      libva: Trying to open /usr/lib/dri/fglrx_drv_video.so&lt;br /&gt;
      libva: va_openDriver() returns 0&lt;br /&gt;
      vainfo: VA API version: 0.32&lt;br /&gt;
      vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8&lt;br /&gt;
      vainfo: Supported profile and entrypoints&lt;br /&gt;
      VAProfileH264High               :	VAEntrypointVLD&lt;br /&gt;
      VAProfileVC1Advanced            :	VAEntrypointVLD&lt;br /&gt;
&lt;br /&gt;
If vainfo returns an error, you may need to create a symlink:&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so  #for 64-bit&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so  #for 32-bit&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
There is possibility to enable &amp;gt; H.264 Level 5.1 decoding in the driver which &amp;quot;has been in the driver for some time but not enabled by default&amp;quot;. This only applies for pre-12.11 beta releases of the drivers. Since 12.11 beta the setting is enabled by default &amp;lt;ref&amp;gt;Kano, Phoronix,[http://phoronix.com/forums/showthread.php?74703-AMD-Catalyst-12-11-Beta-Linux-Driver-Released&amp;amp;p=293310#post293310 AMD Catalyst 12.11 Beta Linux Driver Released]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig --set-pcs-u32=MCIL,HWUVD_H264Level51Support,1&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 sudo service lightdm stop&lt;br /&gt;
 sudo cp -p  /etc/ati/amdpcsdb  /etc/ati/amdpcsdb.bak&lt;br /&gt;
 sudo sed -i &#039;/UvdEnabled=V1/ a HWUVD_H264Level51Support=V1&#039; /etc/ati/amdpcsdb&lt;br /&gt;
 sudo reboot&lt;br /&gt;
&lt;br /&gt;
=Updating Catalyst/fglrx=&lt;br /&gt;
&lt;br /&gt;
DO NOT try to install a new version over an old one. Follow the &#039;Removing Catalyst/fglrx&#039; section below to remove your existing driver, and then you can start at &#039;Downloading the latest Catalyst&#039; to install the new one.&lt;br /&gt;
&lt;br /&gt;
=Removing Catalyst/fglrx=&lt;br /&gt;
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.&lt;br /&gt;
 sudo sh /usr/share/ati/fglrx-uninstall.sh&lt;br /&gt;
 sudo apt-get remove --purge fglrx*&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
 sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon&lt;br /&gt;
 sudo apt-get install xserver-xorg-video-ati&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup&lt;br /&gt;
 sudo rm -f /etc/ati&lt;br /&gt;
&lt;br /&gt;
If you receive&lt;br /&gt;
&lt;br /&gt;
 $ E: Internal Error, No file name for libgl1-mesa-dri&lt;br /&gt;
&lt;br /&gt;
Change the third command above to:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core&lt;br /&gt;
&lt;br /&gt;
= Issues =&lt;br /&gt;
&lt;br /&gt;
== Video Tearing ==&lt;br /&gt;
&lt;br /&gt;
AMD/ATI claims that the &amp;quot;Tear Free Video&amp;quot; option is enabled by default, but that wasn&#039;t the case with Catalyst 12-3 installed on Kubuntu 12.04.&lt;br /&gt;
If you&#039;re having issues with tearing, make sure that &amp;quot;Tear Free Video&amp;quot; is on. You can find this option in the Catalyst Control Center under &#039;Display Options&#039; or you can use the following command:&lt;br /&gt;
 sudo amdconfig --sync-video=on&lt;br /&gt;
The option will not take effect until you restart X (i.e. log out).&lt;br /&gt;
&lt;br /&gt;
If you&#039;re using compositing, you should also make sure that vsync is enabled in the compositor&#039;s settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.&lt;br /&gt;
&lt;br /&gt;
=== kwin === &lt;br /&gt;
You can enable vsync for kwin in System Settings -&amp;gt; Desktop Effects -&amp;gt; Advanced tab&lt;br /&gt;
&lt;br /&gt;
=== Compiz (Unity/GNOME-Shell) ===&lt;br /&gt;
TODO: See if there&#039;s a friendlier way to make sure vsync is enabled without installing ccsm.&lt;br /&gt;
&lt;br /&gt;
Install the compiz settings manager: &lt;br /&gt;
 sudo apt-get install compizconfig-settings-manager&lt;br /&gt;
 ccsm&lt;br /&gt;
&lt;br /&gt;
The &#039;Sync to Vblank&#039; is found in the &#039;OpenGL&#039; subsection of the &#039;General&#039; group&lt;br /&gt;
&lt;br /&gt;
== Hybrid Graphics and Catalyst==&lt;br /&gt;
&lt;br /&gt;
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU&#039;s. Newer systems (those with PowerXpress &amp;gt;= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU&#039;s, and systems with older ATI GPU&#039;s have a mux, but don&#039;t quote that.&lt;br /&gt;
&lt;br /&gt;
=== ATI/ATI Hybrids ===&lt;br /&gt;
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it&#039;s not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig&#039;s PowerXpress options to switch back and forth between the integrated and discrete cards, like so:&lt;br /&gt;
&lt;br /&gt;
 amdconfig --pxl            # List current activated GPU&lt;br /&gt;
 sudo amdconfig --px-dgpu   # Activate discrete GPU (High-Performance mode), must re-start X to take effect&lt;br /&gt;
 sudo amdconfig --px-igpu   # Activate integrated GPU (Power-Saving mode), must re-start X to take effect&lt;br /&gt;
&lt;br /&gt;
After switching, one would log out and back in to restart X.&lt;br /&gt;
&lt;br /&gt;
=== Intel/ATI Hybrids ===&lt;br /&gt;
&lt;br /&gt;
By using the officially provided drivers, there are three problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers that gives an error related to allocation of resources in Xorg log file.&lt;br /&gt;
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)&lt;br /&gt;
&lt;br /&gt;
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration. &lt;br /&gt;
&lt;br /&gt;
If however you suffer from the problem related to intel driver not able to allocate resources, you need to install the older intel driver 2.20.2-1ubuntu1 which can be found at https://launchpad.net/ubuntu/quantal/+source/xserver-xorg-video-intel&lt;br /&gt;
&lt;br /&gt;
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )&lt;br /&gt;
&lt;br /&gt;
A workaround for now is to use the discrete GPU (ATI)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ubuntuforums.org/showthread.php?t=1930450&amp;amp;page=82&amp;amp;p=12755069#post12755069 This post] got both the integrated (Intel 3rd Gen Core processor Graphics Controller) and discrete (Radeon HD 7670M) to work on Ubuntu 13.04 x64.&lt;br /&gt;
&lt;br /&gt;
== Build Fails and Log Shows &amp;quot;mixed implicit and normal rules.  Stop.&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
If the installation fails and you find the above message in /var/lib/dkms/fglrx/&amp;lt;version_number&amp;gt;/build/make.log, it may be because you&#039;re using a pentium-build wrapper around gcc. See what the following ls command returns:&lt;br /&gt;
 ls -la /usr/bin/gcc&lt;br /&gt;
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.8 in Ubuntu Saucy). This should allow you to install fglrx:&lt;br /&gt;
 sudo ln -sf /usr/bin/gcc-4.8 /usr/bin/gcc&lt;br /&gt;
When you&#039;re finished installing the driver, return the gcc link to its original value:&lt;br /&gt;
 sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc&lt;br /&gt;
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot; (on 64-bit systems) ==&lt;br /&gt;
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get -f install&lt;br /&gt;
&lt;br /&gt;
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
 sudo dpkg -i --force-overwrite fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Problems Starting Xserver ==&lt;br /&gt;
&lt;br /&gt;
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.&lt;br /&gt;
&lt;br /&gt;
You can disable the xorg.conf with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled&lt;br /&gt;
&lt;br /&gt;
Reboot and check to see if things work now.&lt;br /&gt;
&lt;br /&gt;
You can reinstate the file with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
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 -&lt;br /&gt;
&lt;br /&gt;
 start on filesystem&lt;br /&gt;
&lt;br /&gt;
 script&lt;br /&gt;
	chmod 0666 /dev/null&lt;br /&gt;
	chmod 0666 /lib/udev/devices/null&lt;br /&gt;
 end script&lt;br /&gt;
&lt;br /&gt;
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It&#039;s worth noting that I had to disable TLS  (amdconfig --tls=0) to get things to stay stable!&lt;br /&gt;
&lt;br /&gt;
If you&#039;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:&lt;br /&gt;
 sudo amdconfig --acpi-services=off&lt;br /&gt;
If this method works, you should consider checking your system vendor&#039;s BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver&#039;s ACPI services.&lt;br /&gt;
&lt;br /&gt;
== Unsupported Hardware Watermark ==&lt;br /&gt;
This can happen if your card&#039;s PCI ID wasn&#039;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&#039;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. &lt;br /&gt;
&lt;br /&gt;
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD&#039;s signature file has a proper signature:&lt;br /&gt;
&lt;br /&gt;
 sudo nano /etc/ati/signature&lt;br /&gt;
&lt;br /&gt;
If the file only contains the word &#039;&#039;UNSIGNED&#039;&#039;, replace the line with:&lt;br /&gt;
 9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc&lt;br /&gt;
&lt;br /&gt;
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you&#039;re running:&lt;br /&gt;
&lt;br /&gt;
 cd ~/; mkdir catalyst12.10; cd catalyst12.10/&lt;br /&gt;
 wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run&lt;br /&gt;
 ./amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo mv /etc/ati/control ~/control.bak&lt;br /&gt;
 sudo cp driver/common/etc/ati/control /etc/ati&lt;br /&gt;
&lt;br /&gt;
==Poor battery life (atieventsd not starting and/or not authenticating)==&lt;br /&gt;
&lt;br /&gt;
The atieventsd daemon is a daemon that monitors various acpi events (it does this by connecting with the acpid daemon), such as a laptop lid close, or an AC connect/disconnect, presumably to let the GPU know for reasons of power saving. See the [http://manpages.ubuntu.com/manpages/hardy/en/man8/atieventsd.8.html man page] for more info.&lt;br /&gt;
On my system, `Ubuntu 13.10`, and with the latest drivers from Catalyst, 13.12, the daemon installs itself at `/etc/alternatives/x86_64-linux-gnu_atieventsd` with a symlink to that at `/usr/bin/atieventsd`. &lt;br /&gt;
&lt;br /&gt;
The Sys-V-init script, `/etc/init.d/atieventsd` thinks the symlink is elsewhere, namely `/usr/sbin/atieventsd` (i.e. `sbin` not where it actually is, `bin`)&lt;br /&gt;
&lt;br /&gt;
So to launch successfully the `atieventsd` on startup I had to do make the change:&lt;br /&gt;
&lt;br /&gt;
     DAEMONPATH=/usr/bin/atieventsd&lt;br /&gt;
&lt;br /&gt;
Then remove/regenerate the run levels:&lt;br /&gt;
&lt;br /&gt;
    cd /etc/init.d&lt;br /&gt;
    mv atieventsd atieventsd.temp&lt;br /&gt;
    update-rc.d atieventsd remove&lt;br /&gt;
    mv atieventsd.temp atieventsd&lt;br /&gt;
    update-rc.d atieventsd defaults&lt;br /&gt;
&lt;br /&gt;
This should now at least allow the daemon to correctly start/stop. You can test with `service atieventsd start`.&lt;br /&gt;
&lt;br /&gt;
On each startup the daemon attempts to launch a script, `/etc/ati/authatieventsd.sh` (by default) , whose purpose is to grant the `atieventsd daemon` authorization access to the X server display, so it can send it various commands. &lt;br /&gt;
&lt;br /&gt;
This script is called by `atieventd` like (see `ps aux | grep atieventsd` after starting the service or booting)&lt;br /&gt;
&lt;br /&gt;
     /etc/ati/authatieventsd.sh grant :0 /tmp/atieventsdGWt098&lt;br /&gt;
&lt;br /&gt;
Here argument one (`$1`) is the action: *grant/revoke*&lt;br /&gt;
, argument two (`$2`) is the X display number (e.g `:0`), and argument three (`$3`) is the file wanting the authority. See the `xauth` [http://www.x.org/archive/X11R6.8.1/doc/xauth.1.html man page] for some more background.&lt;br /&gt;
&lt;br /&gt;
The problem is that if you look at the `/etc/ati/authatieventsd.sh` script you will see it does not support `lightdm`, you need to add the chunk of code inside the `GetServerAuthFile()` function:&lt;br /&gt;
&lt;br /&gt;
    #Check lightdm     &lt;br /&gt;
     LIGHTDM_AUTH_FILE=/var/run/lightdm/root/$1&lt;br /&gt;
     if [ -e $LIGHTDM_AUTH_FILE ]; then&lt;br /&gt;
         SERVER_AUTH_FILE=$LIGHTDM_AUTH_FILE&lt;br /&gt;
         DISP_SEARCH_STRING=&amp;quot;unix$1&amp;quot;&lt;br /&gt;
         return 0&lt;br /&gt;
     fi&lt;br /&gt;
&lt;br /&gt;
to allow it find the correct server authentication file. Save this and you should&lt;br /&gt;
see a file in the `/tmp` directory of the form `atieventsdGWt098`, the next time the `atieventd` is stopped/start (or next reboot), and if you do&lt;br /&gt;
&lt;br /&gt;
    xauth -f /tmp/atievntX.Dh1AJV list&lt;br /&gt;
&lt;br /&gt;
you should get something like&lt;br /&gt;
&lt;br /&gt;
    yourHostname/unix:0  MIT-MAGIC-COOKIE-1  98deg034234kkn34234mmm3242&lt;br /&gt;
&lt;br /&gt;
Showing that the daemon has indeed been granted authority. &lt;br /&gt;
&lt;br /&gt;
You can also look at syslog, if you add the `--debug` option to `/etc/init.d/atieventsd` init file DAEMONOPTS options (regen run levels), and you should see everything is now working correctly, and the daemon is responding to events such as unplugging the AC and lid closes. For example:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: ac_adapter AC 00000080 00000000&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: processor CPU0 00000081 00000000&lt;br /&gt;
    processor CPU1 00000081 00000000&lt;br /&gt;
    processor CPU2 00000081 00000000&lt;br /&gt;
    processor CPU3 00000081 00000000&lt;br /&gt;
&lt;br /&gt;
Maybe this will help extend battery life.&lt;br /&gt;
&lt;br /&gt;
== Hang at logout ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: &lt;br /&gt;
(assuming that the installer is in the directory we used to install)&lt;br /&gt;
&lt;br /&gt;
 cd ~/catalyst{{Catalystversion}}&lt;br /&gt;
 sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh&lt;br /&gt;
 sudo chmod +x /etc/ati/authatieventsd.sh&lt;br /&gt;
&lt;br /&gt;
This problem can be fixed permanently with:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
 sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
 sudo /usr/sbin/update-rc.d -f atieventsd remove&lt;br /&gt;
&lt;br /&gt;
You&#039;ll have to restart for this to take effect.&lt;br /&gt;
&lt;br /&gt;
== Can&#039;t remove fglrx with dpkg (diversion issue) ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&amp;lt;pre&amp;gt;dpkg-divert: mismatch on divert-to&lt;br /&gt;
  when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx&#039;&lt;br /&gt;
  found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
then:&lt;br /&gt;
 sudo dpkg-divert --remove /usr/lib/libGL.so.1.2&lt;br /&gt;
&lt;br /&gt;
== This module/version combo is already installed ==&lt;br /&gt;
&lt;br /&gt;
If you get this error-message, simply uninstall the previous version before installing the new one with:&lt;br /&gt;
 sudo dkms remove -m fglrx --all&lt;br /&gt;
&lt;br /&gt;
== New kernel installed? ==&lt;br /&gt;
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:&lt;br /&gt;
 sudo dkms build -m fglrx -k `uname -r`&lt;br /&gt;
 sudo dkms install -m fglrx -k `uname -r`&lt;br /&gt;
&lt;br /&gt;
if amdcccle doesn&#039;t work and says Identifier is not a valid word. Use lower case letter in xorg.conf&lt;br /&gt;
 &lt;br /&gt;
or specify all the correct parameters. For example:&lt;br /&gt;
 sudo dkms build -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
 sudo dkms install -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
&lt;br /&gt;
== amdconfig not found after installation ==&lt;br /&gt;
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&#039;s website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:&lt;br /&gt;
&amp;lt;pre&amp;gt;amdconfig: command not found&amp;lt;/pre&amp;gt;&lt;br /&gt;
After booting you might receive X error &#039;(EE) Failed to load module &amp;quot;fglrx&amp;quot; (module does not exist, 0)&#039;. These do not necessarily indicate that the installation has failed completely. On command line, do&lt;br /&gt;
 ls /usr/lib/fglrx/bin&lt;br /&gt;
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 &amp;quot;update-alternatives&amp;quot; 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&lt;br /&gt;
 update-alternatives --get-selections | grep gl_conf&lt;br /&gt;
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 &lt;br /&gt;
 sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf&lt;br /&gt;
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:&lt;br /&gt;
 sudo update-alternatives --auto gl_conf&lt;br /&gt;
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;update-alternatives: error&amp;quot; during install ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;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&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can be easily solved by creating directory &amp;quot;drivers&amp;quot; under /usr/lib/xorg/modules/&lt;br /&gt;
 sudo mkdir /usr/lib/xorg/modules/drivers&lt;br /&gt;
&lt;br /&gt;
== &#039;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&#039; during deb generation ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can happen when your /tmp folder is mounted with the option &amp;quot;noexec&amp;quot;. The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.&lt;br /&gt;
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]&lt;br /&gt;
&lt;br /&gt;
== Black screen after uninstalling old amd drivers ==&lt;br /&gt;
Start you computer in recovery mode and exit to root shell.&lt;br /&gt;
Remount your partitions in rw mode:&lt;br /&gt;
 mount -rw -o remount /&lt;br /&gt;
 ...&lt;br /&gt;
Go to your download directory and proceed with building and installing the drivers in recovery mode.&lt;br /&gt;
All should be fine after a reboot.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>24.84.213.185</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10465</id>
		<title>Ubuntu Saucy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10465"/>
		<updated>2014-04-27T02:03:48Z</updated>

		<summary type="html">&lt;p&gt;24.84.213.185: /* Working Method for Installing Catalyst 14-4 Manually */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; __TOC__&lt;br /&gt;
&lt;br /&gt;
= The Options =&lt;br /&gt;
Users with ATI cards have the following driver options:&lt;br /&gt;
* &#039;&#039;&#039;vesa&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;ati&#039;&#039;&#039; - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). &lt;br /&gt;
* &#039;&#039;&#039;radeon&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;Catalyst (a.k.a fglrx)&#039;&#039;&#039; a proprietary &amp;quot;blob&amp;quot; (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. You may want to use this driver for longer battery life on a laptop or for more demanding 3D applications.&lt;br /&gt;
&lt;br /&gt;
= Updated Open Source Driver PPA&#039;s =&lt;br /&gt;
* &#039;&#039;&#039;&amp;quot;Ubuntu-X&amp;quot;&#039;&#039;&#039; : 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&lt;br /&gt;
* &#039;&#039;&#039;Xorg-edgers&#039;&#039;&#039;: 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&lt;br /&gt;
&lt;br /&gt;
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =&lt;br /&gt;
&lt;br /&gt;
{| WIDTH=&amp;quot;650&amp;quot; cellpadding=0 cellspacing=0 style=&amp;quot;background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;&amp;quot; &lt;br /&gt;
| style=&amp;quot;background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;&amp;quot; | &amp;lt;font size=&amp;quot;-1&amp;quot;&amp;gt;&#039;&#039;&#039;ATTENTION RADEON USERS&#039;&#039;&#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
|- &lt;br /&gt;
| &amp;lt;br /&amp;gt;*PLEASE READ FIRST!&lt;br /&gt;
&#039;&#039;&#039;Which Radeon cards are no longer supported by ATI&#039;s Catalyst?&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300&#039;&#039;&#039;&lt;br /&gt;
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.&lt;br /&gt;
NOTE: If you enter your card information on AMD/ATI&#039;s driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn&#039;t support X servers past 1.5, and it will not work with Precise (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 &#039;Removing the Driver&#039; section to restore the default/pre-installed drivers.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI RadeonHD 2x00 - 4xx0 cards&#039;&#039;&#039;&lt;br /&gt;
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).&lt;br /&gt;
This can be done really easily and automaticly (downgrading &amp;amp; installing) by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.&lt;br /&gt;
&lt;br /&gt;
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl &#039;&#039;&#039;+ Shift&#039;&#039;&#039; + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).&lt;br /&gt;
&lt;br /&gt;
== Before you start ==&lt;br /&gt;
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources (System -&amp;gt; Administration -&amp;gt; Software Sources).&lt;br /&gt;
or Applications-&amp;gt;Ubuntu Software Center-&amp;gt;Edit-&amp;gt;Software sources-&amp;gt;Other software: check canonical partners.&lt;br /&gt;
&lt;br /&gt;
Install the prerequisite packages:&lt;br /&gt;
 sudo apt-get install cdbs dh-make dkms execstack dh-modaliases linux-headers-generic libqtgui4&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you are using the x86_64 architecture (64 bit)&#039;&#039;:&lt;br /&gt;
 sudo apt-get install lib32gcc1&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;STABLE&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
 mkdir catalyst{{Catalystversion}} &amp;amp;&amp;amp; cd catalyst{{Catalystversion}}&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 unzip amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ./amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails (since Ubuntu/saucy is currently not supported in the rev. 13.12 release from 19 December, 2013) you can apply a patch folowing [https://gist.github.com/moldcraft/8116528 This instructions] (recommended as you create deb packages) or you can try an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation] which does NOT create deb packages and might cause some trouble when trying to uninstall.&lt;br /&gt;
&lt;br /&gt;
== Working Method for Installing Catalyst 14-4 Manually (from AMD/ATI&#039;s site)   ==&lt;br /&gt;
Above method is broken and doesn&#039;t work, this will.&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
 mkdir ~/catalyst14-4 &amp;amp;&amp;amp; cd ~/catalyst14-4&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;14-4-linux-x86-x86-64.zip&lt;br /&gt;
 unzip amd-catalyst-14-4-linux-x86-x86-64.zip&lt;br /&gt;
 chmod +x ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Install additional dependencies ===&lt;br /&gt;
 sudo apt-get install -y xorg-xserver-dev&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;BETA/EXPERIMENTAL&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
 mkdir catalyst-14.3beta1.0 &amp;amp;&amp;amp; cd catalyst-14.3beta1.0&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/beta/Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 unzip Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&lt;br /&gt;
 cd fglrx-13.35.1005&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
&lt;br /&gt;
 sudo ./amd-driver-installer-13.35.1005-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]&lt;br /&gt;
&lt;br /&gt;
== In case of failure ==&lt;br /&gt;
Remember these steps before you reboot your computer.&lt;br /&gt;
&lt;br /&gt;
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.&lt;br /&gt;
&lt;br /&gt;
 sudo startx&lt;br /&gt;
&lt;br /&gt;
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of &amp;quot;Could not stat /usr/lib64/fglrx/switchlibGL&amp;quot; which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. &lt;br /&gt;
&lt;br /&gt;
If all else fails, revert your xorg.conf and reboot.&lt;br /&gt;
&lt;br /&gt;
 sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
This should return your original display.&lt;br /&gt;
&lt;br /&gt;
== Generate a new /etc/X11/xorg.conf file ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Generic Config ===&lt;br /&gt;
This will work for most people:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
&lt;br /&gt;
=== Minimal Config ===&lt;br /&gt;
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that&#039;s not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
  Identifier &amp;quot;ATI radeon 6870&amp;quot;&lt;br /&gt;
  Driver &amp;quot;fglrx&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
=== X2/Dual GPU Cards ===&lt;br /&gt;
If you have an X2 card (e.g. 5970), use... &#039;&#039;&#039;!!Do not use for two separate cards in crossfire!!&#039;&#039;&#039;&lt;br /&gt;
 sudo amdconfig --initial -f --adapter&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;all&lt;br /&gt;
&lt;br /&gt;
=== Dual/Multi Monitors ===&lt;br /&gt;
If you have a dual monitor display (also known as &amp;quot;Big Desktop&amp;quot;), use:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
 sudo amdconfig --set-pcs-str&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;&amp;quot;DDX,EnableRandR12,FALSE&amp;quot;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Force use of the new xorg.conf &#039;&#039;(if necessary)&#039;&#039;==&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test your installation ==&lt;br /&gt;
NOTE: if you don&#039;t reboot first, fglrxinfo gives an error message.&lt;br /&gt;
Reboot the computer and type&lt;br /&gt;
 fglrxinfo&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)&lt;br /&gt;
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and &lt;br /&gt;
Catalyst version you are using.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Now, try:&lt;br /&gt;
 fgl_glxgears&lt;br /&gt;
If you experience issues or a hang, you may need to disable fast TLS.&lt;br /&gt;
 sudo amdconfig --tls=0&lt;br /&gt;
&lt;br /&gt;
=== Just in case ===&lt;br /&gt;
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&#039;t work.&lt;br /&gt;
&lt;br /&gt;
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b&lt;br /&gt;
&lt;br /&gt;
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: &amp;quot;Raising Skinny Elephants Is Never Utterly Boring&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
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: &amp;quot;BUSIER&amp;quot; or remembering a phrase: &amp;quot;Restart Even If System Utterly Broken&amp;quot;. This would also safely shutdown the system.&lt;br /&gt;
&lt;br /&gt;
= Hardware Video Decode Acceleration (EXPERIMENTAL) =&lt;br /&gt;
&lt;br /&gt;
== Using XBMC player (XvBA) ==&lt;br /&gt;
&lt;br /&gt;
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu&#039;s repositories. To install the XvBA-enabled version of xbmc:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-add-repository ppa:wsnipex/xbmc-xvba&lt;br /&gt;
 sudo apt-get update&lt;br /&gt;
 sudo apt-get install xbmc&lt;br /&gt;
&lt;br /&gt;
NOTE: deprecated as of october 2013. Moved to ppa:wsnipex/xbmc-fernetmenta-master&lt;br /&gt;
&lt;br /&gt;
== Using the xvba-va driver (VA-API) ==&lt;br /&gt;
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.&lt;br /&gt;
&lt;br /&gt;
This is confirmed to work for newer RadeonHD GPU&#039;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&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install xvba-va-driver&lt;br /&gt;
&lt;br /&gt;
A good player the utilizes va-api is VLC. You can enable va-api in Tools -&amp;gt; Preferences -&amp;gt; Input and Codecs. Check the box named &amp;quot;Use GPU accelerated decoding&amp;quot; and then restart VLC.&lt;br /&gt;
&lt;br /&gt;
=== Test the xvba-va driver (VA-API) ===&lt;br /&gt;
The tool &#039;&#039;&amp;quot;vainfo&amp;quot;&#039;&#039; allows you to test the proper functioning of the xvba-va driver.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libva-glx1 libva-x11-1 vainfo&lt;br /&gt;
 vainfo&lt;br /&gt;
&lt;br /&gt;
vainfo should return something like the following (and no errors):&lt;br /&gt;
      libva: libva version 0.32.0&lt;br /&gt;
      Xlib:  extension &amp;quot;XFree86-DRI&amp;quot; missing on display &amp;quot;:0.0&amp;quot;.&lt;br /&gt;
      libva: va_getDriverName() returns 0&lt;br /&gt;
      libva: Trying to open /usr/lib/dri/fglrx_drv_video.so&lt;br /&gt;
      libva: va_openDriver() returns 0&lt;br /&gt;
      vainfo: VA API version: 0.32&lt;br /&gt;
      vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8&lt;br /&gt;
      vainfo: Supported profile and entrypoints&lt;br /&gt;
      VAProfileH264High               :	VAEntrypointVLD&lt;br /&gt;
      VAProfileVC1Advanced            :	VAEntrypointVLD&lt;br /&gt;
&lt;br /&gt;
If vainfo returns an error, you may need to create a symlink:&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so  #for 64-bit&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so  #for 32-bit&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
There is possibility to enable &amp;gt; H.264 Level 5.1 decoding in the driver which &amp;quot;has been in the driver for some time but not enabled by default&amp;quot;. This only applies for pre-12.11 beta releases of the drivers. Since 12.11 beta the setting is enabled by default &amp;lt;ref&amp;gt;Kano, Phoronix,[http://phoronix.com/forums/showthread.php?74703-AMD-Catalyst-12-11-Beta-Linux-Driver-Released&amp;amp;p=293310#post293310 AMD Catalyst 12.11 Beta Linux Driver Released]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig --set-pcs-u32=MCIL,HWUVD_H264Level51Support,1&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 sudo service lightdm stop&lt;br /&gt;
 sudo cp -p  /etc/ati/amdpcsdb  /etc/ati/amdpcsdb.bak&lt;br /&gt;
 sudo sed -i &#039;/UvdEnabled=V1/ a HWUVD_H264Level51Support=V1&#039; /etc/ati/amdpcsdb&lt;br /&gt;
 sudo reboot&lt;br /&gt;
&lt;br /&gt;
=Updating Catalyst/fglrx=&lt;br /&gt;
&lt;br /&gt;
DO NOT try to install a new version over an old one. Follow the &#039;Removing Catalyst/fglrx&#039; section below to remove your existing driver, and then you can start at &#039;Downloading the latest Catalyst&#039; to install the new one.&lt;br /&gt;
&lt;br /&gt;
=Removing Catalyst/fglrx=&lt;br /&gt;
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.&lt;br /&gt;
 sudo sh /usr/share/ati/fglrx-uninstall.sh&lt;br /&gt;
 sudo apt-get remove --purge fglrx*&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
 sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon&lt;br /&gt;
 sudo apt-get install xserver-xorg-video-ati&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup&lt;br /&gt;
 sudo rm -f /etc/ati&lt;br /&gt;
&lt;br /&gt;
If you receive&lt;br /&gt;
&lt;br /&gt;
 $ E: Internal Error, No file name for libgl1-mesa-dri&lt;br /&gt;
&lt;br /&gt;
Change the third command above to:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core&lt;br /&gt;
&lt;br /&gt;
= Issues =&lt;br /&gt;
&lt;br /&gt;
== Video Tearing ==&lt;br /&gt;
&lt;br /&gt;
AMD/ATI claims that the &amp;quot;Tear Free Video&amp;quot; option is enabled by default, but that wasn&#039;t the case with Catalyst 12-3 installed on Kubuntu 12.04.&lt;br /&gt;
If you&#039;re having issues with tearing, make sure that &amp;quot;Tear Free Video&amp;quot; is on. You can find this option in the Catalyst Control Center under &#039;Display Options&#039; or you can use the following command:&lt;br /&gt;
 sudo amdconfig --sync-video=on&lt;br /&gt;
The option will not take effect until you restart X (i.e. log out).&lt;br /&gt;
&lt;br /&gt;
If you&#039;re using compositing, you should also make sure that vsync is enabled in the compositor&#039;s settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.&lt;br /&gt;
&lt;br /&gt;
=== kwin === &lt;br /&gt;
You can enable vsync for kwin in System Settings -&amp;gt; Desktop Effects -&amp;gt; Advanced tab&lt;br /&gt;
&lt;br /&gt;
=== Compiz (Unity/GNOME-Shell) ===&lt;br /&gt;
TODO: See if there&#039;s a friendlier way to make sure vsync is enabled without installing ccsm.&lt;br /&gt;
&lt;br /&gt;
Install the compiz settings manager: &lt;br /&gt;
 sudo apt-get install compizconfig-settings-manager&lt;br /&gt;
 ccsm&lt;br /&gt;
&lt;br /&gt;
The &#039;Sync to Vblank&#039; is found in the &#039;OpenGL&#039; subsection of the &#039;General&#039; group&lt;br /&gt;
&lt;br /&gt;
== Hybrid Graphics and Catalyst==&lt;br /&gt;
&lt;br /&gt;
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU&#039;s. Newer systems (those with PowerXpress &amp;gt;= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU&#039;s, and systems with older ATI GPU&#039;s have a mux, but don&#039;t quote that.&lt;br /&gt;
&lt;br /&gt;
=== ATI/ATI Hybrids ===&lt;br /&gt;
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it&#039;s not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig&#039;s PowerXpress options to switch back and forth between the integrated and discrete cards, like so:&lt;br /&gt;
&lt;br /&gt;
 amdconfig --pxl            # List current activated GPU&lt;br /&gt;
 sudo amdconfig --px-dgpu   # Activate discrete GPU (High-Performance mode), must re-start X to take effect&lt;br /&gt;
 sudo amdconfig --px-igpu   # Activate integrated GPU (Power-Saving mode), must re-start X to take effect&lt;br /&gt;
&lt;br /&gt;
After switching, one would log out and back in to restart X.&lt;br /&gt;
&lt;br /&gt;
=== Intel/ATI Hybrids ===&lt;br /&gt;
&lt;br /&gt;
By using the officially provided drivers, there are three problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers that gives an error related to allocation of resources in Xorg log file.&lt;br /&gt;
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)&lt;br /&gt;
&lt;br /&gt;
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration. &lt;br /&gt;
&lt;br /&gt;
If however you suffer from the problem related to intel driver not able to allocate resources, you need to install the older intel driver 2.20.2-1ubuntu1 which can be found at https://launchpad.net/ubuntu/quantal/+source/xserver-xorg-video-intel&lt;br /&gt;
&lt;br /&gt;
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )&lt;br /&gt;
&lt;br /&gt;
A workaround for now is to use the discrete GPU (ATI)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ubuntuforums.org/showthread.php?t=1930450&amp;amp;page=82&amp;amp;p=12755069#post12755069 This post] got both the integrated (Intel 3rd Gen Core processor Graphics Controller) and discrete (Radeon HD 7670M) to work on Ubuntu 13.04 x64.&lt;br /&gt;
&lt;br /&gt;
== Build Fails and Log Shows &amp;quot;mixed implicit and normal rules.  Stop.&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
If the installation fails and you find the above message in /var/lib/dkms/fglrx/&amp;lt;version_number&amp;gt;/build/make.log, it may be because you&#039;re using a pentium-build wrapper around gcc. See what the following ls command returns:&lt;br /&gt;
 ls -la /usr/bin/gcc&lt;br /&gt;
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.8 in Ubuntu Saucy). This should allow you to install fglrx:&lt;br /&gt;
 sudo ln -sf /usr/bin/gcc-4.8 /usr/bin/gcc&lt;br /&gt;
When you&#039;re finished installing the driver, return the gcc link to its original value:&lt;br /&gt;
 sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc&lt;br /&gt;
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot; (on 64-bit systems) ==&lt;br /&gt;
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get -f install&lt;br /&gt;
&lt;br /&gt;
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
 sudo dpkg -i --force-overwrite fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Problems Starting Xserver ==&lt;br /&gt;
&lt;br /&gt;
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.&lt;br /&gt;
&lt;br /&gt;
You can disable the xorg.conf with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled&lt;br /&gt;
&lt;br /&gt;
Reboot and check to see if things work now.&lt;br /&gt;
&lt;br /&gt;
You can reinstate the file with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
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 -&lt;br /&gt;
&lt;br /&gt;
 start on filesystem&lt;br /&gt;
&lt;br /&gt;
 script&lt;br /&gt;
	chmod 0666 /dev/null&lt;br /&gt;
	chmod 0666 /lib/udev/devices/null&lt;br /&gt;
 end script&lt;br /&gt;
&lt;br /&gt;
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It&#039;s worth noting that I had to disable TLS  (amdconfig --tls=0) to get things to stay stable!&lt;br /&gt;
&lt;br /&gt;
If you&#039;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:&lt;br /&gt;
 sudo amdconfig --acpi-services=off&lt;br /&gt;
If this method works, you should consider checking your system vendor&#039;s BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver&#039;s ACPI services.&lt;br /&gt;
&lt;br /&gt;
== Unsupported Hardware Watermark ==&lt;br /&gt;
This can happen if your card&#039;s PCI ID wasn&#039;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&#039;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. &lt;br /&gt;
&lt;br /&gt;
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD&#039;s signature file has a proper signature:&lt;br /&gt;
&lt;br /&gt;
 sudo nano /etc/ati/signature&lt;br /&gt;
&lt;br /&gt;
If the file only contains the word &#039;&#039;UNSIGNED&#039;&#039;, replace the line with:&lt;br /&gt;
 9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc&lt;br /&gt;
&lt;br /&gt;
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you&#039;re running:&lt;br /&gt;
&lt;br /&gt;
 cd ~/; mkdir catalyst12.10; cd catalyst12.10/&lt;br /&gt;
 wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run&lt;br /&gt;
 ./amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo mv /etc/ati/control ~/control.bak&lt;br /&gt;
 sudo cp driver/common/etc/ati/control /etc/ati&lt;br /&gt;
&lt;br /&gt;
==Poor battery life (atieventsd not starting and/or not authenticating)==&lt;br /&gt;
&lt;br /&gt;
The atieventsd daemon is a daemon that monitors various acpi events (it does this by connecting with the acpid daemon), such as a laptop lid close, or an AC connect/disconnect, presumably to let the GPU know for reasons of power saving. See the [http://manpages.ubuntu.com/manpages/hardy/en/man8/atieventsd.8.html man page] for more info.&lt;br /&gt;
On my system, `Ubuntu 13.10`, and with the latest drivers from Catalyst, 13.12, the daemon installs itself at `/etc/alternatives/x86_64-linux-gnu_atieventsd` with a symlink to that at `/usr/bin/atieventsd`. &lt;br /&gt;
&lt;br /&gt;
The Sys-V-init script, `/etc/init.d/atieventsd` thinks the symlink is elsewhere, namely `/usr/sbin/atieventsd` (i.e. `sbin` not where it actually is, `bin`)&lt;br /&gt;
&lt;br /&gt;
So to launch successfully the `atieventsd` on startup I had to do make the change:&lt;br /&gt;
&lt;br /&gt;
     DAEMONPATH=/usr/bin/atieventsd&lt;br /&gt;
&lt;br /&gt;
Then remove/regenerate the run levels:&lt;br /&gt;
&lt;br /&gt;
    cd /etc/init.d&lt;br /&gt;
    mv atieventsd atieventsd.temp&lt;br /&gt;
    update-rc.d atieventsd remove&lt;br /&gt;
    mv atieventsd.temp atieventsd&lt;br /&gt;
    update-rc.d atieventsd defaults&lt;br /&gt;
&lt;br /&gt;
This should now at least allow the daemon to correctly start/stop. You can test with `service atieventsd start`.&lt;br /&gt;
&lt;br /&gt;
On each startup the daemon attempts to launch a script, `/etc/ati/authatieventsd.sh` (by default) , whose purpose is to grant the `atieventsd daemon` authorization access to the X server display, so it can send it various commands. &lt;br /&gt;
&lt;br /&gt;
This script is called by `atieventd` like (see `ps aux | grep atieventsd` after starting the service or booting)&lt;br /&gt;
&lt;br /&gt;
     /etc/ati/authatieventsd.sh grant :0 /tmp/atieventsdGWt098&lt;br /&gt;
&lt;br /&gt;
Here argument one (`$1`) is the action: *grant/revoke*&lt;br /&gt;
, argument two (`$2`) is the X display number (e.g `:0`), and argument three (`$3`) is the file wanting the authority. See the `xauth` [http://www.x.org/archive/X11R6.8.1/doc/xauth.1.html man page] for some more background.&lt;br /&gt;
&lt;br /&gt;
The problem is that if you look at the `/etc/ati/authatieventsd.sh` script you will see it does not support `lightdm`, you need to add the chunk of code inside the `GetServerAuthFile()` function:&lt;br /&gt;
&lt;br /&gt;
    #Check lightdm     &lt;br /&gt;
     LIGHTDM_AUTH_FILE=/var/run/lightdm/root/$1&lt;br /&gt;
     if [ -e $LIGHTDM_AUTH_FILE ]; then&lt;br /&gt;
         SERVER_AUTH_FILE=$LIGHTDM_AUTH_FILE&lt;br /&gt;
         DISP_SEARCH_STRING=&amp;quot;unix$1&amp;quot;&lt;br /&gt;
         return 0&lt;br /&gt;
     fi&lt;br /&gt;
&lt;br /&gt;
to allow it find the correct server authentication file. Save this and you should&lt;br /&gt;
see a file in the `/tmp` directory of the form `atieventsdGWt098`, the next time the `atieventd` is stopped/start (or next reboot), and if you do&lt;br /&gt;
&lt;br /&gt;
    xauth -f /tmp/atievntX.Dh1AJV list&lt;br /&gt;
&lt;br /&gt;
you should get something like&lt;br /&gt;
&lt;br /&gt;
    yourHostname/unix:0  MIT-MAGIC-COOKIE-1  98deg034234kkn34234mmm3242&lt;br /&gt;
&lt;br /&gt;
Showing that the daemon has indeed been granted authority. &lt;br /&gt;
&lt;br /&gt;
You can also look at syslog, if you add the `--debug` option to `/etc/init.d/atieventsd` init file DAEMONOPTS options (regen run levels), and you should see everything is now working correctly, and the daemon is responding to events such as unplugging the AC and lid closes. For example:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: ac_adapter AC 00000080 00000000&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: processor CPU0 00000081 00000000&lt;br /&gt;
    processor CPU1 00000081 00000000&lt;br /&gt;
    processor CPU2 00000081 00000000&lt;br /&gt;
    processor CPU3 00000081 00000000&lt;br /&gt;
&lt;br /&gt;
Maybe this will help extend battery life.&lt;br /&gt;
&lt;br /&gt;
== Hang at logout ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: &lt;br /&gt;
(assuming that the installer is in the directory we used to install)&lt;br /&gt;
&lt;br /&gt;
 cd ~/catalyst{{Catalystversion}}&lt;br /&gt;
 sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh&lt;br /&gt;
 sudo chmod +x /etc/ati/authatieventsd.sh&lt;br /&gt;
&lt;br /&gt;
This problem can be fixed permanently with:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
 sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
 sudo /usr/sbin/update-rc.d -f atieventsd remove&lt;br /&gt;
&lt;br /&gt;
You&#039;ll have to restart for this to take effect.&lt;br /&gt;
&lt;br /&gt;
== Can&#039;t remove fglrx with dpkg (diversion issue) ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&amp;lt;pre&amp;gt;dpkg-divert: mismatch on divert-to&lt;br /&gt;
  when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx&#039;&lt;br /&gt;
  found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
then:&lt;br /&gt;
 sudo dpkg-divert --remove /usr/lib/libGL.so.1.2&lt;br /&gt;
&lt;br /&gt;
== This module/version combo is already installed ==&lt;br /&gt;
&lt;br /&gt;
If you get this error-message, simply uninstall the previous version before installing the new one with:&lt;br /&gt;
 sudo dkms remove -m fglrx --all&lt;br /&gt;
&lt;br /&gt;
== New kernel installed? ==&lt;br /&gt;
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:&lt;br /&gt;
 sudo dkms build -m fglrx -k `uname -r`&lt;br /&gt;
 sudo dkms install -m fglrx -k `uname -r`&lt;br /&gt;
&lt;br /&gt;
if amdcccle doesn&#039;t work and says Identifier is not a valid word. Use lower case letter in xorg.conf&lt;br /&gt;
 &lt;br /&gt;
or specify all the correct parameters. For example:&lt;br /&gt;
 sudo dkms build -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
 sudo dkms install -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
&lt;br /&gt;
== amdconfig not found after installation ==&lt;br /&gt;
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&#039;s website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:&lt;br /&gt;
&amp;lt;pre&amp;gt;amdconfig: command not found&amp;lt;/pre&amp;gt;&lt;br /&gt;
After booting you might receive X error &#039;(EE) Failed to load module &amp;quot;fglrx&amp;quot; (module does not exist, 0)&#039;. These do not necessarily indicate that the installation has failed completely. On command line, do&lt;br /&gt;
 ls /usr/lib/fglrx/bin&lt;br /&gt;
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 &amp;quot;update-alternatives&amp;quot; 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&lt;br /&gt;
 update-alternatives --get-selections | grep gl_conf&lt;br /&gt;
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 &lt;br /&gt;
 sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf&lt;br /&gt;
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:&lt;br /&gt;
 sudo update-alternatives --auto gl_conf&lt;br /&gt;
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;update-alternatives: error&amp;quot; during install ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;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&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can be easily solved by creating directory &amp;quot;drivers&amp;quot; under /usr/lib/xorg/modules/&lt;br /&gt;
 sudo mkdir /usr/lib/xorg/modules/drivers&lt;br /&gt;
&lt;br /&gt;
== &#039;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&#039; during deb generation ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can happen when your /tmp folder is mounted with the option &amp;quot;noexec&amp;quot;. The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.&lt;br /&gt;
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]&lt;br /&gt;
&lt;br /&gt;
== Black screen after uninstalling old amd drivers ==&lt;br /&gt;
Start you computer in recovery mode and exit to root shell.&lt;br /&gt;
Remount your partitions in rw mode:&lt;br /&gt;
 mount -rw -o remount /&lt;br /&gt;
 ...&lt;br /&gt;
Go to your download directory and proceed with building and installing the drivers in recovery mode.&lt;br /&gt;
All should be fine after a reboot.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>24.84.213.185</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10464</id>
		<title>Ubuntu Saucy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10464"/>
		<updated>2014-04-27T02:02:55Z</updated>

		<summary type="html">&lt;p&gt;24.84.213.185: AMD changed their URL convention and install/download urls no longer work. It also breaks the convention the wiki was using so I added a section we working urls.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; __TOC__&lt;br /&gt;
&lt;br /&gt;
= The Options =&lt;br /&gt;
Users with ATI cards have the following driver options:&lt;br /&gt;
* &#039;&#039;&#039;vesa&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;ati&#039;&#039;&#039; - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). &lt;br /&gt;
* &#039;&#039;&#039;radeon&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;Catalyst (a.k.a fglrx)&#039;&#039;&#039; a proprietary &amp;quot;blob&amp;quot; (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. You may want to use this driver for longer battery life on a laptop or for more demanding 3D applications.&lt;br /&gt;
&lt;br /&gt;
= Updated Open Source Driver PPA&#039;s =&lt;br /&gt;
* &#039;&#039;&#039;&amp;quot;Ubuntu-X&amp;quot;&#039;&#039;&#039; : 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&lt;br /&gt;
* &#039;&#039;&#039;Xorg-edgers&#039;&#039;&#039;: 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&lt;br /&gt;
&lt;br /&gt;
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =&lt;br /&gt;
&lt;br /&gt;
{| WIDTH=&amp;quot;650&amp;quot; cellpadding=0 cellspacing=0 style=&amp;quot;background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;&amp;quot; &lt;br /&gt;
| style=&amp;quot;background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;&amp;quot; | &amp;lt;font size=&amp;quot;-1&amp;quot;&amp;gt;&#039;&#039;&#039;ATTENTION RADEON USERS&#039;&#039;&#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
|- &lt;br /&gt;
| &amp;lt;br /&amp;gt;*PLEASE READ FIRST!&lt;br /&gt;
&#039;&#039;&#039;Which Radeon cards are no longer supported by ATI&#039;s Catalyst?&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300&#039;&#039;&#039;&lt;br /&gt;
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.&lt;br /&gt;
NOTE: If you enter your card information on AMD/ATI&#039;s driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn&#039;t support X servers past 1.5, and it will not work with Precise (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 &#039;Removing the Driver&#039; section to restore the default/pre-installed drivers.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI RadeonHD 2x00 - 4xx0 cards&#039;&#039;&#039;&lt;br /&gt;
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).&lt;br /&gt;
This can be done really easily and automaticly (downgrading &amp;amp; installing) by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.&lt;br /&gt;
&lt;br /&gt;
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl &#039;&#039;&#039;+ Shift&#039;&#039;&#039; + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).&lt;br /&gt;
&lt;br /&gt;
== Before you start ==&lt;br /&gt;
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources (System -&amp;gt; Administration -&amp;gt; Software Sources).&lt;br /&gt;
or Applications-&amp;gt;Ubuntu Software Center-&amp;gt;Edit-&amp;gt;Software sources-&amp;gt;Other software: check canonical partners.&lt;br /&gt;
&lt;br /&gt;
Install the prerequisite packages:&lt;br /&gt;
 sudo apt-get install cdbs dh-make dkms execstack dh-modaliases linux-headers-generic libqtgui4&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you are using the x86_64 architecture (64 bit)&#039;&#039;:&lt;br /&gt;
 sudo apt-get install lib32gcc1&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;STABLE&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
 mkdir catalyst{{Catalystversion}} &amp;amp;&amp;amp; cd catalyst{{Catalystversion}}&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 unzip amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ./amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails (since Ubuntu/saucy is currently not supported in the rev. 13.12 release from 19 December, 2013) you can apply a patch folowing [https://gist.github.com/moldcraft/8116528 This instructions] (recommended as you create deb packages) or you can try an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation] which does NOT create deb packages and might cause some trouble when trying to uninstall.&lt;br /&gt;
&lt;br /&gt;
== Working Method for Installing Catalyst 14-4 Manually  ==&lt;br /&gt;
Above method is broken and doesn&#039;t work, this will.&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
 mkdir ~/catalyst14-4 &amp;amp;&amp;amp; cd ~/catalyst14-4&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;14-4-linux-x86-x86-64.zip&lt;br /&gt;
 unzip amd-catalyst-14-4-linux-x86-x86-64.zip&lt;br /&gt;
 chmod +x ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Install additional dependencies ===&lt;br /&gt;
 sudo apt-get install -y xorg-xserver-dev&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;BETA/EXPERIMENTAL&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
 mkdir catalyst-14.3beta1.0 &amp;amp;&amp;amp; cd catalyst-14.3beta1.0&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/beta/Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 unzip Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&lt;br /&gt;
 cd fglrx-13.35.1005&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
&lt;br /&gt;
 sudo ./amd-driver-installer-13.35.1005-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]&lt;br /&gt;
&lt;br /&gt;
== In case of failure ==&lt;br /&gt;
Remember these steps before you reboot your computer.&lt;br /&gt;
&lt;br /&gt;
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.&lt;br /&gt;
&lt;br /&gt;
 sudo startx&lt;br /&gt;
&lt;br /&gt;
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of &amp;quot;Could not stat /usr/lib64/fglrx/switchlibGL&amp;quot; which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. &lt;br /&gt;
&lt;br /&gt;
If all else fails, revert your xorg.conf and reboot.&lt;br /&gt;
&lt;br /&gt;
 sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
This should return your original display.&lt;br /&gt;
&lt;br /&gt;
== Generate a new /etc/X11/xorg.conf file ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Generic Config ===&lt;br /&gt;
This will work for most people:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
&lt;br /&gt;
=== Minimal Config ===&lt;br /&gt;
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that&#039;s not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
  Identifier &amp;quot;ATI radeon 6870&amp;quot;&lt;br /&gt;
  Driver &amp;quot;fglrx&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
=== X2/Dual GPU Cards ===&lt;br /&gt;
If you have an X2 card (e.g. 5970), use... &#039;&#039;&#039;!!Do not use for two separate cards in crossfire!!&#039;&#039;&#039;&lt;br /&gt;
 sudo amdconfig --initial -f --adapter&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;all&lt;br /&gt;
&lt;br /&gt;
=== Dual/Multi Monitors ===&lt;br /&gt;
If you have a dual monitor display (also known as &amp;quot;Big Desktop&amp;quot;), use:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
 sudo amdconfig --set-pcs-str&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;&amp;quot;DDX,EnableRandR12,FALSE&amp;quot;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Force use of the new xorg.conf &#039;&#039;(if necessary)&#039;&#039;==&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test your installation ==&lt;br /&gt;
NOTE: if you don&#039;t reboot first, fglrxinfo gives an error message.&lt;br /&gt;
Reboot the computer and type&lt;br /&gt;
 fglrxinfo&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)&lt;br /&gt;
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and &lt;br /&gt;
Catalyst version you are using.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Now, try:&lt;br /&gt;
 fgl_glxgears&lt;br /&gt;
If you experience issues or a hang, you may need to disable fast TLS.&lt;br /&gt;
 sudo amdconfig --tls=0&lt;br /&gt;
&lt;br /&gt;
=== Just in case ===&lt;br /&gt;
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&#039;t work.&lt;br /&gt;
&lt;br /&gt;
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b&lt;br /&gt;
&lt;br /&gt;
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: &amp;quot;Raising Skinny Elephants Is Never Utterly Boring&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
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: &amp;quot;BUSIER&amp;quot; or remembering a phrase: &amp;quot;Restart Even If System Utterly Broken&amp;quot;. This would also safely shutdown the system.&lt;br /&gt;
&lt;br /&gt;
= Hardware Video Decode Acceleration (EXPERIMENTAL) =&lt;br /&gt;
&lt;br /&gt;
== Using XBMC player (XvBA) ==&lt;br /&gt;
&lt;br /&gt;
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu&#039;s repositories. To install the XvBA-enabled version of xbmc:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-add-repository ppa:wsnipex/xbmc-xvba&lt;br /&gt;
 sudo apt-get update&lt;br /&gt;
 sudo apt-get install xbmc&lt;br /&gt;
&lt;br /&gt;
NOTE: deprecated as of october 2013. Moved to ppa:wsnipex/xbmc-fernetmenta-master&lt;br /&gt;
&lt;br /&gt;
== Using the xvba-va driver (VA-API) ==&lt;br /&gt;
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.&lt;br /&gt;
&lt;br /&gt;
This is confirmed to work for newer RadeonHD GPU&#039;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&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install xvba-va-driver&lt;br /&gt;
&lt;br /&gt;
A good player the utilizes va-api is VLC. You can enable va-api in Tools -&amp;gt; Preferences -&amp;gt; Input and Codecs. Check the box named &amp;quot;Use GPU accelerated decoding&amp;quot; and then restart VLC.&lt;br /&gt;
&lt;br /&gt;
=== Test the xvba-va driver (VA-API) ===&lt;br /&gt;
The tool &#039;&#039;&amp;quot;vainfo&amp;quot;&#039;&#039; allows you to test the proper functioning of the xvba-va driver.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libva-glx1 libva-x11-1 vainfo&lt;br /&gt;
 vainfo&lt;br /&gt;
&lt;br /&gt;
vainfo should return something like the following (and no errors):&lt;br /&gt;
      libva: libva version 0.32.0&lt;br /&gt;
      Xlib:  extension &amp;quot;XFree86-DRI&amp;quot; missing on display &amp;quot;:0.0&amp;quot;.&lt;br /&gt;
      libva: va_getDriverName() returns 0&lt;br /&gt;
      libva: Trying to open /usr/lib/dri/fglrx_drv_video.so&lt;br /&gt;
      libva: va_openDriver() returns 0&lt;br /&gt;
      vainfo: VA API version: 0.32&lt;br /&gt;
      vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8&lt;br /&gt;
      vainfo: Supported profile and entrypoints&lt;br /&gt;
      VAProfileH264High               :	VAEntrypointVLD&lt;br /&gt;
      VAProfileVC1Advanced            :	VAEntrypointVLD&lt;br /&gt;
&lt;br /&gt;
If vainfo returns an error, you may need to create a symlink:&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so  #for 64-bit&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so  #for 32-bit&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
There is possibility to enable &amp;gt; H.264 Level 5.1 decoding in the driver which &amp;quot;has been in the driver for some time but not enabled by default&amp;quot;. This only applies for pre-12.11 beta releases of the drivers. Since 12.11 beta the setting is enabled by default &amp;lt;ref&amp;gt;Kano, Phoronix,[http://phoronix.com/forums/showthread.php?74703-AMD-Catalyst-12-11-Beta-Linux-Driver-Released&amp;amp;p=293310#post293310 AMD Catalyst 12.11 Beta Linux Driver Released]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig --set-pcs-u32=MCIL,HWUVD_H264Level51Support,1&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 sudo service lightdm stop&lt;br /&gt;
 sudo cp -p  /etc/ati/amdpcsdb  /etc/ati/amdpcsdb.bak&lt;br /&gt;
 sudo sed -i &#039;/UvdEnabled=V1/ a HWUVD_H264Level51Support=V1&#039; /etc/ati/amdpcsdb&lt;br /&gt;
 sudo reboot&lt;br /&gt;
&lt;br /&gt;
=Updating Catalyst/fglrx=&lt;br /&gt;
&lt;br /&gt;
DO NOT try to install a new version over an old one. Follow the &#039;Removing Catalyst/fglrx&#039; section below to remove your existing driver, and then you can start at &#039;Downloading the latest Catalyst&#039; to install the new one.&lt;br /&gt;
&lt;br /&gt;
=Removing Catalyst/fglrx=&lt;br /&gt;
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.&lt;br /&gt;
 sudo sh /usr/share/ati/fglrx-uninstall.sh&lt;br /&gt;
 sudo apt-get remove --purge fglrx*&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
 sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon&lt;br /&gt;
 sudo apt-get install xserver-xorg-video-ati&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup&lt;br /&gt;
 sudo rm -f /etc/ati&lt;br /&gt;
&lt;br /&gt;
If you receive&lt;br /&gt;
&lt;br /&gt;
 $ E: Internal Error, No file name for libgl1-mesa-dri&lt;br /&gt;
&lt;br /&gt;
Change the third command above to:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core&lt;br /&gt;
&lt;br /&gt;
= Issues =&lt;br /&gt;
&lt;br /&gt;
== Video Tearing ==&lt;br /&gt;
&lt;br /&gt;
AMD/ATI claims that the &amp;quot;Tear Free Video&amp;quot; option is enabled by default, but that wasn&#039;t the case with Catalyst 12-3 installed on Kubuntu 12.04.&lt;br /&gt;
If you&#039;re having issues with tearing, make sure that &amp;quot;Tear Free Video&amp;quot; is on. You can find this option in the Catalyst Control Center under &#039;Display Options&#039; or you can use the following command:&lt;br /&gt;
 sudo amdconfig --sync-video=on&lt;br /&gt;
The option will not take effect until you restart X (i.e. log out).&lt;br /&gt;
&lt;br /&gt;
If you&#039;re using compositing, you should also make sure that vsync is enabled in the compositor&#039;s settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.&lt;br /&gt;
&lt;br /&gt;
=== kwin === &lt;br /&gt;
You can enable vsync for kwin in System Settings -&amp;gt; Desktop Effects -&amp;gt; Advanced tab&lt;br /&gt;
&lt;br /&gt;
=== Compiz (Unity/GNOME-Shell) ===&lt;br /&gt;
TODO: See if there&#039;s a friendlier way to make sure vsync is enabled without installing ccsm.&lt;br /&gt;
&lt;br /&gt;
Install the compiz settings manager: &lt;br /&gt;
 sudo apt-get install compizconfig-settings-manager&lt;br /&gt;
 ccsm&lt;br /&gt;
&lt;br /&gt;
The &#039;Sync to Vblank&#039; is found in the &#039;OpenGL&#039; subsection of the &#039;General&#039; group&lt;br /&gt;
&lt;br /&gt;
== Hybrid Graphics and Catalyst==&lt;br /&gt;
&lt;br /&gt;
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU&#039;s. Newer systems (those with PowerXpress &amp;gt;= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU&#039;s, and systems with older ATI GPU&#039;s have a mux, but don&#039;t quote that.&lt;br /&gt;
&lt;br /&gt;
=== ATI/ATI Hybrids ===&lt;br /&gt;
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it&#039;s not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig&#039;s PowerXpress options to switch back and forth between the integrated and discrete cards, like so:&lt;br /&gt;
&lt;br /&gt;
 amdconfig --pxl            # List current activated GPU&lt;br /&gt;
 sudo amdconfig --px-dgpu   # Activate discrete GPU (High-Performance mode), must re-start X to take effect&lt;br /&gt;
 sudo amdconfig --px-igpu   # Activate integrated GPU (Power-Saving mode), must re-start X to take effect&lt;br /&gt;
&lt;br /&gt;
After switching, one would log out and back in to restart X.&lt;br /&gt;
&lt;br /&gt;
=== Intel/ATI Hybrids ===&lt;br /&gt;
&lt;br /&gt;
By using the officially provided drivers, there are three problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers that gives an error related to allocation of resources in Xorg log file.&lt;br /&gt;
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)&lt;br /&gt;
&lt;br /&gt;
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration. &lt;br /&gt;
&lt;br /&gt;
If however you suffer from the problem related to intel driver not able to allocate resources, you need to install the older intel driver 2.20.2-1ubuntu1 which can be found at https://launchpad.net/ubuntu/quantal/+source/xserver-xorg-video-intel&lt;br /&gt;
&lt;br /&gt;
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )&lt;br /&gt;
&lt;br /&gt;
A workaround for now is to use the discrete GPU (ATI)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ubuntuforums.org/showthread.php?t=1930450&amp;amp;page=82&amp;amp;p=12755069#post12755069 This post] got both the integrated (Intel 3rd Gen Core processor Graphics Controller) and discrete (Radeon HD 7670M) to work on Ubuntu 13.04 x64.&lt;br /&gt;
&lt;br /&gt;
== Build Fails and Log Shows &amp;quot;mixed implicit and normal rules.  Stop.&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
If the installation fails and you find the above message in /var/lib/dkms/fglrx/&amp;lt;version_number&amp;gt;/build/make.log, it may be because you&#039;re using a pentium-build wrapper around gcc. See what the following ls command returns:&lt;br /&gt;
 ls -la /usr/bin/gcc&lt;br /&gt;
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.8 in Ubuntu Saucy). This should allow you to install fglrx:&lt;br /&gt;
 sudo ln -sf /usr/bin/gcc-4.8 /usr/bin/gcc&lt;br /&gt;
When you&#039;re finished installing the driver, return the gcc link to its original value:&lt;br /&gt;
 sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc&lt;br /&gt;
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot; (on 64-bit systems) ==&lt;br /&gt;
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get -f install&lt;br /&gt;
&lt;br /&gt;
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
 sudo dpkg -i --force-overwrite fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Problems Starting Xserver ==&lt;br /&gt;
&lt;br /&gt;
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.&lt;br /&gt;
&lt;br /&gt;
You can disable the xorg.conf with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled&lt;br /&gt;
&lt;br /&gt;
Reboot and check to see if things work now.&lt;br /&gt;
&lt;br /&gt;
You can reinstate the file with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
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 -&lt;br /&gt;
&lt;br /&gt;
 start on filesystem&lt;br /&gt;
&lt;br /&gt;
 script&lt;br /&gt;
	chmod 0666 /dev/null&lt;br /&gt;
	chmod 0666 /lib/udev/devices/null&lt;br /&gt;
 end script&lt;br /&gt;
&lt;br /&gt;
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It&#039;s worth noting that I had to disable TLS  (amdconfig --tls=0) to get things to stay stable!&lt;br /&gt;
&lt;br /&gt;
If you&#039;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:&lt;br /&gt;
 sudo amdconfig --acpi-services=off&lt;br /&gt;
If this method works, you should consider checking your system vendor&#039;s BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver&#039;s ACPI services.&lt;br /&gt;
&lt;br /&gt;
== Unsupported Hardware Watermark ==&lt;br /&gt;
This can happen if your card&#039;s PCI ID wasn&#039;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&#039;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. &lt;br /&gt;
&lt;br /&gt;
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD&#039;s signature file has a proper signature:&lt;br /&gt;
&lt;br /&gt;
 sudo nano /etc/ati/signature&lt;br /&gt;
&lt;br /&gt;
If the file only contains the word &#039;&#039;UNSIGNED&#039;&#039;, replace the line with:&lt;br /&gt;
 9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc&lt;br /&gt;
&lt;br /&gt;
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you&#039;re running:&lt;br /&gt;
&lt;br /&gt;
 cd ~/; mkdir catalyst12.10; cd catalyst12.10/&lt;br /&gt;
 wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run&lt;br /&gt;
 ./amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo mv /etc/ati/control ~/control.bak&lt;br /&gt;
 sudo cp driver/common/etc/ati/control /etc/ati&lt;br /&gt;
&lt;br /&gt;
==Poor battery life (atieventsd not starting and/or not authenticating)==&lt;br /&gt;
&lt;br /&gt;
The atieventsd daemon is a daemon that monitors various acpi events (it does this by connecting with the acpid daemon), such as a laptop lid close, or an AC connect/disconnect, presumably to let the GPU know for reasons of power saving. See the [http://manpages.ubuntu.com/manpages/hardy/en/man8/atieventsd.8.html man page] for more info.&lt;br /&gt;
On my system, `Ubuntu 13.10`, and with the latest drivers from Catalyst, 13.12, the daemon installs itself at `/etc/alternatives/x86_64-linux-gnu_atieventsd` with a symlink to that at `/usr/bin/atieventsd`. &lt;br /&gt;
&lt;br /&gt;
The Sys-V-init script, `/etc/init.d/atieventsd` thinks the symlink is elsewhere, namely `/usr/sbin/atieventsd` (i.e. `sbin` not where it actually is, `bin`)&lt;br /&gt;
&lt;br /&gt;
So to launch successfully the `atieventsd` on startup I had to do make the change:&lt;br /&gt;
&lt;br /&gt;
     DAEMONPATH=/usr/bin/atieventsd&lt;br /&gt;
&lt;br /&gt;
Then remove/regenerate the run levels:&lt;br /&gt;
&lt;br /&gt;
    cd /etc/init.d&lt;br /&gt;
    mv atieventsd atieventsd.temp&lt;br /&gt;
    update-rc.d atieventsd remove&lt;br /&gt;
    mv atieventsd.temp atieventsd&lt;br /&gt;
    update-rc.d atieventsd defaults&lt;br /&gt;
&lt;br /&gt;
This should now at least allow the daemon to correctly start/stop. You can test with `service atieventsd start`.&lt;br /&gt;
&lt;br /&gt;
On each startup the daemon attempts to launch a script, `/etc/ati/authatieventsd.sh` (by default) , whose purpose is to grant the `atieventsd daemon` authorization access to the X server display, so it can send it various commands. &lt;br /&gt;
&lt;br /&gt;
This script is called by `atieventd` like (see `ps aux | grep atieventsd` after starting the service or booting)&lt;br /&gt;
&lt;br /&gt;
     /etc/ati/authatieventsd.sh grant :0 /tmp/atieventsdGWt098&lt;br /&gt;
&lt;br /&gt;
Here argument one (`$1`) is the action: *grant/revoke*&lt;br /&gt;
, argument two (`$2`) is the X display number (e.g `:0`), and argument three (`$3`) is the file wanting the authority. See the `xauth` [http://www.x.org/archive/X11R6.8.1/doc/xauth.1.html man page] for some more background.&lt;br /&gt;
&lt;br /&gt;
The problem is that if you look at the `/etc/ati/authatieventsd.sh` script you will see it does not support `lightdm`, you need to add the chunk of code inside the `GetServerAuthFile()` function:&lt;br /&gt;
&lt;br /&gt;
    #Check lightdm     &lt;br /&gt;
     LIGHTDM_AUTH_FILE=/var/run/lightdm/root/$1&lt;br /&gt;
     if [ -e $LIGHTDM_AUTH_FILE ]; then&lt;br /&gt;
         SERVER_AUTH_FILE=$LIGHTDM_AUTH_FILE&lt;br /&gt;
         DISP_SEARCH_STRING=&amp;quot;unix$1&amp;quot;&lt;br /&gt;
         return 0&lt;br /&gt;
     fi&lt;br /&gt;
&lt;br /&gt;
to allow it find the correct server authentication file. Save this and you should&lt;br /&gt;
see a file in the `/tmp` directory of the form `atieventsdGWt098`, the next time the `atieventd` is stopped/start (or next reboot), and if you do&lt;br /&gt;
&lt;br /&gt;
    xauth -f /tmp/atievntX.Dh1AJV list&lt;br /&gt;
&lt;br /&gt;
you should get something like&lt;br /&gt;
&lt;br /&gt;
    yourHostname/unix:0  MIT-MAGIC-COOKIE-1  98deg034234kkn34234mmm3242&lt;br /&gt;
&lt;br /&gt;
Showing that the daemon has indeed been granted authority. &lt;br /&gt;
&lt;br /&gt;
You can also look at syslog, if you add the `--debug` option to `/etc/init.d/atieventsd` init file DAEMONOPTS options (regen run levels), and you should see everything is now working correctly, and the daemon is responding to events such as unplugging the AC and lid closes. For example:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: ac_adapter AC 00000080 00000000&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: processor CPU0 00000081 00000000&lt;br /&gt;
    processor CPU1 00000081 00000000&lt;br /&gt;
    processor CPU2 00000081 00000000&lt;br /&gt;
    processor CPU3 00000081 00000000&lt;br /&gt;
&lt;br /&gt;
Maybe this will help extend battery life.&lt;br /&gt;
&lt;br /&gt;
== Hang at logout ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: &lt;br /&gt;
(assuming that the installer is in the directory we used to install)&lt;br /&gt;
&lt;br /&gt;
 cd ~/catalyst{{Catalystversion}}&lt;br /&gt;
 sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh&lt;br /&gt;
 sudo chmod +x /etc/ati/authatieventsd.sh&lt;br /&gt;
&lt;br /&gt;
This problem can be fixed permanently with:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
 sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
 sudo /usr/sbin/update-rc.d -f atieventsd remove&lt;br /&gt;
&lt;br /&gt;
You&#039;ll have to restart for this to take effect.&lt;br /&gt;
&lt;br /&gt;
== Can&#039;t remove fglrx with dpkg (diversion issue) ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&amp;lt;pre&amp;gt;dpkg-divert: mismatch on divert-to&lt;br /&gt;
  when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx&#039;&lt;br /&gt;
  found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
then:&lt;br /&gt;
 sudo dpkg-divert --remove /usr/lib/libGL.so.1.2&lt;br /&gt;
&lt;br /&gt;
== This module/version combo is already installed ==&lt;br /&gt;
&lt;br /&gt;
If you get this error-message, simply uninstall the previous version before installing the new one with:&lt;br /&gt;
 sudo dkms remove -m fglrx --all&lt;br /&gt;
&lt;br /&gt;
== New kernel installed? ==&lt;br /&gt;
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:&lt;br /&gt;
 sudo dkms build -m fglrx -k `uname -r`&lt;br /&gt;
 sudo dkms install -m fglrx -k `uname -r`&lt;br /&gt;
&lt;br /&gt;
if amdcccle doesn&#039;t work and says Identifier is not a valid word. Use lower case letter in xorg.conf&lt;br /&gt;
 &lt;br /&gt;
or specify all the correct parameters. For example:&lt;br /&gt;
 sudo dkms build -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
 sudo dkms install -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
&lt;br /&gt;
== amdconfig not found after installation ==&lt;br /&gt;
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&#039;s website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:&lt;br /&gt;
&amp;lt;pre&amp;gt;amdconfig: command not found&amp;lt;/pre&amp;gt;&lt;br /&gt;
After booting you might receive X error &#039;(EE) Failed to load module &amp;quot;fglrx&amp;quot; (module does not exist, 0)&#039;. These do not necessarily indicate that the installation has failed completely. On command line, do&lt;br /&gt;
 ls /usr/lib/fglrx/bin&lt;br /&gt;
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 &amp;quot;update-alternatives&amp;quot; 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&lt;br /&gt;
 update-alternatives --get-selections | grep gl_conf&lt;br /&gt;
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 &lt;br /&gt;
 sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf&lt;br /&gt;
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:&lt;br /&gt;
 sudo update-alternatives --auto gl_conf&lt;br /&gt;
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;update-alternatives: error&amp;quot; during install ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;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&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can be easily solved by creating directory &amp;quot;drivers&amp;quot; under /usr/lib/xorg/modules/&lt;br /&gt;
 sudo mkdir /usr/lib/xorg/modules/drivers&lt;br /&gt;
&lt;br /&gt;
== &#039;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&#039; during deb generation ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can happen when your /tmp folder is mounted with the option &amp;quot;noexec&amp;quot;. The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.&lt;br /&gt;
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]&lt;br /&gt;
&lt;br /&gt;
== Black screen after uninstalling old amd drivers ==&lt;br /&gt;
Start you computer in recovery mode and exit to root shell.&lt;br /&gt;
Remount your partitions in rw mode:&lt;br /&gt;
 mount -rw -o remount /&lt;br /&gt;
 ...&lt;br /&gt;
Go to your download directory and proceed with building and installing the drivers in recovery mode.&lt;br /&gt;
All should be fine after a reboot.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>24.84.213.185</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10463</id>
		<title>Ubuntu Saucy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Saucy_Installation_Guide&amp;diff=10463"/>
		<updated>2014-04-27T00:57:41Z</updated>

		<summary type="html">&lt;p&gt;24.84.213.185: /* Download the latest Catalyst package */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; __TOC__&lt;br /&gt;
&lt;br /&gt;
= The Options =&lt;br /&gt;
Users with ATI cards have the following driver options:&lt;br /&gt;
* &#039;&#039;&#039;vesa&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;ati&#039;&#039;&#039; - actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). &lt;br /&gt;
* &#039;&#039;&#039;radeon&#039;&#039;&#039; - 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.&lt;br /&gt;
* &#039;&#039;&#039;Catalyst (a.k.a fglrx)&#039;&#039;&#039; a proprietary &amp;quot;blob&amp;quot; (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. You may want to use this driver for longer battery life on a laptop or for more demanding 3D applications.&lt;br /&gt;
&lt;br /&gt;
= Updated Open Source Driver PPA&#039;s =&lt;br /&gt;
* &#039;&#039;&#039;&amp;quot;Ubuntu-X&amp;quot;&#039;&#039;&#039; : 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&lt;br /&gt;
* &#039;&#039;&#039;Xorg-edgers&#039;&#039;&#039;: 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&lt;br /&gt;
&lt;br /&gt;
= Installing Proprietary Drivers a.k.a. Catalyst/fglrx =&lt;br /&gt;
&lt;br /&gt;
{| WIDTH=&amp;quot;650&amp;quot; cellpadding=0 cellspacing=0 style=&amp;quot;background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;&amp;quot; &lt;br /&gt;
| style=&amp;quot;background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;&amp;quot; | &amp;lt;font size=&amp;quot;-1&amp;quot;&amp;gt;&#039;&#039;&#039;ATTENTION RADEON USERS&#039;&#039;&#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
|- &lt;br /&gt;
| &amp;lt;br /&amp;gt;*PLEASE READ FIRST!&lt;br /&gt;
&#039;&#039;&#039;Which Radeon cards are no longer supported by ATI&#039;s Catalyst?&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500, Mobility RadeonHD 2300&#039;&#039;&#039;&lt;br /&gt;
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.&lt;br /&gt;
NOTE: If you enter your card information on AMD/ATI&#039;s driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn&#039;t support X servers past 1.5, and it will not work with Precise (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 &#039;Removing the Driver&#039; section to restore the default/pre-installed drivers.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;ATI RadeonHD 2x00 - 4xx0 cards&#039;&#039;&#039;&lt;br /&gt;
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).&lt;br /&gt;
This can be done really easily and automaticly (downgrading &amp;amp; installing) by following the instructions given at [[https://launchpad.net/~makson96/+archive/fglrx]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.&lt;br /&gt;
&lt;br /&gt;
I recommend copying and pasting the commands to ensure there are no typing mistakes and speed up the install process. Remember to use Ctrl &#039;&#039;&#039;+ Shift&#039;&#039;&#039; + V or Shift + Insert to paste into the terminal (or go to the terminals menu, select edit and click paste).&lt;br /&gt;
&lt;br /&gt;
== Before you start ==&lt;br /&gt;
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section. Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources (System -&amp;gt; Administration -&amp;gt; Software Sources).&lt;br /&gt;
or Applications-&amp;gt;Ubuntu Software Center-&amp;gt;Edit-&amp;gt;Software sources-&amp;gt;Other software: check canonical partners.&lt;br /&gt;
&lt;br /&gt;
Install the prerequisite packages:&lt;br /&gt;
 sudo apt-get install cdbs dh-make dkms execstack dh-modaliases linux-headers-generic libqtgui4&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you are using the x86_64 architecture (64 bit)&#039;&#039;:&lt;br /&gt;
 sudo apt-get install lib32gcc1&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;STABLE&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
 mkdir catalyst{{Catalystversion}} &amp;amp;&amp;amp; cd catalyst{{Catalystversion}}&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 unzip amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
Above does not function, this will:&lt;br /&gt;
 mkdir ~/catalyst14-4 &amp;amp;&amp;amp; cd ~/catalyst14-4&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/linux/amd-catalyst-&amp;lt;/nowiki&amp;gt;14-4-linux-x86-x86-64.zip&lt;br /&gt;
 unzip amd-catalyst-14-4-linux-x86-x86-64.zip&lt;br /&gt;
 chmod +x ~/catalyst14-4/fglrx-14.10.1006/amd-driver-installer-14.10.1006-x86.x86_64.run&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
 sudo ./amd-catalyst-{{Catalystversion}}-linux-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails (since Ubuntu/saucy is currently not supported in the rev. 13.12 release from 19 December, 2013) you can apply a patch folowing [https://gist.github.com/moldcraft/8116528 This instructions] (recommended as you create deb packages) or you can try an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation] which does NOT create deb packages and might cause some trouble when trying to uninstall.&lt;br /&gt;
&lt;br /&gt;
== Installing Catalyst Manually (from AMD/ATI&#039;s site) &#039;&#039;BETA/EXPERIMENTAL&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== Download the latest Catalyst package ===&lt;br /&gt;
This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
 mkdir catalyst-14.3beta1.0 &amp;amp;&amp;amp; cd catalyst-14.3beta1.0&lt;br /&gt;
 wget &amp;lt;nowiki&amp;gt;--referer=&#039;http://support.amd.com/en-us/download/desktop?os=Linux+x86&#039; http://www2.ati.com/drivers/beta/Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 unzip Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip&lt;br /&gt;
 cd fglrx-13.35.1005&lt;br /&gt;
&lt;br /&gt;
=== Create and install .deb packages ===&lt;br /&gt;
&lt;br /&gt;
 sudo ./amd-driver-installer-13.35.1005-x86.x86_64.run --buildpkg Ubuntu/saucy&lt;br /&gt;
 sudo dpkg -i fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
If building .deb packages fails, there is also an [http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Alternative_Manual_Installation Alternative Manual Installation]&lt;br /&gt;
&lt;br /&gt;
== In case of failure ==&lt;br /&gt;
Remember these steps before you reboot your computer.&lt;br /&gt;
&lt;br /&gt;
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.&lt;br /&gt;
&lt;br /&gt;
 sudo startx&lt;br /&gt;
&lt;br /&gt;
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of &amp;quot;Could not stat /usr/lib64/fglrx/switchlibGL&amp;quot; which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/. &lt;br /&gt;
&lt;br /&gt;
If all else fails, revert your xorg.conf and reboot.&lt;br /&gt;
&lt;br /&gt;
 sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
This should return your original display.&lt;br /&gt;
&lt;br /&gt;
== Generate a new /etc/X11/xorg.conf file ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Generic Config ===&lt;br /&gt;
This will work for most people:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
&lt;br /&gt;
=== Minimal Config ===&lt;br /&gt;
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that&#039;s not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:&lt;br /&gt;
&lt;br /&gt;
 Section &amp;quot;Device&amp;quot;&lt;br /&gt;
  Identifier &amp;quot;ATI radeon 6870&amp;quot;&lt;br /&gt;
  Driver &amp;quot;fglrx&amp;quot;&lt;br /&gt;
 EndSection&lt;br /&gt;
&lt;br /&gt;
=== X2/Dual GPU Cards ===&lt;br /&gt;
If you have an X2 card (e.g. 5970), use... &#039;&#039;&#039;!!Do not use for two separate cards in crossfire!!&#039;&#039;&#039;&lt;br /&gt;
 sudo amdconfig --initial -f --adapter&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;all&lt;br /&gt;
&lt;br /&gt;
=== Dual/Multi Monitors ===&lt;br /&gt;
If you have a dual monitor display (also known as &amp;quot;Big Desktop&amp;quot;), use:&lt;br /&gt;
 sudo amdconfig --initial -f&lt;br /&gt;
 sudo amdconfig --set-pcs-str&amp;lt;nowiki&amp;gt;=&amp;lt;/nowiki&amp;gt;&amp;quot;DDX,EnableRandR12,FALSE&amp;quot;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Force use of the new xorg.conf &#039;&#039;(if necessary)&#039;&#039;==&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test your installation ==&lt;br /&gt;
NOTE: if you don&#039;t reboot first, fglrxinfo gives an error message.&lt;br /&gt;
Reboot the computer and type&lt;br /&gt;
 fglrxinfo&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 12-3 and a RadeonHD 4550 returns:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon HD 4550 (This line may be different depending on what graphics card you are using.)&lt;br /&gt;
OpenGL version string: 3.3.11566 Compatibility Profile Context (This line may be different depending on what graphics card and &lt;br /&gt;
Catalyst version you are using.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Now, try:&lt;br /&gt;
 fgl_glxgears&lt;br /&gt;
If you experience issues or a hang, you may need to disable fast TLS.&lt;br /&gt;
 sudo amdconfig --tls=0&lt;br /&gt;
&lt;br /&gt;
=== Just in case ===&lt;br /&gt;
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&#039;t work.&lt;br /&gt;
&lt;br /&gt;
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b&lt;br /&gt;
&lt;br /&gt;
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: &amp;quot;Raising Skinny Elephants Is Never Utterly Boring&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
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: &amp;quot;BUSIER&amp;quot; or remembering a phrase: &amp;quot;Restart Even If System Utterly Broken&amp;quot;. This would also safely shutdown the system.&lt;br /&gt;
&lt;br /&gt;
= Hardware Video Decode Acceleration (EXPERIMENTAL) =&lt;br /&gt;
&lt;br /&gt;
== Using XBMC player (XvBA) ==&lt;br /&gt;
&lt;br /&gt;
XBMC has added support for accelerating video using XvBA/libxvba directly, but the support is currently not in the xbmc package in Ubuntu&#039;s repositories. To install the XvBA-enabled version of xbmc:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-add-repository ppa:wsnipex/xbmc-xvba&lt;br /&gt;
 sudo apt-get update&lt;br /&gt;
 sudo apt-get install xbmc&lt;br /&gt;
&lt;br /&gt;
NOTE: deprecated as of october 2013. Moved to ppa:wsnipex/xbmc-fernetmenta-master&lt;br /&gt;
&lt;br /&gt;
== Using the xvba-va driver (VA-API) ==&lt;br /&gt;
NOTE: The VA-API wrapper for XvBA has been dead code for a while now. It will probably give you some acceleration of HD formats, but using the previously mentioned xbmc PPA is a better solution.&lt;br /&gt;
&lt;br /&gt;
This is confirmed to work for newer RadeonHD GPU&#039;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&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install xvba-va-driver&lt;br /&gt;
&lt;br /&gt;
A good player the utilizes va-api is VLC. You can enable va-api in Tools -&amp;gt; Preferences -&amp;gt; Input and Codecs. Check the box named &amp;quot;Use GPU accelerated decoding&amp;quot; and then restart VLC.&lt;br /&gt;
&lt;br /&gt;
=== Test the xvba-va driver (VA-API) ===&lt;br /&gt;
The tool &#039;&#039;&amp;quot;vainfo&amp;quot;&#039;&#039; allows you to test the proper functioning of the xvba-va driver.&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install libva-glx1 libva-x11-1 vainfo&lt;br /&gt;
 vainfo&lt;br /&gt;
&lt;br /&gt;
vainfo should return something like the following (and no errors):&lt;br /&gt;
      libva: libva version 0.32.0&lt;br /&gt;
      Xlib:  extension &amp;quot;XFree86-DRI&amp;quot; missing on display &amp;quot;:0.0&amp;quot;.&lt;br /&gt;
      libva: va_getDriverName() returns 0&lt;br /&gt;
      libva: Trying to open /usr/lib/dri/fglrx_drv_video.so&lt;br /&gt;
      libva: va_openDriver() returns 0&lt;br /&gt;
      vainfo: VA API version: 0.32&lt;br /&gt;
      vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8&lt;br /&gt;
      vainfo: Supported profile and entrypoints&lt;br /&gt;
      VAProfileH264High               :	VAEntrypointVLD&lt;br /&gt;
      VAProfileVC1Advanced            :	VAEntrypointVLD&lt;br /&gt;
&lt;br /&gt;
If vainfo returns an error, you may need to create a symlink:&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so  #for 64-bit&lt;br /&gt;
 sudo ln -s /usr/lib/va/drivers/fglrx_drv_video.so /usr/lib/dri/fglrx_drv_video.so  #for 32-bit&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
There is possibility to enable &amp;gt; H.264 Level 5.1 decoding in the driver which &amp;quot;has been in the driver for some time but not enabled by default&amp;quot;. This only applies for pre-12.11 beta releases of the drivers. Since 12.11 beta the setting is enabled by default &amp;lt;ref&amp;gt;Kano, Phoronix,[http://phoronix.com/forums/showthread.php?74703-AMD-Catalyst-12-11-Beta-Linux-Driver-Released&amp;amp;p=293310#post293310 AMD Catalyst 12.11 Beta Linux Driver Released]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 sudo amdconfig --set-pcs-u32=MCIL,HWUVD_H264Level51Support,1&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 sudo service lightdm stop&lt;br /&gt;
 sudo cp -p  /etc/ati/amdpcsdb  /etc/ati/amdpcsdb.bak&lt;br /&gt;
 sudo sed -i &#039;/UvdEnabled=V1/ a HWUVD_H264Level51Support=V1&#039; /etc/ati/amdpcsdb&lt;br /&gt;
 sudo reboot&lt;br /&gt;
&lt;br /&gt;
=Updating Catalyst/fglrx=&lt;br /&gt;
&lt;br /&gt;
DO NOT try to install a new version over an old one. Follow the &#039;Removing Catalyst/fglrx&#039; section below to remove your existing driver, and then you can start at &#039;Downloading the latest Catalyst&#039; to install the new one.&lt;br /&gt;
&lt;br /&gt;
=Removing Catalyst/fglrx=&lt;br /&gt;
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.&lt;br /&gt;
 sudo sh /usr/share/ati/fglrx-uninstall.sh&lt;br /&gt;
 sudo apt-get remove --purge fglrx*&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
 sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon&lt;br /&gt;
 sudo apt-get install xserver-xorg-video-ati&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup&lt;br /&gt;
 sudo rm -f /etc/ati&lt;br /&gt;
&lt;br /&gt;
If you receive&lt;br /&gt;
&lt;br /&gt;
 $ E: Internal Error, No file name for libgl1-mesa-dri&lt;br /&gt;
&lt;br /&gt;
Change the third command above to:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core&lt;br /&gt;
&lt;br /&gt;
= Issues =&lt;br /&gt;
&lt;br /&gt;
== Video Tearing ==&lt;br /&gt;
&lt;br /&gt;
AMD/ATI claims that the &amp;quot;Tear Free Video&amp;quot; option is enabled by default, but that wasn&#039;t the case with Catalyst 12-3 installed on Kubuntu 12.04.&lt;br /&gt;
If you&#039;re having issues with tearing, make sure that &amp;quot;Tear Free Video&amp;quot; is on. You can find this option in the Catalyst Control Center under &#039;Display Options&#039; or you can use the following command:&lt;br /&gt;
 sudo amdconfig --sync-video=on&lt;br /&gt;
The option will not take effect until you restart X (i.e. log out).&lt;br /&gt;
&lt;br /&gt;
If you&#039;re using compositing, you should also make sure that vsync is enabled in the compositor&#039;s settings. I found that vsync was enabled by default, but here are the appropriate settings should you want to experiment.&lt;br /&gt;
&lt;br /&gt;
=== kwin === &lt;br /&gt;
You can enable vsync for kwin in System Settings -&amp;gt; Desktop Effects -&amp;gt; Advanced tab&lt;br /&gt;
&lt;br /&gt;
=== Compiz (Unity/GNOME-Shell) ===&lt;br /&gt;
TODO: See if there&#039;s a friendlier way to make sure vsync is enabled without installing ccsm.&lt;br /&gt;
&lt;br /&gt;
Install the compiz settings manager: &lt;br /&gt;
 sudo apt-get install compizconfig-settings-manager&lt;br /&gt;
 ccsm&lt;br /&gt;
&lt;br /&gt;
The &#039;Sync to Vblank&#039; is found in the &#039;OpenGL&#039; subsection of the &#039;General&#039; group&lt;br /&gt;
&lt;br /&gt;
== Hybrid Graphics and Catalyst==&lt;br /&gt;
&lt;br /&gt;
There are two basic types of hybrid designs. Older hybrid systems use a multiplexor (mux) to switch between GPU&#039;s. Newer systems (those with PowerXpress &amp;gt;= 4.0) are muxless. As far as I can tell, PowerXpress 4.0 started with RadeonHD 6000-series GPU&#039;s, and systems with older ATI GPU&#039;s have a mux, but don&#039;t quote that.&lt;br /&gt;
&lt;br /&gt;
=== ATI/ATI Hybrids ===&lt;br /&gt;
As of Catalyst 11-8, switching between two ATI cards (and maybe Intel/ATI muxless too?) is supposed to be doable, though it&#039;s not clear if that applies to all ATI/ATI hybrids or only the muxless ones. One would use amdconfig&#039;s PowerXpress options to switch back and forth between the integrated and discrete cards, like so:&lt;br /&gt;
&lt;br /&gt;
 amdconfig --pxl            # List current activated GPU&lt;br /&gt;
 sudo amdconfig --px-dgpu   # Activate discrete GPU (High-Performance mode), must re-start X to take effect&lt;br /&gt;
 sudo amdconfig --px-igpu   # Activate integrated GPU (Power-Saving mode), must re-start X to take effect&lt;br /&gt;
&lt;br /&gt;
After switching, one would log out and back in to restart X.&lt;br /&gt;
&lt;br /&gt;
=== Intel/ATI Hybrids ===&lt;br /&gt;
&lt;br /&gt;
By using the officially provided drivers, there are three problems ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1068404 #1068404]):&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server)&lt;br /&gt;
: An incompatibility problem between intel and fglrx drivers that gives an error related to allocation of resources in Xorg log file.&lt;br /&gt;
: Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly)&lt;br /&gt;
&lt;br /&gt;
If you follow the instructions described in the [https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND Binary Driver HOWTO], you should get functional configuration. &lt;br /&gt;
&lt;br /&gt;
If however you suffer from the problem related to intel driver not able to allocate resources, you need to install the older intel driver 2.20.2-1ubuntu1 which can be found at https://launchpad.net/ubuntu/quantal/+source/xserver-xorg-video-intel&lt;br /&gt;
&lt;br /&gt;
There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 #1088220] )&lt;br /&gt;
&lt;br /&gt;
A workaround for now is to use the discrete GPU (ATI)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more information you may want to follow this [http://ubuntuforums.org/showthread.php?p=12324761#post12324761 forum topic]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ubuntuforums.org/showthread.php?t=1930450&amp;amp;page=82&amp;amp;p=12755069#post12755069 This post] got both the integrated (Intel 3rd Gen Core processor Graphics Controller) and discrete (Radeon HD 7670M) to work on Ubuntu 13.04 x64.&lt;br /&gt;
&lt;br /&gt;
== Build Fails and Log Shows &amp;quot;mixed implicit and normal rules.  Stop.&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
If the installation fails and you find the above message in /var/lib/dkms/fglrx/&amp;lt;version_number&amp;gt;/build/make.log, it may be because you&#039;re using a pentium-build wrapper around gcc. See what the following ls command returns:&lt;br /&gt;
 ls -la /usr/bin/gcc&lt;br /&gt;
If it shows that gcc is a link to builder-cc, temporarily redirect the link to point to the real gcc (gcc-4.8 in Ubuntu Saucy). This should allow you to install fglrx:&lt;br /&gt;
 sudo ln -sf /usr/bin/gcc-4.8 /usr/bin/gcc&lt;br /&gt;
When you&#039;re finished installing the driver, return the gcc link to its original value:&lt;br /&gt;
 sudo ln -sf /usr/bin/builder-cc /usr/bin/gcc&lt;br /&gt;
Launchpad link for this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/555957&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot; (on 64-bit systems) ==&lt;br /&gt;
Most likely, you probably did not have the ia32-libs-multiarch:i386 lib32gcc1 libc6-i386 packages installed beforehand. If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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:&lt;br /&gt;
&lt;br /&gt;
 sudo apt-get -f install&lt;br /&gt;
&lt;br /&gt;
Catalyst {{Template:Catalystversion}} on 64-bit systems may require the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
 sudo dpkg -i --force-overwrite fglrx*.deb&lt;br /&gt;
&lt;br /&gt;
== Problems Starting Xserver ==&lt;br /&gt;
&lt;br /&gt;
If you get a black screen hang, the first thing to check is if xorg.conf is the problem.&lt;br /&gt;
&lt;br /&gt;
You can disable the xorg.conf with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled&lt;br /&gt;
&lt;br /&gt;
Reboot and check to see if things work now.&lt;br /&gt;
&lt;br /&gt;
You can reinstate the file with:&lt;br /&gt;
 sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf&lt;br /&gt;
&lt;br /&gt;
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 -&lt;br /&gt;
&lt;br /&gt;
 start on filesystem&lt;br /&gt;
&lt;br /&gt;
 script&lt;br /&gt;
	chmod 0666 /dev/null&lt;br /&gt;
	chmod 0666 /lib/udev/devices/null&lt;br /&gt;
 end script&lt;br /&gt;
&lt;br /&gt;
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It&#039;s worth noting that I had to disable TLS  (amdconfig --tls=0) to get things to stay stable!&lt;br /&gt;
&lt;br /&gt;
If you&#039;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:&lt;br /&gt;
 sudo amdconfig --acpi-services=off&lt;br /&gt;
If this method works, you should consider checking your system vendor&#039;s BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver&#039;s ACPI services.&lt;br /&gt;
&lt;br /&gt;
== Unsupported Hardware Watermark ==&lt;br /&gt;
This can happen if your card&#039;s PCI ID wasn&#039;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&#039;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. &lt;br /&gt;
&lt;br /&gt;
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it is possible to work around the issue. First check if AMD&#039;s signature file has a proper signature:&lt;br /&gt;
&lt;br /&gt;
 sudo nano /etc/ati/signature&lt;br /&gt;
&lt;br /&gt;
If the file only contains the word &#039;&#039;UNSIGNED&#039;&#039;, replace the line with:&lt;br /&gt;
 9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc&lt;br /&gt;
&lt;br /&gt;
Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you&#039;re running:&lt;br /&gt;
&lt;br /&gt;
 cd ~/; mkdir catalyst12.10; cd catalyst12.10/&lt;br /&gt;
 wget http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 unzip amd-driver-installer-catalyst-12.10-x86.x86_64.zip&lt;br /&gt;
 chmod +x amd-driver-installer-catalyst-12.10-x86.x86_64.run&lt;br /&gt;
 ./amd-driver-installer-catalyst-12.10-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo mv /etc/ati/control ~/control.bak&lt;br /&gt;
 sudo cp driver/common/etc/ati/control /etc/ati&lt;br /&gt;
&lt;br /&gt;
==Poor battery life (atieventsd not starting and/or not authenticating)==&lt;br /&gt;
&lt;br /&gt;
The atieventsd daemon is a daemon that monitors various acpi events (it does this by connecting with the acpid daemon), such as a laptop lid close, or an AC connect/disconnect, presumably to let the GPU know for reasons of power saving. See the [http://manpages.ubuntu.com/manpages/hardy/en/man8/atieventsd.8.html man page] for more info.&lt;br /&gt;
On my system, `Ubuntu 13.10`, and with the latest drivers from Catalyst, 13.12, the daemon installs itself at `/etc/alternatives/x86_64-linux-gnu_atieventsd` with a symlink to that at `/usr/bin/atieventsd`. &lt;br /&gt;
&lt;br /&gt;
The Sys-V-init script, `/etc/init.d/atieventsd` thinks the symlink is elsewhere, namely `/usr/sbin/atieventsd` (i.e. `sbin` not where it actually is, `bin`)&lt;br /&gt;
&lt;br /&gt;
So to launch successfully the `atieventsd` on startup I had to do make the change:&lt;br /&gt;
&lt;br /&gt;
     DAEMONPATH=/usr/bin/atieventsd&lt;br /&gt;
&lt;br /&gt;
Then remove/regenerate the run levels:&lt;br /&gt;
&lt;br /&gt;
    cd /etc/init.d&lt;br /&gt;
    mv atieventsd atieventsd.temp&lt;br /&gt;
    update-rc.d atieventsd remove&lt;br /&gt;
    mv atieventsd.temp atieventsd&lt;br /&gt;
    update-rc.d atieventsd defaults&lt;br /&gt;
&lt;br /&gt;
This should now at least allow the daemon to correctly start/stop. You can test with `service atieventsd start`.&lt;br /&gt;
&lt;br /&gt;
On each startup the daemon attempts to launch a script, `/etc/ati/authatieventsd.sh` (by default) , whose purpose is to grant the `atieventsd daemon` authorization access to the X server display, so it can send it various commands. &lt;br /&gt;
&lt;br /&gt;
This script is called by `atieventd` like (see `ps aux | grep atieventsd` after starting the service or booting)&lt;br /&gt;
&lt;br /&gt;
     /etc/ati/authatieventsd.sh grant :0 /tmp/atieventsdGWt098&lt;br /&gt;
&lt;br /&gt;
Here argument one (`$1`) is the action: *grant/revoke*&lt;br /&gt;
, argument two (`$2`) is the X display number (e.g `:0`), and argument three (`$3`) is the file wanting the authority. See the `xauth` [http://www.x.org/archive/X11R6.8.1/doc/xauth.1.html man page] for some more background.&lt;br /&gt;
&lt;br /&gt;
The problem is that if you look at the `/etc/ati/authatieventsd.sh` script you will see it does not support `lightdm`, you need to add the chunk of code inside the `GetServerAuthFile()` function:&lt;br /&gt;
&lt;br /&gt;
    #Check lightdm     &lt;br /&gt;
     LIGHTDM_AUTH_FILE=/var/run/lightdm/root/$1&lt;br /&gt;
     if [ -e $LIGHTDM_AUTH_FILE ]; then&lt;br /&gt;
         SERVER_AUTH_FILE=$LIGHTDM_AUTH_FILE&lt;br /&gt;
         DISP_SEARCH_STRING=&amp;quot;unix$1&amp;quot;&lt;br /&gt;
         return 0&lt;br /&gt;
     fi&lt;br /&gt;
&lt;br /&gt;
to allow it find the correct server authentication file. Save this and you should&lt;br /&gt;
see a file in the `/tmp` directory of the form `atieventsdGWt098`, the next time the `atieventd` is stopped/start (or next reboot), and if you do&lt;br /&gt;
&lt;br /&gt;
    xauth -f /tmp/atievntX.Dh1AJV list&lt;br /&gt;
&lt;br /&gt;
you should get something like&lt;br /&gt;
&lt;br /&gt;
    yourHostname/unix:0  MIT-MAGIC-COOKIE-1  98deg034234kkn34234mmm3242&lt;br /&gt;
&lt;br /&gt;
Showing that the daemon has indeed been granted authority. &lt;br /&gt;
&lt;br /&gt;
You can also look at syslog, if you add the `--debug` option to `/etc/init.d/atieventsd` init file DAEMONOPTS options (regen run levels), and you should see everything is now working correctly, and the daemon is responding to events such as unplugging the AC and lid closes. For example:&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: ac_adapter AC 00000080 00000000&lt;br /&gt;
    &amp;lt;Dbg&amp;gt;: ACPI event: processor CPU0 00000081 00000000&lt;br /&gt;
    processor CPU1 00000081 00000000&lt;br /&gt;
    processor CPU2 00000081 00000000&lt;br /&gt;
    processor CPU3 00000081 00000000&lt;br /&gt;
&lt;br /&gt;
Maybe this will help extend battery life.&lt;br /&gt;
&lt;br /&gt;
== Hang at logout ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Before the following commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: &lt;br /&gt;
(assuming that the installer is in the directory we used to install)&lt;br /&gt;
&lt;br /&gt;
 cd ~/catalyst{{Catalystversion}}&lt;br /&gt;
 sh amd-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver&lt;br /&gt;
 sudo cp driver/packages/Ubuntu/dists/quantal/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh&lt;br /&gt;
 sudo chmod +x /etc/ati/authatieventsd.sh&lt;br /&gt;
&lt;br /&gt;
This problem can be fixed permanently with:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
 sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
 sudo /usr/sbin/update-rc.d -f atieventsd remove&lt;br /&gt;
&lt;br /&gt;
You&#039;ll have to restart for this to take effect.&lt;br /&gt;
&lt;br /&gt;
== Can&#039;t remove fglrx with dpkg (diversion issue) ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&amp;lt;pre&amp;gt;dpkg-divert: mismatch on divert-to&lt;br /&gt;
  when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx&#039;&lt;br /&gt;
  found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
then:&lt;br /&gt;
 sudo dpkg-divert --remove /usr/lib/libGL.so.1.2&lt;br /&gt;
&lt;br /&gt;
== This module/version combo is already installed ==&lt;br /&gt;
&lt;br /&gt;
If you get this error-message, simply uninstall the previous version before installing the new one with:&lt;br /&gt;
 sudo dkms remove -m fglrx --all&lt;br /&gt;
&lt;br /&gt;
== New kernel installed? ==&lt;br /&gt;
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:&lt;br /&gt;
 sudo dkms build -m fglrx -k `uname -r`&lt;br /&gt;
 sudo dkms install -m fglrx -k `uname -r`&lt;br /&gt;
&lt;br /&gt;
if amdcccle doesn&#039;t work and says Identifier is not a valid word. Use lower case letter in xorg.conf&lt;br /&gt;
 &lt;br /&gt;
or specify all the correct parameters. For example:&lt;br /&gt;
 sudo dkms build -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
 sudo dkms install -m fglrx -v &#039;&#039;&#039;9.012&#039;&#039;&#039; -k &#039;&#039;&#039;3.5.0-22&#039;&#039;&#039;-generic&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
&lt;br /&gt;
== amdconfig not found after installation ==&lt;br /&gt;
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&#039;s website). When doing amdconfig --initial after driver installation, you might end up not having the amdconfig available at all:&lt;br /&gt;
&amp;lt;pre&amp;gt;amdconfig: command not found&amp;lt;/pre&amp;gt;&lt;br /&gt;
After booting you might receive X error &#039;(EE) Failed to load module &amp;quot;fglrx&amp;quot; (module does not exist, 0)&#039;. These do not necessarily indicate that the installation has failed completely. On command line, do&lt;br /&gt;
 ls /usr/lib/fglrx/bin&lt;br /&gt;
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 &amp;quot;update-alternatives&amp;quot; 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&lt;br /&gt;
 update-alternatives --get-selections | grep gl_conf&lt;br /&gt;
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 &lt;br /&gt;
 sudo update-alternatives --set gl_conf /usr/lib/fglrx/ld.so.conf&lt;br /&gt;
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:&lt;br /&gt;
 sudo update-alternatives --auto gl_conf&lt;br /&gt;
After that, the alternatives should automatically be configured correctly when the graphics driver .debs are installed.&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;update-alternatives: error&amp;quot; during install ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;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&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can be easily solved by creating directory &amp;quot;drivers&amp;quot; under /usr/lib/xorg/modules/&lt;br /&gt;
 sudo mkdir /usr/lib/xorg/modules/drivers&lt;br /&gt;
&lt;br /&gt;
== &#039;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&#039; during deb generation ==&lt;br /&gt;
During installation you may receive the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;Can&#039;t exec &amp;quot;debian/rules&amp;quot;: Permission denied at /usr/bin/dpkg-buildpackage line 507.&amp;lt;/pre&amp;gt;&lt;br /&gt;
This can happen when your /tmp folder is mounted with the option &amp;quot;noexec&amp;quot;. The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.&lt;br /&gt;
A workaround can be found here: [http://serialized.net/2010/03/getting-around-tmpfs-noexec-problems/]&lt;br /&gt;
&lt;br /&gt;
== Black screen after uninstalling old amd drivers ==&lt;br /&gt;
Start you computer in recovery mode and exit to root shell.&lt;br /&gt;
Remount your partitions in rw mode:&lt;br /&gt;
 mount -rw -o remount /&lt;br /&gt;
 ...&lt;br /&gt;
Go to your download directory and proceed with building and installing the drivers in recovery mode.&lt;br /&gt;
All should be fine after a reboot.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>24.84.213.185</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&amp;diff=5036</id>
		<title>Ubuntu Hardy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&amp;diff=5036"/>
		<updated>2009-05-14T06:41:00Z</updated>

		<summary type="html">&lt;p&gt;24.84.53.120: /* 1. Install necessary build tools and libraries */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;For most users it won&#039;t be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the &amp;quot;ATI accelerated graphics driver&amp;quot;. Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.&lt;br /&gt;
&lt;br /&gt;
After installation, in GNOME or Kubuntu, &#039;&#039;&#039;turn off visual effects&#039;&#039;&#039; or you will notice a flicker in OpenGL.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Method 1: Install the driver the Ubuntu Way ==&lt;br /&gt;
&lt;br /&gt;
This will install the current driver in Ubuntu&#039;s repository. It is older than the one AMD has released, but will be supported by the Ubuntu people. Catalyst 8.3 is in the repositories.&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo apt-get update&lt;br /&gt;
&lt;br /&gt;
$ sudo apt-get install linux-restricted-modules-generic restricted-manager&lt;br /&gt;
&lt;br /&gt;
$ sudo apt-get install xorg-driver-fglrx&lt;br /&gt;
&lt;br /&gt;
$ sudo depmod -a&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The second line may not be necessary as you may already have restricted modules installed. Run it just in case. If the third line fails, you probably don&#039;t have the restricted repository enabled. See Pre-Installation.&lt;br /&gt;
&lt;br /&gt;
After this, you may need to edit Xorg.conf:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo gedit /etc/X11/xorg.conf&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
In the device section, if it is not already there add:&lt;br /&gt;
&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
Driver     &amp;quot;fglrx&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Then to make sure Xorg is set up correctly, you&#039;ll have to let aticonfig &amp;quot;initialize&amp;quot; it:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo aticonfig --initial -f&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
After this you should be able to restart your computer and have the driver working. To test type&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ fglrxinfo&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]&lt;br /&gt;
&lt;br /&gt;
==== Post-Installation Tweaks ====&lt;br /&gt;
To enable hardware accelerated video on pre-R500 cards, edit &#039;&#039;&#039;/etc/X11/xorg.conf&#039;&#039;&#039; to include the following lines without &#039;&#039;&#039;[...]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
:[...]&amp;lt;br /&amp;gt;&lt;br /&gt;
:Driver		&amp;quot;fglrx&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:Option		&amp;quot;VideoOverlay&amp;quot;	&amp;quot;on&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:Option		&amp;quot;OpenGLOverlay&amp;quot;	&amp;quot;off&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:[...]&amp;lt;br /&amp;gt;&lt;br /&gt;
EndSection&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
On newer cards the options below enables Visual Effects and video to be played without flicker. The Textured video option can be turned on, but this can cause flicker or diagonal artifacts when playing videos.&lt;br /&gt;
&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
:[...]&amp;lt;br /&amp;gt;&lt;br /&gt;
:Driver	&amp;quot;fglrx&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:Option	&amp;quot;VideoOverlay&amp;quot;	&amp;quot;off&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:Option	&amp;quot;OpenGLOverlay&amp;quot;	&amp;quot;on&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:Option &amp;quot;TexturedVideo&amp;quot; &amp;quot;off&amp;quot;&amp;lt;br /&amp;gt;&lt;br /&gt;
:[...]&amp;lt;br /&amp;gt;&lt;br /&gt;
EndSection&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Method 2: Manual Install Method ==&lt;br /&gt;
&lt;br /&gt;
Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources.&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;1. Install necessary build tools and libraries&#039;&#039;===&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
 sudo apt-get update&amp;lt;br /&amp;gt;&lt;br /&gt;
 sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)&amp;lt;br /&amp;gt;&lt;br /&gt;
 # If you are using the x86_64 architecture (64 bit, earlier known as amd64), install ia32-libs as well:&amp;lt;br /&amp;gt;&lt;br /&gt;
 sudo apt-get install ia32-libs&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;2. Download the latest Catalyst package.&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
Download page: Catalyst {{catalystversion}}. This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
Open a terminal window and switch to the directory you downloaded the installer to. &lt;br /&gt;
For example:&amp;lt;pre&amp;gt;cd Desktop&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;3. Create .deb packages.&#039;&#039;===&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sh {{catalystfilename}} --buildpkg Ubuntu/hardy&lt;br /&gt;
}}&lt;br /&gt;
(&amp;quot;hardy&amp;quot; is not a typo)&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;4. Add driver to kernel module blacklist.&#039;&#039;===&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;: This step is no longer necessary with fglrx 8.10 or 8.12. Just jump to step 5 in that case.&lt;br /&gt;
&lt;br /&gt;
The ATI driver must be added to the kernel module blacklist so that the new ATI driver will be used. If it is not blacklisted, the official Ubuntu repository version of the ATI driver will be loaded instead.&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo gedit /etc/default/linux-restricted-modules-common&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Add &amp;quot;fglrx&amp;quot; to the line &amp;quot;DISABLED_MODULES&amp;quot;&lt;br /&gt;
{{Box File|/etc/default/linux-restricted-modules-common|&lt;br /&gt;
&amp;lt;pre&amp;gt;DISABLED_MODULES=&amp;quot;fglrx&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Please note that after the modification above, the &amp;quot;Restricted Driver Manager&amp;quot; will signal &amp;quot;ATI accelerated graphics driver&amp;quot; not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: &amp;quot;in use&amp;quot; (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module ({{catalystversion}}) is in use.&lt;br /&gt;
&lt;br /&gt;
You may also need to edit the file(s) (if they exist):&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo gedit /etc/modprobe.d/blacklist-restricted&lt;br /&gt;
&lt;br /&gt;
$ sudo gedit /etc/modprobe.d/blacklist-local&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Put a # in front of the line &amp;quot;blacklist fglrx&amp;quot;, if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;5. Install .debs.&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For 32 Bits&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo dpkg -i xorg-driver-fglrx_8.593-0ubuntu1_i386.deb fglrx-kernel-source_8.593-0ubuntu1_i386.deb fglrx-amdcccle_8.593-0ubuntu1_i386.deb&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Starting Catalyst version 8.10, installing the following package ensures compatibility with restricted drivers&#039; manager:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo dpkg -i fglrx-modaliases_8.593-0ubuntu1_i386.deb&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
64 bit systems should have the same behaviour.&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dpkg -i fglrx-modaliases_8.593-0ubuntu1_amd64.deb&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For 64 Bits&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo dpkg -i xorg-driver-fglrx_8.593-0ubuntu1_amd64.deb fglrx-kernel-source_8.593-0ubuntu1_amd64.deb fglrx-amdcccle_8.593-0ubuntu1_amd64.deb&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Additional 64-bit instructions ===&lt;br /&gt;
&lt;br /&gt;
If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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 amdccle package:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo apt-get install -f&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Catalyst {{catalystversion}} on 64-bit systems requires the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.593*.deb fglrx-kernel-source_8.593-0*.deb fglrx-amdcccle_8.593-0*.deb&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
When installing the packages, if &amp;lt;tt&amp;gt;xorg-driver-fglrx_8.593&amp;lt;/tt&amp;gt; fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].&lt;br /&gt;
&lt;br /&gt;
===Fix for an error:===&lt;br /&gt;
If you are having this error:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
dpkg-shlibdeps: failure: couldn&#039;t find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is &#039;&#039;).&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Fix it by doing the following:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo sh {{catalystfilename}} --extract driver&amp;lt;br /&amp;gt;&lt;br /&gt;
$ cd driver/arch/x86_64/usr/X11R6/lib64&amp;lt;br /&amp;gt;&lt;br /&gt;
$ sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1&amp;lt;br /&amp;gt;&lt;br /&gt;
$ cd ../../../../../&amp;lt;br /&amp;gt;&lt;br /&gt;
$ sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy&amp;lt;br /&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If you get this error from modprobe fglrx:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ERROR: firegl_stub_register failed&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Fix it by doing:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ sudo rmmod radeon&amp;lt;br /&amp;gt;&lt;br /&gt;
$ sudo rmmod drm&amp;lt;br /&amp;gt;&lt;br /&gt;
$ sudo modprobe fglrx&amp;lt;br /&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Finishing the Install: Configuration ===&lt;br /&gt;
&lt;br /&gt;
If you&#039;ve used fglrx previously, you will not need to do this.&lt;br /&gt;
Run&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo aticonfig --initial -f&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now you&#039;ll likely have to edit your xorg.conf (even if just to confirm the above command added the apropriate fglrx line):&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo gedit /etc/X11/xorg.conf&amp;lt;/pre&amp;gt;&lt;br /&gt;
and add the following line to the Device section (if it does not already exist).  Include the following lines without &#039;&#039;&#039;[...]&#039;&#039;&#039;: &lt;br /&gt;
&amp;lt;pre&amp;gt;Section &amp;quot;Device&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
	Driver		&amp;quot;fglrx&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
EndSection&amp;lt;/pre&amp;gt;&lt;br /&gt;
Make the appropriate changes to &amp;quot;TexturedVideo&amp;quot; and &amp;quot;Overlay&amp;quot;, etc., as described above in the &amp;quot;automatic section&amp;quot;.&lt;br /&gt;
Save and exit, then &lt;br /&gt;
in a terminal. If it does not error you should be fine. &lt;br /&gt;
&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Finally, reboot the computer and type&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
fglrxinfo&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.8 looks like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: Radeon X1950 Series&lt;br /&gt;
OpenGL version string: 2.1.7873 Release&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Removing Mesa drivers ===&lt;br /&gt;
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:&lt;br /&gt;
&lt;br /&gt;
*Remove the package xserver-xgl.&lt;br /&gt;
:&amp;lt;pre&amp;gt;sudo apt-get remove xserver-xgl&amp;lt;/pre&amp;gt;&lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; 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&lt;br /&gt;
:&amp;lt;pre&amp;gt;DISPLAY=:0 glxinfo | grep render&amp;lt;/pre&amp;gt;&lt;br /&gt;
: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])&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Warning:&#039;&#039;&#039; 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 &amp;quot;Composite&amp;quot; problem, check that the following is set in the /etc/X11/xorg.conf&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
	Option		&amp;quot;Composite&amp;quot;	&amp;quot;Enable&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: &lt;br /&gt;
:&amp;lt;i&amp;gt;(EE) fglrx(0): [agp] unable to acquire AGP, error -1023&lt;br /&gt;
:(EE) fglrx(0): cannot init AGP&lt;br /&gt;
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.&lt;br /&gt;
:(WW) fglrx(0): * DRI initialization failed!                  *&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
: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: &lt;br /&gt;
&amp;lt;pre&amp;gt;rmmod i82875p_edac&lt;br /&gt;
rmmod fglrx&lt;br /&gt;
rmmod intel-agp&lt;br /&gt;
rmmod agpgart&lt;br /&gt;
modprobe agpgart&lt;br /&gt;
modprobe intel-agp&lt;br /&gt;
modprobe fglrx&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:Blacklist the modules e7xxx_edac so it doesn&#039;t start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:&lt;br /&gt;
:&amp;lt;pre&amp;gt;blacklist i82875p_edac&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).&lt;br /&gt;
 &lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; http://openwetware.org/wiki/Computing/Linux/Ubuntu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Check you are running the correct kernel. &lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; If you&#039;re upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.&lt;br /&gt;
:Run in a terminal:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
$ uname -r&lt;br /&gt;
}}&lt;br /&gt;
: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.&lt;br /&gt;
&lt;br /&gt;
If this doesn&#039;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].&lt;br /&gt;
&lt;br /&gt;
== Specific Issues ==&lt;br /&gt;
&lt;br /&gt;
===Segmentation Fault with glxinfo/fglrxinfo===&lt;br /&gt;
&lt;br /&gt;
If you experience such errors (and have &#039;&#039;glxinfo&#039;&#039; report &#039;&#039;&amp;quot;Direct rendering&amp;quot;&#039;&#039; as &#039;&#039;No&#039;&#039; despite following the whole procedure without any errors) you may want to have a look at the &#039;&#039;&#039;Specific Issues&#039;&#039;&#039; chapter of the &#039;&#039;&#039;Ubuntu Gutsy Installation Guide&#039;&#039;&#039; [[http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#If_you_get__.2Fusr.2FX11R6.2Flib.2Fmodules.2Fdri.2Ffglrx_dri.so_not_found]] as this may be due to missing links or wrong permissions.&lt;br /&gt;
&lt;br /&gt;
=== Hang at logout ===&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo /usr/sbin/update-rc.d -f atieventsd remove&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Suspend/Hibernation ===&lt;br /&gt;
&lt;br /&gt;
Suspend hibernation &#039;&#039;&#039;works&#039;&#039;&#039; with the latest driver.&lt;br /&gt;
&lt;br /&gt;
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
SAVE_VBE_STATE=false&lt;br /&gt;
&lt;br /&gt;
POST_VIDEO=false &lt;br /&gt;
&lt;br /&gt;
ENABLE_LAPTOP_MODE=false&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:&lt;br /&gt;
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
        Option        &amp;quot;Composite&amp;quot;        &amp;quot;Disable&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
       Option  &amp;quot;AIGLX&amp;quot; &amp;quot;off&amp;quot; &lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Resume from suspend failed when using dual monitor configuration in xorg.conf.&lt;br /&gt;
E.g. when using&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
aticonfig --initial=dual-head --screen-layout=right&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Switching back to a single monitor configuration and restarting the xserver (though not beautiful) solves this.&lt;br /&gt;
&lt;br /&gt;
=== Error! This module/version combo is already installed ===&lt;br /&gt;
&lt;br /&gt;
Simply uninstall the previous version before installing the new one with&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dkms remove -m fglrx -v 8.522 --all&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;/div&gt;</summary>
		<author><name>24.84.53.120</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Gutsy_Installation_Guide&amp;diff=4482</id>
		<title>Ubuntu Gutsy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Gutsy_Installation_Guide&amp;diff=4482"/>
		<updated>2008-04-21T05:55:59Z</updated>

		<summary type="html">&lt;p&gt;24.84.57.90: updated to catalyst 8.4 from 8.3. simply changed commands.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Pre-Installation Checks==&lt;br /&gt;
=== Enable &amp;quot;restricted&amp;quot; Repository ===&lt;br /&gt;
Make sure the &#039;&#039;restricted&#039;&#039; repository is enabled in &#039;&#039;/etc/apt/sources.list&#039;&#039; or this guide will not work!&lt;br /&gt;
&lt;br /&gt;
System &amp;gt; Administration &amp;gt; Software Sources.  Check &amp;quot;Proprietary Drivers for Devices (Restricted)&amp;quot; box.&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
For most users it won&#039;t be necessary to go into installation and configuration details of the driver. Ubuntu 7.10 (Gutsy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the &amp;quot;ATI accelerated graphics driver&amp;quot;. Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.&lt;br /&gt;
&lt;br /&gt;
===Method 1: Install the Driver the Ubuntu Way===&lt;br /&gt;
This will install the driver that is currently in the repositories. It may be older than the current version from AMD.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update	&lt;br /&gt;
sudo apt-get install linux-restricted-modules-generic restricted-manager&lt;br /&gt;
sudo apt-get install xorg-driver-fglrx&lt;br /&gt;
sudo depmod -a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The second line of the above may not be necessary.  If apt says it cannot find the &amp;quot;linux-restricted-modules&amp;quot; package, try line 3.  If that fails, check your sources.list (see top of page)&lt;br /&gt;
&lt;br /&gt;
If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.&lt;br /&gt;
&lt;br /&gt;
===Method 2: Install the Catalyst 8.3 Driver Manually===&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;This is just an alternative installation method for the section above. It might help if you still get &#039;DRI missing&#039; errors.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Download the ATI driver installer:&lt;br /&gt;
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-3-x86.x86_64.run ati-driver-installer-8-3-x86.x86_64.run] (this installer is for 32bit &#039;&#039;&#039;and&#039;&#039;&#039; 64bit systems)&lt;br /&gt;
&lt;br /&gt;
Change to the directory you downloaded the file.  Make sure that you have the &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; repositories enabled in &#039;&#039;/etc/apt/sources.list&#039;&#039; before doing these steps.  &lt;br /&gt;
&lt;br /&gt;
There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].&lt;br /&gt;
&lt;br /&gt;
By default, Ubuntu did not enable the Universe and Multiverse repositories, but now in Gutsy, both Universe and Multiverse are activated by default.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Install necessary tools:&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update&lt;br /&gt;
sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Uninstall previous fglrx:&#039;&#039; &lt;br /&gt;
Using Synaptic, completely remove any packages containing &amp;quot;fglrx&amp;quot; in their name.&lt;br /&gt;
&lt;br /&gt;
If using 64bit make sure to collect package &amp;quot;ia32-libs&amp;quot; before you continue!&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create .deb packages:&#039;&#039; &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo sh ati-driver-installer-8-4-x86.x86_64.run --buildpkg Ubuntu/gutsy&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
note: if this step fails with a signal being caught, and you are running the script on an NFS-mounted directory, copy it to a local partition, and it will work.  The same error may result from insufficient disk space.&lt;br /&gt;
&lt;br /&gt;
As an alternative, you can just use&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo ./ati-driver-installer-8-4-x86.x86_64.run --buildpkg Ubuntu --autopkg&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
which will download all the needed packages by itself and also automatically detects the Ubuntu version used.&lt;br /&gt;
&lt;br /&gt;
If this step fails on amd64/x86_64 with a &amp;lt;tt&amp;gt;No such file or directory&amp;lt;/tt&amp;gt; message about missing files in &amp;lt;tt&amp;gt;X11R6/lib&amp;lt;/tt&amp;gt;, [http://emmetcaulfield.net/Tech/Ubuntu64+ATI follow these instructions] and come back here. Also check that your download path does not contain spaces.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Blacklist old fglrx module from linux-restricted-modules:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
As Ubuntu Gutsy&#039;s &#039;&#039;linux-restricted-modules&#039;&#039; package includes the fglrx module from an old driver version (8.37.6), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.&lt;br /&gt;
&lt;br /&gt;
Ubuntu/Gnome users type in:&lt;br /&gt;
&amp;lt;pre&amp;gt;gksu gedit /etc/default/linux-restricted-modules-common&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Kubuntu/KDE users type in:&lt;br /&gt;
&amp;lt;pre&amp;gt;kdesu kate /etc/default/linux-restricted-modules-common&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add &amp;quot;fglrx&amp;quot; to the line &amp;quot;DISABLED_MODULES&amp;quot;&lt;br /&gt;
{{Box File|/etc/default/linux-restricted-modules-common|&lt;br /&gt;
&amp;lt;pre&amp;gt;DISABLED_MODULES=&amp;quot;fglrx&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
Please note that after the modification above, the &amp;quot;Restricted Driver Manager&amp;quot; will signal &amp;quot;ATI accelerated graphics driver&amp;quot; not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: &amp;quot;in use&amp;quot; (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module (8.4) is in use.&lt;br /&gt;
&lt;br /&gt;
You may also need to edit the file (if it exists):&lt;br /&gt;
&amp;lt;pre&amp;gt;gksu gedit /etc/modprobe.d/blacklist-restricted&amp;lt;/pre&amp;gt;&lt;br /&gt;
Put a # in front of the line &amp;quot;blacklist fglrx&amp;quot;, if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Remove any old fglrx debs from /usr/src/:&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo rm /usr/src/fglrx-kernel*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Install .deb packages:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dpkg -i xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Additional 64-bit instructions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you have a 64 bit install, the above dpkg command will likely complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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 amdccle package:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get install -f&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Catalyst 8.3 on 64-bit systems requires the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Troubleshooting Installation Errors====&lt;br /&gt;
&#039;&#039;Kernel -rt users&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running the -rt kernel, you will fail to compile the kernel module with &#039;&#039;&amp;quot;FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol &#039;__rcu_read_lock&#039;&amp;quot;&#039;&#039;. Follow the instructions on [http://64studio.com/node/150#comment-1148 64bitstudio.com] for a workaround.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Missing kernel sources&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at&lt;br /&gt;
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
You must install the specific headers package for your kernel:&lt;br /&gt;
&amp;lt;PRE&amp;gt;&lt;br /&gt;
$ uname -r&lt;br /&gt;
$ sudo aptitude install linux-headers-2.6.22-14-386&lt;br /&gt;
&amp;lt;/PRE&amp;gt;&lt;br /&gt;
Where &amp;quot;2.6.22-14&amp;quot; is the version reported by uname.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Bad file descriptor&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you get a &#039;Bad file descriptor&#039; message concerning the xorg.conf file try switching user to root and repeating the same command without sudo. This might be valid for the following commands too. (Ubuntu Gutsy installs with no password set for root by default. You can set a password for the root by typing &#039;sudo passwd root&#039; first.)&lt;br /&gt;
&lt;br /&gt;
===Configure the Driver===&lt;br /&gt;
*Note Method 2 Users: Before you carry out this step you must reboot your machine. Or else the fglrx driver will not be in use on xorg.conf and using the aticonfig options will cause a memory dump and not intialise the Driver properly.&lt;br /&gt;
*Note: An &#039;&#039;&#039;alternative&#039;&#039;&#039; to the &#039;&#039;&#039;aticonfig --initial&#039;&#039;&#039; command is to edit &#039;&#039;/etc/X11/xorg.conf&#039;&#039; and replace the string &amp;quot;ati&amp;quot; with &amp;quot;fglrx&amp;quot; in the &amp;quot;Device&amp;quot; section. This way you won&#039;t lose your old &amp;quot;Screen&amp;quot; and &amp;quot;Monitor&amp;quot; settings. Afterwards you can use aticonfig for setting overlay etc. Another alternative is &#039;&#039;&#039;aticonfig --initial --force&#039;&#039;&#039; if you encounter issues with the first command.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --initial&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Then:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --overlay-type=Xv&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*Note: Alternative in the overlay-type to &amp;quot;Xv&amp;quot; can be &amp;quot;opengl&amp;quot; or &amp;quot;disable&amp;quot; if the TV-out makes problems in videos.&lt;br /&gt;
&lt;br /&gt;
====Alternative: Configure the Driver, The Manual Way:====&lt;br /&gt;
An alternative to the &amp;quot;&#039;&#039;sudo aticonfig&#039;&#039;&amp;quot; commands is to edit &amp;quot;&#039;&#039;/etc/X11/xorg.conf&#039;&#039;&amp;quot; and change the &amp;quot;Device&amp;quot; section for the video card as shown below. This way you won&#039;t lose your old settings.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
gksu gedit /etc/X11/xorg.conf&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Device&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
#       Driver          &amp;quot;vesa&amp;quot;&lt;br /&gt;
	Driver		&amp;quot;fglrx&amp;quot;&lt;br /&gt;
	Option		&amp;quot;VideoOverlay&amp;quot;		&amp;quot;on&amp;quot;&lt;br /&gt;
	Option		&amp;quot;OpenGLOverlay&amp;quot;		&amp;quot;off&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== TV - Out ====&lt;br /&gt;
The composite TV-Out is not working simultaneously with the VGA on my System. To use it I have turned the VGA off and only the TV on. Attention! This command turns off your Monitor!!&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --enable-monitor=tv&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
To change back to VGA:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --enable-monitor=crt1&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Some have had luck with both mirrored.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --force-monitor=crt1&lt;br /&gt;
sudo aticonfig --enable-monitor=crt1,tv&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
reboot after that and it should mirror the CRT1 onto the TV.&lt;br /&gt;
&lt;br /&gt;
===Finish the Installation===&lt;br /&gt;
Now save any open document and reboot your system:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo shutdown -hr now&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*Note: An &#039;&#039;&#039;alternative&#039;&#039;&#039; to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as &amp;quot;drm&amp;quot; &amp;quot;radeon&amp;quot; or &amp;quot;fglrx&amp;quot; using the &amp;quot;rmmod&amp;quot; command. Example: &amp;lt;code&amp;gt;sudo rmmod fglrx&amp;lt;/code&amp;gt;&lt;br /&gt;
*Note: Another way to reboot:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo reboot&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Post-Installation Checks and Tweaks ==&lt;br /&gt;
===Verifying===&lt;br /&gt;
Run the following command to check its output to ensure the fglrx driver is installed properly:&lt;br /&gt;
&lt;br /&gt;
64bit Users only ( 32bit users can continue to the fglrxinfo test ), after rebooting you may have noticed that you cant open aticonfig and the fglrxinfo test below may not show ati in the info from the test, to fix this in terminal do the following command&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$fglrxinfo &lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI MOBILITY RADEON X300&lt;br /&gt;
OpenGL version string: 2.1.7415 Release&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
The &amp;lt;code&amp;gt;OpenGL vendor string&amp;lt;/code&amp;gt; should read &#039;&#039;&#039;ATI&#039;&#039;&#039; and not &#039;&#039;&#039;Mesa&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If it still says &#039;&#039;Mesa&#039;&#039; and not &#039;&#039;ATI&#039;&#039;, even after re-enabling the driver from the Restricted-manager:&#039;&#039;&#039;&lt;br /&gt;
You can try the following:&lt;br /&gt;
:*&amp;lt;pre&amp;gt;$ less /var/log/Xorg.0.log |grep EE&amp;lt;/pre&amp;gt; if this command returns &amp;lt;code&amp;gt;(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work&amp;lt;/code&amp;gt; then remove the kernel module and reinstall it.&lt;br /&gt;
:: &amp;lt;pre&amp;gt;$ sudo dkms remove -m fglrx -v 8.471 --all&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:*Remove all the packages provided by the &amp;lt;code&amp;gt;xserver-xorg-video-all&amp;lt;/code&amp;gt; meta-package (search for it using Synaptic or Adept), then restart the machine. The X Server should now use the new fglrx driver by force (provided the driver is being used in &#039;&#039;xorg.conf&#039;&#039;).&lt;br /&gt;
::If you can&#039;t log in after this, you&#039;ll have to log in to a terminal in the login screen, and reinstall the &amp;lt;code&amp;gt;xserver-xorg-video-all&amp;lt;/code&amp;gt; package. Your problem is probably somewhere else. (taken from [http://ubuntuforums.org/showpost.php?p=3655658&amp;amp;postcount=139]).&lt;br /&gt;
&lt;br /&gt;
:*Remove the package xserver-xgl. &lt;br /&gt;
::&#039;&#039;&#039;Explanation:&#039;&#039;&#039; 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&lt;br /&gt;
::&amp;lt;pre&amp;gt;DISPLAY=:0 glxinfo | grep render&amp;lt;/pre&amp;gt;&lt;br /&gt;
::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])&lt;br /&gt;
::&#039;&#039;&#039;Warning:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Note: Here is the [[glxinfo]] of a good install (for those interested).&lt;br /&gt;
&lt;br /&gt;
=== Enable laptop mode on battery power ===&lt;br /&gt;
&lt;br /&gt;
Enabling laptop mode on battery power gives you much better battery life, however be aware that sometimes it causes odd hangs.&lt;br /&gt;
&lt;br /&gt;
Switch ENABLE_LAPTOP_MODE to true  &lt;br /&gt;
{{Box File|/etc/default/acpi-support|&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Switch to laptop-mode on battery power - off by default as it causes odd&lt;br /&gt;
# hangs on some machines&lt;br /&gt;
ENABLE_LAPTOP_MODE=true&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Switch FGLRX_ACPI_SWITCH_POWERSTATES to true&lt;br /&gt;
{{Box File|/etc/default/fglrx|&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Uncomment the next line to enable powerstate switching on ACPI&lt;br /&gt;
# events for lid open/close and AC adapter on/off&lt;br /&gt;
FGLRX_ACPI_SWITCH_POWERSTATES=true&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Additional configure with aticonfig tool ===&lt;br /&gt;
You can configure the driver even further with the &#039;&#039;&#039;aticonfig&#039;&#039;&#039; tool, more information can be found at [[Configuring]].&lt;br /&gt;
&lt;br /&gt;
For example: &amp;lt;br&amp;gt;&lt;br /&gt;
* use powerplay option to switch power state for battery friendly or performance mode&lt;br /&gt;
* use dual head or one big desktop mode &lt;br /&gt;
* turn second monitor on/off on the fly&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Specific Issues==&lt;br /&gt;
&lt;br /&gt;
=== 3D desktop effects ===&lt;br /&gt;
The new ATI drivers use AIGLX so there is not need to install XGL that older drivers (&amp;lt; 8.40) required.&lt;br /&gt;
&lt;br /&gt;
Remove this section from to the /etc/X11/xorg.conf file.&lt;br /&gt;
The new xorg server enables &amp;quot;Composite&amp;quot; by default.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
#        Option  &amp;quot;Composite&amp;quot; &amp;quot;0&amp;quot;&lt;br /&gt;
# EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Compiz does not know about the fglrx driver. You can either skip the checks&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;mkdir -p ~/.config/compiz &amp;amp;&amp;amp; echo SKIP_CHECKS=yes &amp;gt;&amp;gt; ~/.config/compiz/compiz-manager&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or add it to the compiz white list, and clear the blacklist pci Ids variable &#039;&#039;&#039;*Recommended*&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo gedit /usr/bin/compiz&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# Driver whitelist&lt;br /&gt;
WHITELIST=&amp;quot;fglrx nvidia intel ati radeon i810&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# blacklist based on the pci ids &lt;br /&gt;
# BLACKLIST_PCIIDS=&amp;quot;$T&amp;quot;&lt;br /&gt;
BLACKLIST_PCIIDS=&amp;quot;&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You might have to modify the path for line 30 and 31&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   COMPIZ_BIN_PATH=&amp;quot;/usr/bin/&amp;quot; # For window decorators and compiz&lt;br /&gt;
   PLUGIN_PATH=&amp;quot;/usr/lib/compiz/&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
The COMPIZ_NAME on line 35 should also be modified accordingly&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   COMPIZ_NAME=&amp;quot;compiz.real&amp;quot; # Final name for compiz (compiz.real) &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the necessary configurations, just restart X and enjoy the cool effects.&lt;br /&gt;
&lt;br /&gt;
If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu [this line may instead be in /etc/xdg/compiz/compiz-manager] and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# . /etc/xdg/compiz/compiz-manager.ubuntu&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For Kubuntu you need some extra steps:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get install compiz compiz-kde compizconfig-settings-manager compiz-core compiz-fusion-plugins-main compiz-plugins&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To test 3D Effects, press ALT+F2 and type &amp;quot;compiz --replace&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
To configure use the tool KMenu-&amp;gt;Settings-&amp;gt;Avanced Desktop Effect Settings.&lt;br /&gt;
&lt;br /&gt;
=== Suspend/Hibernation work with 7.12===&lt;br /&gt;
&lt;br /&gt;
With Gutsy release, there was a big problem using the ATI proprietary drivers.  The Suspend/Hibernate function stopped working. The problem was due to the new SLUB allocator incorporated in 2.6.22 / 2.6.23 Kernel. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The problem has been solved in the AMD Catalyst 7.12 driver release.&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&#039;UPDATE: The problem has NOT been solved in the AMD Catalyst 7.12 driver release.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Suspend/hibernate is not working for FireGL 5250.&lt;br /&gt;
For FireGL 5200, suspend works with the 7.12 fglrx kernel module loaded (which did not work before this release) , but does not work if X is running.&lt;br /&gt;
&lt;br /&gt;
For Thinkpad T60 with ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:&lt;br /&gt;
&lt;br /&gt;
SAVE_VBE_STATE=false&lt;br /&gt;
&lt;br /&gt;
POST_VIDEO=false&lt;br /&gt;
&lt;br /&gt;
Even with the above settings (like POST_VIDEO=false, etc.) my ASUS Z96J with an X1600 does not suspend. &lt;br /&gt;
&lt;br /&gt;
This bug has been a serious issue for several months now.  There is a lot of frustration over this, because Ubuntu/Canonical has not been helpful.  They&#039;ve said things like suggesting not using fglrx (thanks a lot, that really helps).&lt;br /&gt;
&lt;br /&gt;
Current status on this bug can be found here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/&lt;br /&gt;
&lt;br /&gt;
===If you get  /usr/X11R6/lib/modules/dri/fglrx_dri.so not found===&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/ /usr/X11R6/lib/modules&lt;br /&gt;
&lt;br /&gt;
===If you get  /usr/X11R6/lib64/modules/dri/fglrx_dri.so not found===&lt;br /&gt;
&lt;br /&gt;
 sudo ln -s /usr/lib/ /usr/X11R6/lib64/modules&lt;br /&gt;
&lt;br /&gt;
===Segmentation Fault with glxinfo/fglrxinfo===&lt;br /&gt;
If &amp;lt;code&amp;gt;fglrxinfo&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;glxinfo&amp;lt;/code&amp;gt; returns a Segmentation fault like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ fglrxinfo&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon Xpress Series&lt;br /&gt;
OpenGL version string: 1.4 (2.1.7170 Release)&lt;br /&gt;
&lt;br /&gt;
Segmentation fault&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set output of libGL to verbose with&lt;br /&gt;
&amp;lt;pre&amp;gt;$ export LIBGL_DEBUG=verbose&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Run &amp;lt;code&amp;gt;fglrxinfo&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;glxinfo&amp;lt;/code&amp;gt; again&lt;br /&gt;
&amp;lt;pre&amp;gt;libGL: XF86DRIGetClientDriverName: 8.44.3 fglrx (screen 0)&lt;br /&gt;
libGL: OpenDriver: trying /usr/lib/dri/fglrx_dri.so&lt;br /&gt;
libGL error: dlopen /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: cannot open shared object file: Permission denied)&lt;br /&gt;
libGL error: unable to load driver: fglrx_dri.so&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon Xpress Series&lt;br /&gt;
OpenGL version string: 1.4 (2.1.7170 Release)&lt;br /&gt;
&lt;br /&gt;
Segmentation fault&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Don&#039;t know if its always fglrx_dri.so, but the fix is to add read permissions to the file.&lt;br /&gt;
&lt;br /&gt;
Check if read permission is not there&lt;br /&gt;
&amp;lt;pre&amp;gt;ls -l /usr/lib/dri/ |grep fglrx_dri&lt;br /&gt;
-rw-rw---- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add read permission&lt;br /&gt;
&amp;lt;pre&amp;gt;$ sudo chmod +r /usr/lib/dri/fglrx_dri.so&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Check read permission&lt;br /&gt;
&amp;lt;pre&amp;gt;ls -l /usr/lib/dri/ |grep fglrx_dri&lt;br /&gt;
-rw-rw-r-- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== libGL error ===&lt;br /&gt;
* fglrxinfo gives:  libGL.so.1: cannot open shared object file.&lt;br /&gt;
* Check the permission of the libGL.so.1.2 file with command:&lt;br /&gt;
  ls -l /usr/lib/libGL*&lt;br /&gt;
* The file permission of libGL.so.1.2 should be &amp;quot;-rw-rw-r--&amp;quot;.  If the permission reads &amp;quot;-rw-rw----&amp;quot;, do command&lt;br /&gt;
  sudo chmod o+r /usr/lib/libGL.so.1.2&lt;br /&gt;
* If the permission is correct, fixed with command:&lt;br /&gt;
 sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Monitor detection (1680x1050 Resolution Issue)--- SOLVED ===&lt;br /&gt;
&lt;br /&gt;
As specified in the release notes, &amp;quot;Connecting a display device that supports 1680x1050 to a system running Linux may result in a&lt;br /&gt;
maximum display resolution of 1280x1024 only being available&amp;quot;. (from [http://ubuntuforums.org/showthread.php?t=645974 thread])&lt;br /&gt;
&lt;br /&gt;
[&#039;&#039;&#039;It works with the latest driver&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
Fglrx driver does not detect some monitors correctly, so you have to do it manually (google about your monitor spec with keyword: xorg.conf).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;For example:&#039;&#039;&#039; Samsung 205BW 1680x1050 monitor needs manually set:  &lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Monitor&amp;quot;&lt;br /&gt;
       Option &amp;quot;DPMS&amp;quot;&lt;br /&gt;
       Identifier &amp;quot;samsung-monitor&amp;quot;&lt;br /&gt;
       VendorName &amp;quot;Samsung&amp;quot;&lt;br /&gt;
       ModelName &amp;quot;SyncMaster 205BW&amp;quot;&lt;br /&gt;
       HorizSync 31.4 - 80.0&lt;br /&gt;
       VertRefresh 56.000 - 75.000&lt;br /&gt;
       Modeline &amp;quot;1680x1050&amp;quot; 146.25 1680 1784 1960 2240 1050 1053 1059 1089&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;Screen&amp;quot;&lt;br /&gt;
	Identifier	&amp;quot;samsung-screen&amp;quot;&lt;br /&gt;
	Device		&amp;quot;samsung-device&amp;quot;&lt;br /&gt;
	Monitor		&amp;quot;samsung-monitor&amp;quot;&lt;br /&gt;
	Defaultdepth	24&lt;br /&gt;
	SubSection &amp;quot;Display&amp;quot;&lt;br /&gt;
		Depth	24&lt;br /&gt;
		Modes		&amp;quot;1680x1050&amp;quot;&lt;br /&gt;
	EndSubSection&lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== A possible problem with fglrx.ko conflicts ===&lt;br /&gt;
&lt;br /&gt;
NOTE: I&#039;ve run into strange problem building fglrx-kernel-source_8.443.1-1_i386.deb. If pentium-builder is installed, dkms fails to build fglrx.ko for make error (mixed implicit and static pattern rules. Stop.). It is caused by gcc.real and other indirections and wrong gcc version detection. Removing pentium-builder cures the problem.&lt;br /&gt;
&lt;br /&gt;
It&#039;s necessary, because sometimes this file is written by other packages, and so there&#039;s no 3D acceleration.&lt;br /&gt;
Check that the file /lib/modules/$(uname -r)/misc/fglrx.ko has been created.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create the following folder&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo mkdir /lib/modules/$(uname -r)/volatile&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: the volatile directory might already exist at this stage then simply continue with the next step. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create a symbolic link&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NOTE : On my Gutsy install, after a reboot this link was always removed automatically leaving me without an fglrx module loaded, and thus no ATI rendering. There have been several ways of getting around this suggested here, and here is the one that worked for me:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo gedit /etc/init.d/ati-module-fix&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And put this in it:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh -e&lt;br /&gt;
&lt;br /&gt;
# For loading ATI display drivers&lt;br /&gt;
&lt;br /&gt;
ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko&lt;br /&gt;
exit 0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make it executable&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo chmod ugo+x /etc/init.d/ati-module-fix&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now, make this run &#039;&#039;before&#039;&#039; gdm &lt;br /&gt;
&lt;br /&gt;
To check the gdm sequence number, &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ls /etc/rc2.d/&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The value for [seqno] in the section below should be the gdm sequence number -1.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo update-rc.d ati-module-fix defaults [seqno]&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hang at logout ===&lt;br /&gt;
&lt;br /&gt;
If you experience hangs when logging out (of X) try disabling atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo /usr/sbin/update-rc.d -f atieventsd remove&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Revert to Xorg driver ==&lt;br /&gt;
&lt;br /&gt;
If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo dpkg-reconfigure xserver-xorg&amp;lt;/pre&amp;gt;&lt;br /&gt;
and selecting the &amp;quot;ati&amp;quot; driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup. &lt;br /&gt;
&lt;br /&gt;
You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo apt-get install --reinstall libgl1-mesa-glx&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Frequently Asked Questions]]&lt;br /&gt;
*[[Performance Issues]]&lt;br /&gt;
*[[Troubleshooting]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;/div&gt;</summary>
		<author><name>24.84.57.90</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&amp;diff=4884</id>
		<title>Ubuntu Hardy Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&amp;diff=4884"/>
		<updated>2008-03-26T08:34:30Z</updated>

		<summary type="html">&lt;p&gt;24.84.57.90: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Pre-Installation Checks==&lt;br /&gt;
=== Enable &amp;quot;restricted&amp;quot; Repository ===&lt;br /&gt;
Make sure the &#039;&#039;restricted&#039;&#039; repository is enabled in &#039;&#039;/etc/apt/sources.list&#039;&#039; or this guide will not work!&lt;br /&gt;
&lt;br /&gt;
System &amp;gt; Administration &amp;gt; Software Sources.  Check &amp;quot;Proprietary Drivers for Devices (Restricted)&amp;quot; box.&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
For most users it won&#039;t be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the &amp;quot;ATI accelerated graphics driver&amp;quot;. Ubuntu will then install and configure the driver for you. If this does not provide the optimal solution you were looking for, please read ahead.&lt;br /&gt;
&lt;br /&gt;
=== Method 1: Install the driver the Ubuntu Way ===&lt;br /&gt;
&lt;br /&gt;
This will install the current driver in Ubuntu&#039;s repository. It may be older than the one AMD has released, but as of writing, Catalyst 8.3 is in the repositories. It would seem that Ubuntu gets new builds for the Catalyst drivers a few weeks after AMD releases them.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update	&lt;br /&gt;
sudo apt-get install linux-restricted-modules-generic restricted-manager&lt;br /&gt;
sudo apt-get install xorg-driver-fglrx&lt;br /&gt;
sudo depmod -a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The second line may not be necessary as you may already have restricted modules installed. Run it just in case. If the third line fails, you probably don&#039;t have the restricted repository enabled. See Pre-Installation.&lt;br /&gt;
&lt;br /&gt;
After this, you&#039;ll may need to edit Xorg.conf:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo nano /etc/X11/xorg.conf&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the device section, if it is not already there add:&lt;br /&gt;
&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
Driver     &amp;quot;fglrx&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Then to make sure Xorg is set up correctly, you&#039;ll have to let aticonfig &amp;quot;initialize&amp;quot; it:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --initial -f&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After this you should be able to restart your computer and have the driver working. To test type&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
fglrxinfo&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
into a terminal. If the vendor string is not ATI, you&#039;ve done something wrong.&lt;br /&gt;
&lt;br /&gt;
=== Method 2: Manual Method ===&lt;br /&gt;
&lt;br /&gt;
Download the installer:&lt;br /&gt;
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-3-x86.x86_64.run ati-driver-installer-8-3-x86.x86_64.run] (this installer is for 32bit &#039;&#039;&#039;and&#039;&#039;&#039; 64bit systems)&lt;br /&gt;
&lt;br /&gt;
Switch to the directory you downloaded this into and the run the following. (Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update&lt;br /&gt;
sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This installs the dependencies for the installer.&lt;br /&gt;
&lt;br /&gt;
Using Synaptic, completely remove any packages containing &amp;quot;fglrx&amp;quot; in their name.&lt;br /&gt;
&lt;br /&gt;
If using 64bit make sure to collect package &amp;quot;ia32-libs&amp;quot; and &amp;quot; libGL.so.1&amp;quot; before proceeding!&lt;br /&gt;
&lt;br /&gt;
Now use the following command to create the .deb files you will be using for installation:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo sh ati-driver-installer-8-3-x86.x86_64.run --buildpkg Ubuntu/hardy&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As an alternative, you can just use&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo ./ati-driver-installer-8-3-x86.x86_64.run --buildpkg Ubuntu --autopkg&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If i am not mistaken that alternative will not work if you just copy and paste it. You can run this exact command.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo sh ./ati-driver-installer-8-3-x86.x86_64.run --buildpkg Ubuntu --autopkg&lt;br /&gt;
&amp;lt;/pre&lt;br /&gt;
&lt;br /&gt;
which will download all the needed packages by itself and also automatically detects the Ubuntu version used.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now we have to blacklist the driver in Ubuntu&#039;s repository. This is so it doesn&#039;t ever overwrite our installation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo nano /etc/default/linux-restricted-modules-common&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add &amp;quot;fglrx&amp;quot; to the line &amp;quot;DISABLED_MODULES&amp;quot;&lt;br /&gt;
{{Box File|/etc/default/linux-restricted-modules-common|&lt;br /&gt;
&amp;lt;pre&amp;gt;DISABLED_MODULES=&amp;quot;fglrx&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please note that after the modification above, the &amp;quot;Restricted Driver Manager&amp;quot; will signal &amp;quot;ATI accelerated graphics driver&amp;quot; not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: &amp;quot;in use&amp;quot; (green light), but NOT enabled. It simply means that the fglrx module contained in the linux-restricted-modules package is not enabled, but another fglrx module (8.3) is in use.&lt;br /&gt;
&lt;br /&gt;
You may also need to edit the file (if it exists):&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo nano /etc/modprobe.d/blacklist-restricted&amp;lt;/pre&amp;gt;&lt;br /&gt;
Put a # in front of the line &amp;quot;blacklist fglrx&amp;quot;, if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.&lt;br /&gt;
&lt;br /&gt;
Remove any old fglrx .debs:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo rm /usr/src/fglrx-kernel*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Install .debs:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dpkg -i xorg-driver-fglrx_8.471-0*.deb fglrx-kernel-source_8.471-0*.deb fglrx-amdcccle_8.471-0*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Additional 64-bit instructions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you have a 64 bit install, the above dpkg command will likely complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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 amdccle package:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get install -f&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Catalyst 8.3 on 64-bit systems requires the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.471-0*.deb fglrx-kernel-source_8.471-0*.deb fglrx-amdcccle_8.471-0*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now you&#039;ll have to edit your xorg.conf and add the line driver &amp;quot;fglrx&amp;quot; to the Device section. Then run &amp;quot;sudo aticonfig --initial -f&amp;quot; in a terminal. If it does not error you should be fine. Finally reboot the computer and type&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
fglrxinfo&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully.&lt;/div&gt;</summary>
		<author><name>24.84.57.90</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Mandriva&amp;diff=490</id>
		<title>Mandriva</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Mandriva&amp;diff=490"/>
		<updated>2007-05-05T18:28:23Z</updated>

		<summary type="html">&lt;p&gt;24.84.172.249: update (by Adam Williamson, awilliamson A T mandriva D 0 T com)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;ATI commercial driver is included in commercial editions (Mandriva Linux Discovery, Mandriva Linux Powerpack, Mandriva Linux Powerpack+) and in the freely downloadable Mandriva Linux One hybrid live / install CD edition. Commercial driver is not included in freely downloadable Mandriva Linux Free traditional installer edition. ATI commercial driver is available from public non-free section on official mirrors for Mandriva Linux 2007 Spring and later. ATI commercial driver is available from third-party PLF repository for all currently supported Mandriva Linux releases.&lt;br /&gt;
&lt;br /&gt;
== Installation from official mirrors (Mandriva Linux 2007 Spring and later) ==&lt;br /&gt;
&lt;br /&gt;
Ensure non-free repository is set up on your system. Follow instructions at [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software#Making_more_applications_available Mandriva Wiki].&lt;br /&gt;
&lt;br /&gt;
Using Mandriva software installation tools - either rpmdrake or urpmi - install the packages &#039;&#039;&#039;dkms-ati&#039;&#039;&#039; and &#039;&#039;&#039;ati&#039;&#039;&#039; (some other packages will probably be pulled in as dependencies). See [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software Mandriva Wiki] for more instructions on installing packages.&lt;br /&gt;
&lt;br /&gt;
Re-configure graphics card using XFdrake configuration utility (in the Mandriva Control Center, go to &#039;&#039;&#039;Hardware&#039;&#039;&#039; then &#039;&#039;&#039;Set up the graphical server&#039;&#039;&#039;). Select the proprietary driver when offered the choice. Restart the system. Note that &#039;&#039;&#039;aticonfig&#039;&#039;&#039; utility is not currently available in official packages: if you need it, use PLF driver as instructed below.&lt;br /&gt;
&lt;br /&gt;
== Installation from PLF third party repository ==&lt;br /&gt;
&lt;br /&gt;
Set up PLF non-free repository on your system. Use [http://plf.zarb.org/easyurpmi Easy URPMI] or [http://www.mandrivauser.de/smarturpmi Smart URPMI] to generate an urpmi.addmedia command to run at a console as root. See [http://wiki.mandriva.com/en/Docs/Basic_tasks/Being_root Mandriva Wiki] for more instructions on running commands as root.&lt;br /&gt;
&lt;br /&gt;
Using Mandriva software installation tools - either rpmdrake or urpmi - install the packages &#039;&#039;&#039;dkms-ati&#039;&#039;&#039; and &#039;&#039;&#039;ati&#039;&#039;&#039; (some other packages will probably be pulled in as dependencies). See [http://wiki.mandriva.com/en/Docs/Basic_tasks/Installing_and_removing_software Mandriva Wiki] for more instructions on installing packages.&lt;br /&gt;
&lt;br /&gt;
Re-configure graphics card using XFdrake configuration utility (in the Mandriva Control Center, go to &#039;&#039;&#039;Hardware&#039;&#039;&#039; then &#039;&#039;&#039;Set up the graphical server&#039;&#039;&#039;). Select the proprietary driver when offered the choice. Restart the system.&lt;br /&gt;
&lt;br /&gt;
== Installation with ATI installer (not recommended: use only if you cannot use the above methods) ==&lt;br /&gt;
&lt;br /&gt;
First of all, you have to install kernel sources:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ su&lt;br /&gt;
# urpmi kernel-source&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, download ati installer and launch it:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# chmod +x ati-driver-installer-X.X.X.run&lt;br /&gt;
# ./ati-driver-installer-X.X.X.run&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Follow the instructions.&lt;br /&gt;
&amp;lt;!-- Dead link alert...&lt;br /&gt;
&amp;lt;HR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Slightly more information to be found here: &amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;3D Acceleration for ATI cards (works for SuSE, Mandriva and Debian)&amp;quot; at&lt;br /&gt;
&lt;br /&gt;
http://linux.coconia.net/general/ati.htm&amp;lt;br&amp;gt;&lt;br /&gt;
http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{VCT}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Distributions]]&lt;/div&gt;</summary>
		<author><name>24.84.172.249</name></author>
	</entry>
</feed>