Package Details: catalyst-test 15.12-15

Git Clone URL: (read-only)
Package Base: catalyst-test
Description: AMD/ATI Catalyst drivers for linux AKA Crimson. catalyst-dkms + catalyst-utils + lib32-catalyst-utils + experimental powerXpress suppport. PRE-GCN Radeons are optionally supported
Upstream URL:
Licenses: custom
Conflicts: catalyst, catalyst-control, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-hook, catalyst-utils, libegl, libgl, libgles, libglvnd, mesa-libgl, mesa-libgl-git, opencl-amd, opencl-catalyst
Provides: catalyst=15.12, catalyst-dkms=15.12, catalyst-hook=15.12, catalyst-libgl=15.12, catalyst-utils=15.12, dri, libatical=15.12, libegl, libgl, libgles, libtxc_dxtn, mesa-libgl, mesa-libgl-git, opencl-catalyst=15.12, opencl-driver
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 167
Popularity: 0.001064
First Submitted: 2010-02-17 20:49
Last Updated: 2017-05-28 19:55

Dependencies (23)

Required by (676)

Sources (30)

Latest Comments

Vi0L0 commented on 2017-05-25 18:15

Thanks npfeiler, I will add your patch after getting back from vacation leave, in Sunday.
Edit: Done, mesa 17.1.0 has took me some time, I should update more packages tomorrow.

npfeiler commented on 2017-05-25 16:40

4.11 patch v2
EDIT: added a missing line

blueberry commented on 2017-04-23 10:46

@obrez Try to reinstall catalyst-dkms with -Syuu (which allows downgrades).

obrez commented on 2017-04-21 18:09

@blueberry @Vi0L0 Just want to thank you guys, Been fighting this for a month. I moved to LTS kernel for now and everything is working. I am getting these errors though when running pacman.

error: missing 'linux>=3.0' dependency for 'catalyst-dkms'
error: missing 'linux<4.11' dependency for 'catalyst-dkms'
error: missing 'linux-api-headers>=4.10' dependency for 'glibc'

do I need catalyst-dkms?

thanks again guys <3

blueberry commented on 2017-04-17 14:48

Yesterday I updated catalyst-test and xorg "broke" in a sense that it refused connections, but Xorg.0.log and journalctl -b didn't have any unusual errors, except a hint that there was some crash dump connected to xorg/fglrx (but this wasn't so obvious to notice, at least for me). I googled and tried all possible and impossible re/installations, but nothing helped.

I have a pretty unusual configuration with 2x R9 290x + Nvidia 1080 + xmonad + startix with xinitrc, but even plugging out nvidia card didn't help.

The solution (in my case) was to ** switch kernel to linux-lts (4.9).**! I didn't try this before because Vi0L0 is using 4.10, but in the end that segfault prompted me to try kernel 4.9, and that was the solution.

I can't post the actual outputs since there were so many things that I tried, but I hope this can help someone...

herycp commented on 2017-04-16 09:17


all mentioned modules blacklisted

Vi0L0 commented on 2017-04-16 08:17

@herycp: this RIP doesn't look good, but like I said gdm probably won't work, so check other one. Also did you blacklisted all mentioned modules?

herycp commented on 2017-04-16 02:10

Can't initialize KMS backend: could not find drm kms device

but i disable kms :
File: /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=04301697-cfc4-46a3-9c00-f1ff51617609"

herycp commented on 2017-04-16 02:07


i tried install like ur note but blank (just unrespon screen so i cant swich tty and try run startx) in prosses before run dm (i use gdm)

journal :

Apr 16 07:08:50 rio-MPC systemd[565]: Started D-Bus User Message Bus.
Apr 16 07:08:50 rio-MPC gnome-shell[583]: Can't initialize KMS backend: could not find drm kms device
Apr 16 07:08:50 rio-MPC gnome-session[576]: gnome-session-binary[576]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 16 07:08:50 rio-MPC gnome-session-binary[576]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 16 07:08:50 rio-MPC gnome-session-binary[576]: Unrecoverable failure in required component org.gnome.Shell.desktop
Apr 16 07:08:50 rio-MPC gdm[499]: GdmDisplay: display lasted 0,324748 seconds
Apr 16 07:08:50 rio-MPC systemd-logind[462]: Removed session c2.
Apr 16 07:08:50 rio-MPC gdm[499]: Child process -572 was already dead.
Apr 16 07:08:50 rio-MPC gdm[499]: Child process 554 was already dead.
Apr 16 07:08:50 rio-MPC gdm[499]: Unable to kill session worker process

Apr 16 07:08:52 rio-MPC kernel: RIP: KCL_ACPI_GetVfctBios+0x36/0x70 [fglrx] RSP: ffffc900022cba58


Vi0L0 commented on 2017-04-07 21:35

it's working fine (as for catalyst) here on 4.10.8-1-ARCH kernel and plasma desktop. I'm using sddm desktop manager, gdm probably won't work, but GNOME on Xorg should work fine with additional patched packages from [catalyst] like cogl, mutter and imagemagick-nocl.
edit: I now switched to GNOME on xorg and it's also running well. It has compositing, while plasma isn't able to render compositing on catalyst since months

Just a couple of notes:
1. add [xorg117] and [catalyst] repos over other repositories in pacman.conf
2. blacklist some modules:
# cat /etc/modprobe.d/blacklist.conf
blacklist radeon
blacklist amdgpu
blacklist kms
blacklist drm_kms_helper
3. It's better to have xorg.conf with fglrx inside
4. Don't forget about nomodeset in kernel options

Heres what I did to switch from mesa-git to catalyst
- performed steps from notes mentioned above :>
- removed conflicting packages:
pacman -Rdd mesa-libgl-git xf86-video-amdgpu-git lib32-mesa-libgl-git
- downgraded xorg-server and installed other packages (also mesa-noglvnd and mutter should be installed, even when they are not mentioned in command below) from [catalyst] repo:
pacman -Syuu catalyst-dkms catalyst-utils catalyst-libgl opencl-catalyst lib32-catalyst-utils lib32-catalyst-libgl lib32-opencl-catalyst imagemagick-nocl
- rebooted

if that won't help then you should give additional info including info about your GPU + links to pastebin with your:
- Xorg.0.log
- dmesg
- journalctl -b
- try to run startx and note what it returns

All comments