cchtml.com - User contributions [en]

Ubuntu Jaunty Installation Guide

2009-05-21T16:27:40Z

78.53.230.129: /* Open Source Drivers */

__TOC__
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | '''ATTENTION UBUNTU JAUNTY USERS'''
|-
| Warning: Does not work for all system combinations at this time 
|}
= The Alternatives =
Users with ATI cards basically have these options:
# '''Open Source Drivers''' These are stable and nice, but currently have poor 3D performance, if any. If you have a Radeon X1k product or earlier, this is your only option.
# '''The Ubuntu Way''' Use the restricted-driver management system that comes with Ubuntu to install the drivers.
# '''Third (Fourth?) Party Installer''' Use envy/jockey or other installer helper.
# '''Install the drivers manually''' Using the installer downloaded from AMD's site via either package based install or direct install.

= Open Source Drivers =
By default, Ubuntu will already try to use one of the open source drivers for your hardware. If the feature set and stability work for you, then you don't need to change anything.

The drivers that may be used are
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.
* '''ati''' Actually a facade that will invoke the radeon driver.
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.
* '''radeonhd''' An alternate driver support R520 hardware and later.

By default there is no configuration file for X anymore, so X will try to do the right thing.

If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/ mainline-2.6.29.3] did the trick on a few machines.

There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.

= The Ubuntu way =

== Restricted Drivers Manager ==
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available
* Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"
* Ubuntu will then install and configure the driver for you

Note that you will be restricted to the drivers for you version of Ubuntu that Canonical deem as stable. This may not give you the latest drivers, but should be safest.

= Installing the drivers manually =
*PLEASE READ FIRST!
This portion of the guide works, since I have used it myself. I guess the rest of the guide is broken or it may be because the new driver doesn't support any of the older ATI cards anymore. Which cards does ATI no longer support?
''The ATI Radeon 9500-9800,X300-X2100,Xpress. See the complete list [http://wiki.cchtml.com/index.php/9.4] here.''
If your card is on that list, you are restricted to the 9.3 driver - however since 9.3 driver doesn't support xorg-xserver 1.6, it will not work with Jaunty! This guide currently is for installing 9.4. !!!SO BE CAREFUL!!!

_______________________________________________

I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.

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

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

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

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

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

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

Make sure your directory path does not contain spaces

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

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

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

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

===''4. Install .debs.''===

Install the debs, depending on if you're on a 32-bit or 64-bit system:

* For 32-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}

(This may fail due to a missing dpmk. If so install this first. Also check the version numbers (8.561) against the created debs)

* For 64-bit systems

{{Box Terminal|
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb
}}
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''

=== ''5. Additional 64-bit instructions'' ===

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

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

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




===''6. Generate a new /etc/Xorg.conf file''===
{{Box Terminal|
sudo aticonfig --initial -f
}}
in a terminal. If it doesn't give an error you should be good.

===''7. Force use of /etc/Xorg.conf file''===
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>
}}

===''8. Test your installation''===
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 9.4 looks like:
<pre>
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 2.1.8591
</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.

=HOW TO UPDATE DRIVER=

To update your driver to a new version (say 9.3 to 9.4) first disable the current driver through Ubuntu's Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for "xorg-driver-fglrx" without the quotes and mark it for "Complete removal" and hit "Apply" then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal: {{Box Terminal|sudo aticonfig --initial -f
}}

and

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

then reboot.

It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the driver then reinstalled it, it worked perfectly.

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

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

= Issues =

== Installation ==
There are some system configurations on which '''none''' of the installation alternatives work with the latest 9.4 driver (please add; also please add if you got it to work in one of the listed setups):
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4870X2: Framebuffer error, garbled screen.
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.

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

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

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

----

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

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

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

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

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

----

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

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

== Hang at logout ==

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

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

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

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

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

<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre>

<pre>sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre>

(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)

<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre>

just reboot login and ctrl+alt+backspace to try

== Suspend/Hibernation ==

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

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

<pre>
SAVE_VBE_STATE=false

POST_VIDEO=false

ENABLE_LAPTOP_MODE=false
</pre>

<blockquote>
Comment: This is a little surprising, since the comments at the beginning of /etc/default/acpi-support seem to make it quite clear that those settings are ignored unless you add "acpi-support" to SUSPEND_METHODS. --[[User:Bewst|Bewst]] 23:22, 19 December 2008 (UTC)
</blockquote>

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

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

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

== Can't remove fglrx with dpkg ==

If dpkg really-really refuses to remove an older fglrx-package, it might be needed to edit /var/lib/dpkg/diversions and remove a few lines. This is a hack and should be avoided.

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

If you get this error-message, simply uninstall the previous version before installing the new one with:
{{Box Terminal|
sudo dkms remove -m fglrx -v 8.522 --all
}}

== New kernel installed? ==
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.
You can do that by these simple steps:
{{Box Terminal|
sudo dkms build -m fglrx -v 8.552 -k `uname -r` 
sudo dkms install -m fglrx -v 8.552 -k `uname -r`
}}
[[Category:Installation Documentation]]
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf

Ubuntu Hardy Installation Guide

2009-01-14T10:26:21Z

78.53.43.142: /* Suspend/Hibernation */

For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the "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.

After installation, in GNOME or Kubuntu, '''turn off visual effects''' or you will notice a flicker in OpenGL.

== Method 1: Install the driver the Ubuntu Way ==

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by the Ubuntu people. Catalyst 8.3 is in the repositories.

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

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 '''[...]'''

{{Box File|/etc/X11/xorg.conf|
Section "Device"
:[...] 
:Driver "fglrx" 
:Option "VideoOverlay" "on" 
:Option "OpenGLOverlay" "off" 
:[...] 
EndSection
}}

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.

On newer cards the options below enables Visual Effects and video to be played without flicker. The Textured video option can be turned on, but this can cause flicker or diagonal artifacts when playing videos.

{{Box File|/etc/X11/xorg.conf|
Section "Device"
:[...] 
:Driver "fglrx" 
:Option "VideoOverlay" "off" 
:Option "OpenGLOverlay" "on" 
:Option "TexturedVideo" "off" 
:[...] 
EndSection
}}

== Method 2: Manual Install Method ==

''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.
For example:<pre>cd Desktop</pre>

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

===''4. Add driver to kernel module blacklist.''===
'''NOTE''': This step is no longer necessary with fglrx 8-10. Just jump to step 5 in that case.

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 ({{catalystversion}}) 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.''===

'''For 32 Bits'''

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

Starting from 8-10 version of the driver, installing the following package ensures compatibility with restricted drivers' manager:

{{Box Terminal|
$ sudo dpkg -i fglrx-modaliases_8.561-0ubuntu1_i386.deb
}}

64 bit systems should have the same behaviour.
{{Box Terminal|
sudo dpkg -i fglrx-modaliases_8.561-0ubuntu1_amd64.deb
}}

'''For 64 Bits'''

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.561-0ubuntu1_amd64.deb fglrx-kernel-source_8.561-0ubuntu1_amd64.deb fglrx-amdcccle_8.561-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.561*.deb fglrx-kernel-source_8.561-0*.deb fglrx-amdcccle_8.561-0*.deb
}}

When installing the packages, if <tt>xorg-driver-fglrx_8.552</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].

===Fix for an error:===
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:
{{Box Terminal|
$ 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 
}}

=== Finishing the Install: Configuration ===

If you've used fglrx previously, you will not need to do this.
Run
<pre>sudo aticonfig --initial -f</pre>

Now you'll likely have to edit your xorg.conf (even if just to confirm the above command added the apropriate fglrx line):
<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>
Make the appropriate changes to "TexturedVideo" and "Overlay", etc., as described above in the "automatic section".
Save and exit, then
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:
<pre>
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1
</pre>
Finally, reboot the computer and type
<pre>
fglrxinfo
</pre>
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.

=== Removing Mesa drivers ===
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:

*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:
{{Box Terminal|
$ uname -r
}}
: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].

== Specific Issues ==

===Segmentation Fault with glxinfo/fglrxinfo===

If you experience such errors (and have ''glxinfo'' report ''"Direct rendering"'' as ''No'' despite following the whole procedure without any errors) you may want to have a look at the '''Specific Issues''' chapter of the '''Ubuntu Gutsy Installation Guide''' [[http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#If_you_get__.2Fusr.2FX11R6.2Flib.2Fmodules.2Fdri.2Ffglrx_dri.so_not_found]] as this may be due to missing links or wrong permissions.

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

Resume from suspend failed when using dual monitor configuration in xorg.conf.
E.g. when using
<pre>
aticonfig --initial=dual-head --screen-layout=right
</pre>
Switching back to a single monitor configuration and restarting the xserver (though not beautiful) solves this.

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

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 Hardy Installation Guide

2009-01-14T10:23:56Z

78.53.43.142: /* Suspend/Hibernation */

For most users it won't be necessary to go into installation and configuration details of the driver. Ubuntu 8.04 (Hardy) provides a notification saying that there are restricted drivers available. You just have to go there (Restricted Drivers Manager) and enable the "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.

After installation, in GNOME or Kubuntu, '''turn off visual effects''' or you will notice a flicker in OpenGL.

== Method 1: Install the driver the Ubuntu Way ==

This will install the current driver in Ubuntu's repository. It is older than the one AMD has released, but will be supported by the Ubuntu people. Catalyst 8.3 is in the repositories.

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

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 '''[...]'''

{{Box File|/etc/X11/xorg.conf|
Section "Device"
:[...] 
:Driver "fglrx" 
:Option "VideoOverlay" "on" 
:Option "OpenGLOverlay" "off" 
:[...] 
EndSection
}}

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.

On newer cards the options below enables Visual Effects and video to be played without flicker. The Textured video option can be turned on, but this can cause flicker or diagonal artifacts when playing videos.

{{Box File|/etc/X11/xorg.conf|
Section "Device"
:[...] 
:Driver "fglrx" 
:Option "VideoOverlay" "off" 
:Option "OpenGLOverlay" "on" 
:Option "TexturedVideo" "off" 
:[...] 
EndSection
}}

== Method 2: Manual Install Method ==

''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.
For example:<pre>cd Desktop</pre>

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

===''4. Add driver to kernel module blacklist.''===
'''NOTE''': This step is no longer necessary with fglrx 8-10. Just jump to step 5 in that case.

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 ({{catalystversion}}) 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.''===

'''For 32 Bits'''

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

Starting from 8-10 version of the driver, installing the following package ensures compatibility with restricted drivers' manager:

{{Box Terminal|
$ sudo dpkg -i fglrx-modaliases_8.561-0ubuntu1_i386.deb
}}

64 bit systems should have the same behaviour.
{{Box Terminal|
sudo dpkg -i fglrx-modaliases_8.561-0ubuntu1_amd64.deb
}}

'''For 64 Bits'''

{{Box Terminal|
$ sudo dpkg -i xorg-driver-fglrx_8.561-0ubuntu1_amd64.deb fglrx-kernel-source_8.561-0ubuntu1_amd64.deb fglrx-amdcccle_8.561-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.561*.deb fglrx-kernel-source_8.561-0*.deb fglrx-amdcccle_8.561-0*.deb
}}

When installing the packages, if <tt>xorg-driver-fglrx_8.552</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].

===Fix for an error:===
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:
{{Box Terminal|
$ 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 
}}

=== Finishing the Install: Configuration ===

If you've used fglrx previously, you will not need to do this.
Run
<pre>sudo aticonfig --initial -f</pre>

Now you'll likely have to edit your xorg.conf (even if just to confirm the above command added the apropriate fglrx line):
<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>
Make the appropriate changes to "TexturedVideo" and "Overlay", etc., as described above in the "automatic section".
Save and exit, then
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:
<pre>
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1
</pre>
Finally, reboot the computer and type
<pre>
fglrxinfo
</pre>
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.

=== Removing Mesa drivers ===
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:

*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:
{{Box Terminal|
$ uname -r
}}
: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].

== Specific Issues ==

===Segmentation Fault with glxinfo/fglrxinfo===

If you experience such errors (and have ''glxinfo'' report ''"Direct rendering"'' as ''No'' despite following the whole procedure without any errors) you may want to have a look at the '''Specific Issues''' chapter of the '''Ubuntu Gutsy Installation Guide''' [[http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#If_you_get__.2Fusr.2FX11R6.2Flib.2Fmodules.2Fdri.2Ffglrx_dri.so_not_found]] as this may be due to missing links or wrong permissions.

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

Resume from suspend failed when using dual configuration.
E.g. when using
<pre>
aticonfig --initial=dual-head --screen-layout=right
</pre>

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

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

Debian

2008-06-11T17:13:02Z

78.53.121.233: spam removed

== Installation ==
* [[Debian_Installation_Guide|Installation Guide]](recomended for x86_64 users)

Another installation Guide:

* [http://m.domaindlx.com/LinuxHelp/ati/ati.htm 3D Acceleration for your ATI card] (works for SUSE, Mandriva and Debian x86. X86_64 users should not use).

== Tips and Tricks ==
* To build your own .deb packages you will need to install at least the following packages from the apt repositories:
** fakeroot
** debhelper
** build-essential
** make
** module-assistant
* [http://debianhelp.co.uk Debian Help]
* [http://forums.debian.net Debian Forums]

== Related Resources ==
* [http://www.stanchina.net/~flavio/debian-official/fglrx-driver.html Flavio Stanchina's ATI Linux driver packages for Debian]

* Debian [http://wiki.debian.org/AtiHowTo wiki] page refering ATI.
{{VCT}}
[[Category:Distributions]]