Package: fglrx-driver Followup-For: Bug #660571 Although this bug was solved, I wanted to give a few pointers and additional information for users that might get caught with this bug.
Actually, I had exactly the same problem and I managed to solve it as well with the good advice from the packager (Patrick Matthäi) first on the way to solve the bug: - purge all fglrx releated packages on your system aptitude --purge-unused purge '~i fglrx' which removed the following: fglrx-atieventsd fglrx-control fglrx-driver fglrx-glx fglrx-glx-ia32 fglrx-modules-dkms glx-alternative-fglrx libfglrx-ia32 libgl1-fglrx-glx libxvbaw1 xvba-va-driver and then to find the fglrx leftovers files for removal locate fglrx|xargs ls -d 2> /dev/null and this is exactly where I found the culprit: /usr/lib/xorg/modules/drivers/fglrx_drv.so this file was dated back in January, when it was modified by the script fixwatermark.sh (cf. https://gist.github.com/1601436 ) to remove an "unsupported hardware" watermark the problem with this script is that it changes the aforementioned file which was originally a symlink, and then the file is not updated which then leads to the bug of wrong version of DRI/DRM compared to the fglrx driver (EE) fglrx(0): (fglrxdrm.a version = 8.95.3, expected 8.93.4). Disabling DRI. so, all in all in my case the problem was due to the modification of the file /usr/lib/xorg/modules/drivers/fglrx_drv.so by the fixwatermark.sh to solve it, one has to delete this file and reinstall the package fglrx-driver 'hope this helps -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
