<?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=202.134.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=202.134.0.0%2F16"/>
	<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Special:Contributions/202.134.0.0/16"/>
	<updated>2026-11-22T02:19:38Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Ubuntu_Feisty_Installation_Guide&amp;diff=3835</id>
		<title>Ubuntu Feisty Installation Guide</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Ubuntu_Feisty_Installation_Guide&amp;diff=3835"/>
		<updated>2008-06-23T04:02:47Z</updated>

		<summary type="html">&lt;p&gt;202.134.12.11: /* Pre-Installation Checks */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The [[:Category:Releases|latest]] fglrx driver supports Radeon 9500  and the X-series cards up to HD2900. Workstation cards are not supported.&lt;br /&gt;
&lt;br /&gt;
CIiyPa df8v7ydfv83f61fvr58fdz&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
&lt;br /&gt;
===Method 1: Install the Driver the Ubuntu Way===&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update&lt;br /&gt;
sudo apt-get install linux-restricted-modules-generic restricted-manager&lt;br /&gt;
sudo apt-get install xorg-driver-fglrx&lt;br /&gt;
sudo depmod -a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: The second line of the above may not be necessary.  If apt says it cannot find the &amp;quot;linux-restricted-modules&amp;quot; package, try line 3.  If that fails, check your sources.list (see top of page)&lt;br /&gt;
&lt;br /&gt;
If the system complains about dependencies, use your preferred package manager to download python2.4 and, if necessary, its dependencies.&lt;br /&gt;
&lt;br /&gt;
===Method 2: Install the 8.42.3 Driver Manually===&lt;br /&gt;
&lt;br /&gt;
*Note: &#039;&#039;This is just an alternative installation method for the section above. It might help if you still get &#039;DRI missing&#039; errors.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Download the ATI driver installer:&lt;br /&gt;
[https://www2.ati.com/drivers/linux/ati-driver-installer-8.42.3-x86.x86_64.run ati-driver-installer-8.42.3-x86.x86_64.run] (this installer is for 32bit &#039;&#039;&#039;and&#039;&#039;&#039; 64bit systems)&lt;br /&gt;
&lt;br /&gt;
Change to the download directory.  Make sure that you have the &#039;&#039;universe&#039;&#039; and &#039;&#039;multiverse&#039;&#039; repositories enabled in &#039;&#039;/etc/apt/sources.list&#039;&#039; before doing these steps.  &lt;br /&gt;
&lt;br /&gt;
There is a detailed manual with screenshots at [https://wiki.ubuntu.com/AddingRepositoriesHowto Ubuntu Wiki].&lt;br /&gt;
&lt;br /&gt;
By default, Ubuntu does not enable the Universe and Multiverse repositories. But they include some important programs and codecs, so it is highly recommended to activate them.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Install necessary tools:&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get update&lt;br /&gt;
sudo apt-get install module-assistant build-essential fakeroot dh-make debhelper \&lt;br /&gt;
debconf libstdc++5 linux-headers-generic&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create .deb packages:&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo bash ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Ubuntu/feisty&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Blacklist old fglrx module from linux-restricted-modules:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Note: You only need to do this if you&#039;ve installed the driver from Method 2 above.&lt;br /&gt;
&lt;br /&gt;
As ubuntu&#039;s &#039;&#039;linux-restricted-modules&#039;&#039; package includes the fglrx module from an old driver version (8.28.8), we have to blacklist this module to make sure the new kernel module which is needed by the new driver will be used instead.&lt;br /&gt;
&lt;br /&gt;
Ubuntu/Gnome users type in:&lt;br /&gt;
&amp;lt;pre&amp;gt;gksu gedit /etc/default/linux-restricted-modules-common&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Kubuntu/KDE users type in:&lt;br /&gt;
&amp;lt;pre&amp;gt;kdesu kate /etc/default/linux-restricted-modules-common&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Add &amp;quot;fglrx&amp;quot; to the line &amp;quot;DISABLED_MODULES&amp;quot;&lt;br /&gt;
{{Box File|/etc/default/linux-restricted-modules-common|&lt;br /&gt;
&amp;lt;pre&amp;gt;DISABLED_MODULES=&amp;quot;fglrx&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Install .deb packages:&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo dpkg -i xorg-driver-fglrx_8.42.3-1*.deb \&lt;br /&gt;
fglrx-kernel-source_8.42.3-1*.deb \&lt;br /&gt;
fglrx-amdcccle_8.42.3-1*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Note: If you have a 64 bit install, the above dpkg command will likely 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 recieve 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:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get install -f&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Remove any old fglrx debs from /usr/src/:&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo rm /usr/src/fglrx-kernel*.deb&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Fix broken dependencies&#039;&#039;&lt;br /&gt;
*Note: &#039;&#039;You only need to do this if you have installed previous versions of these drivers using this method before.&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo apt-get -f install&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Compile the kernel module:&#039;&#039;&lt;br /&gt;
*Note: &#039;&#039;Since Catalyst 7.12, this step is not needed anymore, because the fglrx-kernel-source package compiles and installs the module.&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo module-assistant prepare&lt;br /&gt;
sudo module-assistant update&lt;br /&gt;
sudo module-assistant build fglrx&lt;br /&gt;
sudo module-assistant install fglrx&lt;br /&gt;
sudo depmod -a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It&#039;s necessary, because sometimes this file is written by other packages, and so there&#039;s no 3D acceleration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create the following folder&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo mkdir /lib/modules/$(uname -r)/volatile&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Create a symbolic link&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;IMPORTANT&#039;&#039;&#039;: You have to recompile the kernel module after each kernel update!&lt;br /&gt;
&lt;br /&gt;
===Configure the Driver===&lt;br /&gt;
*Note Method 2 Users: Before you carry out this step you must reboot your machine. Or else the fglrx driver will not be in use on xorg.conf and using the aticonfig options will cause a memory dump and not intialise the Driver properly.&lt;br /&gt;
*Note: An &#039;&#039;&#039;alternative&#039;&#039;&#039; to the &#039;&#039;&#039;aticonfig --initial&#039;&#039;&#039; command is to edit &#039;&#039;/etc/X11/xorg.conf&#039;&#039; and replace the string &amp;quot;ati&amp;quot; with &amp;quot;fglrx&amp;quot; in the &amp;quot;Device&amp;quot; section. This way you won&#039;t lose your old &amp;quot;Screen&amp;quot; and &amp;quot;Monitor&amp;quot; settings. Afterwards you can use aticonfig for setting overlay etc. Another alternative is &#039;&#039;&#039;aticonfig --initial --force&#039;&#039;&#039; if you encounter issues with the first command.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --initial&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Then:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo aticonfig --overlay-type=Xv&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*Note: Is there an alternative to the previous step?&lt;br /&gt;
&lt;br /&gt;
===Finish the Installation===&lt;br /&gt;
Now save any open document and reboot your system:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo shutdown -r now&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*Note: An &#039;&#039;&#039;alternative&#039;&#039;&#039; to rebooting is to restart the X Server by pressing your CTRL ALT BACKSPACE keys. You must remove any old kernel modules such as &amp;quot;drm&amp;quot; &amp;quot;radeon&amp;quot; or &amp;quot;fglrx&amp;quot; using the &amp;quot;rmmod&amp;quot; command. Example: &amp;lt;code&amp;gt;sudo rmmod fglrx&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Post-Installation Checks ==&lt;br /&gt;
===Verifying===&lt;br /&gt;
Run the following command to check its output to ensure the fglrx driver is installed properly:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ fglrxinfo&lt;br /&gt;
display: :0.0  screen: 0&lt;br /&gt;
OpenGL vendor string: ATI Technologies Inc.&lt;br /&gt;
OpenGL renderer string: ATI MOBILITY RADEON 9600/9700 Series&lt;br /&gt;
OpenGL version string: 2.0.6650 (8.40.4)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
The &amp;lt;code&amp;gt;OpenGL vendor string&amp;lt;/code&amp;gt; should read &#039;&#039;&#039;ATI&#039;&#039;&#039; and not &#039;&#039;&#039;Mesa&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If you see a message like &#039;Xlib: extension &amp;quot;XFree86-DRI&amp;quot; missing on display &amp;quot;:1.0&amp;quot;&#039; then you may have to add the following to /etc/X11/xorg.conf (see [http://ubuntuforums.org/showthread.php?t=292642#post1714920]):&lt;br /&gt;
{{Box File|/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;Disable&amp;quot;&lt;br /&gt;
EndSection&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Additional configure with aticonfig tool ===&lt;br /&gt;
You can even more configure the driver with the &#039;&#039;&#039;aticonfig&#039;&#039;&#039; tool, more information can be found at [[Configuring]].&lt;br /&gt;
&lt;br /&gt;
For example: &amp;lt;br&amp;gt;&lt;br /&gt;
* use powerplay option to switch power state for battery friendly or performance mode&lt;br /&gt;
* use dual head or one big desktop mode &lt;br /&gt;
* turn second monitor on/off on the fly&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Ubuntu-specific Issues==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Revert to Xorg driver ===&lt;br /&gt;
&lt;br /&gt;
If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo dpkg-reconfigure xserver-xorg&amp;lt;/pre&amp;gt;&lt;br /&gt;
and selecting the &amp;quot;ati&amp;quot; driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup. &lt;br /&gt;
&lt;br /&gt;
You also need to remove the xorg-driver-fglrx or your manually installed drivers to get the 3D acceleration back, since it is provided by file /usr/lib/libGL.so.1.2 which belongs to libgl1-mesa package and which is moved to backup and replaced at the installation of xorg-driver-fglrx (or the manually built) package. In case the removal of the fglrx drivers fails to restore the file from libgl1-mesa, you have to reinstall the package by running:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo apt-get install --reinstall libgl1-mesa&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== If suspend is not working ===&lt;br /&gt;
&lt;br /&gt;
If suspend stops working after fglrx installation, meaning display will not initialize after attempting to resume, then changing a few options has been reported to work for some hardware. &amp;lt;!-- ([https://launchpad.net/ubuntu/source/linux-restricted-modules-2.6.20/bug/84991 Bug 84991 ]). #Broken Link--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For ATI X700 and ATI X1100 on Acer Aspire 5051:&lt;br /&gt;
{{Box File|/etc/default/acpi-support|&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
SAVE_VBE_STATE=false&lt;br /&gt;
POST_VIDEO=true&lt;br /&gt;
USE_DPMS=false&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
For ATI X1300 and the ATI X1400 on a Dell Inspiron 9400 or Lenovo Thinkpad T60, also for ATI X1600 on Asus Z96J (using install method 2):&lt;br /&gt;
{{Box File|/etc/default/acpi-support|&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
POST_VIDEO=false&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Frequently Asked Questions]]&lt;br /&gt;
*[[Performance Issues]]&lt;br /&gt;
*[[Troubleshooting]]&lt;br /&gt;
*[http://www.petitiononline.com/x200MLin/petition.html Petition for better ATI/AMD Radeon XPRESS 200M Linux Drivers]&lt;br /&gt;
* [http://ubuntuforums.org/showpost.php?p=2221323&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;/div&gt;</summary>
		<author><name>202.134.12.11</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Troubleshooting&amp;diff=2353</id>
		<title>Troubleshooting</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Troubleshooting&amp;diff=2353"/>
		<updated>2008-04-03T10:42:50Z</updated>

		<summary type="html">&lt;p&gt;202.134.248.217: /* No XVideo support on 690G integrated graphic chipset */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Kernel Related Issues==&lt;br /&gt;
&lt;br /&gt;
=== No 3D acceleration ===&lt;br /&gt;
If you see output that looks like this:&lt;br /&gt;
&lt;br /&gt;
 $ fglrxinfo &lt;br /&gt;
 display: :0.0 screen: 0 &lt;br /&gt;
 OpenGL vendor string: Mesa project: www.mesa3d.org &lt;br /&gt;
 OpenGL renderer string: Mesa GLX Indirect &lt;br /&gt;
 OpenGL version string: 1.2 (1.5 Mesa 6.4.1) &lt;br /&gt;
&lt;br /&gt;
Make sure you do not have Xinerama enabled in your xorg.conf! 3D-acceleration is not supported by fglrx in Xinerama mode.&lt;br /&gt;
&lt;br /&gt;
Then try these two commands:&lt;br /&gt;
&lt;br /&gt;
 sudo mkdir -p /usr/X11R6/lib/modules/dri &lt;br /&gt;
 sudo ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri &lt;br /&gt;
Source&amp;lt;ref&amp;gt;http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In Gentoo &amp;quot;maybe other distros, not sure&amp;quot; you must initiate the ATI opengl interface by typing:&lt;br /&gt;
&lt;br /&gt;
 eselect opengl set ati&lt;br /&gt;
&lt;br /&gt;
Or you can try deleting all files from the /lib/modules/$(uname -r)/volatile folder and relinking:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
sudo rm /lib/modules/$(uname -r)/volatile/*&amp;lt;br&amp;gt;&lt;br /&gt;
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko&lt;br /&gt;
&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If that doesn&#039;t work confirm fglrx is loaded:&lt;br /&gt;
&lt;br /&gt;
 lsmod | grep fglrx&lt;br /&gt;
&lt;br /&gt;
If it returns nothing then try this:&lt;br /&gt;
&lt;br /&gt;
 sudo depmod -ae&lt;br /&gt;
 sudo echo fglrx &amp;gt;&amp;gt; /etc/modules&lt;br /&gt;
(If this returns &amp;quot;bash: /etc/modules: Permission denied&amp;quot; then sudo su first.)&lt;br /&gt;
&lt;br /&gt;
If it doesn&#039;t still work, open up /etc/modprobe.d/lrm-video with an editor, and uncomment any line(s) that contains fglrx in it.&lt;br /&gt;
&lt;br /&gt;
In case nothing above works, open /etc/modprobe.d/blacklist-restricted with an editor and comment any line that might contain fglrx word in it.&lt;br /&gt;
&lt;br /&gt;
=== nForce 3 AGP Issues ===&lt;br /&gt;
&lt;br /&gt;
For nForce3 based motherboards: if the install seems to go well, but fglrx still fails and $ fglrxinfo tells you you&#039;re still running Mesa, there may be a problem with the nVidia AGP-PCI Bridge module&#039;s compatibility with your BIOS (or vice versa, I haven&#039;t yet investigated). (Confirmed at least for ASUS K8N-E Deluxe.) A solution is to downgrade your BIOS to a previous version (see your motherboard manual/manufacturer&#039;s website for instructions). Here is a list of compatible BIOS versions (if your model is not listed here and you find a version that fixes the problem, please add it to the list so others can benefit):&lt;br /&gt;
&lt;br /&gt;
(Update: March 22nd, 2007) It appears that the beta ASUS bios 1012 will also fix the problem. I had the ATI drivers installed but fglrxinfo was still reporting Mesa as the OpenGL provider. I flashed the BIOS to 1012, rebooted into Ubuntu. Problem solved.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The 1012 bios did not work for my K8N-E deluxe mobo and my x800. Bios 1006 works great though.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*ASUS&lt;br /&gt;
**K8N-E Deluxe: Version 1006&lt;br /&gt;
**K8N-E Deluxe: Version 1012 beta&lt;br /&gt;
**K8N Bios versions up 1003 to 1011, my Solution -&amp;gt; K8V-X (Asus with Via-Chipset) It is working really good now. (Always Problems: nForce3 Chipset)&lt;br /&gt;
&lt;br /&gt;
*ASROCK&lt;br /&gt;
**K8Upgrade-NF3&lt;br /&gt;
&lt;br /&gt;
(A little workaround for K8Upgrade-NF3 is to edit xorg.conf, in section &amp;quot;Devices&amp;quot;, adding this line: Option &amp;quot;UseInternalAGPGART&amp;quot; &amp;quot;no&amp;quot;)&lt;br /&gt;
It doesn&#039;t work with Gutsy release yet.&lt;br /&gt;
&lt;br /&gt;
*GIGABYTE&lt;br /&gt;
**GA-K8NSC-939: Bios versions: F1, F2&lt;br /&gt;
&lt;br /&gt;
=== AGP Initialization fails with amd_k7_agp module ===&lt;br /&gt;
With Kernel 2.6.16.x, there came a new feature called &amp;quot;EDAC&amp;quot; which creates a conflict causing amd_k7_agp not to work. This results in a&lt;br /&gt;
 (EE) fglrx(0): [agp] unable to acquire AGP, error &amp;quot;xf86_ENODEV&amp;quot;&lt;br /&gt;
 (EE) fglrx(0): cannot init AGP&lt;br /&gt;
Message in the error-log.&lt;br /&gt;
&lt;br /&gt;
To resolve the problem, in your kernel config change&lt;br /&gt;
 CONFIG_EDAC_AMD76X=y&lt;br /&gt;
to&lt;br /&gt;
 #CONFIG_EDAC_AMD76X is not set&lt;br /&gt;
(just comment it out)&lt;br /&gt;
recompile/reinstall/reboot your kernel. Everything should work now.&lt;br /&gt;
&lt;br /&gt;
=== Using realtime enabled kernels ===&lt;br /&gt;
&lt;br /&gt;
Apparently the official driver doesn&#039;t support realtime enabled kernels, as installation fails to build the kernel module (see /usr/share/ati/fglrx-install.log). Correct this if I&#039;m wrong.&lt;br /&gt;
&lt;br /&gt;
==X Server Related Issues==&lt;br /&gt;
&lt;br /&gt;
=== No high-resolution video modes available ===&lt;br /&gt;
* Recent versions of the fglrx driver (seen with 7.12) seem to have problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.&lt;br /&gt;
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem. &lt;br /&gt;
* No known workaround.&lt;br /&gt;
* The bug seems to be fixed with driver version 8.1 (though I cannot fully verify this since my system locks up hard after (correctly) setting the graphics mode, SuSE 10.0 not supported anymore - [[User:Akhuettel|Akhuettel]])&lt;br /&gt;
&lt;br /&gt;
=== No XVideo support on 690G integrated graphic chipset ===&lt;br /&gt;
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.&lt;br /&gt;
*Motherboard using the 690G IGP chipset don&#039;t have XVideo support. When you execute the &amp;quot;xvinfo&amp;quot; command you get &amp;quot;no adaptors present&amp;quot;. This is the case by using the 8.39.4 FGLRX driver and whenever the &amp;quot;sudo aticonfig --overlay-type=Xv&amp;quot; command or the &amp;quot;sudo aticonfig --overlay-type=opengl&amp;quot; was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.&lt;br /&gt;
* XVideo works with 8-1 release (version 8.45.4).  You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don&#039;t use aticonfig or xorg.conf to set these.  At this time, aticonfig and amdccle don&#039;t change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)&lt;br /&gt;
* With 8-3 release (8.47.1), to get XVideo working I added &#039;&#039;Option &amp;quot;TexturedVideo&amp;quot; &amp;quot;true&amp;quot;&#039;&#039; to the xorg.conf file. It wasn&#039;t necessary to edit the /etc/ati/amdpcsdb file as described in the paragraph above; the open GL overlay can be active and it will still work.&lt;br /&gt;
&lt;br /&gt;
=== System lockup on logout or switch to virtual consoles ===&lt;br /&gt;
&lt;br /&gt;
If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of [http://ati.cchtml.com/show_bug.cgi?id=330 this bug]. It is likely that the problem only occurs for users with an &#039;&#039;&#039;Xorg version of at least 7.0&#039;&#039;&#039;. Probably it only affects users of &#039;&#039;&#039;DVI&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.&lt;br /&gt;
&lt;br /&gt;
This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].&lt;br /&gt;
---------&lt;br /&gt;
Unfortunately &amp;quot;D-sub&amp;quot; users (like me) have the same problem.&lt;br /&gt;
&lt;br /&gt;
=== BigDesktop (Dual screen) doesn&#039;t work after GDM login screen ===&lt;br /&gt;
&lt;br /&gt;
This can occur on Ubuntu Feisty Fawn &amp;amp; Gutsy.&lt;br /&gt;
&lt;br /&gt;
System &amp;gt; Prefrences &amp;gt; Screen Resolution&lt;br /&gt;
&lt;br /&gt;
Select the resolution that is a combination of both screen resolutions wide and your height.&lt;br /&gt;
&lt;br /&gt;
If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, &amp;lt;code&amp;gt;sudo vim /etc/X11/xorg.conf&amp;lt;/code&amp;gt;, and comment out the line which looks like the following:&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
&amp;lt;pre&amp;gt;  Option  &amp;quot;DesktopSetup&amp;quot;  &amp;quot;something&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Computer Freezes while using fglrx (UMA and SIDEPORT)  ===&lt;br /&gt;
If after choosing fglrx as your driver in either xorg.conf or xfree86.conf files, the computer freezes and becomes unresponsive while trying to start X this may be the solution.&lt;br /&gt;
&lt;br /&gt;
Some ATI cards have the ability to run in three modes: UMA, SIDEPORT, or a combination of both. UMA mode is that one in which the video card does not use its dedicated memory, but rather uses and shares the system memory. On the other hand, SIDEPORT mode is the one in which the card uses its own dedicated memory. And finally, the third mode is a combination of the previous modes in which the card uses both the system memory and its dedicated memory.&lt;br /&gt;
&lt;br /&gt;
If your computer hangs, this settings may be where the solution lies. If your computer hangs, try using either UMA by itself or a combination of both. However, if you choose the combination, make sure that the UMA one is at least 128MB. In my case, I have SIDEPORT 128MB and 128MB UMA. If I choose any less for UMA, it does not work. This is definetly not an attractive solution since it compromises your systems performance. Hopefully, this will be solved very soon.&lt;br /&gt;
&lt;br /&gt;
On some systems, the BIOS screen may not offer a choice of UMA or SIDEPORT.  In this case, you can try turning the amount of RAM dedicated to the video card down, from 128Mb to 64Mb for example.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Graphical Anomalies ===&lt;br /&gt;
&lt;br /&gt;
This was experienced with an ATI Radeon X1600 Pro 512mb:&lt;br /&gt;
&lt;br /&gt;
After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information.  If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.&lt;br /&gt;
&lt;br /&gt;
To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too).  The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).&lt;br /&gt;
&lt;br /&gt;
There&#039;s been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.&lt;br /&gt;
&lt;br /&gt;
=== OpenGL framebuffer Corruption ===&lt;br /&gt;
&lt;br /&gt;
This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears &amp;quot;scrambled&amp;quot; and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.&lt;br /&gt;
&lt;br /&gt;
When Anti-Aliasing is forced, the problem resides.&lt;br /&gt;
&lt;br /&gt;
A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled &#039;3D&#039; in the options tree on the left-hand side of the window. From there, select &amp;quot;Anti-Aliasing&amp;quot; and check the box which reads: &amp;quot;Override application setting&amp;quot;. Apply the settings and close the control center.&lt;br /&gt;
&lt;br /&gt;
For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT.&lt;br /&gt;
kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg&lt;br /&gt;
&lt;br /&gt;
=== Blank Screen with Xorg 1.3.0 ===&lt;br /&gt;
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:&lt;br /&gt;
{{Box File|/var/log/Xorg.log|&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]&lt;br /&gt;
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]&lt;br /&gt;
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]&lt;br /&gt;
 &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Then you&#039;re probably using the ati-drivers with Xorg-1.3.0. If that&#039;s the case the only solution (known to me) is to use a version &amp;lt; 1.3.0.&lt;br /&gt;
&lt;br /&gt;
Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try&lt;br /&gt;
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor&lt;br /&gt;
signal sometimes returnes to the internal laptop monitor.&lt;br /&gt;
By switching to a console or shutting down the X-server, the card switches back to vga...&lt;br /&gt;
&lt;br /&gt;
My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)&lt;br /&gt;
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now&lt;br /&gt;
work fine again with Xorg-1.3.0 .&lt;br /&gt;
&lt;br /&gt;
=== Radeon GPU fan is very loud / constantly works ===&lt;br /&gt;
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.&lt;br /&gt;
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively&lt;br /&gt;
even when not in 3D mode. This behaviour will cause the cards&#039; fans to function on full&lt;br /&gt;
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source&lt;br /&gt;
&amp;quot;radeon&amp;quot; driver does not exhibit this problem.&lt;br /&gt;
&lt;br /&gt;
My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it&#039;s because the temp~&lt;br /&gt;
&lt;br /&gt;
It happens too with Radeon X1800 GTO and Radeon X1900 GT.&lt;br /&gt;
&lt;br /&gt;
Possible solution (at least using a Mobility Radeon X1600): &lt;br /&gt;
&amp;lt;pre&amp;gt;aticonfig --set-powerstate=1&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To find out which powerstates your Radeon supports try:&lt;br /&gt;
&amp;lt;pre&amp;gt;aticonfig --lsp&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== System freezes after logout with GDM or KDM&amp;lt;ref&amp;gt;http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm hardlocks after running X session&amp;lt;/ref&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
If you use GDM, which is the default Login Manager on Ubuntu, modify&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo gedit /etc/gdm/gdm.conf&amp;lt;/pre&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{{Box File|/etc/gdm/gdm.conf|&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;AlwaysRestartServer=true&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo kate /etc/kde3/kdm/kdmrc&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Box File|/etc/kde3/kdm/kdmrc|&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;TerminateServer=true&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== System freezes at startup of Fedora 7 after installing the driver ===&lt;br /&gt;
&lt;br /&gt;
Turn off the Redhat Graphical boot from grub config:&lt;br /&gt;
&lt;br /&gt;
Edit the grub config file located at /boot/grub/grub.conf and remove the &#039;rhgb&#039; from the kernel line in order to disable the Redhat Graphical boot.&lt;br /&gt;
&lt;br /&gt;
=== System lockup on logout with catalyst 8.01 &amp;lt;ref&amp;gt;http://www.phoronix.com/forums/showthread.php?t=7448&amp;amp;page=5 System lockup on logout with catalyst 8.01&amp;lt;/ref&amp;gt;===&lt;br /&gt;
To solve this issue you need to disable atieventsd. On ubuntu you can run:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
sudo /usr/sbin/update-rc.d -f atieventsd remove&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Intermittent Freezes/Lockups due to AGPv3 running at 8x ===&lt;br /&gt;
Try forcing X to set AGP Speed to 4x&lt;br /&gt;
{{Box File|/etc/X11/xorg.conf|&lt;br /&gt;
&amp;lt;pre&amp;gt;  Option &amp;quot;AGPv3Mask&amp;quot; &amp;quot;0x00000002&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Installation Documentation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:NeedsUpdating]]&lt;br /&gt;
{{VCT}}&lt;/div&gt;</summary>
		<author><name>202.134.248.217</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=TurboLinux&amp;diff=1500</id>
		<title>TurboLinux</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=TurboLinux&amp;diff=1500"/>
		<updated>2007-12-30T00:37:01Z</updated>

		<summary type="html">&lt;p&gt;202.134.73.50: bocoloelt&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;codome&lt;br /&gt;
{{VCT}}&lt;br /&gt;
[[Category:Distributions]]&lt;br /&gt;
[[Category:NeedsUpdating]]&lt;/div&gt;</summary>
		<author><name>202.134.73.50</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Slashdot&amp;diff=1243</id>
		<title>Slashdot</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Slashdot&amp;diff=1243"/>
		<updated>2007-12-29T12:22:33Z</updated>

		<summary type="html">&lt;p&gt;202.134.73.50: elacroacel&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;roerrelcocov&lt;br /&gt;
&#039;&#039;&#039;2005-07-30&#039;&#039;&#039; : [http://linux.slashdot.org/article.pl?sid=05/07/30/197259  A Look at the State of ATI Linux Drivers]&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:NewsSite]]&lt;/div&gt;</summary>
		<author><name>202.134.73.50</name></author>
	</entry>
	<entry>
		<id>http://wiki.cchtml.com/index.php?title=Installation&amp;diff=2033</id>
		<title>Installation</title>
		<link rel="alternate" type="text/html" href="http://wiki.cchtml.com/index.php?title=Installation&amp;diff=2033"/>
		<updated>2007-12-23T00:41:39Z</updated>

		<summary type="html">&lt;p&gt;202.134.73.50: cadomorc4ttr&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
1&lt;br /&gt;
This covers the distribution-independent way of installing the driver with the Installer.  Ideally, you should install using the [[:Category:Distributions|distribution-specific]] processes for a less painful experience.&lt;br /&gt;
&lt;br /&gt;
Or look into the &#039;&#039;&#039;[[:Category:Installation Documentation|Installation Documentation]]&#039;&#039;&#039; Category.&lt;br /&gt;
&lt;br /&gt;
See the article: [http://m.domaindlx.com/LinuxHelp/ati/ati.htm 3D Acceleration for your ATI card] (works for SUSE, Mandriva and Debian).&lt;/div&gt;</summary>
		<author><name>202.134.73.50</name></author>
	</entry>
</feed>