Package Details: catalyst-hook 15.9-20

Git Clone URL: (read-only)
Package Base: catalyst-hook
Description: AMD/ATI drivers. Auto re-compile fglrx module while shutdown/reboot.
Upstream URL:
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-test
Provides: catalyst=15.9
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 96
Popularity: 0.000003
First Submitted: 2010-09-15 17:45
Last Updated: 2018-04-29 16:33

Dependencies (9)

Required by (3)

Sources (26)

Latest Comments

Vi0L0 commented on 2017-04-03 13:32

package dependency is rather clear: linux<4.11
package comes with patches for 4.10 kernel. It should work fine, not sure about switchable graphics thought - it has been long time since I saw note on this topic.

Also, if you are already using dkms it could be better to use catalyst-dkms package instead of this one.

Just be sure to switch from mesa to mesa-noglvnd, or use [catalyst]/[catalyst-stable] repo, beacuse libglvnd patches have broken catalyst's support.

doria90 commented on 2017-04-03 13:17

New to Arch, been using Antergos to make the transition easy.
I've been trying to get my Radeon HD 8x switchable graphics card to work but it appears that the kernel is at 4.10 while the package is limited to < 4.7.
Is there anything I can do to make this work?

Vi0L0 commented on 2016-10-03 18:52

it is, but it's domain name has changed, was, is

simplykaka commented on 2016-10-03 15:21

Is the mirror($arch) working?

Vi0L0 commented on 2016-08-20 23:51

Atm I'm unable to update wirephire mirror. Don't know when I will get access back.
Please use hactar mirror:
Server =$arch

Dornith commented on 2016-08-20 20:58

Is the Catalyst repo up to date? Pacman says my current is up to date with the repo but it won't let me install linux 4.7 because of dependency conflicts.

Vi0L0 commented on 2016-03-23 21:24

been using 4.5 kernel since rc5 on catalyst, but decided to make some game testing before commiting 4.5 support.
There was no problems except for cs:go which generates some glitches - missing walls :), it could be used as a wallhack, literally, not sure if it is bug or a feature :P. Occures on catalyst 15.9 and 15.12, catalyst-firepro works well.
So if you dont like this bug (could be that im the only one touched by problem) use older linux 4.4 or linux-lts or mentioned catalyst-firepro

Vi0L0 commented on 2016-01-20 14:27

- added 4.4 kernel support

Vi0L0 commented on 2015-12-13 19:56

just like commit says:
- adding new patch from crimson
- removing gcc49 dependency
- adding initial grsec kernel support

should be safe to remove gcc49 pkg :)

Vi0L0 commented on 2015-09-29 20:29

updated to 15.9
4.2 kernel is in [core] and we still don't have support for it.
So for now please use linux-lts kernel.

be aware that I removed linux from dependency array and so it will let linux to update (while it's not supported tongue), if you will not configure bootloader to use kernel older than 4.2, like linux-lts, it will probably boot linux and you will probably gonna see a freeze or blank screen. System should work though, you can ssh to it and config bootloader from here, or use single mode if you can't ssh, or well there's possibility that linux-lts was added before, boot it and config as default kernel to boot.

beroal commented on 2015-08-22 11:40

@Vi0L0: would you be so kind as to update your repository ?

Vi0L0 commented on 2015-08-21 09:32

It supports linux 4.1.
Latelly I started to work on linux 4.2 support but I have problems...

beroal commented on 2015-08-21 08:36

What about "linux 4.1"? Should I downgrade the kernel or wait when Vi0L0 will fix this package?

kox commented on 2015-07-17 07:07

Hello, I use your drivers from catalyst-hd234k and it seems catalyst hook doesn't support linux>=4.1
I can't upgrade my system:
error: failed to prepare transaction (could not satisfy dependencies)
:: catalyst-hook: requires linux<4.1

Vi0L0 commented on 2015-06-04 13:20

updated to 15.5-1 - AKA "nothing interesting":
- it doesn't support xserver 1.17
- looks older than ubuntu vivid driver which we are using ie in catalyst-test@AUR
- i've added initial support for 4.1 kernel (using kolasa's patch, tested on 4.1rc5)
- rel notes:

Vi0L0 commented on 2015-05-04 19:23

- 4.0 kernel support (thanks to kolasa for patch)

Vi0L0 commented on 2015-03-08 13:31

- using kolasa's patch to cover 3.19 kernel support

JoZ3 commented on 2014-10-05 23:51

Thanks for your help, I use Manjaro, the problem is that when updating the catlyst-ustils from AUR deleted me Manjaro basic components, then I'll wait for the Manjaro update to continue using these because I had gotten used to using the kernel ck :(

Vi0L0 commented on 2014-10-05 21:00

Log is pretty clear:

[ 10.859] (WW) fglrx(0): Kernel Module version does *not* match driver.
[ 10.859] (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work

Looks like you didn't update catalyst-utils package (btw ever think about using catalyst-total package? or catalyst-test if wants some beta testing?), because log claims that ie:

[ 10.407] (II) Loading /usr/lib/xorg/modules/drivers/
[ 10.449] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[ 10.449] compiled for, module version = 14.10.2

while should be:
[ 2.591] (II) Loading /usr/lib/xorg/modules/drivers/
[ 2.619] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[ 2.619] compiled for, module version = 14.30.4

JoZ3 commented on 2014-10-05 19:46

Hi, the kernel modules was build, I ran

systemctl enable catalyst-hook
systemctl start catalyst-hook

and late:

catalyst_build_module all

I try all over again to have the Xorg.0.log file:

Vi0L0 commented on 2014-10-05 09:46

Maybe kernel module wasn't build? Have you enabled automatic recompilation with:
systemctl enable catalyst-hook
systemctl start catalyst-hook
You can also build modules manually after every kernel update with:
catalyst_build_module all
I recommand to run it this time and if there's an error paste the error log here.

If there's no compilation error and X didn't start then maybe you will be able to get /var/log/Xorg.0.log ?
Normally there's no problem with logging to tty, even if X failed (maybe you got some problem in systemd?). Check if you will be able to login after disabling your DM/X from autostart.
You should now be able to login an start DM/X manually - if it will fail and you won't be able to get back to tty, reboot the machine (ie. in safe way via ssh), Xorg.0.log should be there with an error.

JoZ3 commented on 2014-10-05 06:46

Hello, I've installed the kernel 3.16.2 and kernel ck 3.16.3 ck without any problem, but after reboot, after the grub, the console appears blinking constantly and it is impossible to enter a username. The xserver 1.15.2

The above version working flawless

Vi0L0 commented on 2014-10-04 18:08

advice: the more details you will give in the bug report the more professional it will look

JoZ3 commented on 2014-10-04 14:42

Unfortunately does not work for the kernel 3.16...

Vi0L0 commented on 2014-10-03 20:55

updated to 14.9-1:
- official, stable release

- it doesn't support xserver 1.16

- I added my fresh patch for kernel 3.17 rc6.
Notes about the patch:
1. it probably wont work on 3.17 kernels older than rc6 because I don't know how to tell preprocessor about rc version :P
2. im unable to test resume/suspend
3. im not the developer, just pressing random keys :P so the patch could be less/more noobish :-)

Vi0L0 commented on 2014-08-18 18:36

14.4-23: added dirty GPL-licensing solution - fglrx_gpl_symbol.patch - workaround for compilation error for i686 on 3.16.1 kernel

Vi0L0 commented on 2014-08-17 14:55

14.4-22: just a pkgrel bump to confirm 3.16 kernel support

Vi0L0 commented on 2014-06-09 20:40

14.4-21: just a pkgrel bump to confirm 3.15 kernel support

Vi0L0 commented on 2014-05-25 11:34

updated to 14.4-20 (catalyst 14.4 rev2):
- which brings some fixes for Witcher 2

Vi0L0 commented on 2014-05-01 19:22

There's a bug in linux 3.14.2:

Temporary workaround is to downgrade linux and linux-headers to 3.14.1 or use gcc from [testing]. The first solution should be imho safer. You can find 3.14.1 at arm:



Vi0L0 commented on 2014-04-28 20:32

updated to 14.4-10, catalyst 14.4 stable:
- xserver 1.15 support
(gotjazz wrote: little warning though - if you use xbmc, get sdl-nobackingstore from the AUR or you'll have tearing during video playback with xorg 1.15)
- many fixes here and there

Vi0L0 commented on 2014-04-05 11:24

added Cold's 3.14 patch

Vi0L0 commented on 2013-12-24 08:49

Let me just copy-paste:
I'm AFK and will so be till saturday.
In case of problems please write on bar and grill thread. If no one will help and there's some serious bug - please write the bug report on bugzilla.

Meanwhile you can still use archive repos like ones for 13.4 and 13.11-beta94:
[catalyst-stable-13.4] and [catalyst-13.11-beta94]
Server's URLs are like on the wiki for [catalyst].

Or build pkgs on your own basing on archive tarballs (use newest ver):

As for the xserver 1.14 - yes, you can safely switch to it. If you are using xvba/vaapi and will notice problems with it (some people noticed problems but it's not the general rule) you can always downgrade to xserver 1.13

harrim4n commented on 2013-12-23 00:35

Is it somehow possible to downgrade to 13.4? 13.12 is giving me a few issues, but I can't find the old package for catalyst-hook. It managed to download the 13.4 binary from the ATI page, but I'm not sure if I should just install it manually.
Also, is it safe to upgrade to Xorg 1.14 with the 13.12 catalyst?

Vi0L0 commented on 2013-12-19 21:45

- AMD marked it as stable, so am I...

@veox: who said you need linux package?

veox commented on 2013-12-18 15:39

Should depend on `linux-headers`, otherwise:

Kernel header files are absent: directory /usr/lib/modules/3.12.5-1-ARCH/build doesn't exist! Game over

Vi0L0 commented on 2013-11-18 19:38

silent update, no pkgrel bump:
- thanks to zoopp and his referer we no longer have to download installer manually :)

Vi0L0 commented on 2013-11-17 19:56

amd's site is not allowing direct download anymore...
read the top of PKGBUILD for instructions.

harrim4n commented on 2013-11-15 17:25

Update failes with: ==> ERROR: One or more files did not pass the validity check!

==> Validating source files with md5sums... ... FAILED
hook-fglrx ... Passed
catalyst_build_module ... Passed ... Passed
makefile_compat.patch ... Passed
catalyst-hook.service ... Passed
gentoo_linux-3.10-proc.diff ... Passed
kolasa_fglrx_fixing_ttys.patch ... Passed
lano1106_fglrx_intel_iommu.patch ... Passed
lano1106_kcl_agp_13_4.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build catalyst-hook.
==> Restart building catalyst-hook ? [y/N]

Vi0L0 commented on 2013-11-08 19:11

- added workaround to bring support of kernel 3.12, by Krzysztof Kolasa

Vi0L0 commented on 2013-10-27 18:35

upgraded to 13.4-15:
- added staticlibs and libtool to the options and it fixed the whole libfglrx_ip.a bug
- the package is a lot bigger because I added !strip to the options, it's leaving symbols in the libraries so the package (and libs themselves) are bigger - but it could be useful, especially in some debugging

Vi0L0 commented on 2013-09-19 19:23

guys, 13.9 has memory leak, it's not stable at all.
AMD could say otherwise but don't listen to them :P

you will find 13.9 at catalyst-test and catalyst-test-pxp @ AUR,
and maybe tomorrow on the [catalyst] repo

SuperBo commented on 2013-09-19 06:40

Catalyst 13.9 official released, now support x.Org 1.14

ckozler commented on 2013-08-26 17:06

Thanks Vi0L0 - for some reason I could not get Catalyst-hook to work with my system but the regular Catalyst did. I may give it another shot but I spent a couple hours to no avail and I just kept segfaulting when starting X

Vi0L0 commented on 2013-08-17 10:32

Yes, you should remove it.
After installing catalyst-hook you won't need catalyst at all.

ckozler commented on 2013-08-15 23:12

Hi -

Does that imply even if we have catalyst and install this that catalyst will be in conflict and we should remove it?

$ >> sudo pacman -U catalyst-hook-13.4-13-x86_64.pkg.tar.xz
[sudo] password for ckozler:
loading packages...
resolving dependencies...
looking for inter-conflicts...
:: catalyst-hook and catalyst are in conflict. Remove catalyst? [y/N]

Vi0L0 commented on 2013-08-11 11:01

Every catalyst-hook version is different because amd's source files (and community patches) which are building it are different - it's not only a "method" of building the modules.
catalyst-hook as a component of catalyst-total-hd234k is completelly different than this catalyst-hook, that's why it's in conflict.

lockheed commented on 2013-08-10 12:14

Why is it that when I try to install catalyst-total-hd234k, it removes this package? Is automatic kernel rebuilding unavailable on anything else than regular catalyst?

Vi0L0 commented on 2013-08-03 13:52

updated to 13.4-13 :
- switching to 3.10 kernel patch of Emil Karlson from gentoo which is genereting correct proc entries

Vi0L0 commented on 2013-07-07 19:28

updated to 13.4-5:
- using kolasa' workaround to bring 3.10 kernel support

Vi0L0 commented on 2013-05-21 15:56

updated to 13.4-3:
- fixes efi support and so ttys bug (thanks to Krzysztof Kolasa ::
- fixes support of intel's iommu (thanks to lano1106)

Anonymous comment on 2013-05-15 04:14

FVDI is last generation diagnostic interface for vehicles and trucks
produced from our company. It works the same as AVDI(ABRITES Vehicle Diagnostic Interface).
Currently FVDI is distributed with following diagnostic software:
1. ABRITES Commander for VAG - VW, Audi, Seat, Skoda
2. ABRITES Commander for Porsche
3. ABRITES Commander for Mercedes/Smart/Maybach
5. ABRITES Commander for BMW
6. ABRITES Commander for Peugeot/Citroen
7. ABRITES Commander for Fiat/Alfa/Lancia
8. Abrites Commander for Renault
9. Abrites Commander for Toyota/Lexus
10. Abrites Commander for Hyundai/KIA
11. Abrites Commander for Nissan/Infiniti
12. ABRITES TAG Key Tool
Welcome to

Anonymous comment on 2013-05-15 04:12

Welcome to

Vi0L0 commented on 2013-05-01 09:54

silent update, no pkg rel bump:
- added 'catalyst-dkms' into conflicts table

@abbradar: well... i'm still adding mkinitcpio hook while installing package (but not while updating), because still there are custom kernels for which it will work. But you can safely remove this hook with command: catalyst_build_module hookrm
Just don't forget to enable catalyst-hook service.

abbradar commented on 2013-04-28 10:12

Thanks for the answer. I have just used my own "catalyst-dkms" for long from times when "catalyst-hook" was mkinitcpio-based and I built and installed custom kernels frequently (so it was slow and painful to use), with custom service that allow me to use my old unsupported muxed PowerXpress and ensure that proper module gets loaded before X.

Vi0L0 commented on 2013-04-27 21:25

updated to 13.4-1:

- because dkms is not safe with it's fglrx compilation while system start, also: do we really need an extra package on the system and an extra dependency?

abbradar commented on 2013-04-27 10:20

Why don't reuse DKMS functionality? It does exactly the same thing as your service file. (maybe no re-compilation on shutdown)

Vi0L0 commented on 2013-04-21 17:36

little update:
removed Before from Service section of catalyst-hook.service

Vi0L0 commented on 2013-04-11 15:30

updated to 13.1-5:
fixing little "bug":

Vi0L0 commented on 2013-04-07 20:25

updated to 13.1-4:
fixing typo

Vi0L0 commented on 2013-04-07 14:31

updated to 13.1-3:
To enable 'automatic re-compilation while system shutdown/reboot' testing feature run these commands as root:
systemctl enable catalyst-hook
systemctl start catalyst-hook

More info here:

Vi0L0 commented on 2013-04-05 15:53

updated to 13.1-2:
SyncFirst was removed from the pacman 4.1 and so we can no longer force linux-headers to be installed in first place...

This mean that AUTOMATIC RE-COMPILATION WON'T WORK properly on kernels with separated headers

If you are using such kernel, like linux or linux-lts, you will have to run command like this:"
catalyst_build_module all
after linux update

Don't forget!

Vi0L0 commented on 2013-03-25 19:11

package has been once again updated, but silently, no pkgrel bump
because AMD has changed files that don't belong to this package, only catalyst-utils/total*

Vi0L0 commented on 2013-03-21 18:53

package has been updated, but silently, no pkgrel bump
because AMD has changed files that don't belong to this package, only catalyst-utils/total*

Vi0L0 commented on 2013-03-16 15:24

silent update, no pkgrel bump:
- i've cleaned up PKGBUILD and catalyst_build_module, from now on it supports only kernels build with proper extramodules support, tested on -ARCH, -ck, -lts and -mainline

Vi0L0 commented on 2013-01-18 14:50

updated to 13.1-1:
- changelog is here:
- i've added "testing" support for 3.8 kernel (through own patch)

Vi0L0 commented on 2012-07-14 19:56

12.6-3 should work fine with glibc 2.16.0-2 and kernel 3.5

Vi0L0 commented on 2012-06-16 12:44

updated to 12.4-6:
got now nice clean patch for 3.4 support on both architectures :)

thx to 3V0LU710N for finding it, and Sebastian Siebert from OpenSUSE for a patch

Vi0L0 commented on 2012-06-11 21:42

yes, i think that adding catalyst-lts into upcoming [catalyst-hd234k] repo would be a good idea

3V0LU710N commented on 2012-06-10 23:00

@Vi0L0: Thanks! Now my older i686 desktop machine is working again as expected! I had to use Linux-LTS for a while...

Btw, will you provide for unfortunate ATI <HD5xxx users (like me, ATM) a "Catalyst-LTS" package/repo?


Vi0L0 commented on 2012-06-10 19:29

should now work also on i686 with kernel 3.4

Vi0L0 commented on 2012-06-03 21:58

updated to 12.4-3:
- support of 3.4 kernel is now provided by other patch found here:
clean and kinda official :)

Vi0L0 commented on 2012-06-03 21:40

updated to 12.4-3:
- support of 3.4 kernel is now provided by other patch found here:
clean and kinda official :)

Vi0L0 commented on 2012-06-03 19:30

updated to 12.4-2:
- added dirt dirty support of 3.4 kernel (basing on w41ter's patches

Vi0L0 commented on 2012-06-03 19:22

updated to 12.4-2:
- added dirt dirty support of 3.4 kernel (basing on w41ter's patches

PhotonX commented on 2012-05-02 15:44

Thanks, in my case removing /lib/modules/extramodules-3.2-ARCH/ and rebuilding catalyst-hook and catalyst-utils did the trick.

Anonymous comment on 2012-05-02 12:42

Same problem here, resolved as follow:

(using a real root shell on any TTY)

1) uninstall catalyst-hook (pacman -R catalyst-hook, don't use -Rnsuc or other recursive method or your whole desktop environment will be dropped)
2) install libgl and answer yes when asked to remove catalyst-utils
3) uninstall xorg-server any xf86-video-* and xf86-input-* packages
4) updatedb
5) locate fglrx
6) delete all files and directories listed by locate command output
7) install xorg-server and any xf86-input-* previously removed from xorg111 repo
8) install catalyst-hook replacing libgl
9) check your configurations (MODULES in /etc/rc.conf, menu.lst ecc...)
10) check also your xorg.conf file
11) reboot

For me worked well, maybe i've left some orphan files from previous catalyst installation of official drivers.

PhotonX commented on 2012-04-28 06:31

Some more info.

Xorg.0.log reports:

[ 1620.030] (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
[ 1620.130] (EE) fglrx(0): XMM failed to open CMMQS connection.(EE) fglrx(0):
[ 1620.130] (EE) fglrx(0): XMM failed to initialize

/var/log/catalyst-install.log reports:

2012-04-28 08:13:12
Building fglrx module for 3.3.3-1-ARCH kernel ...
patching file Makefile
Hunk #1 succeeded at 68 (offset 2 lines).
patching file firegl_public.c
Hunk #1 succeeded at 5807 with fuzz 1 (offset 10 lines).
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /lib/modules/3.3.3-1-ARCH/build/include/generated/autoconf.h says: SMP=1
file /lib/modules/3.3.3-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /lib/modules/3.3.3-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory `/usr/src/linux-3.3.3-1-ARCH'
CC [M] /tmp/catalyst.0iHIZM/firegl_public.o
CC [M] /tmp/catalyst.0iHIZM/kcl_acpi.o
CC [M] /tmp/catalyst.0iHIZM/kcl_agp.o
CC [M] /tmp/catalyst.0iHIZM/kcl_debug.o
CC [M] /tmp/catalyst.0iHIZM/kcl_ioctl.o
CC [M] /tmp/catalyst.0iHIZM/kcl_io.o
CC [M] /tmp/catalyst.0iHIZM/kcl_pci.o
CC [M] /tmp/catalyst.0iHIZM/kcl_str.o
CC [M] /tmp/catalyst.0iHIZM/kcl_iommu.o
CC [M] /tmp/catalyst.0iHIZM/kcl.o
CC [M] /tmp/catalyst.0iHIZM/kcl_wait.o
LD [M] /tmp/catalyst.0iHIZM/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/catalyst.0iHIZM/fglrx.mod.o
LD [M] /tmp/catalyst.0iHIZM/fglrx.ko
make: Leaving directory `/usr/src/linux-3.3.3-1-ARCH'
cat: /lib/modules/extramodules-3.2-ARCH/version: No such file or directory

PhotonX commented on 2012-04-27 15:56

After the last update, fglrx stopped working:

$ lsmod | grep fglrx
fglrx 2818324 3
button 3614 1 fglrx
agpgart 22159 1 fglrx


$ fglrxinfo
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 136 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 15
Current serial number in output stream: 15

I tried to reinstall catalyst-hook, run aticonfig --initial and reboot, but the problem remains.

Anonymous comment on 2012-03-20 17:51

Works with Linux 3.3.... :D

Vi0L0 commented on 2011-09-29 18:24

11.9 sux ;P
downgraded to 11.8 :)

Anonymous comment on 2011-09-29 08:06

hello. I've a problem with the latest package 11.9.
While resize the KDE konsole, server X crash and inside the log i found these line:

[ 863.480] 0: /usr/bin/X (xorg_backtrace+0x26) [0x45e096]
[ 863.480] 1: /usr/bin/X (0x400000+0x62629) [0x462629]
[ 863.480] 2: /lib/ (0x7f7920f1f000+0xf800) [0x7f7920f2e800]
[ 863.480] Segmentation fault at address (nil)
[ 863.480]
Fatal server error:
[ 863.480] Caught signal 11 (Segmentation fault). Server aborting
[ 863.480]
[ 863.480]

and on the terminal appear:
BUG: scheduling while atomic: X/1862/0x00000002

The kernel version is the latest: 3.0-ARCH

I think is a problem related to this kernel and this package. Anyone can confirm this bug?

In this time for me is better to downgrade to the previous catalyst driver.

Thanks Vi0L0 for your support :)

Vi0L0 commented on 2011-07-10 21:40

@Scullder: it was fixed with last update, performed on 8th of July mainly because of new md5sum of ati drivers, it was silent (no pkgrel bump) update so you could miss it ;)

hcartiaux commented on 2011-07-10 17:47

Latest mkinitcpio reports a warning with your hook :
"==> WARNING: Hook 'fglrx' uses a deprecated 'install' function. This should be renamed 'build'"

Thanks :)

Anonymous comment on 2011-06-18 02:18

Blacklisting modules in rc.conf has been obsoleted and no longer works as of initscripts 2011.06.1-1. All blacklisting instructions need to be included in /etc/modprobe.d/.

Anonymous comment on 2011-06-18 02:08

Blacklisting modules in rc.conf has been obsoleted and no longer works as of initscripts 2011.06.1-1. All blacklisting instructions need to be included in /etc/modprobe.d/.

Vi0L0 commented on 2011-04-27 22:05

@oscarbachour: GNOME3 issues are well known, and can be fixed only by catalyst's devs :( - in other words "i have no idea when they will fix this", unfortunatelly...
On the other hand i can say that catalyst's developement is getting better.

Amdcccle is showing different catalyst's version:

Anonymous comment on 2011-04-27 19:23

Nice work, really quickly updated.

Some issues:
I'm using Gnome 3 and getting rainbowish top bar.
I'm also getting some strange flickering when switching between Activities view (top left corner) and Desktop view.
Catalyst Control Center reports Catalyst version 11.3 although pacman says 11.4 is installed.

Vi0L0 commented on 2011-03-29 21:34

edit: no, wait, my last advice is not complete ...
i should say: install both packages in same time or install catalyst-utils first without checking dependencies (usually with -d or -dd switch)

Vi0L0 commented on 2011-03-29 21:20

using same version of catalyst-utils and any other catalyst (like this catalyst-hook) package is highly recommended. After all they are built from the same ati's package.
It's hard to tell what kind of unwanted behaviour you may see if you decide to do otherwise - i guess that segmentation fault of X server is one of examples.

Actually catalyst-utils is a package which provides libraries and utils only, it doesn't compile anything, it's just building (copying files from ati's package), and does not really depend on any other catalyst package - ofcourse to make it work you still need some catalyst package which provides fglrx module.

Anyway if you don't want to see aur's manager (or makepkg) claiming about some dependencies - just update catalyst-utils first, and then catalyst-hook.

Anonymous comment on 2011-03-29 18:32

Catalyst-hook doesn't compile without catalyst-utils 11.3 and catalyst-utils doesn't compile without catalyst-hook 11.3 -.^
I removed the version check for catalyst-utils version 11.3 (I have 11.2 installed) and was able to build catalyst-hook 11.3.

Anonymous comment on 2011-02-28 06:33

Keep up the great work !

Vi0L0 commented on 2011-02-22 20:14

another silent update:
no_bkl.patch will be added when kernel's # CONFIG_BKL is not set
Removing BKL (Big Kernel Lock) is safe move in 2.6.38 kernel (tested on rc5 and rc6).

Vi0L0 commented on 2011-02-22 20:13

another silent update:
no_bkl.patch will be added when kernel's # CONFIG_BKL is not set
Removing BKL (Big Kernel Lock) is save in 2.6.38 kernel (tested on rc5 and rc6).

Vi0L0 commented on 2011-02-10 17:51

Silent update.
I didn't like the way how ati's code was cluttering PKGBUILDs or catalyst_build_module scripts, so i turned this code into file and import it's content with . (source)
New way also fits to ati license better... ;P
Oh and now all AUR catalyst's packages have 2.6.38 patch so they support 38 rc3, rc4 and probably newer rcs (no rc1, rc2 support, but hey rc3 and rc4 are much better).
Change is mainly cosmetical, there's no need to update packages.

OvsInc commented on 2011-01-27 08:53

O! Thanks.
Now I see...

Anonymous comment on 2011-01-27 08:03


The problem is that catalyst-hook package is supposed to recompile kernel module whether kernel package is updated, and it needs these devel packages to do so. They have to be present in the system in case when update occurs, not only for initial packaging.

OvsInc commented on 2011-01-27 07:13

Thanks fo the package.

Can you replase
depends=("catalyst-utils=${pkgver}" 'gcc-libs' 'gcc>4.0.0' 'make' 'patch')
depends=("catalyst-utils=${pkgver}" 'gcc-libs')
makedepends=('gcc>4.0.0' 'make' 'patch')

I think that gcc, make, patch is development packages and don`t needed for workng.

Anonymous comment on 2010-12-20 09:48

If i recompile the module after getting error, OpenGL it works after stopping kdm, unloading and reloading fglrx and restarting kdm. :| So... It seems to be a kernel module incompatibility :|

Anonymous comment on 2010-12-20 09:17

here is the log....

Anonymous comment on 2010-12-20 09:17

here is the log....

Vi0L0 commented on 2010-12-17 13:16

@zeld: is /var/log/catalyst-install.log containing some errors?

+ maybe running:
as root will help?

Anonymous comment on 2010-12-17 09:30

Hi :) i have a problem with this driver. For each reboot i've not the 3D acceleration and the Xorg.log.0 print me these error:

[ 15.143] Current Operating System: Linux Thor 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15.666] (II) Loading extension MIT-SCREEN-SAVER
[ 18.149] (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
[ 18.508] (EE) fglrx(0): XMM failed to open CMMQS connection.
[ 18.508] (EE) fglrx(0): XMM failed to initialize

no one got this problem?


Vi0L0 commented on 2010-12-13 22:52

Updated to 10.12

Thanks Rip-Rip, now i'm using your tip on almost all catalyst packages ;)

Anonymous comment on 2010-11-29 21:43

Hi, I think that the 9th line of catalyst_build_module should be changed to something like: file_patch="${kernver:0:6}.patch"
The file_path="${kernver/-*}.patch" doesn't handle kernel version like 2.6.31.x-MyKernel correctly, since it will try to find the that doesn't exist.

Vi0L0 commented on 2010-10-23 18:27

thanks, updated

like catalyst-test and catalyst 10.10 package - it's now using some lines from ati's file (check catalyst_build_module's ati_make function)

i'm not able to test it right, but on virtual x86_64 it's working fine

Inkaine commented on 2010-10-23 08:50

It's the missing makefile_compat.patch in the -hook and -daemon packages. Once this has been added, the module compiles flawlessly. The previous arch_compat.patch can also be safely removed. However simply replacing one with the other (simply renaming makefile_compat to arch_compat and changing the md5) does not work. I had to patch the makefile in the build section still to make it work.

So copy makefile_compat.patch into the build directory localy and add this to the PKGBUILD:



build() {
cd "${srcdir}/archive_files/"
patch -Np1 -i ../makefile_compat.patch || return 1

Inkaine commented on 2010-10-22 21:24

Can confirm that error too. Arch64 here also.

Anonymous comment on 2010-10-22 20:54

Module fglrx.ko can't be built.

This is the error message in /var/log/catalyst.log:

+ make -C /lib/modules/2.6.35-fbcondecor/build SUBDIRS=/tmp/catalyst.Nb0mDB ARCH=x86_64 modules
make: Entering directory `/usr/src/linux-2.6.35-fbcondecor'
CC [M] /tmp/catalyst.Nb0mDB/firegl_public.o
CC [M] /tmp/catalyst.Nb0mDB/kcl_acpi.o
CC [M] /tmp/catalyst.Nb0mDB/kcl_agp.o
CC [M] /tmp/catalyst.Nb0mDB/kcl_debug.o
CC [M] /tmp/catalyst.Nb0mDB/kcl_ioctl.o
/tmp/catalyst.Nb0mDB/kcl_ioctl.c: In function »KCL_IOCTL_AllocUserSpace32«:
/tmp/catalyst.Nb0mDB/kcl_ioctl.c:196:5: Error: implicit declaration of the function »COMPAT_ALLOC_USER_SPACE«
/tmp/catalyst.Nb0mDB/kcl_ioctl.c:196:24: Warning: initialization makes pointer from integer without a cast
make[1]: *** [/tmp/catalyst.Nb0mDB/kcl_ioctl.o] Error 1
make: *** [_module_/tmp/catalyst.Nb0mDB] Error 2
make: Leaving directory `/usr/src/linux-2.6.35-fbcondecor'
+ return 1

Vi0L0 commented on 2010-09-28 02:56

x86_64 kernel problem:

Vi0L0 commented on 2010-09-26 17:34

3->4 little update: just adding catalyst-generator to conflicts list

Vi0L0 commented on 2010-09-18 16:49


patch for x86_64 kernel that was patched with very important patch that fix some critical security hole

i've found patch here:
Thanks goes to aidanlinz

Vi0L0 commented on 2010-09-16 15:03

update: removing unneeded "if" from catalyst_build_module

Vi0L0 commented on 2010-09-16 01:16

More info here: