Comment 27 for bug 870560

Revision history for this message
Malte Skoruppa (malte-countnumber) wrote :

I experienced the very same bug as everybody when I tried to install the post-release updates for the FGLRX driver through jockey.

I just wanted to let everyone know that I solved the problem on my computer by simply _manually_ installing the latest AMD drivers, as explained in the Ubuntu Wiki:
https://help.ubuntu.com/community/BinaryDriverHowto/ATI

That is, instead of using jockey (i.e., the Ubuntu GUI for third-party driver installation) to install the latest FGLRX drivers, I did it manually by creating the necessary *.deb packages myself. It's very easy to do and it is explained in detail in the Ubuntu Wiki, linked above.

Of course, this does not solve the discrepancy problem between jockey-common and fglrx-updates as described by Jack Foys in the above comment. However, I assume that everybody who experienced this bug and began to look for a solution in the Internet, was actually simply trying to get the latest FGLRX drivers working. With the manual method, this works flawlessly, and I am now running the AMD Catalyst 12.2 drivers on my machine.

$ lspci | grep -i vga
01:00.0 VGA compatible controller: ATI Technologies Inc Cayman PRO [AMD Radeon 6900 Series]

$ fglrxinfo
display: :0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon HD 6900 Series
OpenGL version string: 4.2.11554 Compatibility Profile Context

I hope someone may find this useful.

Cheers,

Malte