http://wiki.cchtml.com/api.php?action=feedcontributions&user=87.127.156.98&feedformat=atomcchtml.com - User contributions [en]2024-03-28T19:03:12ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Fedora_14_Installation_Guide&diff=6571Fedora 14 Installation Guide2011-05-24T00:33:15Z<p>87.127.156.98: </p>
<hr />
<div>ATI's latest Catalyst 10.12 now well supports Xorg-server 1.9.<br />
<br />
Pre-built .rpm packages should be in the non-official RPMFusion repository and corresponding version matching 10.12 is now out there. I strongly recommend all of you use this method since it automatically configures the grub config file and configure DKMS settings.<br />
<br />
An alternate way is, to download the .run installer from www.amd.com, run it using root privileges, follow the instructions on the screen and reboot afterwards. However, you must manually add a 'nomodeset' parameter in the grub entry, or the computer will hang with a black screen after plymouth bootscreen due to a conflict against kernel modesetting and fglrx. <br />
<br />
If you installed the driver from www.amd.com and see no graphical display, do the following:<br />
<br />
- login in text mode as root<br />
<br />
- cd /etc/X11<br />
<br />
- cp xorg.conf xorg.conf.old<br />
<br />
- open the file xorg.conf with a text editor (vi for example)<br />
<br />
- In the section "Device", change the entry "fglrx" to "radeon"<br />
<br />
- save the file and exit the text editor<br />
<br />
- reboot<br />
<br />
At this point graphical display should work.<br />
Now install the driver from the pre-built .rpm packages, not from www.amd.com.</div>87.127.156.98http://wiki.cchtml.com/index.php?title=Debian_Installation_Guide&diff=6152Debian Installation Guide2010-10-27T15:35:00Z<p>87.127.156.98: Removed "wtf is 'comment 1' and 'comment 6'?"</p>
<hr />
<div>2007-11, see http://wiki.debian.org/AtiHowTo<br />
----<br />
As of November 2005, ATI's drivers are in the non-free area of Debian. Make sure your /etc/apt/sources.list contains "contrib non-free" as well as main. You will, however, have to build your own kernel modules.<br />
<br />
''Warning: do not mix the non-free packages with the packages created by the installer as they will conflict in non-obvious ways. Before switching from one method to another, completely remove all fglrx-related packages. Never do upgrade from one method to another directly!''<br />
<br />
== Update the xorg.conf file (Configuration) ==<br />
<pre><br />
sudo aticonfig --initial<br />
</pre><br />
<br />
Now restart X, or reboot for the driver changes to take effect.<br />
<br />
== Confirm that it worked ==<br />
<pre><br />
$ fglrxinfo<br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY RADEON 9700 Generic<br />
OpenGL version string: 1.3.5461 (X4.3.0-8.19.10)<br />
</pre><br />
<br />
If it didn't work, you may need to run:<br />
<pre><br />
# mkdir -p /usr/X11R6/lib/modules/dri<br />
# ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri<br />
</pre><br />
<br />
Thanks to Maciej Matysiak for the clear debug [http://lists.debian.org/debian-amd64/2006/02/msg00217.html here] and solution [http://lists.debian.org/debian-amd64/2006/02/msg00311.html here].<br />
<br />
If it's still not working, try:<br />
<pre><br />
# rm /usr/lib/libGL.so*<br />
# rm /usr/X11R6/lib/libGL.so*<br />
# cd /usr/X11R6/lib<br />
# cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .<br />
# ln -s libGL.so.1.2 libGL.so.1<br />
# ldconfig<br />
</pre><br />
and confirm that 'ldd /usr/bin/fglrxinfo' is pointing to the right one.<br />
<br />
<br />
People seem to be experiencing a broken libGL.so.1 after installing 8.41 on Debian/etch. If `amdcccle` complains that libGL.so.1 does't exist, DONT DELETE /usr/lib/libGL.so.1.2 LIKE IT SAYS ABOVE. Make symbolic link to libGL.so.1.2 (which is included in fglrx package - 14 megs in size):<br />
<pre><br />
# cd /usr/lib<br />
# ln -s libGL.so.1.2 libGL.so.1<br />
</pre><br />
<br />
<br />
[[Category:Installation Documentation]]<br />
<br />
This work fine for ATI mobility radeon 1400<br />
<br />
(make backup the olds xorg.* files in your folder)<br />
<br />
<pre><br />
$ cp /etc/X11/xorg.conf /home/username/xorg.conf.old<br />
$ cp /var/log/Xorg.0.log /home/username/Xorg.0.log.old<br />
</pre><br />
<br />
(add contrib non-free in repositories)<br />
<br />
<pre><br />
$ apt-get update<br />
$ apt-get install module-assistant build-essential fakeroot dh-make debconf bzip2<br />
</pre><br />
<br />
(from www.amd.com download the courent version of driver for your ATI)<br />
<br />
<pre><br />
$ sh ./ati-driver-installer-8.40.4-x86.x86_64.run --buildpkg Debian/lenny<br />
</pre> <br />
<br />
<pre><br />
$ apt-get install fglrx-amdcccle_8.40.4-1_i386.deb<br />
$ apt-get install fglrx-driver-_8.40.4-1_i386.deb<br />
$ apt-get install fglrx-driver-dev_8.40.4-1_i386.deb<br />
$ apt-get install fglrx-kernel-src_8.40.4-1_i386.deb<br />
$ apt-get -f upgrade<br />
$ apt-get update<br />
</pre><br />
<br />
<br />
<br />
<pre><br />
$ module-assistant prepare<br />
$ module-assistant update<br />
$ module-assistant a-i fglrx<br />
</pre><br />
<br />
<pre><br />
$ aticonfig --initial<br />
</pre><br />
<br />
(reboot computer)<br />
<br />
<pre><br />
$ fglrxinfo<br />
</pre><br />
<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: MOBILITY RADEON 9700 Generic<br />
OpenGL version string: 1.3.5461 (X4.3.0-8.19.10)<br />
</pre></div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Jaunty_Installation_Guide&diff=6056Ubuntu Jaunty Installation Guide2010-09-08T10:15:24Z<p>87.127.156.98: /* 2. Create .deb packages. */</p>
<hr />
<div>__TOC__<br />
<br />
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;" <br />
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION UBUNTU JAUNTY USERS'''</font> <br />
|- <br />
| <br />Warning: Does not work for all system combinations at this time<br /><br /><br />
|}<br />
<br />
= The Options =<br />
Users with ATI cards basically have these options:<br />
# '''Standard 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. <br />
# '''Edge Open Source Drivers''' These drivers have improved 3D performance<br />
# '''The Ubuntu Way''' Use the restricted-driver management system that comes with Ubuntu to install the proprietary drivers.<br />
# '''Third (Fourth?) Party Installer''' Use envy/jockey or other installer helper.<br />
# '''Install the drivers manually''' Using the installer downloaded from AMD's site via either package based install or direct install.<br />
<br />
= Open Source Drivers =<br />
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.<br />
<br />
The drivers that may be used are<br />
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.<br />
* '''ati''' Actually a facade that will invoke the radeon driver. <br />
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.<br />
* '''radeonhd''' An alternate driver support R520 hardware and later.<br />
<br />
By default there is no configuration file for X anymore, so X will try to do the right thing.<br />
<br />
If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.<br />
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/ mainline-2.6.29.3] did the trick on a few machines.<br />
<br />
There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future. For more information, see http://wiki.x.org/wiki/RadeonFeature<br />
<br />
= Installing Open Source Edge Drivers =<br />
<br />
These drivers are built regularly from the X.Org git repository. So sometimes they work, sometimes they don't. However, they have been stable for me, and are the only drivers that work for me. The fglrx drivers hang my system, and the standard "radeon" driver does not support a 2560x1600 resolution.<br />
<br />
To install:<br />
<br />
First add the repository https://launchpad.net/~tormodvolden/+archive/ppa. Instructions on how to do that are on that page. Then update your packages using Update Manager, and then add the ''xserver-xorg-video-radeonhd'' package. When you log in, you may be using the new driver, but you will probably still be using the radeon driver. To switch to the radeonhd driver, add this to '''/etc/X11/xorg.conf''' :<br />
<br />
<pre>Section "Device"<br />
Identifier "Default Device"<br />
Driver "radeonhd"<br />
EndSection</pre><br />
<br />
= The Ubuntu way to install the Proprietary Drivers =<br />
<br />
== Restricted Drivers Manager ==<br />
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available<br />
* Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"<br />
* Ubuntu will then install and configure the driver for you<br />
<br />
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. The driver installed this way does not work with Radeon X1300.<br />
<br />
= Installing the drivers manually =<br />
*PLEASE READ FIRST!<br />
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. <br />
<br />
'''Which cards does ATI no longer support?'''<br />
The ATI Radeon 9500-9800, X300-X2100, Xpress. See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]<br />
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.10. !!!SO BE CAREFUL!!!<br />
<br />
_______________________________________________<br />
<br />
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 Ctrl + Shift + V or 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.<br />
<br />
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
===''Before you start''===<br />
Install the necessary programs<br />
{{Box Terminal|<br />
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms libQtGui4<br />
}}<br />
NB in 9.10 (Karmic Koala) libstdc++5 has been superseded by libstdc++6. In some cases, libstdc++5 is still needed; however there is a workaround to this by symlinking libstdc++5 to libstdc++6.<br />
<br />
The workaround is as follows:<br />
{{Box Terminal|<br />
sudo ln -s /usr/lib/libstdc++.so.6 /usr/lib/libstdc++.so.5<br />
}}<br />
Then run ldconfig.<br />
<br />
{{Box Terminal|<br />
sudo ldconfig<br />
}}<br />
<br />
===''1. Download the latest Catalyst package.''===<br />
<br />
Download page: Catalyst {{catalystversion}} -- File: {{catalystfilename}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)<br />
<br />
Make sure your directory path does not contain spaces<br />
<br />
(Errors may be experienced during the creation of the *.deb files for manual install for version 9.12. If so try 9.11 as I tested it myself and had no errors)<br />
<br />
===''2. Create .deb packages.''===<br />
{{Box Terminal|<br />
sh {{Template:Catalystfilename}} --buildpkg Ubuntu/jaunty<br />
}}<br />
''note that if you are following these instructions for karmic to replace Ubuntu/jaunty with Ubuntu/karmic''<br />
<br />
===''3. Just in case''===<br />
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.<br />
<br />
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b<br />
<br />
These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".<br />
<br />
An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remebering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.<br />
<br />
===''4. Install .debs.''===<br />
<br />
Install the debs, depending on if you're on a 32-bit or 64-bit system:<br />
<br />
* For 32-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
}}<br />
<br />
(This may fail due to a missing dkms. If so install this first. Also check the version numbers (8.632) against the created debs)<br />
<br />
* For 64-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
=== ''5. Additional 64-bit instructions'' ===<br />
<br />
--If you have installed the "ia32-libs" package most likely you will not need to do this step.--<br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo apt-get -f install<br />
}}<br />
<br />
Catalyst {{Template:Catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
{{Box Terminal|<br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb fglrx-modaliases_*.deb libamdxvba1_*.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Finishing the Install: Configuration ==<br />
<br />
===''Now you'll have to edit your xorg.conf''===<br />
<br />
'''Note: If you've used fglrx previously, skip down to step 6.'''<br />
<br />
For Ubuntu:<br />
{{Box Terminal|<br />
sudo gedit /etc/X11/xorg.conf<br />
}}<br />
<br />
For Kubuntu:<br />
{{Box Terminal|<br />
sudo kate /etc/X11/xorg.conf<br />
}}<br />
<br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Identifier "SOME IDENTIFIER"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
<br />
===''6. Generate a new /etc/Xorg.conf file''===<br />
<br />
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.<br />
<br />
==== Generic Config ====<br />
This will work for most people:<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f<br />
}}<br />
<br />
==== X2 Cards ====<br />
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all<br />
}}<br />
<br />
==== Dual/Multi Monitors ====<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
}}<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.<br />
<br />
===''7. Force use of /etc/Xorg.conf file''===<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
===''8. Test your installation''===<br />
Finally, reboot the computer and type<br />
{{Box Terminal|<br />
fglrxinfo<br />
}}<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.6 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 2.1.8673<br />
</pre><br />
<br />
* 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.<br />
* Also note: if you don't reboot, fglrxinfo gives an error message - this threw me for a bit as I didn't read the line above the box very carefully.<br />
<br />
=HOW TO UPDATE DRIVER=<br />
<br />
To update your driver to a new version (say 9.5 to 9.6) 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|<br />
sudo aticonfig --initial -f<br />
}}<br />
in a terminal. If it doesn't give an error you should be good.<br />
<br />
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all<br />
}}<br />
instead in a terminal to generate the /etc/Xorg.conf file.<br />
<br />
and <br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
then reboot.<br />
<br />
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 old driver then installed the new one, it worked perfectly.<br />
<br />
=HOW TO REMOVE DRIVER=<br />
<br />
To completely remove the driver 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.<br />
<br />
Alternatively, use the following command from the terminal.<br />
<br />
{{Box Terminal|<br />
sudo apt-get remove --purge xorg-driver-fglrx<br />
}}<br />
<br />
=Tweaks=<br />
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422<br />
# 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.<br />
# 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.<br />
<br />
Done! Now run amdcccle, glxgears, nexuiz, warsow etc :)<br />
<br />
= Issues =<br />
<br />
== Installation ==<br />
There are some system configurations on which '''none''' of the installation alternatives work with the latest 9.5 driver (please add; also please add if you got it to work in one of the listed setups):<br />
* Ubuntu 9.04 (x64 and i386) on x86_64 with Radeon HD4870X2 and 9.5 driver: Framebuffer error ("No valid linear framebuffer address"), garbled screen. <br />
** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.4 driver: use 'aticonfig --initial -f --adapter=all'<br />
** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.6 driver: use 'aticonfig --initial -f' (without adapter=all, if you only have one screen)<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD3870X2 and 9.5 driver: "No supported adapters detected." <br />
* Ubuntu 9.04 (x64) on x86 and x86_64 with Radeon HD4850X2: Framebuffer error, garbled screen.<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4850: Framebuffer error, garbled screen (with automatic log-on, using the restricted drivers manager installation).<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.<br />
**Working Radeon HD 3300 connected to an HDTV, I had a garbled screen before, I reinstalled Ubuntu, then follow manual steps closely. Reinstalled because I didn't know how to remove fglrx, but you may be able to avoid reinstalling by following fglrx complete removal in this guide.<br />
**Working 790GX (A790GMH/128M) with 9.5 driver after manual install (following install with envyng, which might be older version as of 25/5/09). Able to change display resolution which before was not working.<br />
**Working 790GX (MSI 790GX-G65): Now able to call System/Video Configuration which hang up. This driver also reduced the power consumption by 15 W (from 93 W down to 78 W). Thank you for that great installation guide.<br />
** Working Radeon HD 3450 connected to an HDTV on Kubuntu 9.04. Followed manual install of latest drivers (9.6) to the letter, rebooted, and works fully.<br />
<br />
== Mesa drivers ==<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''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<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
: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: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
: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:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''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.<br />
:Run in a terminal:<br />
:<pre>uname -r</pre><br />
: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.<br />
<br />
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].<br />
<br />
<br />
== Hang at logout ==<br />
<br />
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:<br />
<br />
<pre>sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
<br />
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do : <br />
(assuming that the installer is in your home directory)<br />
<br />
<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre> <br />
<br />
<pre>sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre><br />
<br />
(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)<br />
<br />
<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre><br />
<br />
just reboot login and ctrl+alt+backspace to try<br />
<br />
== Suspend/Hibernation ==<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<blockquote><br />
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)<br />
</blockquote><br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
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):<br />
<br />
<code><br />
sudo apt-get install fusion-icon<br />
</code><br />
<br />
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.<br />
<br />
When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)<br />
<br />
KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.<br />
<br />
Hopefully this helped some people, as it did for me!<br />
Solution posted by zwyber@gmail.com<br />
<br />
== Can't remove fglrx with dpkg ==<br />
<br />
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.<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
{{Box Terminal|<br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
}}<br />
<br />
== New kernel installed? ==<br />
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.<br />
You can do that by these simple steps:<br />
{{Box Terminal|<br />
sudo dkms build -m fglrx -v 8.552 -k `uname -r`<br /><br />
sudo dkms install -m fglrx -v 8.552 -k `uname -r`<br />
}}<br />
[[Category:Installation Documentation]]<br />
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf</div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Lucid_Installation_Guide&diff=5945Ubuntu Lucid Installation Guide2010-06-19T23:12:18Z<p>87.127.156.98: /* Removing the Driver */ Removed two unwanted </pre>'s</p>
<hr />
<div>__TOC__<br />
<br />
= The Options =<br />
Users with ATI cards basically have these options:<br />
# '''Standard Open Source Drivers''' Usually stable. These drivers currently have relatively poor 3D performance, but newer 3D drivers using the Gallium3D infrastructure are under development.<br />
# '''Edge Open Source Drivers''' These drivers have improved 3D performance<br />
# '''The Ubuntu Way''' Use the restricted-driver management system (a.k.a jockey) that comes with Ubuntu to install the proprietary drivers.<br />
# '''Install the proprietary drivers manually''' Package-based install of a driver downloaded from AMD/ATI's site.<br />
<br />
= Open Source Drivers =<br />
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.<br />
<br />
The drivers that may be used are<br />
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.<br />
* '''ati''' Actually a thin wrapper that will invoke the radeon driver (or another ati open-source driver for pre-Radeon cards). <br />
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.<br />
* '''radeonhd''' An alternate driver support R520 hardware and later. This driver is now all but officially deprecated in favor of radeon.<br />
<br />
By default there is no configuration file (xorg.conf) for X anymore, so X will try to do the right thing.<br />
<br />
If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.<br />
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/ mainline-2.6.34-lucid] did the trick on a few machines.<br />
<br />
= Installing Open Source Edge Drivers =<br />
<br />
These packages are built regularly from the X.Org git repository, so they may not be fully stable. On Lucid, using this graphics stack now uses the r300g Gallium3D driver for 3D acceleration on Radeon R300-R500 (Radeon 9500 - Radeon X1950) class chips. It's probably a good idea to use the linux kernel provided by this repo if you go this route.<br />
<br />
To install:<br />
$ sudo add-apt-repository ppa:xorg-edgers/ppa<br />
$ sudo apt-get update<br />
Now you can update your packages using Synaptic or Update Manager. <br />
= Proprietary Drivers a.k.a Catalyst/fglrx =<br />
*PLEASE READ FIRST!<br />
'''Which cards do ATI no longer support?'''<br />
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]<br />
If your card is on that list, you are limited to open-source drivers on Ubuntu Lucid. If you really need the proprietary Catalyst/fglrx driver, you will have to use an older Linux distribution, such as Debian Lenny/5.0.x or Ubuntu Hardy/8.04.x.<br />
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;" <br />
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION RADEON USERS'''</font> <br />
|- <br />
| <br />NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Lucid! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers.<br /><br /><br />
|}<br />
<br />
== Restricted Drivers Manager ==<br />
NOTE: You must have the restricted repository enabled in System -> Administration -> Software Sources for this to work. You will be limited to the drivers for your version of Ubuntu that Canonical deems stable. This may not give you the latest drivers, but should be safest. On Ubuntu Lucid, this will install Catalyst 8.723, which is roughly equivalent to Catalyst 10-4. Go to the Restricted Drivers Manager (System -> Administration -> Hardware Drivers) and enable the "ATI accelerated graphics driver" (or double-click the "available driver" notification icon). Ubuntu will then install and configure the driver for you.<br />
<br />
= Installing the drivers manually =<br />
I recommend copying and pasting the commands. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something, use Ctrl + Shift + V or 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.<br />
<br />
===''Before you start''===<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources (System -> Administration -> Software Sources).<br />
<br />
Install the prerequisite packages:<br />
$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget<br />
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''<br />
$ sudo apt-get install ia32-libs<br />
<br />
===''Download the latest Catalyst package.''===<br />
This package contains both the 32-bit and 64-bit driver.<br />
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/<br />
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-{{Catalystversion}}-x86.x86_64.run<br />
$ chmod +x ati-driver-installer-{{Catalystversion}}-x86.x86_64.run<br />
<br />
===''Create .deb packages.''===<br />
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --buildpkg Ubuntu/lucid<br />
<br />
===''Install .debs.''===<br />
$ sudo dpkg -i fglrx*.deb<br />
<br />
=== ''Additional 64-bit instructions'' ===<br />
NOTE: If you have installed the "ia32-libs" package beforehand, you most likely you will not need to do this step.--<br />
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:<br />
<br />
$ sudo apt-get -f install<br />
<br />
Catalyst {{Template:Catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
$ sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb fglrx-modaliases_*.deb libamdxvba1_*.deb<br />
<br />
===''Generate a new /etc/X11/xorg.conf file''===<br />
<br />
Before you do this, back up your current xorg.conf if you have one (Lucid does not have an xorg.conf by default)<br />
<br />
==== Back Up xorg.conf ====<br />
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak<br />
<br />
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.<br />
<br />
==== Generic Config ====<br />
This will work for most people:<br />
$ sudo aticonfig --initial -f<br />
<br />
==== X2 Cards ====<br />
If you have an X2 card (e.g. 4870X2), use... !!Do not use for two separate cards in crossfire!!<br />
$ sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all<br />
<br />
==== Dual/Multi Monitors ====<br />
If you have a dual monitor display (also known as "Big Desktop"), use:<br />
$ sudo aticonfig --initial -f --set-pcs-str<nowiki>=</nowiki>"DDX,EnableRandR12,FALSE"<br />
This was confirmed in http://phoronix.com/forums/showthread.php?t=18553.<br />
<br />
===''Force use of the new xorg.conf (if necessary)''===<br />
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:<br />
<br />
$ sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
<br />
===''Test your installation''===<br />
NOTE: if you don't reboot first, fglrxinfo gives an error message.<br />
Reboot the computer and type<br />
$ fglrxinfo<br />
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:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4300/4500 Series (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 3.3.9901 Compatibility Profile Context (This line may be different depending on what graphics card and Catalyst version you are using.)<br />
</pre><br />
Now, try:<br />
$ fgl_glxgears<br />
If you experience issues or a hang, you may need to disable fast TLS.<br />
$ sudo aticonfig --tls=off<br />
<br />
===''Just in case''===<br />
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.<br />
<br />
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b<br />
<br />
These key-presses will reboot the system safely. To remember the key-presses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring".<br />
<br />
An alternative would be to hold down Ctrl+Alt+SysRq (SysRq is usually the same key as PrintScreen) and type very slowly R E I S U B. A way to remember this is by inverting the word: "BUSIER" or remembering a phrase: "Restart Even If System Utterly Broken". This would also safely shutdown the system.<br />
<br />
<br />
=Updating the Driver=<br />
<br />
DO NOT try to install a new version over an old one. Follow the 'Removing the Driver' section below to remove your existing driver, and then you can start at 'Downloading the latest Catalyst' to install the new one.<br />
<br />
=Removing the Driver=<br />
<br />
$ sudo /usr/share/ati/fglrx-uninstall.sh # (if you installed a downloaded version of Catalyst)<br />
$ sudo apt-get remove --purge fglrx* xorg-driver-fglrx<br />
<br />
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]<br />
$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon<br />
$ sudo apt-get install xserver-xorg-video-ati<br />
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core<br />
$ sudo dpkg-reconfigure xserver-xorg<br />
<br />
= Issues =<br />
<br />
== Crashes in WINE == <br />
For more information, see [http://bugs.winehq.org/show_bug.cgi?id=4561#c6 this WINEHQ bug report]. This issue should be fixed in WINE 1.1.40, so you may want to get an updated version of WINE by using [https://launchpad.net/~vivnet/+archive/vivnet-wine this PPA]. If you prefer the Ubuntu version of WINE, then turn FastTLS off:<br />
$ sudo aticonfig --tls=off<br />
<br />
== Problems Starting Xserver ==<br />
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:<br />
$ sudo aticonfig --acpi-services=off<br />
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.<br />
<br />
== Slow Maximizing Windows/General 2D Slowness ==<br />
As of Catalyst 10-6, a new, faster 2D acceleration method is used as the default, replacing the old XAA method. The new acceleration code was also available in Catalyst 10-2 through 10-5 (including the Catalyst that ships with Lucid), though it was not used by default. If you're using one of those versions, you can try the new acceleration code with the following command:<br />
$ sudo aticonfig --set-pcs-str=DDX,Direct2DAccel,TRUE<br />
Restart X (by logging out or rebooting) to apply the change. If you experience issues and want to return to the older, stable code:<br />
$ sudo aticonfig --del-pcs-key=DDX,Direct2DAccel<br />
If you're using Catalyst 10-6 or later, and are having problems with 2D operations, you may want to fall back to the old XAA. This command will do that:<br />
$ sudo aticonfig --set-pcs-str=DDX,ForceXAA,TRUE <br />
<br />
<br />
== Unsupported Hardware Watermark ==<br />
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.<br />
$ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/<br />
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-{{Catalystversion}}-x86.x86_64.run<br />
$ chmod +x ati-driver-installer-{{Catalystversion}}-x86.x86_64.run<br />
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver<br />
$ sudo mv /etc/ati/control ~/control.bak<br />
$ sudo cp driver/common/etc/ati/control /etc/ati<br />
<br />
If the above workaround causes issues, restore the original control file:<br />
<br />
$ sudo mv ~/control.bak /etc/ati<br />
<br />
== Mesa drivers ==<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:<br />
<br />
*Remove the package xserver-xgl.<br />
$ sudo apt-get remove xserver-xgl<br />
:'''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<br />
$ DISPLAY=:0 glxinfo | grep render<br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
----<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
:If you have Intel 8285P and E7205 chipsets and AGP not detected then you have to remove the i82875p_edac module and restart some others: <br />
$ sudo modprobe -r i82875p_edac<br />
$ sudo modprobe -r fglrx<br />
$ sudo modprobe -r intel-agp<br />
$ sudo modprobe -r agpgart<br />
$ sudo modprobe agpgart<br />
$ sudo modprobe intel-agp<br />
$ sudo modprobe fglrx<br />
<br />
:Blacklist the modules e7xxx_edac so it doesn't start up again when booting<br />
$ gksu gedit /etc/modprobe.d/blacklisti82875p_edac.conf<br />
:add the following line to the blank text file:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''Explanation:''' If you upgraded to your current Ubuntu install (rather than doing a clean install), you may still be using the old kernel without knowing it.<br />
$ uname -r<br />
:If your kernel version is less than 2.6.32, it is a kernel from a previous Ubuntu installation.<br />
<br />
If this doesn't help, try 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].<br />
<br />
<br />
== Hang at logout ==<br />
<br />
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:<br />
<br />
$ sudo mkdir -p /var/lib/xdm/authdir<br />
$ sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
$ sudo /usr/sbin/update-rc.d -f atieventsd remove<br />
<br />
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do: <br />
(assuming that the installer is in the directory we used to install)<br />
<br />
$ cd ~/catalyst{{Catalystversion}}<br />
$ sh ati-driver-installer-{{Catalystversion}}-x86.x86_64.run --extract driver<br />
$ sudo cp driver/packages/Ubuntu/dists/lucid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh<br />
$ sudo chmod +x /etc/ati/authatieventsd.sh</pre><br />
<br />
You'll have to restart for this to take effect.<br />
<br />
== Suspend/Hibernation ==<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
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):<br />
<br />
$ sudo apt-get install fusion-icon<br />
<br />
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.<br />
<br />
When you wake up again, you can (hopefully) unlock your screen and there you go! Now you want Compiz back again, so right-mouse-click on the Compiz Fusion Icon and select Compiz again. Desktop flickering again, but then voila! Your Compiz Fusion Desktop is back again! (At least, that is how it is supposed to work)<br />
<br />
KNOWN PROBLEM: When you switch back, all your windows are on the same desktop. This happens because you switched to metacity.<br />
<br />
Hopefully this helped some people, as it did for me!<br />
Solution posted by zwyber@gmail.com<br />
<br />
== Can't remove fglrx with dpkg (diversion issue) ==<br />
<br />
If dpkg refuses to remove an fglrx package and complains about a diversion of a file, you might need to manually remove it. For example, if dpkg complains:<br />
<pre>dpkg-divert: mismatch on divert-to<br />
when removing `diversion of /usr/lib/libGL.so.1.2 to /usr/share/fglrx/diversions/libGL.so.1.2 by xorg-driver-fglrx'<br />
found `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/libGL.so.1.2.xlibmesa by xorg-driver-fglrx'</pre><br />
then:<br />
$ sudo dpkg-divert --remove /usr/lib/libGL.so.1.2<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
$ sudo dkms remove -m fglrx --all<br />
<br />
== New kernel installed? ==<br />
In theory, DKMS should automatically install the fglrx kernel module for your new kernel the first time you boot it. Should you need to manually install it:<br />
$ sudo dkms build -m fglrx -k `uname -r`<br />
$ sudo dkms install -m fglrx -k `uname -r`<br />
<br />
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf<br />
[[Category:Installation Documentation]]</div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Jaunty_Installation_Guide&diff=5616Ubuntu Jaunty Installation Guide2009-06-20T07:15:04Z<p>87.127.156.98: /* Tweaks */ added Nexuiz</p>
<hr />
<div>__TOC__<br />
<br />
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;" <br />
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION UBUNTU JAUNTY USERS'''</font> <br />
|- <br />
| <br />Warning: Does not work for all system combinations at this time<br /><br /><br />
|}<br />
<br />
= The Alternatives =<br />
Users with ATI cards basically have these options:<br />
# '''Standard 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. <br />
# '''Edge Open Source Drivers''' These drivers have improved 3D performance<br />
# '''The Ubuntu Way''' Use the restricted-driver management system that comes with Ubuntu to install the proprietary drivers.<br />
# '''Third (Fourth?) Party Installer''' Use envy/jockey or other installer helper.<br />
# '''Install the drivers manually''' Using the installer downloaded from AMD's site via either package based install or direct install. <br />
<br />
= Open Source Drivers =<br />
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.<br />
<br />
The drivers that may be used are<br />
* '''vesa''' Lowest common denominator across all graphics vendor, not many features.<br />
* '''ati''' Actually a facade that will invoke the radeon driver. <br />
* '''radeon''' Driver support all radeon classes of hardware - with limited 3D for newer cards.<br />
* '''radeonhd''' An alternate driver support R520 hardware and later.<br />
<br />
By default there is no configuration file for X anymore, so X will try to do the right thing.<br />
<br />
If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.<br />
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/ mainline-2.6.29.3] did the trick on a few machines.<br />
<br />
There's an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future. For more information, see http://wiki.x.org/wiki/RadeonFeature<br />
<br />
= Installing Open Source Edge Drivers =<br />
<br />
These drivers are built regularly from the X.Org git repository. So sometimes they work, sometimes they don't. However, they have been stable for me, and are the only drivers that work for me. The fglrx drivers hang my system, and the standard "radeon" driver does not support a 2560x1600 resolution.<br />
<br />
To install:<br />
<br />
First add the repository https://launchpad.net/~tormodvolden/+archive/ppa. Instructions on how to do that are on that page. Then update your packages using Update Manager, and then add the xserver-xorg-video-radeonhd package. When you log in, you may be using the new driver, but you will probably still be using the radeon driver. To switch to the radeonhd driver, add this to /etc/X11/xorg.conf:<br />
<br />
<pre>Section "Device"<br />
Driver "radeonhd"<br />
EndSection</pre><br />
<br />
= The Ubuntu way to install the Proprietary Drivers =<br />
<br />
== Restricted Drivers Manager ==<br />
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available<br />
* Go to the Restricted Drivers Manager and enable the "ATI accelerated graphics driver"<br />
* Ubuntu will then install and configure the driver for you<br />
<br />
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.<br />
<br />
= Installing the drivers manually =<br />
*PLEASE READ FIRST!<br />
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. <br />
<br />
'''Which cards does ATI no longer support?'''<br />
The ATI Radeon 9500-9800, X300-X2100, Xpress. See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]<br />
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.6. !!!SO BE CAREFUL!!!<br />
<br />
_______________________________________________<br />
<br />
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 Ctrl + Shift + V or 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.<br />
<br />
''If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!''<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
===''Before you start''===<br />
Install the necessary programs<br />
{{Box Terminal|<br />
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms <br />
}}<br />
<br />
===''1. Download the latest Catalyst package.''===<br />
<br />
Download page: Catalyst {{catalystversion}} -- File: {{catalystfilename}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)<br />
<br />
Make sure your directory path does not contain spaces<br />
<br />
===''2. Create .deb packages.''===<br />
{{Box Terminal|<br />
sh {{Template:Catalystfilename}} --buildpkg Ubuntu/jaunty<br />
}}<br />
<br />
===''3. Just in case''===<br />
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.<br />
<br />
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b<br />
<br />
These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: "Raising Skinny Elephants Is Never Utterly Boring"<br />
<br />
===''4. Install .debs.''===<br />
<br />
Install the debs, depending on if you're on a 32-bit or 64-bit system:<br />
<br />
* For 32-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
}}<br />
<br />
(This may fail due to a missing dkms. If so install this first. Also check the version numbers (8.620) against the created debs)<br />
<br />
* For 64-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
=== ''5. Additional 64-bit instructions'' ===<br />
<br />
--If you have installed the "ia32-libs" package most likely you will not need to do this step.--<br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo apt-get install -f<br />
}}<br />
<br />
Catalyst {{Template:Catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
{{Box Terminal|<br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Finishing the Install: Configuration ==<br />
<br />
===''Now you'll have to edit your xorg.conf''===<br />
<br />
'''Note: If you've used fglrx previously, skip down to step 6.'''<br />
<br />
For Ubuntu:<br />
{{Box Terminal|<br />
sudo gedit /etc/X11/xorg.conf<br />
}}<br />
<br />
For Kubuntu:<br />
{{Box Terminal|<br />
sudo kate /etc/X11/xorg.conf<br />
}}<br />
<br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Identifier "SOME IDENTIFIER"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
Save and exit, then run<br />
<br />
===''6. Generate a new /etc/Xorg.conf file''===<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f<br />
}}<br />
in a terminal. If it doesn't give an error you should be good.<br />
<br />
If you have an X2 card (e.g. 4870X2), use<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all<br />
}}<br />
instead in a terminal to generate the /etc/Xorg.conf file.<br />
<br />
===''7. Force use of /etc/Xorg.conf file''===<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
===''8. Test your installation''===<br />
Finally, reboot the computer and type<br />
{{Box Terminal|<br />
fglrxinfo<br />
}}<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.6 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)<br />
OpenGL version string: 2.1.8673<br />
</pre><br />
<br />
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.<br />
<br />
=HOW TO UPDATE DRIVER=<br />
<br />
To update your driver to a new version (say 9.5 to 9.6) 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|<br />
sudo aticonfig --initial -f<br />
}}<br />
in a terminal. If it doesn't give an error you should be good.<br />
<br />
If you have an X2 card (e.g. 4870X2), use<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f --adapter<nowiki>=</nowiki>all<br />
}}<br />
instead in a terminal to generate the /etc/Xorg.conf file.<br />
<br />
and <br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
then reboot.<br />
<br />
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 old driver then installed the new one, it worked perfectly.<br />
<br />
=HOW TO REMOVE DRIVER=<br />
<br />
To completely remove the driver 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.<br />
<br />
=Tweaks=<br />
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422<br />
# 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.<br />
# 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.<br />
<br />
Done! Now run amdcccle, glxgears, nexuiz, warsow etc :)<br />
<br />
= Issues =<br />
<br />
== Installation ==<br />
There are some system configurations on which '''none''' of the installation alternatives work with the latest 9.5 driver (please add; also please add if you got it to work in one of the listed setups):<br />
* Ubuntu 9.04 (x64 and i386) on x86_64 with Radeon HD4870X2: Framebuffer error ("No valid linear framebuffer address"), garbled screen. <br />
** Working 9.04 (x64) on x86_64 with Radeon4870X2 and 9.4 / 9.6 driver (9.5 still does not work): use 'aticonfig --initial -f --adapter=all'<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD3870X2 and 9.5 driver: "No supported adapters detected." <br />
* Ubuntu 9.04 (x64) on x86 and x86_64 with Radeon HD4850X2: Framebuffer error, garbled screen.<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4850: Framebuffer error, garbled screen.<br />
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.<br />
**Working Radeon HD 3300 connected to an HDTV, I had a garbled screen before, I reinstalled Ubuntu, then follow manual steps closely. Reinstalled because I didn't know how to remove fglrx, but you may be able to avoid reinstalling by following fglrx complete removal in this guide.<br />
**Working 790GX (A790GMH/128M) with 9.5 driver after manual install (following install with envyng, which might be older version as of 25/5/09). Able to change display resolution which before was not working.<br />
**Working 790GX (MSI 790GX-G65): Now able to call System/Video Configuration which hang up. This driver also reduced the power consumption by 15 W (from 93 W down to 78 W). Thank you for that great installation guide.<br />
<br />
== Mesa drivers ==<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''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<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
: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: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
: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:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''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.<br />
:Run in a terminal:<br />
:<pre>uname -r</pre><br />
: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.<br />
<br />
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].<br />
<br />
<br />
== Hang at logout ==<br />
<br />
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:<br />
<br />
<pre>sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
<br />
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do : <br />
(assuming that the installer is in your home directory)<br />
<br />
<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre> <br />
<br />
<pre>sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre><br />
<br />
(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)<br />
<br />
<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre><br />
<br />
just reboot login and ctrl+alt+backspace to try<br />
<br />
== Suspend/Hibernation ==<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<blockquote><br />
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)<br />
</blockquote><br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
== Can't remove fglrx with dpkg ==<br />
<br />
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.<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
{{Box Terminal|<br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
}}<br />
<br />
== New kernel installed? ==<br />
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.<br />
You can do that by these simple steps:<br />
{{Box Terminal|<br />
sudo dkms build -m fglrx -v 8.552 -k `uname -r`<br /><br />
sudo dkms install -m fglrx -v 8.552 -k `uname -r`<br />
}}<br />
[[Category:Installation Documentation]]<br />
if amdcccle doesn't work and says Identifier is not a valid word. Use lower case letter in xorg.conf</div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Intrepid_Installation_Guide&diff=5339Ubuntu Intrepid Installation Guide2009-03-03T01:27:41Z<p>87.127.156.98: /* Finishing the Install: Configuration */ Added a copy of fglrxinfo for 9.2</p>
<hr />
<div>= Installation Guide for Ubuntu Intrepid (v 8.10) =<br />
<br />
== The three alternatives ==<br />
<br />
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.<br />
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, a slight hope has arisen for better drivers for ATI-cards on Linux.<br />
<br />
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:<br />
# 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).<br />
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jockey/"restricted" packages). <br />
# Install the drivers manually. This should be your last resort, and may not even work.<br />
<br />
= The open source drivers =<br />
By default, one of the open source drivers are used. If this works for you, you don't need to change anything.<br />
<br />
These come with the X.org X server:<br />
* vesa<br />
* ati<br />
* radeon<br />
* radeonhd<br />
<br />
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.<br />
<br />
= Installing the restricted drivers "the Ubuntu way" =<br />
<br />
== Restricted Drivers Manager ==<br />
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. <br />
<br />
== Post-Installation Tweaks ==<br />
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''<br />
<br />
<pre><br />
Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
Option "VideoOverlay" "on"<br />
Option "OpenGLOverlay" "off"<br />
[...]<br />
EndSection<br />
</pre><br />
<br />
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.<br />
<br />
= Installing the restricted drivers manually =<br />
''If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!''<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
===''Before you start''===<br />
Install the necessary programs<br />
{{Box Terminal|<br />
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms <br />
}}<br />
<br />
===''1. Download the latest Catalyst package.''===<br />
<br />
Download page: Catalyst {{catalystversion}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)<br />
<br />
Make sure your directory path does not contain spaces<br />
<br />
===''2. Create .deb packages.''===<br />
{{Box Terminal|<br />
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid<br />
}}<br />
<br />
===''3. Install .debs.''===<br />
For 32-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_8.582-0ubuntu1_i386.deb fglrx-kernel-source_8.582-0ubuntu1_i386.deb fglrx-amdcccle_8.582-0ubuntu1_i386.deb<br />
}}<br />
<br />
(This may fail due to a missing dpmk. If so install this first)<br />
<br />
or for 64-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_8.582-0ubuntu1_amd64.deb fglrx-kernel-source_8.582-0ubuntu1_amd64.deb fglrx-amdcccle_8.582-0ubuntu1_amd64.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Additional 64-bit instructions ==<br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo apt-get install -f<br />
}}<br />
<br />
Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
{{Box Terminal|<br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.573-0ubuntu1_amd64.deb fglrx-kernel-source_8.573-0ubuntu1_amd64.deb fglrx-amdcccle_8.573-0ubuntu1_amd64.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Finishing the Install: Configuration ==<br />
<br />
'''If you've used fglrx previously, you will not need to do this.'''<br />
<br />
Now you'll have to edit your xorg.conf<br />
<br />
For Ubuntu:<br />
{{Box Terminal|<br />
sudo gedit /etc/X11/xorg.conf<br />
}}<br />
<br />
For Kubuntu:<br />
{{Box Terminal|<br />
sudo kate /etc/X11/xorg.conf<br />
}}<br />
<br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
Save and exit, then run<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f<br />
}}<br />
in a terminal. If it doesn't give an error you should be good. <br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
Finally, reboot the computer and type<br />
{{Box Terminal|<br />
fglrxinfo<br />
}}<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.12 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 3850<br />
OpenGL version string: 2.1.8304 Release<br />
</pre><br />
<br />
Release 9.2 looks like:<br />
<pre><br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 4670<br />
OpenGL version string: 2.1.8494 Release<br />
</pre><br />
<br />
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.<br />
<br />
== Finally ==<br />
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422<br />
# 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.<br />
# 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.<br />
<br />
Done! Now run amdcccle, glxgears, nexuiz, warsow etc :)<br />
<br />
= Issues =<br />
<br />
== Mesa drivers ==<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''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<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
: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: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
: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:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''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.<br />
:Run in a terminal:<br />
:<pre>uname -r</pre><br />
: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.<br />
<br />
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].<br />
<br />
<br />
== Hang at logout ==<br />
<br />
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:<br />
<br />
<pre>sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
<br />
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do : <br />
(assuming that the installer is in your home directory)<br />
<br />
<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre> <br />
<br />
<pre>sudo cp ~/driver/packages/Ubuntu/dists/intrepid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre><br />
<br />
(intrepid is to be replaced by the name used at the building stage (hardy,8.10,8.04,etc...)<br />
<br />
<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre><br />
<br />
just reboot login and ctrl+alt+backspace to try<br />
<br />
== Suspend/Hibernation ==<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<blockquote><br />
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)<br />
</blockquote><br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
A second Radeon 3200 suspend/wake issue seems to be related to the mouse/keyboard itself. Adding a reset to the kernel line of your grub configuration seems to solve this. In other words, update /boot/grub/menu.lst and add an i8042.reset:<br />
<br />
<pre><br />
kernel /boot/vmlinuz-2.6.27-11-generic root=UUID=73293ec3-5ee4-418c-914<br />
4-1457914fb284 ro quiet splash i8042.reset<br />
</pre><br />
<br />
== Can't remove fglrx with dpkg ==<br />
<br />
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.<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
{{Box Terminal|<br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
}}<br />
<br />
== New kernel installed? ==<br />
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.<br />
You can do that by these simple steps:<br />
{{Box Terminal|<br />
sudo dkms build -m fglrx -v 8.552 -k `uname -r`<br /><br />
sudo dkms install -m fglrx -v 8.552 -k `uname -r`<br />
}}<br />
[[Category:Installation Documentation]]<br />
== AMD Control Center ==<br />
You can start the AMD Control Center by typing:<br />
{{Box Terminal|<br />
amdcccle<br />
}}<br />
If amdcccle doesn't work and says Identifier is not a valid word, this may be caused by some of the reasons below:<br /><br />
- Use lower case letter in xorg.conf.<br /><br />
- Make sure lines have no hard returns in them causing some parameters without their corresponding keywords are misinterpreted<br /><br />
- If amdcccle complains about some keyword in your xorg.conf and quits with a segmentation fault, you may just be working with a different xorg.conf than your system uses. I had a copy of some generic xorg.conf in my home directory, and amdcccle complained about stuff it couldn't cope with. You need to start amdcccle in your /etc/X11 directory.<br /></div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Intrepid_Installation_Guide&diff=5338Ubuntu Intrepid Installation Guide2009-03-03T01:19:00Z<p>87.127.156.98: /* Finally */</p>
<hr />
<div>= Installation Guide for Ubuntu Intrepid (v 8.10) =<br />
<br />
== The three alternatives ==<br />
<br />
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.<br />
AMD has traditionally been a bit more Linux-friendly, so after AMD bought ATI, a slight hope has arisen for better drivers for ATI-cards on Linux.<br />
<br />
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:<br />
# 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).<br />
# Use the restricted-driver management system that comes with Ubuntu to install the drivers (envy/jockey/"restricted" packages). <br />
# Install the drivers manually. This should be your last resort, and may not even work.<br />
<br />
= The open source drivers =<br />
By default, one of the open source drivers are used. If this works for you, you don't need to change anything.<br />
<br />
These come with the X.org X server:<br />
* vesa<br />
* ati<br />
* radeon<br />
* radeonhd<br />
<br />
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.<br />
<br />
= Installing the restricted drivers "the Ubuntu way" =<br />
<br />
== Restricted Drivers Manager ==<br />
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. <br />
<br />
== Post-Installation Tweaks ==<br />
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''<br />
<br />
<pre><br />
Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
Option "VideoOverlay" "on"<br />
Option "OpenGLOverlay" "off"<br />
[...]<br />
EndSection<br />
</pre><br />
<br />
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.<br />
<br />
= Installing the restricted drivers manually =<br />
''If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!''<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
===''Before you start''===<br />
Install the necessary programs<br />
{{Box Terminal|<br />
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms <br />
}}<br />
<br />
===''1. Download the latest Catalyst package.''===<br />
<br />
Download page: Catalyst {{catalystversion}}. This package contains both the 32-bit and 64-bit driver.<br />
<br />
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)<br />
<br />
Make sure your directory path does not contain spaces<br />
<br />
===''2. Create .deb packages.''===<br />
{{Box Terminal|<br />
sh {{catalystfilename}} --buildpkg Ubuntu/intrepid<br />
}}<br />
<br />
===''3. Install .debs.''===<br />
For 32-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_8.582-0ubuntu1_i386.deb fglrx-kernel-source_8.582-0ubuntu1_i386.deb fglrx-amdcccle_8.582-0ubuntu1_i386.deb<br />
}}<br />
<br />
(This may fail due to a missing dpmk. If so install this first)<br />
<br />
or for 64-bit systems<br />
<br />
{{Box Terminal|<br />
sudo dpkg -i xorg-driver-fglrx_8.582-0ubuntu1_amd64.deb fglrx-kernel-source_8.582-0ubuntu1_amd64.deb fglrx-amdcccle_8.582-0ubuntu1_amd64.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Additional 64-bit instructions ==<br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo apt-get install -f<br />
}}<br />
<br />
Catalyst {{catalystversion}} on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
{{Box Terminal|<br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.573-0ubuntu1_amd64.deb fglrx-kernel-source_8.573-0ubuntu1_amd64.deb fglrx-amdcccle_8.573-0ubuntu1_amd64.deb<br />
}}<br />
''Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.''<br />
<br />
== Finishing the Install: Configuration ==<br />
<br />
'''If you've used fglrx previously, you will not need to do this.'''<br />
<br />
Now you'll have to edit your xorg.conf<br />
<br />
For Ubuntu:<br />
{{Box Terminal|<br />
sudo gedit /etc/X11/xorg.conf<br />
}}<br />
<br />
For Kubuntu:<br />
{{Box Terminal|<br />
sudo kate /etc/X11/xorg.conf<br />
}}<br />
<br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
Save and exit, then run<br />
{{Box Terminal|<br />
sudo aticonfig --initial -f<br />
}}<br />
in a terminal. If it doesn't give an error you should be good. <br />
<br />
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:<br />
<br />
{{Box Terminal|<br />
sudo aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki><br />
}}<br />
<br />
Finally, reboot the computer and type<br />
{{Box Terminal|<br />
fglrxinfo<br />
}}<br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.12 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: ATI Radeon HD 3850<br />
OpenGL version string: 2.1.8304 Release<br />
</pre><br />
<br />
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.<br />
<br />
== Finally ==<br />
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422<br />
# 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.<br />
# 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.<br />
<br />
Done! Now run amdcccle, glxgears, nexuiz, warsow etc :)<br />
<br />
= Issues =<br />
<br />
== Mesa drivers ==<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''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<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
: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: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
: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:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''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.<br />
:Run in a terminal:<br />
:<pre>uname -r</pre><br />
: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.<br />
<br />
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].<br />
<br />
<br />
== Hang at logout ==<br />
<br />
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:<br />
<br />
<pre>sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
<br />
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do : <br />
(assuming that the installer is in your home directory)<br />
<br />
<pre>sh ati-driver-installer-8-12-x86.x86_64.run --extract driver</pre> <br />
<br />
<pre>sudo cp ~/driver/packages/Ubuntu/dists/intrepid/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh</pre><br />
<br />
(intrepid is to be replaced by the name used at the building stage (hardy,8.10,8.04,etc...)<br />
<br />
<pre>sudo chmod +x /etc/ati/authatieventsd.sh</pre><br />
<br />
just reboot login and ctrl+alt+backspace to try<br />
<br />
== Suspend/Hibernation ==<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<blockquote><br />
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)<br />
</blockquote><br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
A second Radeon 3200 suspend/wake issue seems to be related to the mouse/keyboard itself. Adding a reset to the kernel line of your grub configuration seems to solve this. In other words, update /boot/grub/menu.lst and add an i8042.reset:<br />
<br />
<pre><br />
kernel /boot/vmlinuz-2.6.27-11-generic root=UUID=73293ec3-5ee4-418c-914<br />
4-1457914fb284 ro quiet splash i8042.reset<br />
</pre><br />
<br />
== Can't remove fglrx with dpkg ==<br />
<br />
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.<br />
<br />
== This module/version combo is already installed ==<br />
<br />
If you get this error-message, simply uninstall the previous version before installing the new one with:<br />
{{Box Terminal|<br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
}}<br />
<br />
== New kernel installed? ==<br />
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.<br />
You can do that by these simple steps:<br />
{{Box Terminal|<br />
sudo dkms build -m fglrx -v 8.552 -k `uname -r`<br /><br />
sudo dkms install -m fglrx -v 8.552 -k `uname -r`<br />
}}<br />
[[Category:Installation Documentation]]<br />
== AMD Control Center ==<br />
You can start the AMD Control Center by typing:<br />
{{Box Terminal|<br />
amdcccle<br />
}}<br />
If amdcccle doesn't work and says Identifier is not a valid word, this may be caused by some of the reasons below:<br /><br />
- Use lower case letter in xorg.conf.<br /><br />
- Make sure lines have no hard returns in them causing some parameters without their corresponding keywords are misinterpreted<br /><br />
- If amdcccle complains about some keyword in your xorg.conf and quits with a segmentation fault, you may just be working with a different xorg.conf than your system uses. I had a copy of some generic xorg.conf in my home directory, and amdcccle complained about stuff it couldn't cope with. You need to start amdcccle in your /etc/X11 directory.<br /></div>87.127.156.98http://wiki.cchtml.com/index.php?title=Ubuntu_Hardy_Installation_Guide&diff=4981Ubuntu Hardy Installation Guide2008-10-08T20:47:52Z<p>87.127.156.98: /* Method 1: Install the driver the Ubuntu Way */ removed 'll from you'll</p>
<hr />
<div>== Installation ==<br />
<br />
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.<br />
<br />
<br />
=== Method 1: Install the driver the Ubuntu Way ===<br />
<br />
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.<br />
<br />
<pre><br />
sudo apt-get update <br />
sudo apt-get install linux-restricted-modules-generic restricted-manager<br />
sudo apt-get install xorg-driver-fglrx<br />
sudo depmod -a<br />
</pre><br />
<br />
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.<br />
<br />
After this, you may need to edit Xorg.conf:<br />
<br />
<pre><br />
sudo gedit /etc/X11/xorg.conf<br />
</pre><br />
<br />
In the device section, if it is not already there add:<br />
<br />
{{Box File|/etc/X11/xorg.conf|<br />
Driver "fglrx"<br />
}}<br />
<br />
Then to make sure Xorg is set up correctly, you'll have to let aticonfig "initialize" it:<br />
<br />
<pre><br />
sudo aticonfig --initial -f<br />
</pre><br />
<br />
After this you should be able to restart your computer and have the driver working. To test type<br />
<br />
<pre><br />
fglrxinfo<br />
</pre><br />
<br />
into a terminal. If the vendor string is not ATI, but Mesa, check [[#Removing Mesa drivers]]<br />
<br />
==== Post-Installation Tweaks ====<br />
To enable hardware accelerated video on pre-R500 cards, edit '''/etc/X11/xorg.conf''' to include the following lines without '''[...]'''<br />
<br />
<pre><br />
Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
Option "VideoOverlay" "on"<br />
Option "OpenGLOverlay" "off"<br />
[...]<br />
EndSection<br />
</pre><br />
<br />
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.<br />
<br />
=== Method 2: Manual Method (installing Catalyst 8.8 or 8.9) ===<br />
<br />
wget https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8-9-x86.x86_64.run<br />
<br />
(this installer is for 32bit '''and''' 64bit systems)<br />
<br />
==== Follow These Instructions Carefully ====<br />
<br />
If you are using the x86_64 architecture (64 bit), be sure to inst "ia32-libs" before proceeding!<br />
<br />
<br />
Make sure ''universe'' and ''multiverse'' are enabled in your repository sources.<br />
<br />
<br />
Switch to the directory you downloaded the installer to.<br />
<br />
<br />
<pre><br />
sudo apt-get update<br />
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)<br />
</pre><br />
<br />
(package '''cdbs''' is required starting with Catalyst 8.8). On my machine it was installed during the package build process following the below command.<br />
<br />
Now use the following command to create the .deb files you will be using for installation:<br />
<pre><br />
sh ati-driver-installer-8-9-x86.x86_64.run --buildpkg Ubuntu/hardy<br />
</pre><br />
<br />
If that command does not work, download the driver itself from the official site (ati.com) and move it to your home folder (/home/<username>)<br />
<br />
If that command fails to find libGL.so.1, check your /usr/lib directory for libGL.so with:<br />
<pre><br />
ls /usr/lib/libGL*<br />
</pre><br />
If you can see libGL.so in that list then:<br />
<pre><br />
sudo ln -s /usr/lib/libGL.so /usr/lib/libGL.so.1<br />
</pre><br />
and Repeat<br />
<pre><br />
sh ati-driver-installer-8-9-x86.x86_64.run --buildpkg Ubuntu/hardy<br />
</pre><br />
Now we have to blacklist the driver in Ubuntu's repository, so that the new driver will be used.<br />
<br />
<pre><br />
sudo gedit /etc/default/linux-restricted-modules-common<br />
</pre><br />
<br />
Add "fglrx" to the line "DISABLED_MODULES"<br />
{{Box File|/etc/default/linux-restricted-modules-common|<br />
<pre>DISABLED_MODULES="fglrx"</pre><br />
}}<br />
<br />
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.8) is in use.<br />
<br />
You may also need to edit the file(s) (if they exist):<br />
<pre>sudo gedit /etc/modprobe.d/blacklist-restricted<br />
sudo gedit /etc/modprobe.d/blacklist-local</pre><br />
<br />
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.<br />
<br />
Install .debs. If there are no other versions of the driver in the same folder, you can save yourself some typing work:<br />
<pre><br />
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb<br />
</pre><br />
Otherwise, do not use wildcards. You can use this methode in any case.<br />
<pre><br />
sudo dpkg -i xorg-driver-fglrx_8.532-0ubuntu1_i386.deb fglrx-kernel-source_8.532-0ubuntu1_i386.deb fglrx-amdcccle_8.532-0ubuntu1_i386.deb<br />
</pre><br />
<br />
==== Additional 64-bit instructions ====<br />
<br />
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:<br />
<br />
<pre><br />
sudo apt-get install -f<br />
</pre><br />
<br />
Catalyst 8.8 on 64-bit systems requires the ''--force-overwrite'' command in the above ''dpkg'' command:<br />
<pre><br />
sudo dpkg -i --force-overwrite xorg-driver-fglrx_8.522*.deb fglrx-kernel-source_8.522-0*.deb fglrx-amdcccle_8.522-0*.deb<br />
</pre><br />
<br />
When installing the packages, if <tt>xorg-driver-fglrx_8.522</tt> fails to install due to a diverted file conflict, you can [http://emmetcaulfield.net/Tech/ATIv84+Hardy/ fix the package with this procedure].<br />
<br />
====Fix for an error:====<br />
If you are having this error:<br />
<pre><br />
dpkg-shlibdeps: failure: couldn't find library libfglrx_gamma.so.1 needed by debian/xorg-driver-fglrx/usr/bin/fglrx_xgamma (its RPATH is '').<br />
</pre><br />
<br />
Fix it by doing the following:<br />
<pre><br />
sudo sh ati-driver-installer-8-7-x86.x86_64.run --extract driver<br />
cd driver/arch/x86_64/usr/X11R6/lib64<br />
sudo ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1<br />
cd ../../../../../<br />
sudo sh ati-installer.sh -- --buildpkg Ubuntu/hardy<br />
</pre><br />
<br />
==== Finishing the Install: Configuration ====<br />
<br />
If you've used fglrx previously, you will not need to do this.<br />
<br />
Now you'll have to edit your xorg.conf<br />
<pre>sudo gedit /etc/X11/xorg.conf</pre><br />
and add the following line to the Device section (if it does not already exist). Include the following lines without '''[...]''': <br />
<pre>Section "Device"<br />
[...]<br />
Driver "fglrx"<br />
[...]<br />
EndSection</pre><br />
Save and exit, then run<br />
<pre>sudo aticonfig --initial -f</pre><br />
in a terminal. If it does not error you should be fine. <br />
<br />
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:<br />
<pre><br />
sudo aticonfig --input=/etc/X11/xorg.conf --tls=1<br />
</pre><br />
Finally, reboot the computer and type<br />
<pre><br />
fglrxinfo<br />
</pre><br />
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 8.8 looks like:<br />
<pre><br />
display: :0.0 screen: 0<br />
OpenGL vendor string: ATI Technologies Inc.<br />
OpenGL renderer string: Radeon X1950 Series<br />
OpenGL version string: 2.1.7873 Release<br />
</pre><br />
<br />
<br />
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.<br />
<br />
=== Removing Mesa drivers ===<br />
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, check:<br />
<br />
*Remove the package xserver-xgl.<br />
:<pre>sudo apt-get remove xserver-xgl</pre><br />
:'''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<br />
:<pre>DISPLAY=:0 glxinfo | grep render</pre><br />
: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])<br />
<br />
:'''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<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Enable"<br />
EndSection<br />
</pre><br />
<br />
<br />
----<br />
<br />
<br />
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: <br />
:<i>(EE) fglrx(0): [agp] unable to acquire AGP, error -1023<br />
:(EE) fglrx(0): cannot init AGP<br />
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.<br />
:(WW) fglrx(0): * DRI initialization failed! *</i><br />
<br />
: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: <br />
<pre>rmmod i82875p_edac<br />
rmmod fglrx<br />
rmmod intel-agp<br />
rmmod agpgart<br />
modprobe agpgart<br />
modprobe intel-agp<br />
modprobe fglrx</pre><br />
<br />
: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:<br />
:<pre>blacklist i82875p_edac</pre><br />
<br />
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).<br />
<br />
:'''Explanation:''' http://openwetware.org/wiki/Computing/Linux/Ubuntu<br />
<br />
<br />
----<br />
<br />
<br />
*Check you are running the correct kernel. <br />
:'''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.<br />
:Run in a terminal:<br />
:<pre>uname -r</pre><br />
: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.<br />
<br />
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].<br />
<br />
== Specific Issues ==<br />
<br />
=== Hang at logout ===<br />
<br />
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:<br />
<br />
<pre>sudo mkdir -p /var/lib/xdm/authdir<br />
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles</pre><br />
<br />
If that doesn't work then you can disable atieventsd with this command:<br />
<br />
<pre>sudo /usr/sbin/update-rc.d -f atieventsd remove</pre><br />
<br />
=== Suspend/Hibernation ===<br />
<br />
Suspend hibernation '''works''' with the latest driver.<br />
<br />
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:<br />
<br />
<pre><br />
SAVE_VBE_STATE=false<br />
<br />
POST_VIDEO=false <br />
<br />
ENABLE_LAPTOP_MODE=false<br />
</pre><br />
<br />
<br />
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:<br />
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)<br />
<br />
<pre><br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
Section "ServerFlags"<br />
Option "AIGLX" "off" <br />
EndSection<br />
</pre><br />
<br />
=== Error! This module/version combo is already installed ===<br />
<br />
Simply uninstall the previous version before installing the new one with<br />
<pre><br />
sudo dkms remove -m fglrx -v 8.522 --all<br />
</pre><br />
<br />
[[Category:Installation Documentation]]</div>87.127.156.98