Have you tried running AMD proprietary drivers in Linux Mint 17.1?
Linux mint has a driver manager under control panel (that is unique to mint, Ubuntu doesn't have it) that is as simple as clicking the box for which proprietary drivers a person wants to be used. All that is required after that is a full reboot of the computer. (which they don't tell a person do..... but is apparently required to get everything working straight)
P.S. One major downside that I can determine is that the latest proprietary drivers are not an option with mint driver manager.
Haven't bothered with Mint, though Ubuntu does offer pushbutton driver installation for proprietary drivers in Synaptic. You can pick fglrx and fglrx-updates. When I used that, it just sort of locked up and did nothing. I have never had problems with that using an Nvidia card.
The main issues right now with Catalyst under Linux is the wine incompatibility (which is only an issue for those that want to use wine, mind you) and the silly Xorg incompatibility. The Xorg issue ceased to be a problem when they rolled out an Ubuntu-only update to 14.9 that fixed that little problem (14.12 is also compatible with Xorg 1.16 and later). The wine problem . . . is still there, and may be for awhile.
Then there's the monitor autodetect flaw built into fglrx (and, it turns out, the Windows driver too). The driver seems to detect resolution support that is a fiction (example: my junky Gateway monitor supports 1280x1024 max, but the driver seems to think it can do 1600x1200). It defaults to the highest detected resolution which results in the monitor going out of range, and for some bizarre reason this breaks xrandr/xset badly enough that the resolution can not be changed by hand from the command line. Fixing that problem involves setting up an xorg.conf file which Ubuntu (and many other distros) not longer even uses by default. Fortunately, aticonfig --initial creates a base file that is relatively easy to modify.
In Windows, thanks to MS not being criminally insane (all the time), the OS will default to a resolution that will actually work assuming a similar resolution was in use before installing Catalyst. Sure, Catalyst will still offer me non-functional resolutions like 1600x1200, but the important thing is that it doesn't default to any of those.
Bottom line is this: it is theoretically possible that you could pick a Linux distro with pushbutton fglrx installation, grab a version of 14.9 that is compatible with the standard version of X, and still have problems thanks to the monitor being pushed irreparably into an unsupported resolution. The solution involves hand-editing a .conf file in a directory which has contents that generally can not be altered by hand unless the user asserts root privs. And that doesn't even cover the wine thing.
edit: in all fairness to AMD, they have been rolling out drivers rapidly over the last year, and many things have changed. It isn't that hard to get 14.12 to work once you figure out what's going wrong. It's not like the driver itself is completely non-functional (though it seems to break some games for people under Linux and Windows . . . not sure why). In fact, it's very nice compared to Gallium .4 . The real problem is the shortage of good information on what to do if your driver install goes off the rails. That unsupported monitor resolution thing has been repeatedly reported for years, and for most, it's a show-stopper.