<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.cchtml.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=217.43.0.0%2F16</id>
	<title>cchtml.com - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.cchtml.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=217.43.0.0%2F16"/>
	<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Special:Contributions/217.43.0.0/16"/>
	<updated>2026-11-18T13:03:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Talk:Ubuntu_Oneiric_Installation_Guide&amp;diff=8370</id>
		<title>Talk:Ubuntu Oneiric Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Talk:Ubuntu_Oneiric_Installation_Guide&amp;diff=8370"/>
		<updated>2012-04-03T23:44:16Z</updated>

		<summary type="html">&lt;p&gt;217.43.76.92: /* Problems */ no worries.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Other Fixes ==&lt;br /&gt;
&lt;br /&gt;
Other fixes that may not appropriate for the guide.&lt;br /&gt;
&lt;br /&gt;
=== Unity 3D Slowness ===&lt;br /&gt;
&lt;br /&gt;
In natty/oneiric ubuntu (11.04 + 11.10) some fglrx drivers and unity are extremely slow by default, it can be improved a lot :&lt;br /&gt;
&lt;br /&gt;
1. via compizconfig settings manager, general set the refresh rate ( re-draw speed of compiz ) to the highest you can ( up to 200 ) and disable &amp;quot;auto detect refresh rate&amp;quot; , &lt;br /&gt;
&lt;br /&gt;
2. disable in OpenGL settings of compiz : vsync, but enable it ( &amp;quot;tear-free&amp;quot; )  in the Ati Control Panel &lt;br /&gt;
&lt;br /&gt;
In the daily &#039;&#039;&#039;12.04&#039;&#039;&#039; build of today and fglrx from ubuntus own repo all this is no longer necessary, unity3d is finally very fast out of the box and &amp;quot;just works&amp;quot; wonderful. But for all earlier versions the above tweaks do a lot improvements. &lt;br /&gt;
&lt;br /&gt;
thks&lt;br /&gt;
&lt;br /&gt;
a german [[hd4650 mobility]] , M96/ device id 0x9480 (1gb vram ) user&lt;br /&gt;
&lt;br /&gt;
--[[Special:Contributions/78.50.84.241|78.50.84.241]] 14:47, 28 February 2012 (CST)&lt;br /&gt;
&lt;br /&gt;
=== &amp;quot;Jittery&amp;quot; Video After Installing Manual ATI Drivers From AMD Website ===&lt;br /&gt;
&lt;br /&gt;
I am 270% (down from 300%) new to Ubuntu, Video Settings and Mathematical Percentages. So if this is covered somewhere else, please excuse this post, I was unable to find those in my searches and I wanted to help.&lt;br /&gt;
&lt;br /&gt;
In two installs of Ubuntu (11.10 and 11.04), after installing the drivers from ATI, the video would get choppy as though two interlaced streams were offset. When taking screenshots, the video looked normal (making asking for support difficult). &lt;br /&gt;
After using this guide, I enabled Tear-Free video with no effect.&lt;br /&gt;
Through a stroke of genius (dumb luck), I changed the image options to &amp;quot;use grpahics processor for scaling&amp;quot; (Catalyist Control Center &amp;gt; Display Manager &amp;gt; Display In Use &amp;gt; Adjustments) . After hitting apply, the problem was resolved.&lt;br /&gt;
&lt;br /&gt;
== Update Guide Suggestions ==&lt;br /&gt;
&lt;br /&gt;
Suggestions that should be fixed/added/subtracted from the guide.&lt;br /&gt;
&lt;br /&gt;
=== Got Several ===&lt;br /&gt;
&lt;br /&gt;
GDM is not being used any more in Ubuntu 11.10, instead LightDM has replaced it. Therefore the section &amp;quot;Slow Maximizing Windows/General 2D Slowness&amp;quot; is outdated. &lt;br /&gt;
&lt;br /&gt;
Using &amp;quot;sudo aticonfig --set-pcs-str=&amp;quot;DDX,EnableRandR12,FALSE&amp;quot;&amp;quot; is redundant as well. It either does not apply any more or it will be ignored anyway, judged by the xorg log. &lt;br /&gt;
&lt;br /&gt;
When trying to completely remove fglrx, the package &amp;quot;xorg-driver-fglrx&amp;quot; can not be removed (any more?) because it&#039;s a virtual package. It can therefore be left out in the guide. &lt;br /&gt;
&lt;br /&gt;
Things like these should not be just taken over without actually checking if it is still required. What is the point of creating a new page for a new distributing version if the contents is just being copied anyway? &lt;br /&gt;
I bet there&#039;s plenty of other stuff that does not apply any more because of a new distro update or new driver versions. These things should be checked first before taking them over. Just copying might do more harm then good to a system. It might also unnecessarily reduce system performance.&lt;br /&gt;
&lt;br /&gt;
Also. It has never been clear to me why this guide is going through all the trouble of creating .deb file of the proprietary driver. What&#039;s the point? Why make things more difficult for a user if he can just as well run the installer provided by ATI right away? I&#039;d say stick to that and create a separate page explaining why and how to create the .deb files. This way the info does not have to keep duplicated every time and things become less complicated for the casual user because you&#039;re sticking to the essentials in the main guide.--[[User:Forage|Forage]] 12:10, 31 October 2011 (CDT)&lt;br /&gt;
&lt;br /&gt;
(**Response to above)&lt;br /&gt;
Thanks for pointing these things out. I wrote/edited a lot of the Ubuntu guide beginning with Lucid, and I &amp;quot;inherited&amp;quot; 2 obsolete tips you pointed out, so I wasn&#039;t exactly sure about them. I didn&#039;t like the thought of removing peoples&#039; work if I wasn&#039;t 100% sure that it was obsolete/harmful. TBH, I personally don&#039;t use Ubuntu much anymore (and usually run it in Virtualbox when I do), so I didn&#039;t think about the lightdm thing. FWIW, I don&#039;t see those sections/commands as being too dangerous (though I&#039;ll definitely remove them). On the other hand, running the ati installer without building packages is dangerous because it doesn&#039;t properly handle libgl(x) alternatives (and there are other Debian policy violations too). It can easily leave inexperienced users with no X if they install a normal update of mesa (which overwrites the proprietary ATI version of libgl(x).so as a side effect). I&#039;m personally not going to recommend that on a distro where a lot of users have no terminal experience/skill beyond copying and pasting commands.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;manually install Catalyst&amp;quot; portion of the guide existed because Ubuntu would only provide one version of fglrx per release and leave it at that. With the advent of the fglrx-updates package to automatically get/install Catalyst updates, I&#039;ll probably recommend that (but I&#039;m personally not going to remove the manual build in case users need it). I haven&#039;t used fglrx-updates yet, so give me a few days to play with it (or, better yet, someone who has more interet/experience can add that section). --[[User:Dtl131|Dtl131]] 15:06, 31 October 2011 (CDT)&lt;br /&gt;
&lt;br /&gt;
On amd64, amdcccle crashes when clicking &#039;apply&#039; after trying to set Multi-display desktop.  Is there a work-around?  Still broken with 11.12.&lt;br /&gt;
&lt;br /&gt;
=== Root Privledges, Package Creation Unnecessary ===&lt;br /&gt;
&lt;br /&gt;
Building a package doesn&#039;t require root permission.  Instead this can be used:&lt;br /&gt;
&lt;br /&gt;
 ./amd-driver-installer-12-2-x86.x86_64.run --buildpkg Ubuntu/oneiric&lt;br /&gt;
&lt;br /&gt;
==Problems==&lt;br /&gt;
Hi, I had the 12.2 proprietary driver working really well. Unfortunately I fear a apt-get upgrade may have broken the driver, so I&#039;m trying to upgrade the driver.&lt;br /&gt;
I&#039;ve followed the instructions to first remove the existing driver which seemed to work ok - cmd line suggested I autoremove a few packages in addition to the instruction, which I have done.&lt;br /&gt;
I&#039;ve downloaded the new 12.3 driver and get to the line, sudo sh ./amd-driver-installer-12-3-x86.x86_64.run --buildpkg Ubuntu/oneiric&lt;br /&gt;
which fails. Follows is the last bit of the script before failure......&lt;br /&gt;
&lt;br /&gt;
 #Run the normal stuff&lt;br /&gt;
 dh binary-arch&lt;br /&gt;
   dh_auto_install -a -Nfglrx -Nfglrx-amdcccle&lt;br /&gt;
   dh_install -a -Nfglrx -Nfglrx-amdcccle&lt;br /&gt;
   dh_installdocs -a -Nfglrx&lt;br /&gt;
   dh_installchangelogs -a -Nfglrx&lt;br /&gt;
   dh_installexamples -a -Nfglrx&lt;br /&gt;
   dh_installman -a -Nfglrx&lt;br /&gt;
   dh_installcatalogs -a -Nfglrx&lt;br /&gt;
   dh_installcron -a -Nfglrx&lt;br /&gt;
   dh_installdebconf -a -Nfglrx&lt;br /&gt;
   dh_installemacsen -a -Nfglrx&lt;br /&gt;
   dh_installifupdown -a -Nfglrx&lt;br /&gt;
   dh_installinfo -a -Nfglrx&lt;br /&gt;
   dh_pysupport -a -Nfglrx&lt;br /&gt;
   dh_installinit -a -Nfglrx&lt;br /&gt;
   dh_installmenu -a -Nfglrx&lt;br /&gt;
   dh_installmime -a -Nfglrx&lt;br /&gt;
   dh_installmodules -a -Nfglrx&lt;br /&gt;
   dh_installlogcheck -a -Nfglrx&lt;br /&gt;
   dh_installlogrotate -a -Nfglrx&lt;br /&gt;
   dh_installpam -a -Nfglrx&lt;br /&gt;
   dh_installppp -a -Nfglrx&lt;br /&gt;
   dh_installudev -a -Nfglrx&lt;br /&gt;
   dh_installwm -a -Nfglrx&lt;br /&gt;
   dh_installxfonts -a -Nfglrx&lt;br /&gt;
   dh_installgsettings -a -Nfglrx&lt;br /&gt;
   dh_bugfiles -a -Nfglrx&lt;br /&gt;
   dh_ucf -a -Nfglrx&lt;br /&gt;
   dh_lintian -a -Nfglrx&lt;br /&gt;
   dh_gconf -a -Nfglrx&lt;br /&gt;
   dh_icons -a -Nfglrx&lt;br /&gt;
   dh_perl -a -Nfglrx&lt;br /&gt;
   dh_usrlocal -a -Nfglrx&lt;br /&gt;
   dh_link -a -Nfglrx&lt;br /&gt;
   dh_compress -a&lt;br /&gt;
   dh_fixperms -a&lt;br /&gt;
   dh_strip -a&lt;br /&gt;
   dh_makeshlibs -a&lt;br /&gt;
 objdump: debian/fglrx/usr/lib/pxpress/alt_ld.so.conf: File truncated&lt;br /&gt;
 objdump: debian/fglrx/usr/lib/pxpress/ld.so.conf: File format not recognized&lt;br /&gt;
 objdump: debian/fglrx/usr/lib/fglrx/alt_ld.so.conf: File truncated&lt;br /&gt;
 objdump: debian/fglrx/usr/lib/fglrx/ld.so.conf: File format not recognized&lt;br /&gt;
   debian/rules override_dh_shlibdeps&lt;br /&gt;
 make[1]: Entering directory `/tmp/fglrx.0W1fVM&#039;&lt;br /&gt;
 dh_shlibdeps -l/tmp/fglrx.0W1fVM/debian/fglrx/usr/lib/fglrx:/tmp/fglrx.0W1fVM/debian/fglrx/usr/lib32/fglrx -Xlib32&lt;br /&gt;
 dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/libAMDXvBA.so.1.0 contains an unresolvable reference to symbol dlsym: it&#039;s probably a plugin.&lt;br /&gt;
 dpkg-shlibdeps: warning: 21 other similar warnings have been skipped (use -v to see them all).&lt;br /&gt;
 dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/bin/atieventsd contains an unresolvable reference to symbol XauFileName: it&#039;s probably a plugin.&lt;br /&gt;
 dpkg-shlibdeps: warning: debian/fglrx/usr/lib/fglrx/libGL.so.1.2 contains an unresolvable reference to symbol XOpenDisplay: it&#039;s probably a plugin.&lt;br /&gt;
 dpkg-shlibdeps: warning: 31 other similar warnings have been skipped (use -v to see them all).&lt;br /&gt;
 dpkg-shlibdeps: error: no dependency information found for /usr/share/ati/lib64/libQtCore.so.4 (used by debian/fglrx/usr/lib/fglrx/bin/amdnotifyui).&lt;br /&gt;
 dh_shlibdeps: dpkg-shlibdeps -Tdebian/fglrx.substvars debian/fglrx/usr/lib/fglrx/libAMDXvBA.so.1.0 debian/fglrx/usr/lib/fglrx/libatiadlxx.so debian/fglrx/usr/lib/fglrx/libfglrx_dm.so.1.0 debian/fglrx/usr/lib/fglrx/libXvBAW.so.1.0 debian/fglrx/usr/lib/fglrx/libamdocl64.so debian/fglrx/usr/lib/fglrx/libaticalcl.so debian/fglrx/usr/lib/fglrx/libaticaldd.so debian/fglrx/usr/lib/fglrx/libaticalrt.so debian/fglrx/usr/lib/fglrx/libatiuki.so.1.0 debian/fglrx/usr/lib/fglrx/libOpenCL.so.1 debian/fglrx/usr/lib/fglrx/libSlotMaximizerAg.so debian/fglrx/usr/lib/fglrx/libSlotMaximizerBe.so debian/fglrx/usr/lib/fglrx/libGL.so.1.2 debian/fglrx/usr/lib/fglrx/xorg/modules/amdxmm.so debian/fglrx/usr/lib/fglrx/xorg/modules/glesx.so debian/fglrx/usr/lib/fglrx/xorg/modules/extensions/libglx.so  debian/fglrx/usr/lib/fglrx/xorg/modules/linux/libfglrxdrm.so debian/fglrx/usr/lib/fglrx/xorg/modules/drivers/fglrx_drv.so debian/fglrx/usr/lib/fglrx/dri/fglrx_dri.so debian/fglrx/usr/lib/fglrx/bin/amdnotifyui debian/fglrx/usr/lib/fglrx/bin/atieventsd debian/fglrx/usr/lib/fglrx/bin/aticonfig debian/fglrx/usr/lib/fglrx/bin/atiodcli debian/fglrx/usr/lib/fglrx/bin/atiode debian/fglrx/usr/lib/fglrx/bin/fgl_glxgears debian/fglrx/usr/lib/fglrx/bin/fglrxinfo returned exit code 2&lt;br /&gt;
 make[1]: *** [override_dh_shlibdeps] Error 2&lt;br /&gt;
 make[1]: Leaving directory `/tmp/fglrx.0W1fVM&#039;&lt;br /&gt;
 make: *** [binary-arch] Error 2&lt;br /&gt;
 dpkg-buildpackage: error: debian/rules binary gave error exit status 2&lt;br /&gt;
 Removing temporary directory: fglrx-install.mMmVPT&lt;br /&gt;
&lt;br /&gt;
any thoughts on how to fix this? Many thanks, Russ [[Special:Contributions/81.155.73.131|81.155.73.131]] 12:35, 31 March 2012 (CDT)&lt;br /&gt;
&lt;br /&gt;
Actually scrub this - it wasn&#039;t an update that screwed my existing driver but my SSD hardrive dying - had to reinstall from scratch anyway. --[[Special:Contributions/217.43.76.92|217.43.76.92]] 18:44, 3 April 2012 (CDT)&lt;/div&gt;</summary>
		<author><name>217.43.76.92</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Jaunty_Installation_Guide&amp;diff=5571</id>
		<title>Ubuntu Jaunty Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Jaunty_Installation_Guide&amp;diff=5571"/>
		<updated>2009-05-25T18:51:52Z</updated>

		<summary type="html">&lt;p&gt;217.43.174.169: /* Installation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
{| WIDTH=&amp;quot;650&amp;quot; cellpadding=0 cellspacing=0 style=&amp;quot;background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;&amp;quot; &lt;br /&gt;
| style=&amp;quot;background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;&amp;quot; | &amp;lt;font size=&amp;quot;-1&amp;quot;&amp;gt;&#039;&#039;&#039;ATTENTION UBUNTU JAUNTY USERS&#039;&#039;&#039;&amp;lt;/font&amp;gt; &lt;br /&gt;
|- &lt;br /&gt;
| &amp;lt;br /&amp;gt;Warning: Does not work for all system combinations at this time&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
= The Alternatives =&lt;br /&gt;
Users with ATI cards basically have these options:&lt;br /&gt;
# &#039;&#039;&#039;Open Source Drivers&#039;&#039;&#039; 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. &lt;br /&gt;
# &#039;&#039;&#039;The Ubuntu Way&#039;&#039;&#039;  Use the restricted-driver management system that comes with Ubuntu to install the drivers.&lt;br /&gt;
# &#039;&#039;&#039;Third (Fourth?) Party Installer&#039;&#039;&#039; Use envy/jockey or other installer helper.&lt;br /&gt;
# &#039;&#039;&#039;Install the drivers manually&#039;&#039;&#039;  Using the installer downloaded from AMD&#039;s site via either package based install or direct install. &lt;br /&gt;
&lt;br /&gt;
= Open Source Drivers =&lt;br /&gt;
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&#039;t need to change anything.&lt;br /&gt;
&lt;br /&gt;
The drivers that may be used are&lt;br /&gt;
* &#039;&#039;&#039;vesa&#039;&#039;&#039; Lowest common denominator across all graphics vendor, not many features.&lt;br /&gt;
* &#039;&#039;&#039;ati&#039;&#039;&#039; Actually a facade that will invoke the radeon driver. &lt;br /&gt;
* &#039;&#039;&#039;radeon&#039;&#039;&#039; Driver support all radeon classes of hardware - with limited 3D for newer cards.&lt;br /&gt;
* &#039;&#039;&#039;radeonhd&#039;&#039;&#039; An alternate driver support R520 hardware and later.&lt;br /&gt;
&lt;br /&gt;
By default there is no configuration file for X anymore, so X will try to do the right thing.&lt;br /&gt;
&lt;br /&gt;
If you run into stability problems with 3D applications using the radeon/radeonhd drivers, consider trying a more recent kernel.&lt;br /&gt;
[http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/ mainline-2.6.29.3] did the trick on a few machines.&lt;br /&gt;
&lt;br /&gt;
There&#039;s an ongoing debate about how and if the radeon and radeonhd drivers will be used in the future.&lt;br /&gt;
&lt;br /&gt;
= The Ubuntu way =&lt;br /&gt;
&lt;br /&gt;
== Restricted Drivers Manager ==&lt;br /&gt;
* Ubuntu 9.04 (Jaunty) provides a notification saying that there are restricted drivers available&lt;br /&gt;
* Go to the Restricted Drivers Manager and enable the &amp;quot;ATI accelerated graphics driver&amp;quot;&lt;br /&gt;
* Ubuntu will then install and configure the driver for you&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Installing the drivers manually =&lt;br /&gt;
*PLEASE READ FIRST!&lt;br /&gt;
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&#039;t support any of the older ATI cards anymore. Which cards does ATI no longer support?&lt;br /&gt;
&#039;&#039;The ATI Radeon 9500-9800,X300-X2100,Xpress.  See the complete list [http://wiki.cchtml.com/index.php/9.4] here.&#039;&#039;&lt;br /&gt;
If your card is on that list, you are restricted to the 9.3 driver - however since 9.3 driver doesn&#039;t support xorg-xserver 1.6, it will not work with Jaunty!  This guide currently is for installing 9.5. !!!SO BE CAREFUL!!!&lt;br /&gt;
&lt;br /&gt;
_______________________________________________&lt;br /&gt;
&lt;br /&gt;
I recommend using copy and paste. However, you can Ctrl + C in your browser but you cannot Ctrl + V in the terminal. When you have copied something simply use Shift + Insert to paste into the terminal or go to the terminals menu, select edit and click paste. This method will ensure there are no typing mistakes and will greatly speed up the install process.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you are using the x86_64 architecture (64 bit), be sure to install &amp;quot;ia32-libs&amp;quot; before proceeding!&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Make sure &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; are enabled in your repository sources.&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;Before you start&#039;&#039;===&lt;br /&gt;
Install the necessary programs&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++5 dkms &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;1. Download the latest Catalyst package.&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
Download page: Catalyst 9.5 https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-9-5-x86.x86_64.run. This package contains both the 32-bit and 64-bit driver.&lt;br /&gt;
&lt;br /&gt;
Open a terminal window and switch to the directory you downloaded the installer to. (Example: $ cd Desktop)&lt;br /&gt;
&lt;br /&gt;
Make sure your directory path does not contain spaces&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;2. Create .deb packages.&#039;&#039;===&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sh ati-driver-installer-9-5-x86.x86_64.run --buildpkg Ubuntu/jaunty&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;3. Just in case&#039;&#039;===&lt;br /&gt;
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&#039;t work.&lt;br /&gt;
&lt;br /&gt;
Alt+PrntScr+r, Alt+PrntScr+s, Alt+PrntScr+e, Alt+PrntScr+i, Alt+PrntScr+n, Alt+PrntScr+u, Alt+PrntScr+b&lt;br /&gt;
&lt;br /&gt;
These keypresses will reboot the system safely. To remember the keypresses, remember this nonsensical phrase: &amp;quot;Raising Skinny Elephants Is Never Utterly Boring&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;4. Install .debs.&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
Install the debs, depending on if you&#039;re on a 32-bit or 64-bit system:&lt;br /&gt;
&lt;br /&gt;
* For 32-bit systems&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
(This may fail due to a missing dpmk(maybe it&#039;s dkms?check it). If so install this first.  Also check the version numbers (8.561) against the created debs)&lt;br /&gt;
&lt;br /&gt;
* For 64-bit systems&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;5. Additional 64-bit instructions&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
If you have a 64 bit install, the above dpkg command may complain that &amp;quot;Errors were encountered while processing: fglrx-amdcccle&amp;quot;.  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:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo apt-get install -f&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Catalyst 9.5 on 64-bit systems requires the &#039;&#039;--force-overwrite&#039;&#039; command in the above &#039;&#039;dpkg&#039;&#039; command:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dpkg -i --force-overwrite xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;Using [http://en.wikipedia.org/wiki/Command_line_completion tab completion] can make this command easier.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Finishing the Install: Configuration ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039; Note: try auto config first (what in the heck is auto config??), and follow the question guide, reboot; if no effect observed, restore &#039;&#039;xorg.conf-bkp&#039;&#039; &#039;&#039;&lt;br /&gt;
I personally don&#039;t recommend this method but it does work. I find the method starting with &amp;quot;If you&#039;ve used fglrx previously, you will not need to do this.&amp;quot; to be faster and easier.&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf-bkp &amp;lt;br /&amp;gt;&lt;br /&gt;
sudo dpkg-reconfigure xserver-xorg&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;Now you&#039;ll have to edit your xorg.conf&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note: If you&#039;ve used fglrx previously, you will not need to do this.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For Ubuntu:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo gedit /etc/X11/xorg.conf&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
For Kubuntu:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo kate /etc/X11/xorg.conf&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
and add the following line to the Device section (if it does not already exist).  Include the following lines without &#039;&#039;&#039;[...]&#039;&#039;&#039;: &lt;br /&gt;
&amp;lt;pre&amp;gt;Section &amp;quot;Device&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
	Driver		&amp;quot;fglrx&amp;quot;&lt;br /&gt;
	[...]&lt;br /&gt;
EndSection&amp;lt;/pre&amp;gt;&lt;br /&gt;
Save and exit, then run&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;6. Generate a new /etc/Xorg.conf file&#039;&#039;===&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo aticonfig --initial -f&lt;br /&gt;
}}&lt;br /&gt;
in a terminal. If it doesn&#039;t give an error you should be good. &lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;7. Force use of /etc/Xorg.conf file&#039;&#039;===&lt;br /&gt;
Some people find that changes to xorg.conf don&#039;t get used by the driver. To force the ati driver to adopt changes made to xorg.conf, type the following command:&lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo aticonfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;8. Test your installation&#039;&#039;===&lt;br /&gt;
Finally, reboot the computer and type&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
fglrxinfo&lt;br /&gt;
}}&lt;br /&gt;
into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Release 9.4 looks like:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI Radeon HD 4800 Series (This line may be different depending on what graphics card you are using.)&lt;br /&gt;
OpenGL version string: 2.1.8664&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=HOW TO UPDATE DRIVER=&lt;br /&gt;
&lt;br /&gt;
To update your driver to a new version (say 9.4 to 9.5) first disable the current driver through Ubuntu&#039;s Hardware Manager or use EnvyNG to remove the driver, then go to synaptic and search for &amp;quot;xorg-driver-fglrx&amp;quot; without the quotes and mark it for &amp;quot;Complete removal&amp;quot; and hit &amp;quot;Apply&amp;quot; then reboot your computer. Now simply repeat steps #1, 2, 4 and finally run these commends in a terminal: {{Box Terminal|sudo aticonfig --initial -f&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
and &lt;br /&gt;
&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo aticonfig &amp;lt;nowiki&amp;gt;--input=/etc/X11/xorg.conf --tls=1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
then reboot.&lt;br /&gt;
&lt;br /&gt;
It is very important that you COMPLETELY remove the old driver which includes the config files because when upgrading without uninstalling the old driver I noticed even though the new driver installed and worked there were some annoying problems that I experienced but after I completely uninstalled the driver then reinstalled it, it worked perfectly.&lt;br /&gt;
&lt;br /&gt;
=Tweaks=&lt;br /&gt;
# Add tweaks as needed: http://ubuntuforums.org/showthread.php?t=849422&lt;br /&gt;
# Restart X, if it doesn&#039;t work, you can use the &amp;quot;vesa&amp;quot;, &amp;quot;ati&amp;quot;, &amp;quot;radeon&amp;quot; or &amp;quot;radeonhd&amp;quot; driver in the mean time, until you make it work.&lt;br /&gt;
# If you downgraded X to make fglrx work: enter synaptic, make sure all packages with &amp;quot;xorg&amp;quot; and &amp;quot;x11&amp;quot; are locked so that you can update and upgrade without worries.&lt;br /&gt;
&lt;br /&gt;
Done! Now run amdcccle, glxgears, warsow etc :)&lt;br /&gt;
&lt;br /&gt;
= Issues =&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
There are some system configurations on which &#039;&#039;&#039;none&#039;&#039;&#039; of the installation alternatives work with the latest 9.4 driver (please add; also please add if you got it to work in one of the listed setups):&lt;br /&gt;
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD4870X2: Framebuffer error, garbled screen.&lt;br /&gt;
* Ubuntu 9.04 (x64) on x86_64 with Radeon HD 3300 (790GX): garbled screen.&lt;br /&gt;
**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&#039;t know how to remove fglrx, but you may be able to avoid reinstalling by following fglrx complete removal in this guide.&lt;br /&gt;
**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.&lt;br /&gt;
&lt;br /&gt;
== Mesa drivers ==&lt;br /&gt;
If fglrxinfo reports that Indirect rendering by Mesa is in place, even though you have installed ATI driver, you might want to remove Mesa:&lt;br /&gt;
&lt;br /&gt;
*Remove the package xserver-xgl.&lt;br /&gt;
:&amp;lt;pre&amp;gt;sudo apt-get remove xserver-xgl&amp;lt;/pre&amp;gt;&lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; 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&lt;br /&gt;
:&amp;lt;pre&amp;gt;DISPLAY=:0 glxinfo | grep render&amp;lt;/pre&amp;gt;&lt;br /&gt;
: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])&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Warning:&#039;&#039;&#039; 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 &amp;quot;Composite&amp;quot; problem, check that the following is set in the /etc/X11/xorg.conf&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
	Option		&amp;quot;Composite&amp;quot;	&amp;quot;Enable&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Check for AGP and DRI errors in /var/log/Xorg.0.log like these are: &lt;br /&gt;
:&amp;lt;i&amp;gt;(EE) fglrx(0): [agp] unable to acquire AGP, error -1023&lt;br /&gt;
:(EE) fglrx(0): cannot init AGP&lt;br /&gt;
:(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.&lt;br /&gt;
:(WW) fglrx(0): * DRI initialization failed!                  *&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
: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: &lt;br /&gt;
&amp;lt;pre&amp;gt;rmmod i82875p_edac&lt;br /&gt;
rmmod fglrx&lt;br /&gt;
rmmod intel-agp&lt;br /&gt;
rmmod agpgart&lt;br /&gt;
modprobe agpgart&lt;br /&gt;
modprobe intel-agp&lt;br /&gt;
modprobe fglrx&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:Blacklist the modules e7xxx_edac so it doesn&#039;t start up again when booting - add the following line at the beginning of /etc/modprobe.d/blacklist:&lt;br /&gt;
:&amp;lt;pre&amp;gt;blacklist i82875p_edac&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:This has been known to fix issues with -Mesa -AGP -DRI -Google earth and -suspend to RAM (s2ram).&lt;br /&gt;
 &lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; http://openwetware.org/wiki/Computing/Linux/Ubuntu&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Check you are running the correct kernel. &lt;br /&gt;
:&#039;&#039;&#039;Explanation:&#039;&#039;&#039; If you&#039;re upgrading from Gutsy to Hardy in some instances the Grub bootloader does not get updated and the new kernel is not loaded.&lt;br /&gt;
:Run in a terminal:&lt;br /&gt;
:&amp;lt;pre&amp;gt;uname -r&amp;lt;/pre&amp;gt;&lt;br /&gt;
: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.&lt;br /&gt;
&lt;br /&gt;
If this doesn&#039;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].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Hang at logout ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo mkdir -p /var/lib/xdm/authdir&lt;br /&gt;
sudo ln -s /var/run/xauth /var/lib/xdm/authdir/authfiles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work then you can disable atieventsd with this command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo /usr/sbin/update-rc.d -f atieventsd remove&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Before the above commands verify that /etc/ati/authatieventsd.sh exists after build and install, if not just do  : &lt;br /&gt;
(assuming that the installer is in your home directory)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sh ati-driver-installer-8-12-x86.x86_64.run --extract driver&amp;lt;/pre&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo cp ~/driver/packages/Ubuntu/dists/jaunty/replacements/authatieventsd.sh /etc/ati/authatieventsd.sh&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(jaunty is to be replaced by the name used at the building stage (intrepid,hardy,8.10,8.04,etc...)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo chmod +x /etc/ati/authatieventsd.sh&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
just reboot login and ctrl+alt+backspace to try&lt;br /&gt;
&lt;br /&gt;
== Suspend/Hibernation ==&lt;br /&gt;
&lt;br /&gt;
Suspend hibernation &#039;&#039;&#039;works&#039;&#039;&#039; with the latest driver.&lt;br /&gt;
&lt;br /&gt;
For ATI X1400, to get the laptop to wake up from suspend, I had to change the following in /etc/default/acpi-support:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
SAVE_VBE_STATE=false&lt;br /&gt;
&lt;br /&gt;
POST_VIDEO=false &lt;br /&gt;
&lt;br /&gt;
ENABLE_LAPTOP_MODE=false&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&lt;br /&gt;
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 &amp;quot;acpi-support&amp;quot; to SUSPEND_METHODS.  --[[User:Bewst|Bewst]] 23:22, 19 December 2008 (UTC)&lt;br /&gt;
&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For Radeon 3200, to wake up from suspend, I had to add the following lines to /etc/X11/xorg.conf:&lt;br /&gt;
(This settings is not good option, if you are using compiz-fusion or any other transparency-based thingie. Not working for HD 3850)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Section &amp;quot;Extensions&amp;quot;&lt;br /&gt;
        Option        &amp;quot;Composite&amp;quot;        &amp;quot;Disable&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&lt;br /&gt;
Section &amp;quot;ServerFlags&amp;quot;&lt;br /&gt;
       Option  &amp;quot;AIGLX&amp;quot; &amp;quot;off&amp;quot; &lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Can&#039;t remove fglrx with dpkg ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== This module/version combo is already installed ==&lt;br /&gt;
&lt;br /&gt;
If you get this error-message, simply uninstall the previous version before installing the new one with:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dkms remove -m fglrx -v 8.522 --all&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== New kernel installed? ==&lt;br /&gt;
I found out that when getting a new kernel the fglrx kernel-module is not installed for your new kernel.&lt;br /&gt;
You can do that by these simple steps:&lt;br /&gt;
{{Box Terminal|&lt;br /&gt;
sudo dkms build -m fglrx -v 8.552 -k `uname -r`&amp;lt;br /&amp;gt;&lt;br /&gt;
sudo dkms install -m fglrx -v 8.552 -k `uname -r`&lt;br /&gt;
}}&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
if amdcccle doesn&#039;t work and says Identifier is not a valid word. Use lower case letter in xorg.conf&lt;/div&gt;</summary>
		<author><name>217.43.174.169</name></author>
	</entry>
</feed>