Ubuntu starts and runs with the open source driver, but once I go into Additional Drivers and activate the Fglrx or Fglrx-updates proprietary drivers and restart, after I login nothing in Ubuntu shows up… other then the water mark. It appears to break unity.
I have to reinstall ubuntu to get back to open-source, what is my next plan of action to get Catalyst to work?
V: 13.04
A: HD 5730 ATI
Best Answer
There seems to be lot of problems with proprietary drivers in Raring. It is a fresh release and not everything is always working as it should.
Make sure that you don't have proprietary and open source drivers installed at the same time. When you try different drivers, always keep track of which one is loaded. To do that you can use this command:
If you get into situation where something crashes and you will not be able to fix things by using graphical user interface you can still get to command line. Firstly you can try pressing Ctrl+Alt+F<1-6>( chose number between 1 and 6). Another option is to enter “recovery mode” at boot that also gives you access to command line. So maybe you don't have reinstall entire OS.
You get a list of installed packages with this:
When you remove a packages with apt-get use “purge”:
Fglrx packages:
Fglrx-update packages:
Open source driver packages:
To install a package use good old:
If you really want the benefits of the proprietary driver then you could also download proprietary drivers directly from amd support site.
Inside the zip-file there is a run-installer. I suggest you create deb-file from that (more details and tips here and here)as then the driver is easier to remove if it doesn't work. If you have to do it all from command line then these are the steps:
Download the driver:
Unzip the driver:
Make the file executable:
Create deb-file from the run-installer:
This might give you an error as you might lack necessary packages. According to this site at least Precise needed these packages to be installed.
Install the deb file (replace * sign with the real ending – to check the correct file name you can use
ls -l
command):If that also doesn't work I guess, you are stuck with open source drivers until problems get fixed. Also than when something is supposed to work but doesn't it is a bug and these only get fixed if bugs are reported. On reporting bugs see this. Always check that the bug has not been reported already but even if it has you should still click that you are been affected by the bug as it raises its importance.