Package Details: catalyst-total-hd234k 13.1-42

Git Clone URL: https://aur.archlinux.org/catalyst-total-hd234k.git (read-only)
Package Base: catalyst-total-hd234k
Description: AMD/ATI legacy drivers. catalyst-dkms+ catalyst-utils + lib32-catalyst-utils
Upstream URL: https://www.amd.com
Licenses: custom
Conflicts: catalyst, catalyst-daemon, catalyst-dkms, catalyst-generator, catalyst-test, catalyst-utils, libegl, libgl, libgles, libglvnd, mesa-libgl, mesa-libgl-git, nvidia, nvidia-utils, opencl-amd, xf86-video-ati, xf86-video-radeonhd
Provides: catalyst=13.1, catalyst-dkms=13.1, catalyst-libgl=13.1, catalyst-utils=13.1, dri, libatical=13.1, libegl, libgl, libgles, libtxc_dxtn, opencl-catalyst=13.1, opencl-driver
Submitter: Vi0L0
Maintainer: Vi0L0
Last Packager: Vi0L0
Votes: 34
Popularity: 0.000004
First Submitted: 2012-06-12 16:59
Last Updated: 2018-04-29 16:55

Dependencies (23)

Required by (728)

Sources (35)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

Vi0L0 commented on 2017-04-02 16:41

@AwesomeHaircut: also did this package work for you?
I'm asking because I don't have confirmation.
Also please note that to run it in post-libglvnd era you have to use pre-libglvnd mesa's packages, you can find it ie in [catalyst] repo.
I am planning to also paste it in [catalyst-hd234k] repo
Edit: I also created non-libglvnd packages: mesa-noglvnd and lib32-mesa-noglvnd groups
[1]https://aur.archlinux.org/pkgbase/mesa-noglvnd/
[2]https://aur.archlinux.org/pkgbase/lib32-mesa-noglvnd/
(tho on AUR it comes with *mesa-libgl* packages which should be avoid by catalyst users, I left it there for package base to be more "general")

Vi0L0 commented on 2017-04-02 16:38

@AwesomeHaircut: you are right, thanks.
I don't know where this *** came from...
Anyhow should be fine now

AwesomeHaircut commented on 2017-03-30 13:24

I think you forgot to add "hd234k" (or some other change) at the end of these two changes in build() in your last commit :

+ patch -Np1 -i ../4.9_over_4.6-arch-get_user_pages_remote.patch
+ patch -Np1 -i ../4.10-arch-sling00-virtual_address-acpi_get_table_with_size.patch

I kept getting file missing when using makepkg -s

patch: **** Can't open patch file ../4.9_over_4.6-arch-get_user_pages_remote.patch : No such file or directory

I have to append hd234k so that it can build.

Vi0L0 commented on 2017-03-04 18:14

I was able to succesfully compile module on 4.10.1 kernel with this new patch.
Can't promise if it will really work, I'm afraid that it needs general rewrite and not some simple patches...

ElNinijo commented on 2016-12-12 21:55

Vi0L0 any version kernel from 4.8 brick my X-Server. I have to back to 4.7 version kernel

Vi0L0 commented on 2016-12-12 20:05

-39 update is fixing libcl/opencl-icd-loader dependencies

@ElNinijo: did you also check some early 4.8 kernel like 4.8.1?

I'm not sure if we could jump it around without bisecting kernel code, but who would find time for this? anybody? ;)

ElNinijo commented on 2016-12-02 16:04

Hi Vi0L0

I have the same problem like @Moggele
When I install kernel from 4.8.x line my Xserver freeze but when i back to 4.7.x everything is perfect

Vi0L0 commented on 2016-11-24 16:52

was it working on previous kernel of 4.8 line?

Moggele commented on 2016-11-23 12:34

I have an [AMD/ATI] R700 [Radeon HD 4850 X2] have installed the new kernel 4.8.10 fglrx Compiles but if i try to run XServer the whole system freez. I get no errors in Xorg or by loading the Kernel Module i switched back to the LTS kernel evering worked fine

Megameneer commented on 2016-09-07 13:56

I am using an ATI Radeon 4650. I used the technique described in the Arch wiki: running this script:
#!/bin/sh
DRIVER=/usr/lib/xorg/modules/drivers/fglrx_drv.so
for x in $(objdump -d $DRIVER|awk '/call/&&/EnableLogo/{print "\\x"$2"\\x"$3"\\x"$4"\\x"$5"\\x"$6}'); do
sed -i "s/$x/\x90\x90\x90\x90\x90/g" $DRIVER
done

I haven't tried to use a different control file. I could do that if I find the time for it: the control files older than 13.1 are quite hard to find.
I also have to say that aticonfig --initial didn't work for me. But the driver works fine without running it, except for the Unsupported hardware logo of course.