Changes

Jump to: navigation, search

Ubuntu Lucid Installation Guide

150 bytes removed, 02:48, 19 June 2010
m
Command Formatting
To install:
<pre> $ sudo add-apt-repository ppa:xorg-edgers/ppa $ sudo apt-get update</pre>
Now you can update your packages using Synaptic or Update Manager.
= Proprietary Drivers a.k.a Catalyst/fglrx =
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).
Install the prerequisite packages:{{Box Terminal| $ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget}}
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''
{{Box Terminal| $ sudo apt-get install ia32-libs}}
===''Download the latest Catalyst package.''===
This package contains both the 32-bit and 64-bit driver.
<pre> $ cd ~/; mkdir catalyst; cd catalyst/ $ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-6-x86.x86_64.run $ chmod +x ati-driver-installer-10-6-x86.x86_64.run</pre>
===''Create .deb packages.''===
{{Box Terminal| $ sh ati-driver-installer-{{Template:Catalystversion}}-x86.x86_64.run --buildpkg Ubuntu/lucid}}
===''Install .debs.''===
{{Box Terminal| $ sudo dpkg -i fglrx*.deb}}
=== ''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 -f install}}
Catalyst {{Template: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 fglrx-modaliases_*.deb libamdxvba1_*.deb}}
===''Generate a new /etc/X11/xorg.conf file''===
==== Back Up xorg.conf ====
{{Box Terminal| $ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak}}
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:
{{Box Terminal| $ sudo aticonfig --initial -f}}
==== X2 Cards ====
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!
{{Box Terminal| $ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all}}
==== Dual/Multi Monitors ====
If you have a dual monitor display (also known as "Big Desktop"), use:
{{Box Terminal| $ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"}}
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.
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>}}
===''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. Using fglrxinfo on a system with Catalyst 10-6 and a RadeonHD 4550 returns:
<pre>
=HOW TO REMOVE DRIVER=
<pre> $ sudo /usr/share/ati/fglrx-uninstall.sh # (if you installed a downloaded version of Catalyst) $ sudo apt-get remove --purge fglrx* xorg-driver-fglrx</pre>
If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver this Ubuntu wiki page]
<pre> $ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon $ sudo apt-get install xserver-xorg-video-ati $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core $ sudo dpkg-reconfigure xserver-xorg</pre>
= Issues =
== Unsupported Hardware Watermark ==
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 possible to work around the issue by using a control file from a different version of Catalyst. I use Catalyst 10-6 in this example because it is the latest at the time this was written. If you use a later version, replace 10-6 with the new version.
<pre> $ cd ~/; mkdir catalyst; cd catalyst/ $ wget http://www2.ati.com/drivers/linux/ati-driver-installer-10-6-x86.x86_64.run $ chmod +x ati-driver-installer-10-6-x86.x86_64.run $ sh ati-driver-installer-10-6-x86.x86_64.run --extract driver $ sudo mv /etc/ati/control ~/control.bak $ sudo cp driver/common/etc/ati/control /etc/ati</pre>}}
If the above workaround causes issues, restore the original control file:
{{Box Terminal| $ sudo mv ~/control.bak /etc/ati
== Mesa drivers ==
*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])
:(WW) fglrx(0): * DRI initialization failed! *</i>
: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 $ sudo modprobe -r i82875p_edacrmmod $ sudo modprobe -r fglrxrmmod $ sudo modprobe -r intel-agprmmod $ sudo modprobe -r agpgart $ sudo modprobe agpgart $ sudo modprobe intel-agp $ sudo 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 $ gksu gedit /etc/modprobe.d/blacklistblacklisti82875p_edac.conf:add the following line to the blank text file:
:<pre>blacklist i82875p_edac</pre>
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:
(assuming that the installer is in the directory we used to install)
<pre> $ cd ~/catalyst $ sh ati-driver-installer-10-6{{Catalystversion}}-x86.x86_64.run --extract driver $ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh $ sudo chmod +x /etc/ati/authatieventsd.sh</pre>
You'll have to restart for this to take effect.
Another way to get it working is to do enable Composite, but when you want to suspend simply disable Compiz Fusion. How would you do that? Easy! Install the fusion-icon package (in repos by default):
<code> $ sudo apt-get install fusion-icon</code>
After you have done that, launch it (Applications > System > Compiz Fusion Icon) and it appears in your notification area. To switch, simply right-mouse click on the icon and select Metacity. Your desktop will flicker and windows will dissapear, but after a while they appear again. Now try to suspend.
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre>
then:
{{Box Terminal| $ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2}}
== 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 --all}}
== New kernel installed? ==
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. SHould Should you need to manually install it:{{Box Terminal| $ sudo dkms build -m fglrx -k `uname -r`<br /> $ sudo dkms install -m fglrx -k `uname -r`}}if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
[[Category:Installation Documentation]]
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf
331
edits

Navigation menu