Package Details: catalyst-total 15.9-19

Git Clone URL: https://aur.archlinux.org/catalyst-total.git (read-only)
Package Base: catalyst-total
Description: AMD/ATI Catalyst drivers for linux. catalyst-dkms + catalyst-utils + lib32-catalyst-utils + experimental powerXpress suppport. Radeons HD 2 3 4 xxx ARE NOT SUPPORTED
Upstream URL: http://www.amd.com
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-hook, catalyst-utils, libegl, libgl, libgles, libglvnd, mesa-libgl, mesa-libgl-git, opencl-amd
Provides: catalyst=15.9, catalyst-hook=15.9, catalyst-libgl=15.9, catalyst-utils=15.9, dri, libatical=15.9, libegl, libgl, libgles, libtxc_dxtn, mesa-libgl, mesa-libgl-git, opencl-catalyst=15.9, opencl-driver
Submitter: None
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 130
Popularity: 0.129983
First Submitted: 2009-11-11 05:59
Last Updated: 2017-05-31 18:37

Dependencies (23)

Required by (677)

Sources (30)

Pinned Comments

Vi0L0 commented on 2017-03-11 18:21

ok, so for now I've added mesa packages of 17.0.1-1 version to [catalyst]* and [catalyst-stable] - simply copied from archive: https://archive.archlinux.org/packages/

Please downgrade if you updated mesa to -2 version.
After new version of mesa came out, I will build new mesa packages without glvnd support. Then I will most probably add new mesa package to aur. Will let know when it will happen

*
[catalyst]
Server = http://mirror.hactar.xyz/Vi0L0/catalyst/$arch

Latest Comments

parjanya commented on 2017-04-30 08:05

I had problems after upgrading the kernel, so I’ve installed the LTS instead and now, after some dependency conflicts, catalyst is working here. I had to uninstall lots of stuff, like wine. I’m trying to install wine, and it asks me to select which package to use for lib32-libgl, which I choose the lib32-catalyst-libgl one. Next it asks for the opengl-driver. It gave me just two options conflicting with catalyst, until I installed lib32-mesa-noglvnd. I was going to ask about this and solved as I tested and wrote this. Thanks! :)

slaecker commented on 2017-04-23 10:47

I get nothing but a black screen with white cursor where, posted on the forum: https://bbs.archlinux.org/viewtopic.php?id=225424

bolvarak commented on 2017-03-15 15:02

I was able to test for a bit with kernel 4.10, there are no errors in the Xorg.0.log nor the lightdm.log, however once the system starts up and LightDM launches it just sits there with a black screen and white blinking cursor. I have also blacklisted amdgpu

Vi0L0 commented on 2017-03-14 19:27

@Flowneee: it's easier to maintenance and save both you and me lot of network traffic and time ie. if I had to update fglrx to fit newer kernel I only had to update one small package like catalyst-dkms, not the whole big catalyst-total. Also you may not need opencl - because its in separate package, you don't have to install it.
These are pros of the repo.

Anyhow if you want all packages which catalyst-total brings, then you will have to install these packages from the repo (assuming you are x86_64 with multilib):
pacman -S catalyst-dkms catalyst-utils catalyst-libgl opencl-catalyst lib32-catalyst-utils lib32-catalyst-libgl lib32-opencl-catalyst

Flowneee commented on 2017-03-14 14:14

thanks Vi0L0, never knew about [catalyst] repo. But why there is no catalyst-total package in [catalyst] repo?

rtlnx commented on 2017-03-14 06:50

thanks Vi0L0
after blacklist amdgpu - it`s work

Vi0L0 commented on 2017-03-13 22:13

@rtlnx:
blacklist amdgpu:
# cat /etc/modprobe.d/blacklist.conf
blacklist amdgpu

edit: if that won't help you can also:
blacklist kms
blacklist drm_kms_helper

rtlnx commented on 2017-03-13 18:25

for me not work on kernel l4.10.1-1 and linux-lts (4.9.13-1)
switching to linux-lts 4.4.52-1-lts...

With new kernels i have error on boot(amdgpu)
*ERROR* VGACON disables amdgpu kernel modesetting.

Vi0L0 commented on 2017-03-12 17:35

it works fine (i mean as for fglrx ;P) here on 4.10.1-1-ARCH x86_64.

would you be able to brings some more info in a free time?

bolvarak commented on 2017-03-12 16:50

There seems to be some incompatibility with the 4.10.1-1 kernel. I wasn't able to debug as I needed my computer up and running, but switching to linux-lts (4.9.13-1) solved the issue. Just a heads up for anyone who hasn't updated in a while.

All comments