cchtml.com - User contributions [en]

Ubuntu Gutsy Installation Guide

2013-06-26T14:48:54Z

180.194.172.28:

== Installation ==

For most users it won'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 "ATI accelerated graphics driver". 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. ''[http://januvialawyers.fotopages.com/ Januvia Lawyers Blog]''

===Method 1: Install the Driver the Ubuntu Way===
This will install the driver that is currently in the repositories. It may be older than the current version from AMD.
<pre>
sudo apt-get update
sudo apt-get install linux-restricted-modules-generic restricted-manager
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
</pre>

The second line of the above may not be necessary. If apt says it cannot find the "linux-restricted-modules" package, try line 3. If that fails, check your sources.list (see top of page)

If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.

===Method 2: Install the Catalyst Driver Manually===

:''This is just an alternative installation method for the section above. It might help if you still get 'DRI missing' errors.''

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

Change to the directory you downloaded the file. Make sure that you have the ''universe'' and ''multiverse'' repositories enabled in ''/etc/apt/sources.list'' before doing these steps.

There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].

By default, Ubuntu did not enable the Universe and Multiverse repositories, but now in Gutsy, both Universe and Multiverse are activated by default.

''Install necessary tools:''
{{Box Terminal|
sudo apt-get update

sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

''Uninstall previous fglrx:''
Using Synaptic, completely remove any packages containing "fglrx" in their name.

If using 64bit make sure to collect package "ia32-libs" before you continue!

''Create .deb packages:''
{{Box Terminal|
sudo sh {{catalystfilename}} --buildpkg Ubuntu/gutsy
}}
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.

As an alternative, you can just use
{{Box Terminal|
sudo sh ./{{catalystfilename}} --buildpkg Ubuntu --autopkg
}}
which will download all the needed packages by itself and also automatically detects the Ubuntu version used.

If this step fails on amd64/x86_64 with a <tt>No such file or directory</tt> message about missing files in <tt>X11R6/lib</tt>, [http://emmetcaulfield.net/Tech/Ubuntu64+ATI follow these instructions] and come back here. Also check that your download path does not contain spaces.

''Blacklist old fglrx module from linux-restricted-modules:''

As Ubuntu Gutsy's ''linux-restricted-modules'' 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.

Ubuntu/Gnome users type in:
<pre>gksu gedit /etc/default/linux-restricted-modules-common</pre>

Kubuntu/KDE users type in:
<pre>kdesu kate /etc/default/linux-restricted-modules-common</pre>

Add "fglrx" to the line "DISABLED_MODULES"
{{Box File|/etc/default/linux-restricted-modules-common|
<pre>DISABLED_MODULES="fglrx"</pre>
}}
Please note that after the modification above, the "Restricted Driver Manager" will signal "ATI accelerated graphics driver" not enabled (unticked). This is perfectly correct. At the end of the installation procedure it will signal in Status: "in use" (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.

You may also need to edit the file (if it exists):
<pre>gksu gedit /etc/modprobe.d/blacklist-restricted</pre>
Put a # in front of the line "blacklist fglrx", if it is present. Otherwise, the kernel module will not load automatically, and you will not get 3D acceleration.

''Remove any old fglrx debs from /usr/src/:''
<pre>
sudo rm /usr/src/fglrx-kernel*.deb
</pre>

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.476-0*.deb fglrx-kernel-source_8.476-0*.deb fglrx-amdcccle_8.476-0*.deb
</pre>

''Additional 64-bit instructions''

If you have a 64 bit install, the above dpkg command will likely complain that "Errors were encountered while processing: fglrx-amdcccle". This is because of a dependency of the amdccle package on 32 bit libraries. If you receive this error, issue the following command after the above dpkg command, which will force the installation of all of the 32 bit dependencies, and then the amdccle package:

<pre>
sudo apt-get install -f
</pre>

Catalyst 8.3 on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
<pre>
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
</pre>

Im not wrhoty to be in the same forum. ROTFL

===Configure the Driver===
*NOTE THIS WILL ERASE SETTINGS IN /etc/X11/xorg.conf you should be sure there is a backup.
*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.
*Note: An '''alternative''' to the '''aticonfig --initial''' command is to edit ''/etc/X11/xorg.conf'' and replace the string "ati" with "fglrx" in the "Device" section. This way you won't lose your old "Screen" and "Monitor" settings. Afterwards you can use aticonfig for setting overlay etc. Another alternative is '''aticonfig --initial --force''' if you encounter issues with the first command.
<pre>
sudo aticonfig --initial
</pre>
Then:
<pre>
sudo aticonfig --overlay-type=Xv
</pre>
*Note: Alternative in the overlay-type to "Xv" can be "opengl" or "disable" if the TV-out makes problems in videos.

====Alternative: Configure the Driver, The Manual Way:====
An alternative to the "''sudo aticonfig''" commands is to edit "''/etc/X11/xorg.conf''" and change the "Device" section for the video card as shown below. This way you won't lose your old settings.
<pre>
gksu gedit /etc/X11/xorg.conf
</pre>
<pre>
Section "Device"
[...]
# Driver "vesa"
Driver "fglrx"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
[...]
EndSection
</pre>

==== TV - Out ====
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!!
<pre>
sudo aticonfig --enable-monitor=tv
</pre>
To change back to VGA:
<pre>
sudo aticonfig --enable-monitor=crt1
</pre>
Some have had luck with both mirrored.
<pre>
sudo aticonfig --force-monitor=crt1
sudo aticonfig --enable-monitor=crt1,tv
</pre>
reboot after that and it should mirror the CRT1 onto the TV.

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -hr now
</pre>
*Note: An '''alternative''' to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as "drm" "radeon" or "fglrx" using the "rmmod" command. Example: <code>sudo rmmod fglrx</code>
*Note: Another way to reboot:
<pre>
sudo reboot
</pre>

== Post-Installation Checks and Tweaks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:

<pre>
$fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X300
OpenGL version string: 2.1.7415 Release
</pre>

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
<pre>
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1
</pre>

The <code>OpenGL vendor string</code> should read '''ATI''' and not '''Mesa'''.

'''If it still says ''Mesa'' and not ''ATI'', even after re-enabling the driver from the Restricted-manager:'''
You can try the following:
:*<pre>$ less /var/log/Xorg.0.log |grep EE</pre> if this command returns <code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code> then remove the kernel module and reinstall it.
:: <pre>$ sudo dkms remove -m fglrx -v 8.471 --all</pre>

:*Remove all the packages provided by the <code>xserver-xorg-video-all</code> 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 ''xorg.conf'').
::If you can't log in after this, you'll have to log in to a terminal in the login screen, and reinstall the <code>xserver-xorg-video-all</code> package. Your problem is probably somewhere else. (taken from [http://ubuntuforums.org/showpost.php?p=3655658&postcount=139]).

:*Remove the package xserver-xgl.
::'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
::<pre>DISPLAY=:0 glxinfo | grep render</pre>
::If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])
::'''Warning:''' This might make your compiz stop working as it is configured to use XGl. A solution might be to run the Envy script in order to configure compiz.

Note: Here is the [[glxinfo]] of a good install (for those interested).

=== Enable laptop mode on battery power ===

Enabling laptop mode on battery power gives you much better battery life, however be aware that sometimes it causes odd hangs.

Switch ENABLE_LAPTOP_MODE to true
{{Box File|/etc/default/acpi-support|
<pre>
# Switch to laptop-mode on battery power - off by default as it causes odd
# hangs on some machines
ENABLE_LAPTOP_MODE=true
</pre>
}}

Switch FGLRX_ACPI_SWITCH_POWERSTATES to true
{{Box File|/etc/default/fglrx|
<pre>
# Uncomment the next line to enable powerstate switching on ACPI
# events for lid open/close and AC adapter on/off
FGLRX_ACPI_SWITCH_POWERSTATES=true
</pre>
}}

=== Additional configure with aticonfig tool ===
You can configure the driver even further with the '''aticonfig''' tool, more information can be found at [[Configuring]].

For example: 
* use powerplay option to switch power state for battery friendly or performance mode
* use dual head or one big desktop mode
* turn second monitor on/off on the fly

==Specific Issues==

Your awnser was just what I needed. Its made my day!

=== Suspend/Hibernation work with 7.12===

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.

'''The problem has been solved in the AMD Catalyst 7.12 driver release.'''
'''UPDATE: The problem has NOT been solved in the AMD Catalyst 7.12 driver release.'''

Suspend/hibernate is not working for FireGL 5250.
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.

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:

SAVE_VBE_STATE=false

POST_VIDEO=false

Even with the above settings (like POST_VIDEO=false, etc.) my ASUS Z96J with an X1600 does not suspend.

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've said things like suggesting not using fglrx (thanks a lot, that really helps).

Current status on this bug can be found here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/121653/

===If you get /usr/X11R6/lib/modules/dri/fglrx_dri.so not found===

sudo ln -s /usr/lib/ /usr/X11R6/lib/modules

It may be necessary to create the /usr/X11R6/lib directory first:

sudo mkdir /usr/X11R6/lib

===If you get /usr/X11R6/lib64/modules/dri/fglrx_dri.so not found===

sudo ln -s /usr/lib/ /usr/X11R6/lib64/modules

===Segmentation Fault with glxinfo/fglrxinfo===
If <code>fglrxinfo</code> or <code>glxinfo</code> returns a Segmentation fault like this:
<pre>
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 1.4 (2.1.7170 Release)

Segmentation fault
</pre>

Set output of libGL to verbose with
<pre>$ export LIBGL_DEBUG=verbose</pre>

Run <code>fglrxinfo</code> or <code>glxinfo</code> again
<pre>libGL: XF86DRIGetClientDriverName: 8.44.3 fglrx (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/fglrx_dri.so
libGL error: dlopen /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx_dri.so: cannot open shared object file: Permission denied)
libGL error: unable to load driver: fglrx_dri.so
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 1.4 (2.1.7170 Release)

Segmentation fault</pre>

Don't know if its always fglrx_dri.so, but the fix is to add read permissions to the file.

Check if read permission is not there
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri
-rw-rw---- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so
</pre>

Add read permission
<pre>$ sudo chmod +r /usr/lib/dri/fglrx_dri.so</pre>

Check read permission
<pre>ls -l /usr/lib/dri/ |grep fglrx_dri
-rw-rw-r-- 1 root root 17462688 2008-01-13 17:42 fglrx_dri.so
</pre>

Now I know who the brainy one is, Ill keep lokinog for your posts.

=== Monitor detection (1680x1050 Resolution Issue)--- SOLVED ===

As specified in the release notes, "Connecting a display device that supports 1680x1050 to a system running Linux may result in a
maximum display resolution of 1280x1024 only being available". (from [http://ubuntuforums.org/showthread.php?t=645974 thread])

['''It works with the latest driver''']

Fglrx driver does not detect some monitors correctly, so you have to do it manually (google about your monitor spec with keyword: xorg.conf).

'''For example:''' Samsung 205BW 1680x1050 monitor needs manually set:
{{Box File|/etc/X11/xorg.conf|
<pre>
Section "Monitor"
Option "DPMS"
Identifier "samsung-monitor"
VendorName "Samsung"
ModelName "SyncMaster 205BW"
HorizSync 31.4 - 80.0
VertRefresh 56.000 - 75.000
Modeline "1680x1050" 146.25 1680 1784 1960 2240 1050 1053 1059 1089
EndSection

Section "Screen"
Identifier "samsung-screen"
Device "samsung-device"
Monitor "samsung-monitor"
Defaultdepth 24
SubSection "Display"
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
</pre>
}}

This has made my day. I wish all positngs were this good.

=== Hang at logout ===

If you experience hangs when logging out (of X) try disabling atieventsd with this command:

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

== Revert to Xorg driver ==

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

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:

<pre>sudo apt-get install --reinstall libgl1-mesa-glx</pre>

==See Also==
*[[Frequently Asked Questions]]
*[[Performance Issues]]
*[[Troubleshooting]]

[[Category:Installation Documentation]]

Ubuntu Oneiric Installation Guide

2013-06-26T13:53:13Z

180.194.172.28:

__TOC__

'''''[http://januvialawyers.tumblr.com/ Januvia Lawyers News Update]'''''

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

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

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

== Using Ubuntu-supplied fglrx/Catalyst ==

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

=== Command line ===

sudo apt-get install fglrx fglrx-amdcccle

=== GUI ===

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

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

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

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

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

sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=Updating Catalyst/fglrx=

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

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

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

If you receive

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

Change the third command above to:

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

= Issues =

== XvBA Video Acceleration ==

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

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

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

== Video Tearing ==

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

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

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

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

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

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

== Hybrid Graphics and Catalyst==

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

=== Intel/ATI Hybrids ===

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

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

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

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

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

sudo apt-get -f install

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

== Problems Starting Xserver ==

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

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

Reboot and check to see if things work now.

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

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

start on filesystem

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

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

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

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

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

== Hang at logout ==

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

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

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

This problem can be fixed permanently with:

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

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

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

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

== Suspend/Hibernation ==

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

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

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

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

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

sudo apt-get install fusion-icon

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== References ==

<references/>