cchtml.com - User contributions [en]

Ubuntu Intrepid Installation Guide

2008-11-02T00:02:37Z

66.171.137.121: /* Finishing the Install: Configuration */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

For Ubuntu

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/default/linux-restricted-modules-common
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):

For Ubuntu

{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo gedit /etc/modprobe.d/blacklist-local 
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-local
}}

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.

===''5. Install .debs.''===
For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}

or for 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf

For Ubuntu

<pre>sudo gedit /etc/X11/xorg.conf</pre>

For Kubuntu

<pre>sudo nano /etc/X11/xorg.conf </pre>

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

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T22:41:16Z

66.171.137.121: /* Finishing the Install: Configuration */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

For Ubuntu

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/default/linux-restricted-modules-common
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):

For Ubuntu

{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo gedit /etc/modprobe.d/blacklist-local 
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-local
}}

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.

===''5. Install .debs.''===
For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}

or for 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf

For Ubuntu

<pre>sudo gedit /etc/X11/xorg.conf</pre>

For Kubuntu

<pre>sudo nano /etc/X11/xorg.conf ;kubuntu</pre>

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

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T22:39:56Z

66.171.137.121: /* 4. Add driver to kernel module blacklist. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

For Ubuntu

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/default/linux-restricted-modules-common
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):

For Ubuntu

{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo gedit /etc/modprobe.d/blacklist-local 
}}

For Kubuntu

{{Box Terminal|
sudo nano /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-local
}}

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.

===''5. Install .debs.''===
For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}

or for 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
<pre>sudo nano /etc/X11/xorg.conf ;kubuntu</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T22:34:33Z

66.171.137.121: /* 5. Install .debs. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===
For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}

or for 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
<pre>sudo nano /etc/X11/xorg.conf ;kubuntu</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:12:55Z

66.171.137.121: /* Finishing the Install: Configuration */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
<pre>sudo nano /etc/X11/xorg.conf ;kubuntu</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:10:27Z

66.171.137.121: /* Additional 64-bit instructions */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:09:07Z

66.171.137.121: /* 3. Create .deb packages. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:08:37Z

66.171.137.121: /* 1. Install necessary build tools. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
sudo apt-get update 
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
$ sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:07:58Z

66.171.137.121: /* Installation */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
sudo apt-get update 
sudo apt-get install linux-restricted-modules-generic restricted-manager 
sudo apt-get install xorg-driver-fglrx 
sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
sudo gedit /etc/X11/xorg.conf 
sudo nano /etc/X11/xorg.conf ;kubuntu
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
$ sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:04:53Z

66.171.137.121: /* 4. Add driver to kernel module blacklist. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install linux-restricted-modules-generic restricted-manager 
$ sudo apt-get install xorg-driver-fglrx 
$ sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
$ sudo gedit /etc/X11/xorg.conf
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
$ sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
$ fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
$ sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
sudo gedit /etc/default/linux-restricted-modules-common 
sudo nano /etc/default/linux-restricted-modules-common;kubuntu
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local 
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T16:02:50Z

66.171.137.121: /* 4. Add driver to kernel module blacklist. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install linux-restricted-modules-generic restricted-manager 
$ sudo apt-get install xorg-driver-fglrx 
$ sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
$ sudo gedit /etc/X11/xorg.conf
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
$ sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
$ fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
$ sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
$ sudo gedit /etc/default/linux-restricted-modules-common
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
sudo gedit /etc/modprobe.d/blacklist-restricted 
sudo nano /etc/modprobe.d/blacklist-restricted ;kubuntu 
sudo gedit /etc/modprobe.d/blacklist-local
sudo nano /etc/modprobe.d/blacklist-local ;kubuntu
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Intrepid Installation Guide

2008-11-01T15:58:38Z

66.171.137.121: /* 5. Install .debs. */

= Installation Guide for Ubuntu Intrepid (v 8.10) =

== The three alternatives ==

ATI has a bad track-record when it comes to drivers for Linux. There are countless stories about black screens, hours of configuring X, installing drivers and swearing at the computer.
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, there has arised a slight hope for better drivers for ATI-cards on Linux.

However, creating better drivers takes some time, so while the people at AMD are doing their thing, people with ATI cards basically have these options:
# Use the open source drivers. These are stable and nice, but currently they have poor 3D-performance, if any. If that's not a problem, they are the Right Choice (tm).
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jocky/"restricted" packages).
# Install the drivers manually. This should be your last resort, and may not even work.

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

These comes with the X.org X server:
* vesa
* ati
* radeon
* radeonhd

The "ati" driver will automatically choose the best driver for your video card. There is no need to change it from "ati" or even create an xorg.conf file in most cases. The xorg.conf file is being deprecated.

= Installing the restricted drivers "the Ubuntu way" =

== Restricted Drivers Manager ==
For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.10 (Intrepid) 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.

== Installation ==

Just use the hardware manager on the system menu (jocky-gtk), or this:

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by Ubuntu.
Note that there are different version-numbers for Catalyst itself and the amdccle program that comes with Catalyst!

{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install linux-restricted-modules-generic restricted-manager 
$ sudo apt-get install xorg-driver-fglrx 
$ sudo depmod -a 
}}

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't have the restricted repository enabled. See Pre-Installation.

After this, you may need to edit Xorg.conf:

{{Box Terminal|
$ sudo gedit /etc/X11/xorg.conf
}}

In the device section, if it is not already there add:

{{Box File|/etc/X11/xorg.conf|
Driver "fglrx"
}}

Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:

{{Box Terminal|
$ sudo aticonfig --initial -f
}}

aticonfig must be used every time you change xorg.conf!

After this you should be able to restart your computer and have the driver working. To test type

{{Box Terminal|
$ fglrxinfo
}}

into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]

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

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

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

= Installing the restricted drivers manually =

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

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

===''1. Install necessary build tools.''===
{{Box Terminal|
$ sudo apt-get update 
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
}}

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

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

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

===''3. Create .deb packages.''===
{{Box Terminal|
$ sh {{catalystfilename}} --buildpkg Ubuntu/intrepid
}}
("intrepid" is not a typo)

===''4. Add driver to kernel module blacklist.''===
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.

{{Box Terminal|
$ sudo gedit /etc/default/linux-restricted-modules-common
}}

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.10) is in use.

You may also need to edit the file(s) (if they exist):
{{Box Terminal|
$ sudo gedit /etc/modprobe.d/blacklist-restricted 
$ sudo gedit /etc/modprobe.d/blacklist-local
}}

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.

===''5. Install .debs.''===

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.542-0ubuntu1_amd64.deb fglrx-kernel-source_8.542-0ubuntu1_amd64.deb fglrx-amdcccle_8.542-0ubuntu1_amd64.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

== Additional 64-bit instructions ==

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

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

Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:
{{Box Terminal|
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.542-0ubuntu1_i386.deb fglrx-kernel-source_8.542-0ubuntu1_i386.deb fglrx-amdcccle_8.542-0ubuntu1_i386.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

When installing the packages, if <tt>xorg-driver-fglrx_8.542</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].
If you get problems with dkms, you can patch the temporary sources and compile them yourself: http://www.phoronix.com/forums/showthread.php?t=12546

If you can't get past these problems, consider using Hardy and just upgrading the kernel manually and installing the packages you need from Intrepid. "EnvyNG" is also an idea.

== Finishing the Install: Configuration ==

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

Now you'll have to edit your xorg.conf
<pre>sudo gedit /etc/X11/xorg.conf</pre>
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''':
<pre>Section "Device"
[...]
Driver "fglrx"
[...]
EndSection</pre>
Save and exit, then run
{{Box Terminal|
$ sudo aticonfig --initial -f
}}
in a terminal. If it does not error you should be fine.

Some people find that changes to xorg.conf don't get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:

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

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

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

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

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

= Issues =

== Couldn't find library libfglrx_gamma.so.1 ==
If you are having this error:
<pre>
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').
</pre>

Fix it by doing the following:
<pre>
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver
cd driver/arch/x86_64/usr/X11R6/lib64
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
cd ../../../../../
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy
</pre>

== Mesa drivers ==
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:

*Remove the package xserver-xgl.
:<pre>sudo apt-get remove xserver-xgl</pre>
:'''Explanation:''' If you installed this previously in order to make compiz work, it will not allow direct rendering on your display. You can check out if this is what it causing the problem by running
:<pre>DISPLAY=:0 glxinfo | grep render</pre>
:If it returns an ATI renderer, it means that xgl is being displayed indirectly on the display 1. (Taken from [http://ubuntuforums.org/showthread.php?t=740287])

:'''Warning:''' This might make your compiz stop working as it is configured to use XGL. A solution might be to run the Envy script in order to configure compiz. Or, if Compiz stopped working due to "Composite" problem, check that the following is set in the /etc/X11/xorg.conf
<pre>
Section "Extensions"
Option "Composite" "Enable"
EndSection
</pre>

----

*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are:
:(EE) fglrx(0): [agp] unable to acquire AGP, error -1023
:(EE) fglrx(0): cannot init AGP
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
:(WW) fglrx(0): * DRI initialization failed! *

:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart a some others:
<pre>rmmod i82875p_edac
rmmod fglrx
rmmod intel-agp
rmmod agpgart
modprobe agpgart
modprobe intel-agp
modprobe fglrx</pre>

:Blacklist the modules e7xxx_edac so it doesn't start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:
:<pre>blacklist i82875p_edac</pre>

:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).

:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu

----

*Check you are running the correct kernel.
:'''Explanation:''' If you're upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.
:Run in a terminal:
:<pre>uname -r</pre>
:If the output starts with 2.6.22 or below you are not using the current kernel and the Ati drivers will not load properly.

If this doesn't help, try [[Ubuntu Gutsy Installation Guide#Verifying]], or other links: [http://wiki.cchtml.com/index.php/Troubleshooting#No_3D_acceleration], [http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian], [http://ubuntuforums.org/archive/index.php/t-475699.html].

== Hang at logout ==

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

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

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

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

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This sort of trickery should be avoided until you've tried absolutely everything else, though.

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

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

[[Category:Installation Documentation]]

Ubuntu Gutsy Installation Guide

2008-03-05T22:37:41Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[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 '''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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.471-0*.deb fglrx-kernel-source_8.471-0*.deb fglrx-amdcccle_8.471-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:35:09Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[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 '''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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:13:25Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[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 '''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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:12:44Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.03-x86.x86_64.run ati-driver-installer-8.03-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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:11:54Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-03-x86.x86_64.run ati-driver-installer-8-03-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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:08:25Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[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 '''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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:04:42Z

66.171.112.211: /* Method 2: Install the Catalyst 8.3 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.03-x86.x86_64.run ati-driver-installer-8.03-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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8.03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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 Gutsy Installation Guide

2008-03-05T22:03:35Z

66.171.112.211: /* Method 2: Install the Catalyst 8.2 Driver Manually */

==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===
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 8.3 Driver Manually===

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

*Note: ''The newest 8.455.2 does not enable DRI using gutsy. It needs a more recent X.org for this, but 2D does work.'' "(II) fglrx(0): driver needs X.org 7.1.x.y with x.y >= 0.0"

*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'"''.'' (Follow these instructions for a workaround: http://64studio.com/node/150#comment-1148)

Download the ATI driver installer:
[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-03-x86.x86_64.run ati-driver-installer-8-03-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 build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms
</pre>

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

''Create .deb packages:''
<pre>
sudo sh ati-driver-installer-8-03-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. The same error may result from insufficient disk space.

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 downloadpath 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 (7.12) 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.455.2-0*.deb fglrx-kernel-source_8.455.2-0*.deb fglrx-amdcccle_8.455.2-0*.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 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>

Nevertheless the previous command is always recommended.

*Note: I attempted the above and received the following error message:

<pre>
Error! Your kernel source for kernel 2.6.22-14-386 cannot be found at
/lib/modules/2.6.22-14-386/build or /lib/modules/2.6.22-14-386/source.
</pre>

Google eventually lead me to 1) the [http://www2.ati.com/drivers/linux/linux_8.16.20.html ATI release notes] and
2) the Feisty installation guide here [[Ubuntu_Feisty_Installation_Guide]], both of which lead me to suspect that I need to install kernel sources or kernel headers.

However, I already have the linux-headers-generic package installed. Somebody on #ubuntu recommended that I install the specific headers package for my kernel:

<PRE>
$ uname -r
$ sudo aptitude install linux-headers-2.6.22-14-386
</PRE>

This seemed to fix it, the aptitude command installed the headers and then proceeded to complete the installation of fglrx-kernel-source_8.452.1-1*.deb.

===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 brute''' 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 Radeon Xpress Series
OpenGL version string: 2.1.7281 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:
:*<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.452.1 --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]).

'''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:
$ ls -l /usr/lib/libGL*
* The file permission should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
$ sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
<pre>$ sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1</pre>

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

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

You might have to modify the path for line 30 and 31
<pre>
COMPIZ_BIN_PATH="/usr/bin/" # For window decorators and compiz
PLUGIN_PATH="/usr/lib/compiz/"
</pre>
The COMPIZ_NAME on line 35 should also be modified accordingly
<pre>
COMPIZ_NAME="compiz.real" # Final name for compiz (compiz.real)
</pre>

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

If it still does not work, locate /etc/xdg/compiz/compiz-manager.ubuntu and see if it contains an infinite loop in it. If it does, comment out the line that causes the infinite loop.
<pre>
# . /etc/xdg/compiz/compiz-manager.ubuntu
</pre>

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.

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

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

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

=== libGL error ===
* fglrxinfo gives: libGL.so.1: cannot open shared object file.
* Check the permission of the libGL.so.1.2 file with command:
ls -l /usr/lib/libGL*
* The file permission of libGL.so.1.2 should be "-rw-rw-r--". If the permission reads "-rw-rw----", do command
sudo chmod o+r /usr/lib/libGL.so.1.2
* If the permission is correct, fixed with command:
sudo ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1

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

=== A possible problem with fglrx.ko conflicts ===

NOTE: I'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.

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, and here is the one that worked for me:

<pre>
sudo gedit /etc/init.d/ati-module-fix
</pre>

And put this in it:
<pre>
#!/bin/sh -e

# For loading ATI display drivers

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

</pre>

Make it executable

<pre>
sudo chmod ugo+x /etc/init.d/ati-module-fix
</pre>

Now, make this run ''before'' gdm

To check the gdm sequence number,
<pre>
ls /etc/rc2.d/
</pre>

The value for [seqno] in the section below should be the gdm sequence number -1.

<pre>
sudo update-rc.d ati-module-fix defaults [seqno]
</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]]