AMD Catalyst 15.5 Beta Linux Driver Surfaces
AMD is finally out with a big Catalyst Linux driver update!
This morning was a big AMD Radeon vs. NVIDIA GeForce Linux graphics card comparison in celebration of Phoronix turning eleven this week. Coincidentally, a new Catalyst Linux driver has now surfaced.
The Catalyst 15.5 driver is newer than the last official Linux driver releases -- Catalyst 14.12 Omega from last December. This Catalyst 15.5 Linux driver is marked in the fglrx 15.101 release stream, which pegs it newer than the 14.12 driver and just not some bug-fixes squeezed in, but it's older than the Catalyst driver unofficially released to Catalyst for Ubuntu 15.04. Found within Ubuntu 15.04 is a driver from the fglrx 15.20 series, which is the driver used for benchmarking this morning.
As soon as I have more information on this Catalyst 15.5 Linux driver update I'll certainly pass it along, but don't expect any miracles given it's still older than the Ubuntu Vivid driver. The download link is here but first needing to visit the AMD site due to it checking the HTTP referrer.
This morning was a big AMD Radeon vs. NVIDIA GeForce Linux graphics card comparison in celebration of Phoronix turning eleven this week. Coincidentally, a new Catalyst Linux driver has now surfaced.
The Catalyst 15.5 driver is newer than the last official Linux driver releases -- Catalyst 14.12 Omega from last December. This Catalyst 15.5 Linux driver is marked in the fglrx 15.101 release stream, which pegs it newer than the 14.12 driver and just not some bug-fixes squeezed in, but it's older than the Catalyst driver unofficially released to Catalyst for Ubuntu 15.04. Found within Ubuntu 15.04 is a driver from the fglrx 15.20 series, which is the driver used for benchmarking this morning.
As soon as I have more information on this Catalyst 15.5 Linux driver update I'll certainly pass it along, but don't expect any miracles given it's still older than the Ubuntu Vivid driver. The download link is here but first needing to visit the AMD site due to it checking the HTTP referrer.
63 Comments