Package Details: catalyst-dkms 15.9-17

Git Clone URL: https://aur.archlinux.org/catalyst-dkms.git (read-only)
Package Base: catalyst-dkms
Description: AMD/ATI drivers AKA Crimson. Sources to build fglrx module on DKMS.
Upstream URL: http://www.amd.com
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-generator, catalyst-hook, catalyst-test
Provides: catalyst=15.9
Submitter: maxqia
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 2
Popularity: 0.000253
First Submitted: 2016-05-08 22:07
Last Updated: 2017-10-16 20:31

Dependencies (10)

Required by (3)

Sources (22)

Latest Comments

radialhat commented on 2017-10-11 20:07

So here's what I've done to make it work:
I've cloned the git repository of the catalyst-dkms and changed the PKGBUILD to ignore the linux (kernel) pkg. IgnorePKG = linux and built it on the lts-kernel (4.9) I then installed the catalyst-total package through yaourt.

Thanks for all your help Vi0L0

Vi0L0 commented on 2017-10-11 17:19

also since you are on radeon 6k when using catalyst-test you should edit PKGBUILD and change this switch:

_old_control=n
to
_old_control=y

or maybe it would be safer to get back to catalyst-total which should support your gpu out of the box

Vi0L0 commented on 2017-10-11 17:12

I have following blacklists:
cat /etc/modprobe.d/blacklist.conf
blacklist radeon
blacklist amdgpu
blacklist kms
blacklist drm_kms_helper

The system on which I'm testing is very fresh, and its working pretty good, so should your. I have same kernel, yet your is catching some nasty things in dmesg, mine is clean.

Try to prepare xorg.conf, at least the basic one:
cat /etc/X11/xorg.conf.d/20-fglrx.conf
Section "Device"
Identifier "Radeon"
Driver "fglrx"
EndSection

Turn off desktop manager from autostart, reboot, as root:
modprobe fglrx
prompt in new line means it's fine. check if there are errors in dmesg
then try to startx
check output, also look at journalctl -b
plus maybe /var/log/Xorg.0.log

How to test if catalyst-test works... hmm... if you are able to load fglrx module and start x - it almost works ;P, if you have acceleration in x - it works

basic command to check opengl acceleration:
glxinfo | grep -i opengl
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon R9 200 Series
OpenGL core profile version string: 4.5.13399 Core Profile Context 15.302
OpenGL core profile shading language version string: 4.40
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.13399 Compatibility Profile Context 15.302
OpenGL shading language version string: 4.40
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:

where's glxinfo?
pkgfile -s glxinfo
extra/mesa-demos

also - there are some problems with some desktop managers, but sddm should work out of the box, if you want gdm you have to disable its default wayland
to use gnome you need modified packages ie from [catalyst] repository
again plasma/kde should work out of the box

radialhat commented on 2017-10-11 13:48

Answering to your questions:
I'm on x86_64 with xorg-server 1.17.4-2 with mesa-noglvnd installed (lib32 one is not installed though)

I have "options nomodeset" on my systemdboot conf and "blacklist radeon" under "/etc/modprobe.d/modprobe.conf"

How would one normally test if catalyst-test works?

No, it's a desktop, my specs are as follows:
Phenom II x4 955 on a M5A97 Evo Board - 8GB Gskills
GPU: Sapphire HD6850

Vi0L0 commented on 2017-10-11 13:23

uuuUUUuu... it doesn't look good.
Are you on x86_64 with xorg-server 1.17 and mesa-noglvnd installed?
Did you remember to add nomodeset and blacklist radeon and amdgpu modules? probably also blacklisting kms-related modules would be a good idea.

If you checked everything above, can you also check if catalyst-test is working?

Do you have some hybrid graphics maybe, with additional intel gpu, like powerXpress? - this could be a problem

radialhat commented on 2017-10-11 11:55

@Vi0L0 I've successfully installed catalyst-total on my system. There is although something preventing X from starting up, I've pasted the 'dmesg' trace here: https://pastebin.com/Z6XDLtFV - "WARNING: kernel stack frame pointer at ffffa2008167ba48 in Xorg:464 has bad value ffff8d5af3d78000" That's one of the lines that caught my attention.

EDIT: On kernel 4.13.5-1

radialhat commented on 2017-10-11 10:23

Thank you for your prompt response Vi0L0

Vi0L0 commented on 2017-10-11 10:17

You are missing linux kernel. This dependency is hardcoded in PKGBUILD.
I won't move this dependency because a lot of people was asking for it time ago, but you can change it mannually to linux-lts.

plus feel free to switch to catalyst-test or catalyst-total, they are working fine with kernel 4.13, soon I will also update this one to work with newer kernel.

If you still want to use catalyst-dkms and have linux kernel installed - then you have to disable linux pacage from upgrade with IgnorePkg (if i recall correctly) in /etc/pacman.conf

radialhat commented on 2017-10-11 10:09

I've switched kernels from 4.13 to lts and while "uname -a" outputs "4.9.54-1-lts" trying to install catalyst-dkms yields the message "cannot resolve "linux<4.13", a dependency of "catalyst-dkms".

What am I missing here?

maxqia commented on 2016-08-24 05:03

Made Vi0L0 maintainer because I don't currently use an amd gpu. Have Fun :P

All comments