Jump to: navigation, search

Ubuntu Quantal Installation Guide

7,095 bytes added, 02:59, 29 January 2013
Test your installation
'''ATI RadeonHD 2x00 - 4xx0 cards'''
If you have one of these cards, you do have the option of using the Catalyst Legacy driver, but only on Ubuntu 12.04/Precise and earlier. The if you downgrade your Xserver version (the Catalyst Legacy driver does not support the kernel version (3.5) or the Xserver version (1.13) that Ubuntu Quantal/12.10 uses).This can be done really easily by following the instructions given at [[]]. This PPA downgrades the Xserver and install a patched version of fglrx that supports kernel version 3.5 of Ubuntu Quantal.
== Using Ubuntu-supplied fglrx/Catalyst ==
On Ubuntu Quantal, this will install fglrx/Catalyst 9.000, which is roughly equivalent to Catalyst 12-9. NOTE: You must have the restricted repository enabled in Applications -> Ubuntu Software Center -> Edit -> Software Sources... for this to work. After you complete the install, skip to [[Ubuntu_Quantal_Installation_Guide#Generate_a_new_.2Fetc.2FX11.2Fxorg.conf_file|Generate a new /etc/X11/xorg.conf file]].
=== Command line ===
sudo apt-get install linux-source fglrx fglrx-amdcccle
=== GUI ===
''If you are using the x86_64 architecture (64 bit)'':
sudo apt-get install ia32-libs lib32gcc1 cd /usr ; sudo ln -svT lib /usr/lib64
===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
wget unzip chmod +x
===''Create and install .deb packages.'' ===
sudo sh ./ --buildpkg Ubuntu/quantal
sudo dpkg -i fglrx*.deb
===''In case of failure:''===
Remember these steps before you reboot your computer.
If the X server fails to start, switch to a new TTY using ctrl+alt+F2. Log in, and attempt to start the X server.
sudo startx
If it fails to start, you will likely see a stacktrace, and immediately above it will be something along the lines of "Could not stat /usr/lib64/fglrx/switchlibGL" which means that you failed to copy the executables properly. Ctrl+c, and immediately copy the switchlibGL and switchlibglx executables to the fglrx folder in /usr/lib64/ or /usr/lib32/.
If all else fails, revert your xorg.conf and reboot.
sudo cp /etc/X11/xorg.conf.orig /etc/X11/xorg.conf
This should return your original display.
==''Generate a new /etc/X11/xorg.conf file''==
Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.
=== Generic Config ===
This will work for most people:
sudo 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 amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon HD 6870:
Section "Device"
Identifier "ATI radeon 6870"
Driver "fglrx"
=== X2/Dual GPU Cards ===
If you have an X2 card (e.g. 5970), use... '''!!Do not use for two separate cards in crossfire!!'''
sudo amdconfig --initial -f --adapter<nowiki>=</nowiki>all
=== Dual/Multi Monitors ===
If you have a dual monitor display (also known as "Big Desktop"), use:
sudo amdconfig --initial -f
sudo amdconfig --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"
This was confirmed in Be advised that you may need to manually set the correct refresh rate for your second monitor through catalyst.
==''Force use of the new xorg.conf (if necessary)''==
Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:
sudo amdconfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>
Korvin77 Catalyst AI is used to detect older soarwfte and implement OGL Extension list restriction to run them correctly. If you turn it off those games may not work. However even with AI turned ON JK:JA works for me only if I change executable name to quake3.exe@Frank I believe JeGX has tandem of AMD and NV cards, one for rendering and one for CUDA/PhysX testing.
== Installing Catalyst Manually (from AMD/ATI's site) BETA/EXPERIMENTAL ==
''If you are using the x86_64 architecture (64 bit)'':
sudo apt-get install ia32-libs lib32gcc1 cd /usr ; sudo ln -svT lib /usr/lib64 
===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
wget unzip chmod +x
===''Create and install .deb packages.'' ===
sudo sh ./ --buildpkg Ubuntu/quantal
sudo dpkg -i fglrx*.deb
If building .deb packages fails, there is also an [ Alternative Manual Installation]
When running the dpkg line, you may receive an error like:
Errors were encountered while processing:
They may have attempted to install out of order. Install them individually as:
sudo dpkg -i fglrx_*.deb
sudo dpkg -i fglrx-amdcccle*.deb
sudo dpkg -i fglrx-dev*.deb
You should see a successful result similar to:
user@user-ubuntu:~# sudo dpkg -i fglrx_9.010-0ubuntu1_amd64.deb
(Reading database ... 168748 files and directories currently installed.)
Preparing to replace fglrx 2:9.010-0ubuntu1 (using fglrx_9.010-0ubuntu1_amd64.deb) ...
Removing all DKMS Modules
Error! There are no instances of module: fglrx
9.010 located in the DKMS tree.
Unpacking replacement fglrx ...
Setting up fglrx (2:9.010-0ubuntu1) ...
update-alternatives: using /usr/lib/fglrx/ to provide /etc/ (x86_64-linux-gnu_gl_conf) in auto mode
update-alternatives: using /usr/lib/fglrx/ to provide /etc/ (i386-linux-gnu_gl_conf) in auto mode
update-initramfs: deferring update (trigger activated)
Loading new fglrx-9.010 DKMS files...
First Installation: checking all kernels...
Building only for 3.5.0-17-generic
Building for architecture x86_64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
update-initramfs: deferring update (trigger activated)
Processing triggers for ureadahead ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.5.0-17-generic
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
user@user-ubuntu:~# sudo dpkg -i fglrx-amdcccle_9.010-0ubuntu1_amd64.deb
(Reading database ... 168748 files and directories currently installed.)
Preparing to replace fglrx-amdcccle 2:9.010-0ubuntu1 (using fglrx-amdcccle_9.010-0ubuntu1_amd64.deb) ...
Unpacking replacement fglrx-amdcccle ...
Setting up fglrx-amdcccle (2:9.010-0ubuntu1) ...
user@user-ubuntu:~# sudo dpkg -i fglrx-dev_9.010-0ubuntu1_amd64.deb
(Reading database ... 168748 files and directories currently installed.)
Preparing to replace fglrx-dev 2:9.010-0ubuntu1 (using fglrx-dev_9.010-0ubuntu1_amd64.deb) ...
Unpacking replacement fglrx-dev ...
Setting up fglrx-dev (2:9.010-0ubuntu1) ...
===''In case of failure:''===
=== Intel/ATI Hybrids ===
TODOBy using the officially provided drivers, there are two problems ( Launchpad Bug: Status unknown [ #1068404]):: An incompatibility problem between intel and fglrx drivers (This gives segmentation fault at X server): Some paths missing for openGL operation of the fglrx driver (This prevents applications that require direct rendering, e.g. Unity/games/etc, from loading correctly) If you follow the instructions described in the [ Binary Driver HOWTO], you should get functional configuration  There is still another bug if you use the integrated GPU (Intel), making the X server crashing ( Launchpad Bug: [ #1088220] ) A workaround for now is to use the discrete GPU (ATI)  For more information you may want to follow this time[ forum topic] ==== Script solution ==== :Script by anion155, can help you install & uninstall fglrx drivers for this configuration.:You must change 13 line in the script for your directory.
== Build Fails and Log Shows "mixed implicit and normal rules. Stop." ==
This can happen if your card's PCI ID wasn't officially certified to work with a particular version of Catalyst. It does not necessarily mean that your card is unsupported, but it does mean that you shouldn't file bugs with that particular card/driver combination. If you installed the driver by downloading it from AMD/ATI, installing a newer version of Catalyst will probably help.
If you installed the proprietary driver included with Ubuntu or you do not want to upgrade to a newer version, it may be is possible to work around the issue by . First check if AMD's signature file has a proper signature:  sudo nano /etc/ati/signature If the file only contains the word ''UNSIGNED'', replace the line with: 9777c589791007f4aeef06c922ad54a2:ae59f5b9572136d99fdd36f0109d358fa643f2bd4a2644d9efbb4fe91a9f6590a145:f612f0b01f2565cd9bd834f8119b309bae11a1ed4a2661c49fdf3fad11986cc4f641f1ba1f2265909a8e34ff1699309bf211a7eb4d7662cd9f8e3faf14986d92f646f1bc Reboot and see if the watermark is gone. If not, try using a control file from a older version of Catalyst than the one you're running.: 
cd ~/; mkdir catalyst12.10; cd catalyst12.10/
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
or specify all the correct parameters. For example:
sudo dkms build -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic
sudo dkms install -m fglrx -v '''9.012''' -k '''3.5.0-22'''-generic
[[Category:Installation Documentation]]
Anonymous user

Navigation menu