Originally posted by vein
View Post
3. Run application
With NV drivers, it just works. With AMD, its time to upgrade to 4.12 kernel, load Mesa from Git, and descend into Dante's 9th circle of regression hell. Look at all Michael's benches: in an effort to make AMD look better he keeps using Beta/Alpha/Git snapshot software including the Kernel. While this might be fun for dual-boot tinkerers it is unacceptable for mission-critical workstations.
My son plays dozens of steam games, many of them unavailable on AMD GPUs. The total time spent tinkering to make those games work on our GPU is almost always 0 minutes per week. Not my experience with AMD. At all.
No worries mate, buy what makes you happy. But let's be honest with the Linux newbies and professionals who want and need things to work reliably with minimal trouble.
EDIT: To wit, check out this latest article: http://www.phoronix.com/scan.php?pag...new-1710&num=1 Alpha, Beta, Git. And a gem of a quote that sums it up all the constant trouble getting performant and stable AMD drivers from anywhere:
The AMDGPU-PRO 17.10 driver was tested on Ubuntu 16.10 since the hybrid driver doesn't yet support Ubuntu 17.04 / newer Linux kernel / X.Org Server releases. But the Padoka PPA no longer ships the latest drivers for 16.10 and when building Mesa Git on Ubuntu 16.10, I ended up hitting Unity/GLAMOR issues. So for the open-source tests I did that from Ubuntu 17.04.
Comment