Package Details: 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
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: vulkan-driver
Submitter: LEW21
Maintainer: Ashark (mesmer)
Last Packager: mesmer
Votes: 125
Popularity: 0.65
First Submitted: 2016-03-28 22:44 (UTC)
Last Updated: 2024-12-11 23:16 (UTC)

Dependencies (4)

Required by (73)

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 .. 47 48 49 50 51 52 53 54 55 56 57 .. 60 Next › Last »

headkase commented on 2016-07-31 04:56 (UTC)

There is a serious issue with this package. When building anything from the AUR that requires OpenGL includes/headers at least with CMake it will fail because it can't find them. Confirmed with rbdoom and gzdoom.

headkase commented on 2016-07-29 03:37 (UTC)

I'm having issues launching XCOM 2 and Alien Isolation with AMDGPU Pro. Both launched previously without out it just using MESA's AMDGPU. Other Steam games work fine with Pro, XCOM 2 is the one I'd like to get working.

KillerByte commented on 2016-07-22 05:50 (UTC)

Never mind, turns out when it is trying to load amdgpu_dri.so, it does not seem to search the correct directory. I ended up creating a symbolic link: ln -s /usr/lib/x86_64-linux-gnu/dri/amdgpu_dri.so / Now everything appears to be working.

KillerByte commented on 2016-07-22 05:38 (UTC)

@shazeal The patches you provided were very helpful! After the installation of the dkms module, I still had to run depmod -a before the driver would load properly. Unfortunately, glxgears does not seem to be working. In the xorg log, I have stuff like: [ 46.827] (II) AMDGPU(0): Direct rendering enabled [ 46.884] (II) AMDGPU(0): Use GLAMOR acceleration. [ 46.884] (II) AMDGPU(0): Acceleration enabled But when I try to run glxgears, it prints "Error: couldn't get an RGB, Double-buffered visual". glxinfo prints a similar error. Any ideas? Thanks for your help.

shazeal commented on 2016-07-21 23:21 (UTC)

The patches from the gentoo vulkan overlay work nicely for the DKMS module... https://github.com/Lucretia/vulkan-overlay/tree/master/sys-kernel/amdgpu-pro-dkms/files/16.30.3-306809 I also had to disabled the -Werror flag in /usr/src/amdgpu-pro-16.30.3-306809/amd/dal/Makefile to get it to build.

KillerByte commented on 2016-07-10 19:24 (UTC)

@Corngood I have read the article you mentioned before, and last night I tried to do everything it said, but I am still ending up with no direct rendering. I am using mesa-git, libdrm-git, xf86-video-amdgpu-git, linux of the polaris test branch, linux-firmware-git As for the dkms... I certainly would not describe the build process as being "trivial". While most of the compiler errors were pretty easy to decipher and fix, I ran into problems booting with the newly installed module. Not to mention that it took me over an hour to go through all the compiler errors.

Corngood commented on 2016-07-09 00:16 (UTC)

16.30.3.306809-4 - add license string - add make dependency on wget - don't build dkms and firmware packages unless $ALL_PACKAGES=true

Corngood commented on 2016-07-09 00:11 (UTC)

@KillerByte I did go through the process of getting the dkms module to compile (on 4.6) at one point. It was all trivial stuff, but I abandoned it because everything I needed was in mainline anyway. I suggest following the instructions on that link @ecloud posted: http://www.phoronix.com/scan.php?page=news_item&px=RX-480-OSS-Steps Build the polaris-test kernel, install the firmware, make sure mesa is updated with polaris support. Then once you have the open source stack working, you should be able to replace mesa with amgdpu-pro using this package. If you do want to continue using dkms, you'll either need to fix those compile errors in the driver, or build it against the kernel it's meant for (4.2 I think?). Then you'll also need to install the firmwares.

KillerByte commented on 2016-07-08 08:09 (UTC)

I also have an RX480. Just arrived today! Anyway, spent all afternoon trying to get the drivers to work, but unfortunately the furthest I have been able to get is KMS with Xorg loading without direct rendering. For some reason OpenCL works, though. Here is how I got this far: * I installed xf86-video-amdgpu * My computer would not KMS, so I updated to the linux-mainline kernel * After I observed direct rendering not working in Xorg, I tried to install this AUR package. Everything installs properly, but I run into numerous compilation errors when dkms install executes. Without the kernel module properly built, I cannot achieve proper rendering. So... any ideas on how to fix dkms?

Corngood commented on 2016-07-05 19:11 (UTC)

@ecloud So I'm guessing amdgpu+mesa doesn't work for you either? When you built your custom kernel did you use the polaris-test branch? Did you update firmwares? Keep in mind that this package doesn't update firmware blobs, and will use whatever you have installed (typically from the arch firmware package). I'm not sure about the console driver. I certainly never changed anything related to that.