cchtml.com - User contributions [en]

Ubuntu Dapper Installation Guide

2012-08-06T21:08:39Z

213.144.132.98: /* Method 1: Installing Dapper's Included Driver (8.25.18) */

'''NOTE:''' This guide is '''only''' for Ubuntu 6.06 (Dapper)! Guides for other versions of Ubuntu can be found at the [[Ubuntu]] page.

In Ubuntu Dapper you can choose between two methods of installing the proprietary ATI driver. If you are new to linux you should use the first method as it is a lot easier than the second one and will work well in most cases. The second method describes how to install the very latest driver version, but requires some additional work and knowledge.
Hello! kdkcegf interesting kdkcegf site! I'm really like it! Very, very kdkcegf good!

== Post-Installation Checks ==
===Verifying===
Run the following command to check its output to ensure the fglrx driver is installed properly:
<pre>
$fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 2.0.6286 (8.33.6)
</pre>

<pre>
$ glxinfo | grep render
direct rendering: Yes
</pre>

If your direct rendering is disabled then you may have to ensure '''fglrx_dri.so''' is where it should be. Try to symblink the '''dri''' folder if you get no direct rendering:

<pre>
sudo mkdir /usr/X11R6/lib/modules
sudo ln -s /usr/lib/dri /usr/X11R6/lib/modules/
</pre>

=== Troubleshooting for Method 2===

==== Problems with module-assistant ====

If module-assistant is unable to build the module you may have to provide a Makefile.cpu file:
<pre>
cd /usr/src
sudo touch kernel-headers-(version)/arch/i386/Makefile.cpu
cd /usr/src/linux
sudo make scripts/
</pre>

With recent fglrx, the <tt>make.sh</tt> in <tt>/usr/src/fglrx.tar.bz2</tt> (installed by the fglrx-kernel-source package) is not executable. You may need the following in order to make module-assistant happy:
<pre>
mkdir /tmp/scratch
pushd /tmp/scratch
tar xjf /usr/src/fglrx.tar.bz2
chmod +x modules/fglrx/make.sh
sudo tar cjf /usr/src/fglrx.tar.bz2 modules
popd
</pre>

If installing over a custom-built kernel (for example 2.6.18), the procedure above may need to be modified slightly, especially if you didn't use <tt>make-kpkg</tt> to install your kernel:
<pre>
# sudo module-assistant prepare # no ubuntu package for 2.6.18
sudo module-assistant update
sudo module-assistant build -k path/to/my/kernel/sources fglrx
sudo module-assistant install -k path/to/my/kernel/sources fglrx
sudo depmod -a
</pre>

==== xorg.conf ====

The '''aticonfig --initial''' command will not update the xorg.conf file if it already has a "fglrx" Device section.
However, you may force aticonfig to generate default Monitor, Device, and Screen sections with the following command:

<pre>
sudo aticonfig --force --initial
</pre>

==== Missing fglrx.ko ====

If '''fglrx.ko''' is not being loaded properly, then <tt>/var/log/Xorg.0.log</tt> will say things like :
<pre>
[drm] failed to load kernel module "fglrx"
(WW) fglrx(0): Failed to load DRM connection
(EE) GART is not initialized, disabling DRI
</pre>

<tt>modprobe</tt> shows the problem is
<pre>
sudo modprobe fglrx
FATAL: Could not open '/lib/modules/2.6.15-26-386/volatile/fglrx.ko': No such file or directory
</pre>

You could copy <tt>/lib/modules/2.6.15-26-386/misc/fglrx.ko</tt> into the volatile directory, then restart GDM, but you lose it again at the next re-boot.

The solution is to run <tt>depmod</tt> again with the <tt>-e</tt> option.
<pre>
sudo depmod -ae
</pre>
Then re-boot.

==== Upgrade from Breezy ====
If method 2 doesn't work first time round, and you have upgraded from a Breezy installation, try this:

Remove previous versions of the fglrx driver:
<pre>
sudo dpkg -r fglrx-control
sudo dpkg -r fglrx-kernel-source
sudo dpkg -r xorg-driver-fglrx
</pre>

dpkg will list dependencies for xorg-driver-fglrx which will need up be removed, for example:

<pre>
sudo dpkg -r fglrx-kernel
sudo dpkg -r fglrx-kernel-2.6.12-10-686-smp
sudo dpkg -r xorg-driver-fglrx
</pre>

Proceed with method 2

 

== Troubleshooting for both Methods ==

=== General ===

The output of '''dmesg | grep fglrx''' and /var/log/Xorg.0.log are most useful when looking for errors.

Also, '''LIBGL_DEBUG=verbose glxinfo''' can display missing files you can 'fix' by linking directories.

=== 2D speed ===

If you suffer from slow 2D speed it might help to set
Option "XaaNoOffscreenPixmaps"
in the fglrx section of ''/etc/X11/xorg.conf''

=== Black Screen when supposed to see login screen ===

Try adding
Option "BusType" "PCI"
in the fglrx section of ''/etc/X11/xorg.conf''

=== Is the rebooting really necessary? ===

No.

However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.

Note: You may also having to rebuild your module dependency by using "depmod -a".

=== HP Notebook dv5029us / dv5040us / zv6000 / dv8000 / nw8440 ===

If you have an HP Notebook Computer (or Compaq) such as the HP dv5029us, dv5040us or zv6000 series, it is needed to modify the BIOS configuration. It seems for some reason using sideport memory (the card's onboard memory only) leads to an apparent system crash although the logs show successful initialization of DRI. It is needed to run the BIOS setup screen, go to memory options, and select UMA+Sideport memory and assign a value to it (I assigned an extra 128M from the system RAM). Boot the computer and the fglrx driver will work. FGLRX version is 8.24.8 on an i386 Ubuntu Dapper install. '''NEW''': ATI has fixed this problem with their latest drivers - there is no longer a need to use the old 8.24.8 drivers, nor is there need to use the extra 128M of system RAM. Just install the latest drivers -- it worked for me when nothing else did.

* Ubuntu FGLRX drivers 8.25.18, do not work properly on the dv5029us (Radeon Xpress 200M) as of this writing (5/30/2006). It is needed to revert to 8.24.8 for this specific computer in order to get proper 3D acceleration, and 2D with no tearing off.

** ATI Driver 8.26.18, does not work with the Radeon Express 200M. Some HP/Compaq laptops only have working 3D support with ONLY UMA video memory( Sideport+UMA won't work ). This is due to a 1 year old flaw in the ATI driver. If you want to use your onboard/Sideport memory, you can only get 2D support by adding [ Option "no_dri" "yes"] to the fglrx driver section of /etc/X11/xorg.conf

* jul-22-2006, marciowb wrote: I have a HP Pavilion zv6000 - a notebook computer with AMD64 - and it have a ATI Radeon Xpress 200M with 128MB of dedicated memory (Sideport) and it accepts to use shared memory (UMA), also. But if I try to use Sideport or Sideport+UMA the 3D acceleration fails and/or my computer hangs. It works fine if I configure its BIOS to use only UMA, including with a good 3D acceleration performance. Configured to use only UMA it works with the ATI Driver 8.26.18 and 8.25.18, but I was unable to do it works the ATI Driver 8.24.8. I tried several times to use 8.24.8 but it doesn't seem to work with 3D acceleration, only 2D. I see the Xorg.log file the fglrx driver fails to load the DRI driver. I used the Kubuntu with the Linux kernel 2.6.15-26-amd64-generic.

* aug-7-2006, mde wrote: I have an HP dv8120ca / dv8000 laptop with a Radeon Xpress 200M. After installing the 8.27.10 driver, no matter what I set the bios to (128 UMA+Sideport or just Sideport, UMA Only is not an option in my bios), I get the black screen/99% cpu usage problem. '''NEW''': ATI has fixed this problem with their latest drivers! I just installed their latest driver, and everything works perfectly. No need to do anything funny with the BIOS -- you can use sideport only or whatever. Good news :) Thank you AMD/ATI for responding to our requests to fix this problem!

* sep-12-2006, tekNico wrote: on an HP dv5008EA with the 200M adapter, DRI works with the 8.24.8 driver, and setting the BIOS to Sideport+UMA to 128MB video memory. The 8.28.8 breaks some on-screen widgets.

* Sep-27-2006: HP Pavilion dv8000 (Radeon Xpress 200M). Turned off Sideport and installed the driver from the repositories, ver 8.25.18. The computer started up fine, but was extremely unstable and crashed in about 5 minutes of work. Same thing with driver ver 8.29.6. At the end I installed ver 8.24.8 and that seemed to work well.

* Oct-17-2006: webbertiger wrote: on my HP Pavilion dv8309us with Radeon Xpress 200M and AMD64 cpu, the driver (ati-driver-installer-8.29.6.run) downloaded from [ATI website[https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/64bit/ati-driver-installer-8.29.6.run]] works fine. I also manually added "1440x900" in xorg.conf to get the wide screen. [Can you confirm that dri (direct rendering also works fine?) glxgears should run with a high (over 1000fps) frame rate?]

* Oct-30-2006: on my hp nw8440 i had to disable the composite extension to get full 3D accelleration ( chipset: ati V5200, driver ati 8.29.6 )
Section "Extensions"
Option "Composite" "false"
EndSection

=== HP zt3000 / Compaq nx7000 ===
Beginning with ATI driver version 8.19, the drivers fail to properly detect modelines that are compatible with the LCD screen of the HP zt3000 (and equivalent Compaq nx7000 model), and they must be inserted into xorg.conf manually. For the 1680x1050 LCD screen, inserting the following modelines into the "Monitor" section works:
Modeline "640x350" 119.12 640 1728 1760 1840 350 1052 1058 1080
Modeline "640x400" 119.12 640 1728 1760 1840 400 1052 1058 1080
Modeline "720x400" 119.12 720 1728 1760 1840 400 1052 1058 1080
Modeline "640x480" 119.12 640 1728 1760 1840 480 1052 1058 1080
Modeline "800x600" 119.12 800 1728 1760 1840 600 1052 1058 1080
Modeline "1024x768" 119.12 1024 1728 1760 1840 768 1052 1058 1080
Modeline "1152x864" 119.12 1152 1728 1760 1840 864 1052 1058 1080
Modeline "1280x960" 119.12 1280 1728 1760 1840 960 1052 1058 1080
Modeline "1280x1024" 119.12 1280 1728 1760 1840 1024 1052 1058 1080
Modeline "832x624" 119.12 832 1728 1760 1840 624 1052 1058 1080
Modeline "1280x768" 119.12 1280 1728 1760 1840 768 1052 1058 1080
Modeline "1280x800" 119.12 1280 1728 1760 1840 800 1052 1058 1080
Modeline "1152x768" 119.12 1152 1728 1760 1840 768 1052 1058 1080
Modeline "1400x1050" 119.12 1400 1728 1760 1840 1050 1052 1058 1080
Modeline "1440x900" 119.12 1440 1728 1760 1840 900 1052 1058 1080
Modeline "1600x1024" 119.12 1600 1728 1760 1840 1024 1052 1058 1080
Modeline "1680x1050" 119.12 1680 1728 1760 1840 1050 1052 1058 1080

If you have the "1920x1200" version of the HP zt3000 the Modeline is:
Modeline "1920x1200" 150.75 1920 2016 2048 2185 1200 1202 1208 1235

If you have the "1280x800" version of the HP zt3000 the Modeline should be:
ModeLine "1280x800" 69.8 1280 1336 1368 1440 800 802 808 823 -hsync -vsync

** If the above ModeLine still makes the screen flicker (as it did in my zt3000) use the following ModeLine
ModeLine "1280x800" 70.875 1280 1336 1368 1440 800 802 808 823 -hsync +vsync
** Try this as well if the other two don't work. Determined using powerstrip in windows.
ModeLine "1280x800" 68.625 1280 1336 1368 1440 800 802 808 823 -hsync -vsync

If you have the compaq nx7010 with 1280x800 screen then the following modeline should work:
Modeline "1280x800" 70.875 1280 1320 1352 1456 800 801 804 820 +hsync +vsync
This was determined using powerstrip in windows.

** If the above ModeLine still makes the screen flicker (as it did on my nx7010) use the following
Modeline "1280x800" 68.625 1280 1304 1336 1408 800 804 808 816 +hsync +vsync
This was determined using powerstrip in windows.

When using a Compaq NX7010 (Radeon R250Lf Mobility M9) with 1650x1050 screen, powerstrip gives the following working params (CApiTAlisation important), just use one single ModeLine:
ModeLine "1650x1050" 121.500 1680 1712 1800 1872 1050 1051 1054 1065 +Hsync +Vsync
On the Compaq NX7010, be sure to copy the 8.24.8 libGL.so.1.2 as in Troubleshooting for Method 1 above.

''Note: This line will also work on the Compaq X1000 series''

=== Revert to Xorg driver ===

If (for any reason) the fglrx install fails, you can revert to the Xorg driver by executing
<pre>sudo dpkg-reconfigure xserver-xorg</pre>
and selecting the "ati" driver, or simply restoring the previous /etc/X11/xorg.conf file, if you made a backup.

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:

<pre>sudo apt-get install --reinstall libgl1-mesa</pre>

[[Category:Installation Documentation]]

Troubleshooting

2012-05-31T22:49:55Z

213.144.132.98: /* Installer Issues */

Hello! kgdcake interesting kgdcake site! I'm really like it! Very, very kgdcake good!

==X Server Related Issues==

=== No high-resolution video modes available ===
* Versions of the fglrx driver following 7.12 had 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.
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem; it is '''fixed''' since driver version 8.2
* Looks like it reappeared again some version above ati-driver-installer-8-12-x86.x86_64.run . Version ati-driver-installer-9.2-x86.x86_64.run, and ati-driver-installer-9-4-x86.x86_64.run has this bug. At least on integrated HD3200 card.

=== No XVideo support on 690G integrated graphic chipset ===
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
*Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.
* 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't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)
* With 8-3 release (8.47.1), to get XVideo working I added ''Option "TexturedVideo" "true"'' to the xorg.conf file. It wasn'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.

=== System lockup on logout or switch to virtual consoles ===

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 '''Xorg version of at least 7.0'''. Probably it only affects users of '''DVI'''.

There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.

This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].
---------
Unfortunately "D-sub" users (like me) have the same problem.

=== BigDesktop (Dual screen) doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn & Gutsy.

System > Prefrences > Screen Resolution

Select the resolution that is a combination of both screen resolutions wide and your height.

If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, <code>sudo vim /etc/X11/xorg.conf</code>, and comment out the line which looks like the following:
{{Box File|/etc/X11/xorg.conf|
<pre> Option "DesktopSetup" "something"</pre>
}}

=== Computer Freezes while using fglrx (UMA and SIDEPORT) ===
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.

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.

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.

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.

On some ACER laptops (at least the TimelineX), this means that you need to set display adapter mode to DISCRETE in BIOS.

=== Graphical Anomalies ===

This was experienced with an ATI Radeon X1600 Pro 512mb:

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.

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).

There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.

=== OpenGL framebuffer Corruption ===

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 "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.

When Anti-Aliasing is forced, the problem resides.

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 '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.

For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]

This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT.
kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg

=== Blank Screen with Xorg 1.3.0 ===
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
{{Box File|/var/log/Xorg.log|
<nowiki>
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
</nowiki>
}}

Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.

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
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor
signal sometimes returnes to the internal laptop monitor.
By switching to a console or shutting down the X-server, the card switches back to vga...

My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now
work fine again with Xorg-1.3.0 .

=== Radeon GPU fan is very loud / constantly works ===
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively
even when not in 3D mode. This behaviour will cause the cards' fans to function on full
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source
"radeon" driver does not exhibit this problem.

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's because the temp~

It happens too with Radeon X1800 GTO and Radeon X1900 GT.

Possible solution (at least using a Mobility Radeon X1600):
<pre>aticonfig --set-powerstate=1</pre>

To find out which powerstates your Radeon supports try:
<pre>aticonfig --lsp</pre>

=== System freezes after logout with GDM, KDM or XDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm/xdm hardlocks after running X session</ref> ===

If you use GDM, which is the default Login Manager on Ubuntu, modify
<pre>sudo gedit /etc/gdm/gdm.conf</pre>

{{Box File|/etc/gdm/gdm.conf|
<nowiki>AlwaysRestartServer=true</nowiki>
}}

If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following

<pre>sudo kate /etc/kde3/kdm/kdmrc</pre>

{{Box File|/etc/kde3/kdm/kdmrc|
<nowiki>TerminateServer=true</nowiki>
}}

if you use xdm, add the following to
<pre>sudo gedit /etc/X11/xdm/xdm-config</pre>

{{Box File|/etc/X11/xdm/xdm-config|
<nowiki>DisplayManager*terminateServer: true</nowiki>
}}

=== System freezes at startup of Fedora 7 or RHEL 5.3 after installing the driver ===

Turn off the Redhat Graphical boot from grub config:

Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.

This also works for Red Hat Enterprise Linux 5.3.

=== System lockup on logout with catalyst 8.01 <ref>http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01</ref>===
To solve this issue you need to disable atieventsd. On ubuntu you can run:
<pre>
sudo /usr/sbin/update-rc.d -f atieventsd remove
</pre>

=== Intermittent Freezes/Lockups due to AGPv3 running at 8x ===
Try forcing X to set AGP Speed to 4x
{{Box File|/etc/X11/xorg.conf|
<pre> Option "AGPv3Mask" "0x00000002"</pre>
}}
((Would be nice to put down WHERE to change this, not just to change this. The same applies to just about every hint shown above.))

+ You add it to the "Device" section for your graphics card in /etc/X11/xorg.conf.

Great hammer of Thor, that is powerfully helpufl!

=== _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 ===

UPDATE: The problem I have reported here is no more reproducible with the fglrx revision 11.03 (ati-driver-installer-11-3-x86.x86_64.run) within two months of testing. Many thanks to the guys that fixed this !

Strange name for a bug but this is what your kernel might say if your screen freeze completely while using two sessions and switching between them. The bug is more likely to occur while doing the session switch, but can also occur in a later moment. I have observed it while starting a new application, or while doing a simple page scrolling. Anyway, in case of this bug the graphic is completely unusable as well as the console switching, but the OS and non graphic application continue to work. A reboot it the only way I know to bring back the screen to normal operations. Then your /var/log/kernel.log might contain something like this:
<pre>

Dec 16 07:22:13 cube kernel: [1178220.704151] BUG: unable to handle kernel NULL pointer dereference at 00000000000001c0
Dec 16 07:22:13 cube kernel: [1178220.704168] IP: [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704319] PGD 171a1b067 PUD 1b5376067 PMD 0
Dec 16 07:22:13 cube kernel: [1178220.704330] Oops: 0000 [#1] SMP
Dec 16 07:22:13 cube kernel: [1178220.704337] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Dec 16 07:22:13 cube kernel: [1178220.704346] CPU 1
Dec 16 07:22:13 cube kernel: [1178220.704351] Modules linked in: cramfs ext2 iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables fglrx(P) ftdi_sio usbserial ext3 jbd mbcache btrfs nls_utf8 zlib_deflate nls_cp437 crc32c vfat
fat libcrc32c radeon ttm drm_kms_helper drm i2c_algo_bit ppdev lp sco bridge stp bnep rfcomm l2cap crc16 powernow_k8 cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace binfmt_misc fuse loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_usb_audio snd
_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_usb_lib snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device sd_mod btusb crc_t10dif usblp asus_atk0110 bluetooth snd parport_pc i2c_piix4 parport psmouse rfkill button k8tem
p i2c_core shpchp serio_raw processor pcspkr evdev soundcore pci_hotplug edac_core snd_page_alloc edac_mce_amd usbhid hid nfs lockd fscache nfs_acl auth_rpcgss sunrpc usb_storage ata_generic ahci firewire_ohci fi
Dec 16 07:22:13 cube kernel: rewire_core crc_itu_t sky2 thermal thermal_sys pata_atiixp libata ohci_hcd ehci_hcd scsi_mod usbcore nls_base [last unloaded: fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] Pid: 7344, comm: Xorg Tainted: P W 2.6.32-5-amd64 #1 System Product Name
Dec 16 07:22:13 cube kernel: [1178220.704516] RIP: 0010:[<ffffffffa030ef0f>] [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] RSP: 0018:ffff88003e91bc38 EFLAGS: 00010292
Dec 16 07:22:13 cube kernel: [1178220.704516] RAX: 0000000000000000 RBX: ffffc9001236f620 RCX: 00000000000006b0
Dec 16 07:22:13 cube kernel: [1178220.704516] RDX: 0000000000000000 RSI: ffffc90012398e00 RDI: 0000000000000140
Dec 16 07:22:13 cube kernel: [1178220.704516] RBP: ffffc90012398e00 R08: ffff88020b560008 R09: ffffc9001237b620
Dec 16 07:22:13 cube kernel: [1178220.704516] R10: 00000000000006bc R11: 0000000000000001 R12: ffff88003e91bc58
Dec 16 07:22:13 cube kernel: [1178220.704516] R13: 00000000000001c0 R14: ffffc90012398e00 R15: 0000000000000140
Dec 16 07:22:13 cube kernel: [1178220.704516] FS: 00007f52b107d700(0000) GS:ffff880008480000(0000) knlGS:00000000f75858d0
Dec 16 07:22:13 cube kernel: [1178220.704516] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0 CR3: 00000001712a7000 CR4: 00000000000006e0
Dec 16 07:22:13 cube kernel: [1178220.704516] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 16 07:22:13 cube kernel: [1178220.704516] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 16 07:22:13 cube kernel: [1178220.704516] Process Xorg (pid: 7344, threadinfo ffff88003e91a000, task ffff88020bf5a350)
Dec 16 07:22:13 cube kernel: [1178220.704516] Stack:
Dec 16 07:22:13 cube kernel: [1178220.704516] 000000001238c660 ffffffffa0389489 0000000000000100 0000000000000148
Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 0000000000000000 0000000000000000 000002af00000068 ffffffffa038c6e7
Dec 16 07:22:13 cube kernel: [1178220.704516] <0> 00000000000001c0 000000000019330c 00007f52ab7a2000 ffffc9001236f620
Dec 16 07:22:13 cube kernel: [1178220.704516] Call Trace:
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa0311680>] ? _ZN3MSF9free_surfEP9CMMDriverP10CMMSurface+0x50/0xe0 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa030d391>] ? CMMFreeSurface+0x131/0x1b0 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa031d24c>] ? _Z8uCWDDEQCmjjPvjS_+0x68c/0xf00 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d2114>] ? firegl_cmmqs_CWDDE_32+0x334/0x440 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0ba0>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02d0b30>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffffa02b0b5a>] ? firegl_ioctl+0x1ea/0x250 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa4c7>] ? vfs_ioctl+0x56/0x6c
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810fa9e0>] ? do_vfs_ioctl+0x48d/0x4cb
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff812fd946>] ? do_page_fault+0x2e0/0x2fc
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff810faa6f>] ? sys_ioctl+0x51/0x70
Dec 16 07:22:13 cube kernel: [1178220.704516] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
Dec 16 07:22:13 cube kernel: [1178220.704516] Code: 4c 8d 64 24 20 c7 44 24 04 00 00 00 00 4c 8d af 80 00 00 00 48 c7 44 24 20 00 00 00 00 48 c7 44 24 28 00 00 00 00 4c 89 6c 24 40 <49> 8b 5d 00 31 c0 48 85 db 48 89 5c 24 30 74 04 48 8b 43 30 49
Dec 16 07:22:13 cube kernel: [1178220.704516] RIP [<ffffffffa030ef0f>] _ZN17SegmentMapManager13deleteMappingEP9CMMClient+0x3f/0x170 [fglrx]
Dec 16 07:22:13 cube kernel: [1178220.704516] RSP <ffff88003e91bc38>
Dec 16 07:22:13 cube kernel: [1178220.704516] CR2: 00000000000001c0
Dec 16 07:22:13 cube kernel: [1178220.705883] ---[ end trace c9192c1a2722dc89 ]---
</pre>
As fglrx source is closed, it will b difficult to catch this bug without AMD internal resource. If someone from AMD read this: please catch this bug. It is there from a least the last couple of monthly driver and really make my machine unable to do the work it was intended to do. I first see this bug using a Debian Lenny AMD64 with a old kernel. I recently upgraded to Debian Squeeze AMD64 with his last kernel, but the bug is exactly the same.

=== [SOLVED] System freeze / Catalyst 11-9 / "unable to handle kernel NULL pointer dereference at ..." ===

Similar to previous section, mouse and keyboard unresponsive afer a ramdomly amount of time.

-----------------------------------------------------------------------------------------------
Computer
-----------------------------------------------------------------------------------------------
<pre>
Linux Debian Squeeze + sid fglrx packages
Desktop
Motherboaord ASUS P5KPL - 4GB RAM
Intel E8500 3.16GHz
ACPI DISABLED
</pre>
-----------------------------------------------------------------------------------------------
xorg server
-----------------------------------------------------------------------------------------------
<pre>
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.37-trunk-amd64 x86_64 Debian
Current Operating System: Linux Joelle 2.6.32-[01] #1 SMP Sat Oct 8 21:03:45 CEST 2011 x86_64
xorg-server 2:1.7.7-13
Current version of pixman: 0.16.4Section "Device"
</pre>
-----------------------------------------------------------------------------------------------
xorg.conf
-----------------------------------------------------------------------------------------------
<pre>
Section "Device"
Identifier "RADEON HD2600 - fglrx"
Driver "fglrx"
BusID "PCI:2:0:0"
#Option "SWCursor" "true"
Option "TexturedVideo" "on"
Option "TexturedVideoSync" "true"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
# ATI
#Option "AccelMethod" "EXA"
#Option "AGPMode" "4"
#Option "EnablePageFlip" "true"
#Option "DDCMode"
# NOTUSED Option "RenderAccel" "true"
#Option "SubPixelOrder" "NONE"
#Option "ColorTiling" "false"
#Option "backingstore" "true"
#----
# NOTUSED Option "XAANoOffscreenPixmaps" "true"
# NOTUSED Option "AddARGBGLXVisuals" "true"
# NOTUSEDOption "AllowGLXWithComposite" "true"
EndSection
</pre>
------------------------------------------------------------------------------------------------
lspci
------------------------------------------------------------------------------------------------
<pre>
Vendor: ATI Technologies Inc
Device: RV630 [Radeon HD 2600 Series]
SVendor: PC Partner Limited
SDevice: Device e410
</pre>
------------------------------------------------------------------------------------------------
/proc/ati/0/...
------------------------------------------------------------------------------------------------
<pre>
BIOS_CREATION_DATE="09/05/07 21:52"
BIOS_MSG="11X-1E410ASA-001 RV630 GDDR2 128BIT 256MB 600E/500M"
BIOS_KIT_VERSION="BK-ATI VER010.059.000.003.000000"
BIOS_PN="113-B1E41QIM-X01"
</pre>
------------------------------------------------------------------------------------------------
amdcccle info
------------------------------------------------------------------------------------------------
BIOS
Date 09/05/07 21:52
Version 010.059.000.003.000000
Part Number 113-B1E41QIM-X01
Memory
Type DDR2
Clock 500 MHz
Size 256 MB
Bandwidth 16.0 GBytes/s
BUS
Graphics Capability PCI Express
Maximum Setting x16
Core Clock 600 MHz
Software
Catalyst version 10.9
Driver Packaging Version 8.771-100825a-104565C-ATI
2D Driver Version 8.89.4
Catalyst Control Center Version 2.13
RandR Version 1.3
OpenGL
OpenGL Provider Advanced Micro Devices, Inc.
OpenGL Renderer ATI Radeon HD 2600 Pro
OpenGL Version 3.3.11079 Compatibilty Profile COntext
------------------------------------------------------------------------------------------------
BUG trace in syslog
------------------------------------------------------------------------------------------------
<pre>
Oct 8 23:17:33 Joelle kernel: [ 3922.443571] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Oct 8 23:17:33 Joelle kernel: [ 3922.443576] IP: [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443623] PGD 37736067 PUD 5cfd6067 PMD 0
Oct 8 23:17:33 Joelle kernel: [ 3922.443626] Oops: 0002 [#1] SMP
Oct 8 23:17:33 Joelle kernel: [ 3922.443628] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/uevent
Oct 8 23:17:33 Joelle kernel: [ 3922.443631] CPU 1
Oct 8 23:17:33 Joelle kernel: [ 3922.443632] Modules linked in: binfmt_misc fuse coretemp w83627ehf hwmon_vid drm loop snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_i801 soundcore snd_page_alloc i2c_core pcspkr fglrx(P) rng_core evdev psmouse serio_raw ext3 jbd mbcache dm_mod sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan]
Oct 8 23:17:33 Joelle kernel: [ 3922.443656] Pid: 1521, comm: Xorg Tainted: P 2.6.32-[01] #1 System Product Name
Oct 8 23:17:33 Joelle kernel: [ 3922.443657] RIP: 0010:[<ffffffffa024b8d1>] [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443686] RSP: 0018:ffff8800370bb970 EFLAGS: 00010297
Oct 8 23:17:33 Joelle kernel: [ 3922.443687] RAX: ffff880037638008 RBX: ffffc9000144a150 RCX: 0000000000000000
Oct 8 23:17:33 Joelle kernel: [ 3922.443689] RDX: 0000000000000000 RSI: ffffc9000144a018 RDI: ffff880037638de8
Oct 8 23:17:33 Joelle kernel: [ 3922.443690] RBP: 0000000000000002 R08: ffffffffa0278bb0 R09: ffff880037638008
Oct 8 23:17:33 Joelle kernel: [ 3922.443692] R10: ffffc9000144a090 R11: ffff880037638008 R12: ffff880037638de8
Oct 8 23:17:33 Joelle kernel: [ 3922.443693] R13: 0000000000000040 R14: 0000000000000000 R15: 0000000000000000
Oct 8 23:17:33 Joelle kernel: [ 3922.443695] FS: 00007fb0e561d700(0000) GS:ffff880001700000(0000) knlGS:0000000000000000
Oct 8 23:17:33 Joelle kernel: [ 3922.443697] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 8 23:17:33 Joelle kernel: [ 3922.443698] CR2: 0000000000000008 CR3: 000000003776b000 CR4: 00000000000006e0
Oct 8 23:17:33 Joelle kernel: [ 3922.443700] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 8 23:17:33 Joelle kernel: [ 3922.443702] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 8 23:17:33 Joelle kernel: [ 3922.443704] Process Xorg (pid: 1521, threadinfo ffff8800370ba000, task ffff8800377d3100)
Oct 8 23:17:33 Joelle kernel: [ 3922.443705] Stack:
Oct 8 23:17:33 Joelle kernel: [ 3922.443706] ffffffffa024b2f6 0000000000000000 ffff880037638de8 ffff880037638e78
Oct 8 23:17:33 Joelle kernel: [ 3922.443709] <0> 0000000000000200 0000000000000000 ffffffffa01e45d5 0000000000080000
Oct 8 23:17:33 Joelle kernel: [ 3922.443711] <0> ffff880037638de8 ffffffffa0278bb0 ffffffffa01e4938 0000000000000000
Oct 8 23:17:33 Joelle kernel: [ 3922.443714] Call Trace:
Oct 8 23:17:33 Joelle kernel: [ 3922.443743] [<ffffffffa024b2f6>] ? _ZN7CMMHeap15createPoolSpaceI21CMMPoolAsicAccessibleEEbj+0xb6/0xc0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443788] [<ffffffffa01e45d5>] ? _ZN20CMMHeap_SystemMemory10obtainPoolEv+0x85/0xc0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443831] [<ffffffffa01e4938>] ? _ZN16CMMHeap_PAGEABLE10expandHeapEm+0x18/0xb0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443860] [<ffffffffa024b0ea>] ? _ZN7CMMHeap10expandHeapEmRmPv+0xa/0x10 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443904] [<ffffffffa01e32ed>] ? _ZN7CMMHeap21allocateMorePoolSpaceEmPv+0x8d/0x1b0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443947] [<ffffffffa01e1cbe>] ? _ZN14CMMHeapManager13allocPageableEjR14CMM_ALLOCATION+0xbe/0x100 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.443992] [<ffffffffa020a1f1>] ? AddrComputeSurfaceInfo+0x31/0x50 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444036] [<ffffffffa01ebc57>] ? _ZN9CMMObjectnwEmP8CMM_CORE+0x37/0x70 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444080] [<ffffffffa01ef7a2>] ? _ZN8MSF_CORE21get_surface_structureEv+0xc2/0xe0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444122] [<ffffffffa01da40f>] ? _ZN3MSF11create_surfEP9CMMClientP9CMMDriverPvRA4_K14CMM_ALLOCATIONP16MSF_SURF_ATTRIBS+0x1f/0x1c0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444164] [<ffffffffa01dbaf3>] ? _ZN3MSF21handle_shared_surfaceEP9CMMClientP9CMMDriverP10CMMSurfaceP16MSF_SURF_ATTRIBSP15_CMM_RETURNCODE+0x113/0x280 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444206] [<ffffffffa01d61aa>] ? CMMAllocSurface_WA+0x62a/0xab0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444235] [<ffffffffa018a522>] ? firegl_trace+0x72/0x1e0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444278] [<ffffffffa01e7219>] ? _Z8uCWDDEQCmjjPvjS_+0xb59/0x10c0 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444307] [<ffffffffa018ca32>] ? firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444336] [<ffffffffa018b360>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444365] [<ffffffffa018b2f0>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444389] [<ffffffffa0169fd8>] ? firegl_ioctl+0x1e8/0x250 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444412] [<ffffffffa0160c75>] ? ip_firegl_unlocked_ioctl+0x9/0xd [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444417] [<ffffffff810e34d8>] ? vfs_ioctl+0x19/0x83
Oct 8 23:17:33 Joelle kernel: [ 3922.444419] [<ffffffff810e3a22>] ? do_vfs_ioctl+0x46e/0x4b2
Oct 8 23:17:33 Joelle kernel: [ 3922.444422] [<ffffffff810d8216>] ? vfs_read+0xc7/0xfc
Oct 8 23:17:33 Joelle kernel: [ 3922.444424] [<ffffffff810e3aa2>] ? sys_ioctl+0x3c/0x5c
Oct 8 23:17:33 Joelle kernel: [ 3922.444428] [<ffffffff8100ba6b>] ? system_call_fastpath+0x16/0x1b
Oct 8 23:17:33 Joelle kernel: [ 3922.444429] Code: 00 00 00 00 00 00 00 00 00 00 48 8d 47 60 c3 00 00 00 00 00 00 00 00 00 00 00 31 c9 48 8b 97 90 00 00 00 83 7e 18 02 48 0f 44 ce <48> 89 51 08 ff 87 98 00 00 00 48 89 8f 90 00 00 00 c3 00 00 00
Oct 8 23:17:33 Joelle kernel: [ 3922.444449] RIP [<ffffffffa024b8d1>] _ZN20CMMHeap_SystemMemory8pushPoolEP7CMMPool+0x11/0x40 [fglrx]
Oct 8 23:17:33 Joelle kernel: [ 3922.444477] RSP <ffff8800370bb970>
Oct 8 23:17:33 Joelle kernel: [ 3922.444478] CR2: 0000000000000008
Oct 8 23:17:33 Joelle kernel: [ 3922.444480] ---[ end trace dbbddd5ad13ce08c ]---
</pre>

<hr>
<hr>
Edit 29.10.2011
<hr>
<hr>
Tried : Installed a more recent kernel ( 2.6.32.38 ) , Removed sid fglrx package, and installed a previous version "ati-driver-installer-11-6-x86.x86_64.run" downloaded from ADM site -> bug still present

Trying now "ati-driver-installer-10-9-x86.x86_64.run"

<hr>
<hr>
Edit 06.03.2012
<hr>
<hr>
Solved ! New ATI drivers conflict with kms. So you have to disable kms ( for example append "nomodeset" on your kernel boot line )

=== An Example of a working Xorg.conf ===
Lots of trial and error changing Options to get Compiz-Fusion running under Mandriva 2008-2010. X Server 1.6.5
(Sadly, the 'drak' tools that come with Mandriva to configure are worthless.)

In this instance it was chosen to remove packaged drivers and install from .bin file from AMD/ATI.

Most Options were added per 'aticonfig -f --initial ... ...'.
And the rest were added as needed. Constantly checking '/var/log/Xorg.0.log' for errors and warnings.

<pre> Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0 # The extra zeros are necessary for some reason
Option "AIGLX"
EndSection

Section "Files"
EndSection

Section "Module"
Load "dbe"
Load "v4l"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "Hewlett-Packard"
Option "ModelName" "HP D2845 Ergo 1600 21-inch Display"
HorizSync 31.5-95.0
VertRefresh 50.0-160.0
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
Option "UseFastTLS" "2"
Option "Textured2D" "on"
Option "TexturedXrender" "off"
Option "BackingStore" "on"
Option "VideoOverlay" "off"
Option "OpenGLOverlay" "off"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Extensions"
Option "Composite" "on"
Option "RENDER" "on" # essential for proper window border rendering
Option "DAMAGE" "on" # compiz-fusion calls for explicitly
EndSection
</pre>

Open for scrutiny and testing.

=== Sticky mouse cursor ===

Some users reported that the mouse cursor gets stuck when the mouse is moved to the lower right corner. At least in several versions of Ubuntu using Gnome desktop and starting with Catalyst 11.4.

That seems to be solved when adding ""load "dri"" to "Section Module" of xorg.conf.

==aticonfig Issues==
If you get the message ‘‘aticonfig: No supported adapters detected’’, you might have a card not officially supported by the fglrx driver but that might still work when forcing the driver to load. See [[Ubuntu#Unsupported_adapter]].

=== X server dies at start, possibly with error segmentation fault at address 0x8 ===
* aticonfig can mess up the fglrx config in /etc/ati/amdpcsdb, try overwriting with /etc/ati/amdpcsdb.default
"VideoOverlay" "on"
"OpenGLOverlay" "off"
"UseInternalAGPGART" "yes"
(10/2011, on cat-11.9, ATI 6300 aka 9803)

==AMD installer script completes, fglrx X driver loads, fglrxinfo reports error==

Xorg.log reports 2d/3d acceleration disabled, DRI disabled and uki errors related to /proc/ati files. AMD control panel works.

This can happen if there is a problem w/ the AMD installer compiling the fglrx.ko kernel module. The installation completes anyway with the fglrx Xorg driver in place. As per 2.6.42.9 and the 12.1 AMD driver there was a compile error in/usr/src/fglrx-8.93/firegl_public.c, due to TS_USEDFPU macro not being defined. Other compile-time errors will produce a similar problem. Check the contents of /usr/share/ati/fglrx-install.log, note if there was a compile error. If so, re-running the AMD installer will not fix the problem since the compile error will just recur. Likewise, patching the bug ie

http://phoronix.com/forums/showthread.php?68922-Patch-to-compile-fgrlx-module-on-Linux-3-3-rc4-with-x86-32-bit-arch

and then reinstalling won't help either since the installer re-extracts the source from the archive. To fix, apply whatever fix is required to the sourcecode that the installer leaves in /usr/src/fglrx-xxx and use dkms to compile and install the driver.

dkms add fglrx/8.93 /usr/src/fglrx-8.93 
dkms build fglrx/8.93 
dkms install fglrx/8.93 

Apply fixes to the fglrx source and repeat the dkms build step until the build completes, then install & reboot. Check lsmod output to see if fglrx.ko is loaded, confirm DRI and proc stuff in Xorg.log is working.

In the 2.6.42.9 w/ 12.1 bug case, the fix is to add the TS_USEDFPU ifdef in firegl_public.c as below;

void ATI_API_CALL KCL_fpu_begin(void) 
{ 
<nowiki>#ifdef CONFIG_X86_64</nowiki>
kernel_fpu_begin();
<nowiki>#else</nowiki> 
<nowiki>#ifndef TS_USEDFPU</nowiki>
preempt_disable();
if (__thread_has_fpu(current))
__save_init_fpu(current);
<nowiki>#else</nowiki>
struct thread_info *cur_task = current_thread_info();
preempt_disable();
if (cur_task->status & TS_USEDFPU)
__save_init_fpu(cur_task->task);
<nowiki>#endif</nowiki>
else
clts();
<nowiki>#endif</nowiki>
}

==References==
<references/>

[[Category:Installation Documentation]]

[[Category:NeedsUpdating]]
{{VCT}}

Troubleshooting

2012-05-14T21:58:20Z

213.144.132.98: /* X Server Related Issues */

Hello! cbbafaf interesting cbbafaf site! I'm really like it! Very, very cbbafaf good!

Very nice site!

==aticonfig Issues==
If you get the message ‘‘aticonfig: No supported adapters detected’’, you might have a card not officially supported by the fglrx driver but that might still work when forcing the driver to load. See [[Ubuntu#Unsupported_adapter]].

=== X server dies at start, possibly with error segmentation fault at address 0x8 ===
* aticonfig can mess up the fglrx config in /etc/ati/amdpcsdb, try overwriting with /etc/ati/amdpcsdb.default
"VideoOverlay" "on"
"OpenGLOverlay" "off"
"UseInternalAGPGART" "yes"
(10/2011, on cat-11.9, ATI 6300 aka 9803)

==AMD installer script completes, fglrx X driver loads, fglrxinfo reports error==

Xorg.log reports 2d/3d acceleration disabled, DRI disabled and uki errors related to /proc/ati files. AMD control panel works.

This can happen if there is a problem w/ the AMD installer compiling the fglrx.ko kernel module. The installation completes anyway with the fglrx Xorg driver in place. As per 2.6.42.9 and the 12.1 AMD driver there was a compile error in/usr/src/fglrx-8.93/firegl_public.c, due to TS_USEDFPU macro not being defined. Other compile-time errors will produce a similar problem. Check the contents of /usr/share/ati/fglrx-install.log, note if there was a compile error. If so, re-running the AMD installer will not fix the problem since the compile error will just recur. Likewise, patching the bug ie

http://phoronix.com/forums/showthread.php?68922-Patch-to-compile-fgrlx-module-on-Linux-3-3-rc4-with-x86-32-bit-arch

and then reinstalling won't help either since the installer re-extracts the source from the archive. To fix, apply whatever fix is required to the sourcecode that the installer leaves in /usr/src/fglrx-xxx and use dkms to compile and install the driver.

dkms add fglrx/8.93 /usr/src/fglrx-8.93 
dkms build fglrx/8.93 
dkms install fglrx/8.93 

Apply fixes to the fglrx source and repeat the dkms build step until the build completes, then install & reboot. Check lsmod output to see if fglrx.ko is loaded, confirm DRI and proc stuff in Xorg.log is working.

In the 2.6.42.9 w/ 12.1 bug case, the fix is to add the TS_USEDFPU ifdef in firegl_public.c as below;

void ATI_API_CALL KCL_fpu_begin(void) 
{ 
<nowiki>#ifdef CONFIG_X86_64</nowiki>
kernel_fpu_begin();
<nowiki>#else</nowiki> 
<nowiki>#ifndef TS_USEDFPU</nowiki>
preempt_disable();
if (__thread_has_fpu(current))
__save_init_fpu(current);
<nowiki>#else</nowiki>
struct thread_info *cur_task = current_thread_info();
preempt_disable();
if (cur_task->status & TS_USEDFPU)
__save_init_fpu(cur_task->task);
<nowiki>#endif</nowiki>
else
clts();
<nowiki>#endif</nowiki>
}

==References==
<references/>

[[Category:Installation Documentation]]

[[Category:NeedsUpdating]]
{{VCT}}