Package Details: catalyst-test 15.12-6

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 NOT SUPPORTED
Upstream URL:
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-hook, catalyst-utils, libcl, libgl, mesa-libgl, mesa-libgl-git
Provides: catalyst=15.12, catalyst-hook=15.12, catalyst-libgl=15.12, catalyst-utils=15.12, dri, libatical=15.12, libcl, libgl, libtxc_dxtn, mesa-libgl, mesa-libgl-git, opencl-catalyst=15.12
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 168
Popularity: 1.854267
First Submitted: 2010-02-17 20:49
Last Updated: 2016-05-13 19:02

Dependencies (22)

Required by (658)

Sources (25)

  • 4.3-gentoo-mtrr.patch
  • 4.3-kolasa-seq_printf.patch
  • 4.4-manjaro-xstate.patch
  • 4.6-arch-get_user_pages-page_cache_release.patch
  • arch-fglrx-authatieventsd_new.patch
  • atieventsd.service
  • catalyst.conf
  • crimson_i686_xg.patch
  • dkms.conf
  • fglrx_gpl_symbol.patch
  • grsec_arch.patch
  • lano1106_fglrx_intel_iommu.patch
  • lano1106_kcl_agp_13_4.patch
  • makefile_compat.patch
  • makesh-dont-check-gcc-version.patch
  • pxp_switch_catalyst
  • switchlibGL
  • switchlibglx
  • temp-links-catalyst.service
  • temp_links_catalyst

Latest Comments

Vi0L0 commented on 2016-05-13 20:55

thanks again :) so it stores modules in two different places... oukaaaay 8)
Arch/dkms wiki should definitelly have more details

runnytu commented on 2016-05-13 20:26

@Vi0L0, no problem we are all humans after all ;P, the best way to clean is 'rm -fr /var/lib/dkms/fglrx' and to install the module for all the installed kernels with 'dkms autoinstall -m fglrx-15.12 -v 6' later with 'dkms status' should see a output like this for all installed kernels, 2 in my case:
fglrx-15.12, 6, 4.5.4-1-ARCH, x86_64: installed
fglrx-15.12, 6, 4.5.4-1-zen, x86_64: installed

Vi0L0 commented on 2016-05-13 19:48

you got the point runnytu, nice finding

I have removed dkms commands from install script, should be fine now.
Previous version was taken from original catalyst-dkms version and it didn't fit arch's newer dkms.
It was creating fglrx.ko module for booted kernel (with "dkms -v fglrx"), then it was overwritten (because defined module name is the same) by dkms itself (with "dkms -m fglrx-15.12").

I'm just not sure how is dkms going to find out about overwritten module (as it was generated using different version, could generate some trash from it that will have to be removed manually. Sorry for the inconvinience.
Possibly the best way to clean after -5 version is to:
1. use `dkms remove -m fglrx-15.12 -v 5 --all` or `dkms remove -m fglrx-15.12 -v 6 --all` after update to -6
2. use `find /usr/lib/modules/ -iname '*fglrx*'` to trace trash and use rm to remove it manually
3. use `dkms install -m fglrx-15.12 -v 6` to build module for booted kernel or reinstall catalyst-test if you got more kernels - I don't know simple way to build modules for all kernels. One can use some loop like `for` for it, but there should be some easier way available.
But even without cleaning it should work fine, eventually there will be some fglrx module trash left after kernel's version bump ;P.

Thanks again runnytu.
And sorry for missing it.

runnytu commented on 2016-05-12 18:04

Hi, @Vi0L0, you should remove the 'dkms install -m fglrx -v $1' in post_install() and post_upgrade() and the 'dkms remove -m fglrx -v $1 --all' in pre_remove() in the file catalyst-test.install because pacman installs and removes the DKMS modules automatically at the beginning, to remove and at the end to install, with this commands installs the DKMS modules twice, one with your scipt, named fglrx that fails sometimes and the automatic pacman, named fglrx-15.12 that works fine, could you check it?

rg_arc commented on 2016-05-12 16:48

@Vi0L0 Good deal. As always keep up the good work, I'll stick around.

Vi0L0 commented on 2016-05-12 16:22

definitelly not too old, phoronix said that it might be soon supported by amdgpu:
For now use radeon, it should be good and stable.

rg_arc commented on 2016-05-12 15:02

@Vi0L0 I've used the open sourced one before as well and I think there was something minor that annoyed me, I can't remember at the moment. This is my current GPU: is this under the "too old" category?

Vi0L0 commented on 2016-05-12 12:54

I keep switching from one to another. It's both safe and easy :). In fact I think that everyone should check out both.
Cs:go should work well on open driver, thought on mine 290x it's more fluid on fglrx.
For older cards pick up radeon, for newer amdgpu, it's all in the wiki.
For open I personally preffer lordheavy's [mesa-git] repo which comes with the newest git drivers + linux-mainline kernel (also availabe on miffe's repo).
BTW: just a note, you can always have linux-lts installed next to linux and switch between them, don't have to downgrade
Edit: and no, I heven't seen such wallhack glitches on open drivers.

rg_arc commented on 2016-05-12 12:17

@Vi0L0 I hate to ask, but would it be safe to say switching over to the open sourced driver would fix this issue? I'm not downgrading my kernel for CS:GO.

Vi0L0 commented on 2016-05-12 11:50

it doesn't solve this issue at all. It's still there for both 4.5 and 4.6. For now I don't know how to fix it.
The only workaround for now is to use kernel < 4.5, in example linux-lts (now in 4.4).

All comments