Comment 5 for bug 552782

Revision history for this message
Abdó Roig-Maranges (aroig) wrote :

This workaround partially worked for me. Using it I managed to cleanly install fglrx, but after the apparently successful installation there were some missing files.

I upgraded from karmic to lucid in a 64 bit machine with an ATI graphics card using fglrx (i.e. I had the package xorg-driver-fglrx installed on karmic).

1 - Some files in /etc/ati were missing, not sure which ones. It seems that the upgrade script backed up the old karmic files, but forgot to install the new ones. This made aticonfig complain about a missing /etc/ati/control, for example.

2 - Some libraries in /usr/lib/fglrx/ were also missing. The one I remember is libGL.so.1.2. Not sure why this happened.

The solution I found to both this problems is removing fglrx and fglrx-amdcccle completely with:

aptitude purge fglrx fglrx-amdcccle

deleting manually /usr/lib/fglrx and /etc/ati:

rm -R /usr/lib/fglrx
rm -R /etc/ati

and then reinstalling both packages:

aptitude install fglrx

3 - The files libglx.so and libdri.so in /usr/lib/xorg/modules/extensions/ were also missing. Those files belong to the package xserver-xorg-core, and are the ones involved in the diversion thing discussed in this thread. This prevented the open source driver radeon from working, leaving the framebuffer as the only working alternative just after upgrade.

The solution to this was reinstalling xserver-xorg-core:

aptitude reinstall xserver-xorg-core

Oh, by the way, I have ended up with the open source driver by the moment. The fglrx apparently works fine, but the performance is terrible ! 894 fps in glxgears (vs 2620 fps with the radeon driver). Any clue about this ? It may be an upstream issue ?