Package Details: catalyst-firepro 15.302.2301-5

Git Clone URL: (read-only, click to copy)
Package Base: catalyst-firepro
Description: AMD/ATI drivers for FirePro/GL/MV brand cards. catalyst-dkms + catalyst-utils + lib32-catalyst-utils + experimental powerXpress suppport.
Upstream URL:
Licenses: custom
Conflicts: catalyst, catalyst-control, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-utils, libegl, libgl, libgles, libglvnd, mesa-libgl, mesa-libgl-git, opencl-amd
Provides: catalyst=15.302.2301, catalyst-dkms=15.302.2301, catalyst-libgl=15.302.2301, catalyst-utils=15.302.2301, dri, libatical=15.302.2301, libegl, libgl, libgles, libtxc_dxtn, mesa-libgl, mesa-libgl-git, opencl-catalyst=15.302.2301, opencl-driver
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 6
Popularity: 0.000000
First Submitted: 2011-01-25 17:19
Last Updated: 2017-04-03 19:13

Dependencies (23)

Required by (907)

Sources (28)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Vi0L0 commented on 2017-04-03 19:07

@good: catalyst-control is not necessary when using this pkg, I will add it to conflict

as for No supported adapters - well... there's a reason why it has catalyst in pkgname - it's not "perfect" :>

good commented on 2017-03-18 03:17

error: file owned by 'catalyst-control' and 'catalyst-firepro': 'etc/ati/control'

I get this error everytime I run pacman. Could you give me advise and tell me whether it means that both packages owning the same folder/file?

Second Question: aticonfig: No supported adapters detected
My gpu is Firepro M6100. Therefore, it should be supported I guess.

Thanks @Vi0L0

Vi0L0 commented on 2017-03-11 18:32

If you see this conflict:

looking for conflicting packages...
:: mesa and catalyst-firepro are in conflict (mesa-libgl). Remove catalyst-firepro? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: mesa and catalyst-firepro are in conflict

for now I've added mesa packages of 17.0.1-1 version to [catalyst]* and [catalyst-stable] - simply copied from archive:

Please downgrade if you updated mesa to -2 version.
After new version of mesa came out, I will build new mesa packages without glvnd support. Then I will most probably add new mesa package to aur. Will let know when it will happen

Server =$arch

Vi0L0 commented on 2016-09-03 07:21

Nah, you can leave amdpcsdb alone, this tip was only added because otherwise it was showing wrong version of the driver in amdcccle, but theres no problems because of that.

I was switching between this and amdgpu a lot latelly and has no problems with this process.
You can backup xorg.conf for future use. Don't forget to add nomoedeset to kernel options, additionally you can blacklist some modules like:
$ cat /etc/modprobe.d/blacklist.conf
blacklist radeon
blacklist amdgpu
blacklist kms
blacklist drm_kms_helper

Malekeith commented on 2016-09-01 21:32


Before, I update and screw things up which is highly probable. Do I need to do anything ? kill X for example ? I've read the Ati_Catalyst wiki, but I'm not to sure what else to do? the only steps I notice was "remove /etc/ati/amdpcsdb" ?

Vi0L0 commented on 2016-08-17 17:18

updated to 15.302.2301:
+ added 4.7 kernel patch (also works on linux-zen 4.7-1)
- still no xserver 1.18 support :(

xserver 1.18 is not supported, you have to use 1.17 from archive repo:
or compile your own from sources ie. from www.archlinux git:
(--> download --> <name>.tar.xz)

polo commented on 2016-07-31 14:21

Building xorg-server 1.18 from AUR but i have xorg-server alredy installed from extra repository.

Vi0L0 commented on 2016-06-13 17:47

download is fixed now

Vi0L0 commented on 2016-06-12 19:46

updated to 15.302.2001 with our 4.6 kernel support, DKMS and acpi script from aslmaswd.

Don't have time to look at why direct download doesn't work, maybe some nice bit or something, so please download manually from:
and paste zip next to PKGBUILD

Malekeith commented on 2015-12-28 08:12


I've fix the problem, it wasn't GDM making the drivers unable to display.

It was actually xorg, interfering with the installation process. Since every time, I killed xorg with pkill x and re-installed drivers, the next time they boot up it works fine.

the only problem now is, reinstalling the driver every time xorg fails. Well not really a big problem, since I can actually use gdm now

Well, thanks Vi0l0