Package Details: lib32-vulkan-amdgpu-pro 24.20_2044449-1

Git Clone URL: https://aur.archlinux.org/amdgpu-pro-installer.git (read-only, click to copy)
Package Base: amdgpu-pro-installer
Description: AMDGPU Pro Vulkan driver (32-bit)
Upstream URL: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-22-40
Licenses: custom: AMDGPU-PRO EULA
Groups: Radeon_Software_for_Linux
Provides: lib32-vulkan-driver
Submitter: LEW21
Maintainer: Ashark (mesmer)
Last Packager: mesmer
Votes: 125
Popularity: 0.59
First Submitted: 2016-03-28 22:44 (UTC)
Last Updated: 2024-12-11 23:16 (UTC)

Dependencies (4)

Required by (3)

Sources (18)

Pinned Comments

mesmer commented on 2022-12-23 04:31 (UTC) (edited on 2023-05-28 19:28 (UTC) by mesmer)

IF PROBLEM HAPPEN

this package is our try to put amdgpu in ARCH, but this could break or have problems as amd update and change their packages for ubuntu

if anything happens you can always download a older tag in https://github.com/Ashark/archlinux-amdgpu-pro/releases and get the PKGBUILD there, and use makepkg with that build while we update or try to fix :)

ALWAYS USE LINUX-FIRMWARE-GIT IF LATEST DRIVER FAIL BEFORE ISSUE SOME ERROR

https://aur.archlinux.org/packages/linux-firmware-git

Ashark commented on 2019-12-09 20:52 (UTC) (edited on 2022-12-06 08:45 (UTC) by Ashark)

PKGBUILD generator is located here: https://github.com/Ashark/archlinux-amdgpu-pro

AMDGPU PRO wiki page: https://wiki.archlinux.org/index.php/AMDGPU_PRO

New versions will appear here: https://repo.radeon.com/amdgpu/.

Latest Comments

« First ‹ Previous 1 .. 39 40 41 42 43 44 45 46 47 48 49 .. 60 Next › Last »

parkerlreed commented on 2016-12-23 03:45 (UTC)

@nmset Is there a reason 16.50 is not part of the main AUR package yet?

nmset commented on 2016-12-21 15:01 (UTC)

@DarenK : You should not be having this error with 16.50 and http://pastebin.com/Pfsirxtb Good luck.

disc-kuraudo commented on 2016-12-21 14:42 (UTC)

When installing I'm getting this: :: amdgpu-pro-libopencl-dev and ocl-icd are in conflict (libcl). Remove ocl-icd? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: imagemagick: removing ocl-icd breaks dependency 'opencl-icd-loader' It doesn't replace the opencl libraries needed by imagemagick, any solution?

libcg commented on 2016-12-18 08:40 (UTC)

I would be interested in maintaining the DKMS part. I'll try to get the 16.50 driver rolling soon. My goal is to get the Vulkan and OpenCL drivers working along with Mesa. @Corngood could you make this package orphan? Thanks.

viennaa commented on 2016-12-15 12:25 (UTC)

@Muxoid add --ignore ocl-icd to pacman command

Muxoid commented on 2016-12-14 23:07 (UTC)

:: ocl-icd and amdgpu-pro-libopencl-dev are in conflict (libcl)

nmset commented on 2016-12-12 21:50 (UTC)

@adb : No, I don't intend to be a maintainer of this package. I just wished to share what I did to get to work what AMD releases. It would be nice that you fork to a clean package.

adb commented on 2016-12-12 20:59 (UTC)

@nmset: Are you planning to take the role of a maintainer for this package? I was going to fork the repo and have a go at patching it for 16.50, with what we have so far.

tpruvot commented on 2016-12-11 19:53 (UTC)

Look like AMD remove all older drivers packages, real pain to find a mirror. For OpenCL, the last stable for me is the libamdocl64.so from 16.30 (16.40 is unstable) and the first 16.50 which use Clang 3.9 seems.. different. Else, well this first 16.50 kernel module is not proper imo.. lot of warnings, some reggressions in kernel backports (ttm) The encountered OpenCL problems can be reproduced on Windows too. For now i use all the latest stuff with the old ocl64 lib which seems to work fine. Another thing, the new RHEL 7.2 installer seems closer to ARCH (and Slackware) paths, it uses lib64 style for the libraries.

nmset commented on 2016-12-11 08:44 (UTC)

@marcio : Your Xorg log says KMS is not being used. You should check that your boot command line does not have any KMS inhibitors like 'nomodeset'. Don't use any xorg.conf file neither. That's all I can say.