Package Details: catalyst-test 15.12-11

Git Clone URL: https://aur.archlinux.org/catalyst-test.git (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: http://www.amd.com
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-hook, catalyst-utils, 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, libgl, libtxc_dxtn, mesa-libgl, mesa-libgl-git, opencl-catalyst=15.12
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 167
Popularity: 0.033944
First Submitted: 2010-02-17 20:49
Last Updated: 2016-12-06 21:01

Dependencies (22)

Required by (637)

Sources (26)

  • 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
  • 4.7-arch-cpu_has_pge-v2.patch
  • arch-fglrx-authatieventsd_new.patch
  • ati-powermode.sh
  • atieventsd.service
  • atieventsd.sh
  • catalyst.conf
  • catalyst.sh
  • crimson_i686_xg.patch
  • dkms.conf
  • fglrx_gpl_symbol.patch
  • grsec_arch.patch
  • http://www2.ati.com/drivers/linux/radeon-crimson-15.12-15.302-151217a-297685e.zip
  • lano1106_fglrx_intel_iommu.patch
  • lano1106_kcl_agp_13_4.patch
  • lib32-catalyst.sh
  • 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-12-07 18:24

interesting - after compiling imagemagick (6.9.6-7 version as 6.9.6-6 is unavailable) with disable-opencl configure option CPU spikes are gone...
I believe it's general problem, not just mine. Can someone confirm CPU usage spikes on default imagemagick @ GNOME?

Vi0L0 commented on 2016-12-06 21:14

thanks npfeiler, I used your patch
I hope it will work fine with non-catalyst libOpenCL - my short testing of running and compiling simple opencl apps showed it's fine.
If you will notice bad behaviour - let me know asap please.

For now I noticed one bug, but it was there before changes: converter (a bin which comes with imagemagick package) is taking a lot of my CPU resources - every seconds its eating 100% CPU, causing spikes on system's monitor ;P. It does look terrible and for now I don't know how to fix it, can somebody confirm bug?

If on upate process installer will tell something about missing libcl, then force install of catalyst-test with pacman -Udd /path-to_catalyst-test, and then additionally install ocl-icd

Within days (maybe tomorrow) I should update repos with this newer non-libcl version of catalyst.

Vi0L0 commented on 2016-12-05 15:01

thanks for the headup guys, i will look at it after getting out of my medical treatment, will update propably tomorrow

Morn commented on 2016-12-05 11:48

@npfeiler: Imagemagick is required by CUPS, so I think Violo should fix this clash in the PKGBUILD. I think most Arch installs use CUPS for printing, so this problem literally affects 99% of Arch computers.

npfeiler commented on 2016-12-04 17:13

i used the following patch to make it work with ocl-icd
http://pastebin.com/zKtQXmw6

Morn commented on 2016-12-04 12:37

There is a conflict now with the new ocl-icd package in extra, which is required by imagemagick among others. Looks like /usr/lib/libOpenCL.so is the problem.

DOobR commented on 2016-11-05 14:19

How should i satisfy xorg < 1.18.0 dependency if currently i have 1.18 xorg-server?

Vi0L0 commented on 2016-10-20 19:21

Sorry mate, no way you can see update for this pkg in pacman.
But if you want see such updates then feel free to use [catalyst] repo

mikaelbrun commented on 2016-10-20 16:10

I have been using yaourt all the time. (yaourt -S catalyst-test)
I ran yaourt -Sau now, and some updates came up.

But I am shure I have seen some catalyst update some times using pacman, is it only the drivers/catalyst-software that is beeing updated and not the package?

I'm learing everyday :-)
(this is not the right place to discuss this, I know, but it came up)

Vi0L0 commented on 2016-10-20 16:03

pacman is a package manager, so it knows all packages which were installed on your system, doesn't matter if they came from official repos or unofficial repos or if they were created locally from any source (including AUR). But pacman is unable to update locally created packages (including AUR) on its own, and it's logical as pacman is not able to create a package, it only works on packages which are already built. AUR only brings scheme on how to build package. But pacman on its own doesn't know how to build package from this scheme. You probably used some aur helper [1] to build catalyst-test package, some of them are able to update packages, but pacman is not and won't be able to do it (though it can see catalyst-test package which you created some time ago, and see it's dependencies - that's why it's not allowing you to update kernel).
[1] https://wiki.archlinux.org/index.php/AUR_helpers

All comments