Method 2 for Catalysy 7.11

Done.

Suspend/Hibernation with Catalyst 7.11 & Gutsy

I hoped that with these drivers and Gutsty, the suspend problem would have been solved. Unfortunately it isn't for me.
I tried also to apply the patches to "acpi-support" (like doing with Feisty) but unsuccessfully.
Any working experiences? Solutions? Workarounds?

installation hint

I followed this guide and fglrxinfo yielded the desired output.

But then I still got the following problems:

crash/restart of X when trying to run glxgears

crash/restart of X when trying to watch mythtv recording

visual artefacts from window creation

The cause I assumed in that:

glxinfo | grep direct

did not yield 'yes' but 'no' and 'Mesa Indirect'

Long search, quick solution:

sudo apt-get remove xserver-xgl

Note: I don't really know what this actually does in the context of a desired installation, so try at your own risk. I assume this being installed from my earlier Feisty installation where I tried out compiz and AIGLX was not supported by the driver.

After removing the xserver-xgl package, all problems described above vanished.

Maybe someone with more detailed knowledge might find it useful to add a paragraph to the page.

Comment: I had a lot of trouble until I found your solution. Removing xserver-xgl made most of the graphical artifacts disappear (I still have some black bars in the bottom right corner of one screen), and made my dual screen setup work again. Should this be in the general guide?

Comment: I was seeing some very similar behavior after following this tutorial. glxgears would cause gdm to crash and the artifacts were left on the screen. The system would also be dog slow, moving windows was very laggy. Removing xserver-xgl did the trick for me!

Any Ideas? It did work before (on feisty, using older drivers)!! Help!! --212.62.64.34 14:08, 22 November 2007 (CST)

I SOLVED (subvertigo):
The problem was the fglrx.ko . The symbolic link have been overwritten at each reboot.
Check if the fglrx.ko in the "volatile" folder is a symbolic link or not to that in the "misc" folder (Gnome reports an arrow on the icon if it is, and must have the same dimension). If it is the same problem see the first paragraph to see how I solved.

The symbolic link is gone after a reboot. Filesize of the one in the misc folder is 2084611 bytes and the one in the volatile folder is 1058754 bytes. I don't know where/what this copying is done. :(

So where this 1058754 bytes sized version exists on the system is unclear to me.

(Partially) Installed but 7.11 Driver NOT used

The catalyst control center is available under "accessories" and list the following.

Software:

Driver version : 8.43.2

Catalyst Control Center Version : 1.6

OpenGL:

.. Provider : Mesa project ...

.. Renderer : Mesa GLX Indirect

.. Version : 1.4 (2.1 Mesa 7.0.1)

Checklist:

"Restricted" repositories not commented

The "restricter driver manager" says that the driver is enabled and in use.

Symbolic link exists

Really don't know what the problem is.

EDIT (subvertigo) The problem is almost surely the "fglrx.ko"... see the first paragraph for the solution.
Moreover the "restricted manager" should say that the driver is NOT enabled (equivalent to blacklist the original "fglrx" in linux-restricted-modules-common).

After a reboot this link was always removed automatically

I installed the latest Radeon driver using the ATI installer and found myself trying to solve this reboot problem. Eventually I deduced that the modules in the Gutsy /lib/modules/(uname -r)/volatile/ directory are generated (compiled?) on a reboot from the files in the directories contained in /lib/linux-restricted-modules/(uname -r)/. By replacing the three files in fglrx with the matching named files from ATI's /lib/modules/fglrx/build_mod/ it appeared to work happily on a reboot.

I am not entirely convinced by this empirical solution as I do not understand the compilation process well enough. (Hugh Kernohan)