cchtml.com - User contributions [en]

Talk:Ubuntu Gutsy Installation Guide

2007-11-25T20:50:06Z

87.2.201.133: cleaned

== Method 2 for Catalysy 7.11 ==
Done.

== Suspend/Hibernation with Catalyst 7.11 & Gutsy ==
I hoped that with these drivers and Gutsty, the suspend problem would have been solved. Unfortunately it isn't for me.
I tried also to apply the patches to "acpi-support" (like doing with Feisty) but unsuccessfully.
Any working experiences? Solutions? Workarounds?

== installation hint ==

I followed this guide and fglrxinfo yielded the desired output.

But then I still got the following problems:
* crash/restart of X when trying to run glxgears
* crash/restart of X when trying to watch mythtv recording
* visual artefacts from window creation

The cause I assumed in that:

<code>glxinfo | grep direct</code>

did not yield 'yes' but 'no' and 'Mesa Indirect'

Long search, quick solution:

<code>sudo apt-get remove xserver-xgl</code>

'''Note:''' I don't really know what this actually does in the context of a desired installation, so try at your own risk. I assume this being installed from my earlier Feisty installation where I tried out compiz and AIGLX was not supported by the driver.

After removing the xserver-xgl package, all problems described above vanished.

Maybe someone with more detailed knowledge might find it useful to add a paragraph to the page.

Comment: I had a lot of trouble until I found your solution. Removing xserver-xgl made most of the graphical artifacts disappear (I still have some black bars in the bottom right corner of one screen), and made my dual screen setup work again. Should this be in the general guide?

Comment: I was seeing some very similar behavior after following this tutorial. glxgears would cause gdm to crash and the artifacts were left on the screen. The system would also be dog slow, moving windows was very laggy. Removing xserver-xgl did the trick for me!

== still Mesa ==

Hi,

I never had problems until Gutsy & 7.11 came:
(bmhm@Sentinux)[~] $ cat /var/log/Xorg.0.log | grep "(WW)"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *

and

(bmhm@Sentinux)[~] $ cat /var/log/Xorg.0.log | grep "(EE)"
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1000)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(EE) AIGLX: Screen 0 is not DRI capable

Any Ideas? It did work before (on feisty, using older drivers)!! Help!! --[[User:212.62.64.34|212.62.64.34]] 14:08, 22 November 2007 (CST)

I SOLVED (subvertigo):
The problem was the fglrx.ko . The symbolic link have been overwritten at each reboot.
Check if the fglrx.ko in the "volatile" folder is a symbolic link or not to that in the "misc" folder (Gnome reports an arrow on the icon if it is, and must have the same dimension). If it is the same problem see the first paragraph to see how I solved.

The symbolic link is gone after a reboot. Filesize of the one in the misc folder is 2084611 bytes and the one in the volatile folder is 1058754 bytes. I don't know where/what this copying is done. :(

Performing the following command:

find / -name 'fglrx*.ko'

Results in:

/lib/modules/2.6.22-14-generic/volatile/fglrx.ko
/lib/modules/2.6.22-14-generic/misc/fglrx.ko

So where this 1058754 bytes sized version exists on the system is unclear to me.

== (Partially) Installed but 7.11 Driver NOT used ==

The catalyst control center is available under "accessories" and list the following.

Software:
* Driver version : 8.43.2
* Catalyst Control Center Version : 1.6

OpenGL:
* .. Provider : Mesa project ...
* .. Renderer : Mesa GLX Indirect
* .. Version : 1.4 (2.1 Mesa 7.0.1)

Checklist:
* "Restricted" repositories not commented
* The "restricter driver manager" says that the driver is enabled and in use.
* Symbolic link exists

Really don't know what the problem is.

EDIT (subvertigo) The problem is almost surely the "fglrx.ko"... see the first paragraph for the solution.
Moreover the "restricted manager" should say that the driver is NOT enabled (equivalent to blacklist the original "fglrx" in linux-restricted-modules-common).

== Method 1 fails, since xorg-driver-fglrx and fglrx kernel module versions differ ==
xorg-driver-fglrx is version is 8.38.7-1 and the fglrx kernel module version in linux-restricted-modules-generic is still 8.37.6.

Xorg complains:
ad@homer:~$ cat /var/log/Xorg.0.log | grep "(EE)"
(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
(EE) AIGLX: Screen 0 is not DRI capable

Talk:Ubuntu Gutsy Installation Guide

2007-11-24T15:37:20Z

87.2.201.133: /* (Partially) Installed but 7.11 Driver NOT used */

== Need update the topic to Catalyst 7.11 ==
Can anyone update the installation method 2 to AMD Catalyst 7.11?
The procedure is the same or not? Has hanyone tested it?

-> I just tested the procedure. It is the (nearly) same ...
Found some issues till it worked for me.

sudo gedit /etc/init.d/ati-module-fix

In ati-module-fix I replaced

ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/
with
ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko

after savig the file
sudo chmod +x /etc/init.d/ati-module-fix

In my installation gdm starts with sequence 13. So I did

sudo update-rc.d ati-module-fix defaults 12

"If you check the box to enable the restricted driver and reboot, it should work."

If I check the the box in "resricted manager" the line
DISABLED_MODULES="fglrx"
in etc/default/linux-restricted-modules-common is changed back to
DISABLED_MODULES=""
I leaved it unchecked now.

So my "restricted manager" reports for the ATI driver
activated: no in use: yes

EDIT (subvertigo): doesn't work for me... then I solved removing the surrounding IF statement in the ati-module-fix ! Now it works!
Can you explain me how find gdm sequence number (i don't know what it is).

EDIT (exyll): Removing the IF statement does NOT work for me. On my system GDM is listed as 30gdm. You can retrieve the sequence number(s) by running the following statement:

ls /etc/rc2.d/

== Updated some information only applicable for Gutsy ==
I've updated some minor details about the fglrx-installation in Gutsy:
* By default, Gutsy (and Feisty too) now have Universe and Multiverse enabled
* The fglrx-version in Gutsy's linux-restricted-modules is 8.37.6 and not 8.28.8
[[User:Jealma|Jealma]] 04:35, 19 October 2007 (CDT)

== libGL error ==
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Fixed with command:
sudo ln /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

== installation hint ==

I followed this guide and fglrxinfo yielded the desired output.

But then I still got the following problems:
* crash/restart of X when trying to run glxgears
* crash/restart of X when trying to watch mythtv recording
* visual artefacts from window creation

The cause I assumed in that:

<code>glxinfo | grep direct</code>

did not yield 'yes' but 'no' and 'Mesa Indirect'

Long search, quick solution:

<code>sudo apt-get remove xserver-xgl</code>

'''Note:''' I don't really know what this actually does in the context of a desired installation, so try at your own risk. I assume this being installed from my earlier Feisty installation where I tried out compiz and AIGLX was not supported by the driver.

After removing the xserver-xgl package, all problems described above vanished.

Maybe someone with more detailed knowledge might find it useful to add a paragraph to the page.

Comment: I had a lot of trouble until I found your solution. Removing xserver-xgl made most of the graphical artifacts disappear (I still have some black bars in the bottom right corner of one screen), and made my dual screen setup work again. Should this be in the general guide?

Comment: I was seeing some very similar behavior after following this tutorial. glxgears would cause gdm to crash and the artifacts were left on the screen. The system would also be dog slow, moving windows was very laggy. Removing xserver-xgl did the trick for me!

== still Mesa ==

Hi,

I never had problems until Gutsy & 7.11 came:
(bmhm@Sentinux)[~] $ cat /var/log/Xorg.0.log | grep "(WW)"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *

and

(bmhm@Sentinux)[~] $ cat /var/log/Xorg.0.log | grep "(EE)"
(EE) fglrx(0): [pcie] Failed to gather memory of size 262144Kb for PCIe. Error (-1000)
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(EE) AIGLX: Screen 0 is not DRI capable

Any Ideas? It did work before (on feisty, using older drivers)!! Help!! --[[User:212.62.64.34|212.62.64.34]] 14:08, 22 November 2007 (CST)

NEW (by subvertigo):
I have the same identical problem (identical logs). Before with Feisty+8.43.2 or Gutsy+8.43.2 i had no problems... :-(
My pc is a Dell Inspiron 6400 with ATI X1400.
fglrinfo reports using Mesa drivers.

I tried to add or remove "fglrx" from /etc/default/linux-restricted-modules-common and it has no effects. The "restricted manager" signals that ati driver is not in use when fglrx is blacklisted. I don't understand if it have to be blacklisted or not.

I SOLVED (subvertigo):
The problem was the fglrx.ko . The symbolic link have been overwritten at each reboot.
Check if the fglrx.ko in the "volatile" folder is a symbolic link or not to that in the "misc" folder (Gnome reports an arrow on the icon if it is, and must have the same dimension). If it is the same problem see the first paragraph to see how I solved.

The symbolic link is gone after a reboot. Filesize of the one in the misc folder is 2084611 bytes and the one in the volatile folder is 1058754 bytes. I don't know where/what this copying is done. :(

Performing the following command:

find / -name 'fglrx*.ko'

Results in:

/lib/modules/2.6.22-14-generic/volatile/fglrx.ko
/lib/modules/2.6.22-14-generic/misc/fglrx.ko

So where this 1058754 bytes sized version exists on the system is unclear to me.

==Install .deb packages: ==

Update for the 7.11 article.

Previous:

sudo dpkg -i xorg-driver-fglrx_8.42.3-1*.deb \
fglrx-kernel-source_8.42.3-1*.deb \
fglrx-amdcccle_8.42.3-1*.deb

7.11:

sudo dpkg -i xorg-driver-fglrx_8.433-1_i386.deb \
fglrx-kernel-source_8.433-1_i386.deb \
fglrx-amdcccle_8.433-1_i386.deb

== (Partially) Installed but 7.11 Driver NOT used ==

The catalyst control center is available under "accessories" and list the following.

Software:
* Driver version : 8.43.2
* Catalyst Control Center Version : 1.6

OpenGL:
* .. Provider : Mesa project ...
* .. Renderer : Mesa GLX Indirect
* .. Version : 1.4 (2.1 Mesa 7.0.1)

Checklist:
* "Restricted" repositories not commented
* The "restricter driver manager" says that the driver is enabled and in use.
* Symbolic link exists

Really don't know what the problem is.

EDIT (subvertigo) The problem is almost surely the "fglrx.ko"... see the first paragraph for the solution.
Moreover the "restricted manager" should say that the driver is NOT enabled (equivalent to blacklist the original "fglrx" in linux-restricted-modules-common).

Talk:Ubuntu Gutsy Installation Guide

2007-11-24T15:36:05Z

87.2.201.133: /* (Partially) Installed but 7.11 Driver NOT used */

Talk:Catalyst 7.11

2007-11-22T16:04:52Z

87.2.201.133:

Where does it state that it solves the Suspend/Hibernation problems?

RE: It fully support the 2.6.23, and that means that it support SLUB memory allocator, so the problems are solved. http://www.phoronix.com/scan.php?page=article&item=922&num=1
The SLUB memory allocator is the default also with Ubuntu 7.10 (2.6.22 kernel, now).

Talk:Main Page

2007-11-22T15:18:03Z

87.2.201.133: /* Catalyst Linux 7.11 */

NEW VERSION https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-7-11-x86.x86_64.run

Please read about OGP at http://wiki.duskglow.com/tiki-index.php?page=Open-Graphics

== Wiki name ==

"Unofficial ATI Linux Driver Wiki" is a very ambiguous and confusing title for
this page - it sounds like a wiki for an unofficial ATI Linux driver, but in
fact is an unofficial Wiki for Ati's proprietory Linux driver. "ATI Linux Driver,
unofficial Wiki" would be a rather clearer title. Othe3rwise, people looking for
info on the fully open source driver for ATI video cards would think this was a
good place to start looking. A.E.R.Waddington, UK.
: I have edited the title to be more appropriate. Thanks for the suggestion. [[User:Mooninite|Mooninite]] 11:33, 4 December 2006 (CST)
: Any chance that you could update the graphic / logo to reflect the less ambiguous name as well? [[User:Riaanvn|Riaanvn]] 00:13, 2 November 2007 (CDT)

== Pages that aren't really pages ==

# [[ATI Radeon Xpress 1150]]
# [[Holarse]]
# [[InTheNews]]
# [[InTheNewsBySite]]
# [[Index.php]]

== 8.42.3 ==

[http://www.phoronix.com/scan.php?page=article&item=887&num=1 It's out]. — [[User:SheeEttin|SheeEttin]] {[[User_talk:SheeEttin|T]]/[[Special:Contributions/SheeEttin|C]]} 14:06, 23 October 2007 (CDT)

== Catalyst Linux 7.11 ==

[http://www.phoronix.com/scan.php?page=article&item=922&num=1 It's out]. — [[User:gollum12345678|gollum12345678]] {[[User_talk:gollum12345678|T]]/[[Special:Contributions/gollum12345678|C]]} 20:35, 21 November 2007 (CDT)

I made the new release page. http://wiki.cchtml.com/index.php/Catalyst_7.11

== RedHat Enterprise -> Red Hat Enterprise Linux ==

I mistakenly created an ugly double-redirect from RedHat Enterprise to Red Hat Enterprise (Since there should be a space in the company name), to Red Hat Enterprise Linux (since this is the official name of the Red Hat family of Linux products, and just calling it Red Hat Enterprise is somewhat of a "bastardization" (with all respect), even though I can understand that you guys want to try and avoid the proliferation of having "Linux" in every distribution name. '''Question''': will someone with edit permissions to the wiki home page please change RedHat Enterprise to Red Hat Enterprise Linux . Thank you very much.

[[User:Riaanvn|Riaanvn]] 23:41, 1 November 2007 (CDT)

Catalyst 7.11

2007-11-22T15:12:50Z

87.2.201.133: ATI Catalyst Linux 7.11 driver release

ATI Catalyst Linux 7.11 driver

Release date: November 21, 2007

The new driver release carry a new name (the same used for the Windows counterpart) and version numbering (7.11 stays for year 2007, month November). It is still a proprietary closed-source driver.

The main improvement is the full support to 2.6.23 kernel. This solves the Suspend/Hibernation problems recently found due to the incompatibilities between older fglrx driver and SLUB memory allocator (default in the 2.6.23 kernel).

==External links==

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

[[Category:Releases]]

Ubuntu Gutsy Installation Guide

2007-11-22T14:48:56Z

87.2.201.133: /* Attention: Suspend/Hibernation will not work */

The [[:Category:Releases|latest]] fglrx driver supports Radeon 9500 and the X-series cards up to HD2900. Workstation cards are not supported.

==Pre-Installation Checks==
=== Enable "restricted" Repository ===
Make sure the ''restricted'' repository is enabled in ''/etc/apt/sources.list'' or this guide will not work!

System > Administration > Software Sources. Check "Proprietary Drivers for Devices (Restricted)" box.

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

===Method 1: Install the Driver the Ubuntu Way===
<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>

Note: 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.

(Note: This method did not work with ATI X1300 Radeon on Gutsy whereas method 2 worked perfectly for us. 26/10/2007)

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

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

*Note: ''If you are running the -rt kernel, you will fail to compile the kernel module with ''"FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol '__rcu_read_lock'"''.''

Download the ATI driver installer:
[http://www2.ati.com/drivers/linux/ati-driver-installer-8.42.3-x86.x86_64.run ati-driver-installer-8.42.3-x86.x86_64.run] (this installer is for 32bit '''and''' 64bit systems)

Change to the download directory. 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:''
<pre>
sudo apt-get update
sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper \
debconf libstdc++5 linux-headers-generic
</pre>

''Create .deb packages:''

<pre>
sudo bash ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Ubuntu/gutsy
</pre>
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.

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.

''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>
}}

''Install .deb packages:''

<pre>
sudo dpkg -i xorg-driver-fglrx_8.42.3-1*.deb \
fglrx-kernel-source_8.42.3-1*.deb \
fglrx-amdcccle_8.42.3-1*.deb
</pre>

*Note: If you get a 'Bad file descriptor' 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 'sudo passwd root' first.)

*Note: 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 recieve 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 pacakge:

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

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

''Fix broken dependencies''
*Note: ''You only need to do this if you have installed previous versions of these drivers using this method before.''
<pre>
sudo apt-get -f install
</pre>

''Compile the kernel module:''
<pre>
sudo module-assistant prepare,update
sudo module-assistant build,install fglrx -f
sudo depmod -a
</pre>

It's necessary, because sometimes this file is written by other packages, and so there's no 3D acceleration.
Check that the file /lib/modules/$(uname -r)/misc/fglrx.ko has been created.

''Create the following folder''

<pre>
sudo mkdir /lib/modules/$(uname -r)/volatile
</pre>

Note: the volatile directory might already exist at this stage then simply continue with the next step.

''Create a symbolic link''

<pre>
sudo ln -sf /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</pre>

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, but my experience with recent installs and updates still leads to a MESA driver being installed. This became very frustrating as I tried every method and step here with no success. A new way around this is to let the old MESA fglrx load, then as a final step in the boot process, edit rc.local :

<pre>
sudo gedit /etc/rc.local
</pre>

copy these two line at the beginning of the file right on top of the command "set 0" :
<pre>
rmmod fglrx
insmod /lib/modules/$(uname -r)/misc/fglrx.ko
</pre>

This removes the Ubuntu fglrx module in the first line, and then the second line loads the newly installed one. This should now force the ATI module in and you should get the correct results in the following steps.

'''IMPORTANT''': You have to recompile the kernel module after each kernel update!
(Note: This does not affect you until the next time you update your kernel.)

===Configure the Driver===
*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: Is there an alternative to the previous step?

===Finish the Installation===
Now save any open document and reboot your system:
<pre>
sudo shutdown -r 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>

== Post-Installation Checks ==
===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 Radeon Xpress Series
OpenGL version string: 2.0.6958 Release
</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:
:*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]).

'''If it says '' libGL.so.1: cannot open shared object file: No such file or directory''...'''
Check if you have a ''/usr/lib/libGL.so.1.2'', if so do this:
<pre>sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

If you see a message like "Xlib: extension "XFree86-DRI" missing on display ":0.0"." you may simply need to enable the restricted drivers.

Ubuntu and Kubuntu use a Restricted-Driver manager to load/unload non-FOSS drivers. Even if they are installed and specified in the xorg.conf does not mean they'll load properly.

To start the restricted manager in both Ubuntu & Kbuntu:
<pre>sudo /usr/bin/restricted-manager</pre>

If you check the box to enable the restricted driver and reboot, it should work.

=== 3D desktop effects ===
The new ATI drivers use AIGLX so there is not need to install XGL that older drivers (< 8.40) required.

Remove this section from to the /etc/X11/xorg.conf file.
The new xorg server enables "Composite" by default.
<pre>
# Section "Extensions"
# Option "Composite" "0"
# EndSection
</pre>

Compiz does not know about the fglrx driver. You can either skip the checks

<pre>mkdir -p ~/.config/compiz && echo SKIP_CHECKS=yes >> ~/.config/compiz/compiz-manager</pre>

or add it to the compiz white list, and clear the blacklist pci Ids variable '''*Recommended*'''

<pre>sudo gedit /usr/bin/compiz</pre>

<pre>
# Driver whitelist
WHITELIST="fglrx nvidia intel ati radeon i810"
</pre>

<pre>
# blacklist based on the pci ids
# BLACKLIST_PCIIDS="$T"
BLACKLIST_PCIIDS=""
</pre>

After the necessary configurations, just restart X and enjoy the cool effects.

For Kubuntu you need some extra steps:
<pre>
sudo apt-get install compiz compiz-kde compizconfig-settings-manager compiz-core compiz-fusion-plugins-main compiz-plugins
</pre>

To test 3D Effects, press ALT+F2 and type "compiz --replace".

To configure use the tool KMenu->Settings->Avanced Desktop Effect Settings.

=== 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: <br>
* 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

==Ubuntu-specific Issues==

=== If installing on Ubuntu x64... ===

(thanks to Michael at Phoronix forums and aolana at Ubuntuforums.org)

Building packages for Ubuntu 64-Bit is known to be broken. If you're installing on Ubuntu 64-Bit, do this:

Download this: [http://www.michaellarabel.com/downloads/fglrx-8.42-ubuntu+debian-2.tar.bz2 fglrx-8.42-ubuntu+debian-2.tar.bz2]

Extract the installer:

<pre>
bash ati-driver-installer-8.42.3-x86.x86_64.run --extract somedirectory
</pre>

Extract the archive you downloaded to the directory that you extracted the driver's installation files to.

Then build the package:

<pre>
./ati-installer.sh 8.42.3 --buildpkg Ubuntu/gutsy
</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</pre>

=== Attention: Suspend/Hibernation will not work===

With Gutsy release, there's a big problem using the ATI proprietary drivers. The Suspend/Hibernate function will stop working.
The problem is due to the new SLUB allocator incorporated in 2.6.22 / 2.6.23 Kernel.
There are no workaround, except:

- Return to Feisty (with 2.6.20 kernel, and apply specific solutions: see Feisty installation guide).

- Use default Mesa Drivers (the easiest way is to disable ATI driver from Restricted Driver Manager).

- Recompiler your Kernel to use SLAB.

Unfortunately some new ATI cards couldn't start X with Mesa drivers, so the only workaround is returning to Feisty.

The problem has been solved in the AMD Catalysy 7.11 driver release (fully supporting the 2.6.23 kernel).

A similar problem appears with nVidia cards. No explanation or workaround has been forthcoming.

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

[[Category:Installation Documentation]]