For example, from the archlinux wiki:
As has been said, recovering should work when reinstalling mesa and libgl.Quote:
Warning: Using the installer from ati.com/amd.com is NOT recommended for inexperienced users! It may cause file conflicts and X failures. You must be familiar with booting to the command-line if you wish to attempt this.
But how exactly should AMD do it better? I mean, they could back up the files they overwrite, but then they would maybe restore old files to a way newer mesa/libgl release that has been happening in the meantime...
And I wonder: When you use the ati installer and then update mesa/libgl, won't the package manager overwrite files belonging to fglrx and break it?
It would just need LIBGL_DRIVERS_PATH for example set in /etc/profile.d/ and to check when the fglrx kernel module is loaded I think.
Straight from the read me ...
Launch the Terminal Application/Window and navigate to the /usr/share/fglrx folder.
With super user permissions, enter the command "sh./fglrx-uninstall.sh"
The script will usually restore all the correct mesa files and symlinks.
Their official installer is nasty shit, seriously. Don't use it. :) (OK, it is your system, but don't say nobody warned you.) If you feel comfortable poking around figuring out why X won't load, use their installer. If you want it packaged in a semi-sane manner that probably won't destroy your system* use the distribution specific packages.
(*This isn't to say that FGLRX won't randomly lock up your system forcing you to hold in the power button, but that's on a bad month, like this month's 11.9 release. Usually.)
Thats correct, do not use the nvidia install on ubuntu >= 10.04. that introduced the gl_conf alternatives switching and will stop working correctly then. it works fine with debian squeeze however.
I always run "sudo dpkg-reconfigure -phigh xserver-xorg" when I am finished to ensure the system is back to default. Then when back to a desktop open a term and run xvinfo and glxinfo to make sure the Mesa driver is working. The mesa-utils package must be installed to provide glxinfo.
I do agree that removing fglrx is often a lot more messy than removing nvidia.
Letting users easily install it from their official installer with no warning at all just contributes to this whole "ZOMG, I broke everything, Linux sucks" problem caused by their proprietary drivers. Not that they care. (AMD's download page = radeon_linux.aspx) :)
I agree with grege on this, I have also used the AMD's uninstaller many times without problems. Although one thing needs to be kept in mind, when ever one is working outside the package management system one does need to be switched on.
I normaly use AMD's binary blob directly to install, I have used Kano's script and it works well but it does need a GOOD internet connection and this is something I do not (and likely never will) have. So this restricts how I can do things.
Note: I have not used FGLRX now for at least 6 months as I find the OS driver superior for the type of 3D develpment work I do.