Jump to: navigation, search

Ubuntu Natty Installation Guide

503 bytes added, 00:11, 30 January 2013
Protected "Ubuntu Natty Installation Guide": Excessive vandalism (‎[edit=autoconfirmed] (indefinite) ‎[move=autoconfirmed] (indefinite))
This package contains both the 32-bit and 64-bit driver.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget <nowiki></nowiki>{{Catalystdashversion}}
===''Create .deb packages.''===
$ sh ./atiamd-driver-installer-{{Catalystdashversion}} --buildpkg Ubuntu/natty
===''Install .debs.''===
==== Generic Config ====
This will work for most people:
$ sudo aticonfig amdconfig --initial -f
==== Minimal Config ====
A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by aticonfigamdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon 6870:
Section "Device"
==== X2/Dual GPU Cards ====
If you have an X2 card (e.g. 4870X2 or 5970), use... '''!!Do not use for two separate cards in crossfire!!'''
$ sudo aticonfig amdconfig --initial -f --adapter<nowiki>=</nowiki>all
==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
$ sudo aticonfig amdconfig --initial -f $ sudo aticonfig amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:
$ sudo aticonfig amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>
===''Test your installation''===
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig amdconfig --tls=0
===''Just in case''===
$ end script
This has been tested using Ubuntu 10.04 64-bit on a ATI Radeon HD 4830 (HP Envy 15-1060ea). It's worth noting that I had to disable TLS (aticonfig amdconfig --tls=0) to get things to stay stable!
If you've properly installed the driver, but experience problems when starting the X server, such as hanging, black/white/gray screen, distortion, etc., your system BIOS may have a buggy ACPI implementation. To work around, press Ctrl+Alt+F1 to get to a terminal (or failing that, boot to recovery mode) and run:
$ sudo aticonfig amdconfig --acpi-services=off
If this method works, you should consider checking your system vendor's BIOS changelogs for relevant ACPI fixes, updating your BIOS, and reenabling the driver's ACPI services.
== Slow Maximizing Windows/General 2D Slowness ==
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. If you're not running compositing/desktop effects, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:
$ sudo aticonfig amdconfig --set-pcs-str=DDX,ForceXAA,TRUE
In the last case (at least) it is essential to run it without the Xorg server working. To do so, press CTRL+ALT+F1, log in and type the following (this will close all your programs so save your work before):
$ sudo service gdm stop
$ sudo aticonfig amdconfig --set-pcs-str=DDX,ForceXAA,TRUE
$ sudo service gdm start
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be possible to work around the issue by using a control file from a newer version of Catalyst than the one you're running.
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget <nowiki></nowiki>{{Catalystdashversion}} $ chmod +x atiamd-driver-installer-{{Catalystdashversion}} $ sh atiamd-driver-installer-{{Catalystdashversion}} --extract driver
$ sudo mv /etc/ati/control ~/control.bak
$ sudo cp driver/common/etc/ati/control /etc/ati
$ cd ~/catalyst{{Catalystversion}}
$ sh atiamd-driver-installer-{{Catalystversion}} --extract driver
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/ /etc/ati/
$ sudo chmod +x /etc/ati/
[[Category:Installation Documentation]]
== Aticonfig amdconfig not found after installation & "module does not exist" after boot ==This scenario is possible when the driver installation has seemingly succeeded and is possibly related to previous use of fglrx through the Jockey (i.e. you first used drivers provided by Ubuntu but then upgraded to ones available from AMD's website). When doing aticonfig amdconfig --initial after driver installation, you might end up not having the aticonfig amdconfig available at all:<pre>aticonfigamdconfig: command not found</pre>
After booting you might receive X error '(EE) Failed to load module "fglrx" (module does not exist, 0)'. These do not necessarily indicate that the installation has failed completely. On command line, do
$ ls /usr/lib/fglrx/bin
Heck yeah this == 'Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.' during deb generation ==During installation you may receive the following message:<pre>Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 507.</pre>This can happen when your /tmp folder is excalty what I neededmounted with the option "noexec". The noexec is suggested by many howtos regarding Ubuntu on SSD, when placing the /tmp in memory.A workaround can be found here: []

Navigation menu