Package Details: amdgpu-pro-libgl 22.10_1395274-1

Git Clone URL: (read-only, click to copy)
Package Base: amdgpu-pro-installer
Description: AMDGPU Pro Advanced Multimedia Framework
Upstream URL:
Licenses: custom: AMDGPU-PRO EULA
Provides: libgl
Submitter: LEW21
Maintainer: Ashark
Last Packager: Ashark
Votes: 110
Popularity: 1.21
First Submitted: 2016-03-28 22:44 (UTC)
Last Updated: 2022-04-01 05:40 (UTC)

Required by (699)

Sources (19)

Pinned Comments

Ashark commented on 2019-12-09 20:52 (UTC) (edited on 2022-03-07 22:43 (UTC) by Ashark)

PKGBUILD generator is located here:

AMDGPU PRO wiki page:

New versions will appear here:

Latest Comments

Ashark commented on 2022-05-17 17:55 (UTC)

I am not updating only because I hoped this package could not be needed if is solved. Regarding the error, can you try again, and if problem persist, open an issue in the repo?

Ping-High commented on 2022-05-17 14:35 (UTC)

I wanted to PR and update this package ,but i got this problem: Aptly Failed! It skips the process of entering a password

I just enter the command, then I get this

Loading packages...
Generating metadata files and linking package files...
Finalizing metadata files...
Signing file 'Release' with gpg, please enter your passphrase when prompted:
gpg: WARNING: unsafe permissions on homedir '/root/.gnupg'
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
ERROR: unable to publish: unable to detached sign file: exit status 2

I really didn't press double enter!

bob-xygene commented on 2022-03-25 01:26 (UTC)

If you don't need professional features of the AMD proprietary driver then just install vulkan-radeon package (its the RADV open source vulkan driver for the open source amdgpu driver included in the kernel).

Wa11aa commented on 2022-03-16 05:18 (UTC) (edited on 2022-03-16 05:21 (UTC) by Wa11aa)

I don't have the AMDGPU PRO proprietary driver i have mesa can i use the vulkan driver without problems?

bob-xygene commented on 2022-03-16 01:44 (UTC) (edited on 2022-03-16 02:17 (UTC) by bob-xygene)

I don't know what other update fixed it but today i reinstalled this amdgpu-pro V21.50.2 Vulkan, AMF & libgl and its working. At least my test encode does not crash.

If i go further and try to mix vulkan hardware decoding + vulkan filter with amf encoding it crashes :

[scale_vulkan @ 0x557258b9ec40] shaderc compile status 'success' (0 errors, 0 warnings)
[scale_vulkan @ 0x557258b9ec40] Shader scale_compute compiled! Size: 1872 bytes
[h264_amf @ 0x5572569fde80] AMF initialisation succeeded via Vulkan.
0122-02-16 03:09:16 9C663900 [EncodeQueueVulkan]    Info: EncodeQueueServiceVulkanImpl::Initialize() new encode queue extension is not supported
0122-02-16 03:09:16 9C663900 [EncodeQueueService] Warning: Failed to create encode queue serivce.
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreBaseImpl] Warning: Failed to initialize EncodeQueueFactory.
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreBaseImpl] Warning: Failed to create encode queue serivce.
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreH264] Warning: Encode Core dll not found, fall back to UVE path
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreH264] Warning: CreateServices failed.
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreH264]    Info: *****Fallback to UVE path!
0122-02-16 03:09:16 9C663900 [AMFEncoderCoreH264]   Debug: AMFEncoderCoreH264Impl::Terminate()

So for now, only very basic AMF encoding woks, as long as frames comes from some software path or vaapi hardware accel (opencl filters combinaison works too, sad there are no opencl scale filters in ffmpeg).

Ashark commented on 2022-03-10 01:40 (UTC)

I am getting [h264_amf @ 0x55e1ae1016c0] DLL failed to open instead of yours [h264_amf @ 0x55fe454cfec0] AMF initialisation succeeded via Vulkan.. I tested that with RX580. Did they drop support for it in amf?

bob-xygene commented on 2022-03-08 23:38 (UTC) (edited on 2022-03-09 17:14 (UTC) by bob-xygene)

~/VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json; ffmpeg -hide_banner -loglevel verbose -probesize 256M -rtbufsize 128M -vsync passthrough -f lavfi -i testsrc=duration=10:size=1280x720:rate=60 -c:v h264_amf -log_to_dbg false -vf format=nv12 -f null /dev/null

With V21.30 i obtain :

[Parsed_testsrc_0 @ 0x55fe454ca880] size:1280x720 rate:60/1 duration:10.000000 sar:1/1
Input #0, lavfi, from 'testsrc=duration=10:size=1280x720:rate=60':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: rawvideo, 1 reference frame (RGB[24] / 0x18424752), rgb24, 1280x720 [SAR 1:1 DAR 16:9], 60 tbr, 60 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_amf))
Press [q] to stop, [?] for help
[graph 0 input from stream 0:0 @ 0x55fe454d0c80] w:1280 h:720 pixfmt:rgb24 tb:1/60 fr:60/1 sar:1/1
[auto_scale_0 @ 0x55fe454d67c0] w:iw h:ih flags:'' interl:0
[Parsed_format_0 @ 0x55fe454d2940] auto-inserting filter 'auto_scale_0' between the filter 'graph 0 input from stream 0:0' and the filter 'Parsed_format_0'
[auto_scale_0 @ 0x55fe454d67c0] w:1280 h:720 fmt:rgb24 sar:1/1 -> w:1280 h:720 fmt:nv12 sar:1/1 flags:0x0
[h264_amf @ 0x55fe454cfec0] AMF initialisation succeeded via Vulkan.
Output #0, null, to '/dev/null':
    encoder         : Lavf59.16.100
  Stream #0:0: Video: h264, 1 reference frame, nv12(tv, progressive), 1280x720 (0x0) [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 60 fps, 60 tbn
      encoder         : Lavc59.18.100 h264_amf
No more output streams to write to, finishing.:09.18 bitrate=N/A speed=9.18x    
frame=  600 fps=552 q=-0.0 Lsize=N/A time=00:00:10.00 bitrate=N/A speed= 9.2x    
video:1820kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Input file #0 (testsrc=duration=10:size=1280x720:rate=60):
  Input stream #0:0 (video): 600 packets read (1658880000 bytes); 600 frames decoded; 
  Total: 600 packets (1658880000 bytes) demuxed
Output file #0 (/dev/null):
  Output stream #0:0 (video): 600 frames encoded; 600 packets muxed (1863394 bytes); 
  Total: 600 packets (1863394 bytes) muxed

(Removed vulkan-amdgpu-pro and amf-amdgpu-pro V21.30 and reinstalled the same package in V21.50.2) With V21.50.2 i obtain :

[Parsed_testsrc_0 @ 0x55e807bdc880] size:1280x720 rate:60/1 duration:10.000000 sar:1/1
Input #0, lavfi, from 'testsrc=duration=10:size=1280x720:rate=60':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: rawvideo, 1 reference frame (RGB[24] / 0x18424752), rgb24, 1280x720 [SAR 1:1 DAR 16:9], 60 tbr, 60 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_amf))
Press [q] to stop, [?] for help
[graph 0 input from stream 0:0 @ 0x55e807be2c80] w:1280 h:720 pixfmt:rgb24 tb:1/60 fr:60/1 sar:1/1
[auto_scale_0 @ 0x55e807be87c0] w:iw h:ih flags:'' interl:0
[Parsed_format_0 @ 0x55e807be4940] auto-inserting filter 'auto_scale_0' between the filter 'graph 0 input from stream 0:0' and the filter 'Parsed_format_0'
[auto_scale_0 @ 0x55e807be87c0] w:1280 h:720 fmt:rgb24 sar:1/1 -> w:1280 h:720 fmt:nv12 sar:1/1 flags:0x0
[h264_amf @ 0x55e807be1ec0] AMF initialisation succeeded via Vulkan.
[h264_amf @ 0x55e807be2280] CreateComponent(AMFVideoEncoderVCE_AVC) failed with error 1
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

If you want AMF debugging to stderr you can pass : -log_to_dbg true (just after the -c:v h264_amf)

Ashark commented on 2022-03-08 22:28 (UTC)

Can you write the specific command with which you test? Can you try it in ubuntu and say if it works? Maybe there is a problem with library, included with this version. Maybe with dependencies. Are you sure that opencl is required for that? Also note that opencl-amd currently uses 21.50, while this pkgbase is for 21.50.2.

bob-xygene commented on 2022-03-08 19:15 (UTC) (edited on 2022-03-09 17:11 (UTC) by bob-xygene)

ffmpeg h264_amf was working with previous amdgpu-pro-installer and opencl-amd since 21.50.2_1384495-1 h264_amf won't load.

I saw a new dependency for rocm-opencl-runtime, so i removed opencl-amd and installed all dependency : hsakmt-roct rocm-cmake rocm-llvm rocm-device-libs comgr hsa-amd-aqlprofile-bin hsa-rocr rocm-opencl-runtime

Still AMF is dead :

<some ffmpeg h264_amf compression that works with software encoding and worked with amf before update>
[auto_scale_0 @ 0x5623a0546f80] w:1280 h:720 fmt:rgb24 sar:1/1 -> w:1280 h:720 fmt:nv12 sar:1/1 flags:0x0
[h264_amf @ 0x5623a053d380] AMF initialisation succeeded via Vulkan.
0122-02-08 19:57:56 A5712900 [AMFEncoderCoreH264]   Error: ../../../../../runtime/src/components/EncoderCore/EncoderCoreH264Impl.cpp(186):Assertion failed:Failed to create service!
0122-02-08 19:57:56 A5712900 [AMFEncoderCoreH264]   Error: ../../../../../runtime/src/components/EncoderCore/EncoderCoreH264Impl.cpp(318):AMF_ERROR 1 : AMF_FAIL: Failed to create encode service!
0122-02-08 19:57:56 A5712900 [AMFEncoderCoreH264] Warning: CreateServices failed.
[h264_amf @ 0x5623a053d740] CreateComponent(AMFVideoEncoderVCE_AVC) failed with error 1
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

~/uname -a
Linux punch 5.16.12-zen1-1-zen #1 ZEN SMP PREEMPT Wed, 02 Mar 2022 12:22:53 +0000 x86_64 GNU/Linux

Number of platforms                               1
  Platform Name                                   AMD Accelerated Parallel Processing
  Platform Vendor                                 Advanced Micro Devices, Inc.
  Platform Version                                OpenCL 2.2 AMD-APP.dbg (3406.0)
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_icd cl_amd_event_callback 
  Platform Extensions function suffix             AMD
  Platform Host timer resolution                  1ns

  Platform Name                                   AMD Accelerated Parallel Processing
Number of devices                                 1
  Device Name                                     gfx1010:xnack-
  Device Vendor                                   Advanced Micro Devices, Inc.
  Device Vendor ID                                0x1002
  Device Version                                  OpenCL 2.0 
  Driver Version                                  3406.0 (HSA1.1,LC)
  Device OpenCL C Version                         OpenCL C 2.0 
  Device Type                                     GPU
  Device Board Name (AMD)                         AMD Radeon RX 5700 XT
  Device PCI-e ID (AMD)                           0x731f
  Device Topology (AMD)                           PCI-E, 0000:2f:00.0
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Max compute units                               20
  SIMD per compute unit (AMD)                     4
  SIMD width (AMD)                                32
  SIMD instruction width (AMD)                    1
  Max clock frequency                             2100MHz
  Graphics IP (AMD)                               10.1
  Device Partition                                (core)
    Max number of sub-devices                     20
    Supported partition types                     None
    Supported affinity domains                    (n/a)

~/lspci -k
2f:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
    Subsystem: Gigabyte Technology Co., Ltd Radeon RX 5700 XT Gaming OC
    Kernel driver in use: amdgpu
    Kernel modules: amdgpu


ERROR: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /usr/lib/ says it supports interface version 6 but still exports core entrypoints (Policy #LDP_DRIVER_6)
Vulkan Instance Version: 1.2.203
GPU id : 0 (AMD Radeon RX 5700 XT):
    Surface type = VK_KHR_wayland_surface
    Formats: count = 2
            format = FORMAT_B8G8R8A8_UNORM
            colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR
            format = FORMAT_B8G8R8A8_SRGB
            colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR
    Present Modes: count = 3

interface: 'wl_compositor',                              version:  4, name:  1
interface: 'zwp_tablet_manager_v2',                      version:  1, name:  2
interface: 'zwp_keyboard_shortcuts_inhibit_manager_v1',  version:  1, name:  3
interface: 'xdg_wm_base',                                version:  3, name:  5
interface: 'zwlr_layer_shell_v1',                        version:  3, name:  6
interface: 'zxdg_decoration_manager_v1',                 version:  1, name:  7
interface: 'wp_viewporter',                              version:  1, name:  8
interface: 'wl_shm',                                     version:  1, name:  9
    formats: 'XB30'(0x30334258) 'AB30'(0x30334241) 'XR30'(0x30335258) 'AR30'(0x30335241) XRGB8888 ARGB8888
interface: 'kde_output_device_v2',                       version:  2, name: 42
interface: 'wl_output',                                  version:  3, name: 43
    x: 0, y: 0, scale: 1,
    physical_width: 710 mm, physical_height: 400 mm,
    make: 'BNQ', model: 'BenQ BL3200/GCE00501SL0',
    subpixel_orientation: unknown, output_transform: normal,
        width: 2560 px, height: 1440 px, refresh: 59.951 Hz,
        flags: current

Any clue why that "encode service" won't run ? (under X11 it crashes the same)

strace says the error pops in the new library ""

Checking out V21.30 (instead of V21.50.2) and installing repairs AMF encoding.

d2_ricci commented on 2022-03-07 23:24 (UTC)

I saw rocm in the added dependencies. It will be a while before I can test it but have a few people that I will bug to see if anything is broken.

Ashark commented on 2022-03-07 23:14 (UTC)

I am glad to release it. Today I spent the whole day to prepare generator.
I however did not tested pro vulkan yet, and also amf. The amf depends on rocm it seems, and I do not know yet where it is used.

d2_ricci commented on 2022-03-07 22:56 (UTC)

Thanks for pushing 21.50

Raymo111 commented on 2021-10-13 04:44 (UTC) (edited on 2021-10-13 04:45 (UTC) by Raymo111)

Why did this package disappear off the AUR? Even the git link is broken? Edit: nvm it's a pkgbase... wtf??

vighbox commented on 2021-10-13 01:47 (UTC) (edited on 2021-10-13 01:51 (UTC) by vighbox)

Something is causing the validity check to fail

paru  -S amf-amdgpu-pro amdgpu-pro-libgl lib32-amdgpu-pro-libgl vulkan-amdgpu-pro lib32-vulkan-amdgpu-pro
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...

Aur (1) amdgpu-pro-installer-21.30_1290604-1 (vulkan-amdgpu-pro amf-amdgpu-pro amdgpu-pro-libgl lib32-amdgpu-pro-libgl lib32-vulkan-amdgpu-pro)

:: Proceed to review? [Y/n]: Y

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
 nothing new to review
fetching devel info...
==> Making package: amdgpu-pro-installer 21.30_1290604-1 (Tue Oct 12 21:44:54 2021)
==> Retrieving sources...
  -> Found amdgpu-pro-21.30-1290604-ubuntu-20.04.tar.xz
  -> Found progl
  -> Found progl.bash-completion
==> Validating source files with sha256sums...
    amdgpu-pro-21.30-1290604-ubuntu-20.04.tar.xz ... FAILED
    progl ... Passed
    progl.bash-completion ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'amdgpu-pro-installer-21.30_1290604-1 (vulkan-amdgpu-pro amf-amdgpu-pro amdgpu-pro-libgl lib32-amdgpu-pro-libgl lib32-vulkan-amdgpu-pro)': 
error: packages failed to build: amdgpu-pro-installer-21.30_1290604-1 (vulkan-amdgpu-pro amf-amdgpu-pro amdgpu-pro-libgl lib32-amdgpu-pro-libgl lib32-vulkan-amdgpu-pro)

ArchBoxHero commented on 2021-10-06 15:12 (UTC) (edited on 2021-10-06 15:42 (UTC) by ArchBoxHero)

Hey I wanted to mention that if anybody is using the pro installer here and also running "No Man's Sky" with steam that one of the latest updates for either steam, mesa, or this amdgpu-pro-installer might not work for launching the game. I've uninstalled the packages provided and it launches fine without them. And then I reinstall them after playing the game. So to reiterate the problem is when I have the amdgpu-pro-installer drivers that, while steam launches the game No Man's Sky, you can make it to the main game menu but after starting your game it renders erratically with colors and what not and then crashes. I'll open up a bug report but not sure yet where to do that with either the steam package or the amdgpu or even mesa. *Also, when I run the game with these drivers I get this dialog box before loading the game: NVIDIA DLSS cannot be loaded due to outdated driver m inimum version required 0.0

Other games like Doom Eternal, Shadow of Tomb radeider, and CSGO load and play fine. Well CSGO has other issues sometimes but not related to this.

pikasalt commented on 2021-07-23 04:44 (UTC) (edited on 2021-07-26 18:14 (UTC) by pikasalt)

I'm experiencing the same issues as @xochikobrick. Oddly enough, Resolve reports my 4700u as having 0.5 gb of memory available, which seems to coincide with Darktable reporting that the system has insufficient memory with 512 mb of memory. This line from dmesg also stuck out me:

[  240.123814] amdgpu 0000:04:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR

EDIT: The issue seems to stem from opencl-amd and not this package. Downgrading to opencl-amd 20.40 fixed this

Ashark commented on 2021-07-16 16:10 (UTC)

@xochikubrick Try to use DR checker as suggested by Arch Wiki. If that does not help, try to ask in forums.

xochikubrick commented on 2021-07-16 15:59 (UTC)

Hi Asharrk, I did, but no success still, also did a re-install, still the same problem... This update is not working for me. Any suggestions?

Ashark commented on 2021-07-12 03:57 (UTC)

You probably did not updated the opencl-amd.

xochikubrick commented on 2021-07-12 02:35 (UTC)

After last update (21.20) Davinci will send "GPU error code=0" and freeze my system, Blender crashes and Steam games won't start... Any advice?

Ashark commented on 2021-07-07 05:30 (UTC)

AruMoon ameeno Thanks, I will fix it soon. Can you name the application for which you need 32 bit pro driver? This is for my own curiosity.

ameeno commented on 2021-07-06 23:09 (UTC)

lib32-nx-x11 needed for lib32-amdgpu-pro-libgl, but there are no such lib32 package. Only 64 bit

I agree with AruMoon. this is not installable.

AruMoon commented on 2021-07-06 21:45 (UTC) (edited on 2021-07-06 21:46 (UTC) by AruMoon)

lib32-nx-x11 needed for lib32-amdgpu-pro-libgl, but there are no such lib32 package. Only 64 bit

1retfel commented on 2021-06-18 12:37 (UTC) (edited on 2021-06-18 16:51 (UTC) by 1retfel)

Won't work with WebGL, Blender and games. Blender, Mikytracker etc don't starts.

slightlyfaulty commented on 2021-06-17 17:58 (UTC)

@Ashark Thanks for the clarification. Makes sense now :)

Ashark commented on 2021-06-17 17:53 (UTC)

@slightlyfaulty it is not a package, but a package base.

slightlyfaulty commented on 2021-06-17 17:42 (UTC)

I can't find this package when searching the AUR. Is it delisted or something?

Ashark commented on 2021-04-27 04:19 (UTC)

Updated to 21.10_1247438-1. progl works for DR, but I did not test vulkan and amf.

D3SOX commented on 2021-04-26 15:08 (UTC)

Version 21.10 is out. It tried it with the PKGBUILD generator but I have not managed to build the packages.

Ashark commented on 2021-03-11 19:19 (UTC)

@tz4678 you should specify the actual package name, for example, amdgpu-pro-libgl. You are specifying a package group (if I call this thing correctly).

sperg512 commented on 2021-03-11 06:00 (UTC)

@tz4678 you misspelled it, its installer, not install

tz4678 commented on 2021-03-11 05:59 (UTC) (edited on 2021-03-11 16:21 (UTC) by tz4678)

How to fix?

❯ yay -S amdgpu-pro-installer  
:: Resolving dependencies...
error: could not find all required packages:
    amdgpu-pro-installer (target)

damnbro commented on 2021-01-19 10:37 (UTC)

thank u

sperg512 commented on 2021-01-19 10:26 (UTC)

@damnbro probably a partial download, remove the tarball then try again

damnbro commented on 2021-01-19 08:52 (UTC)

ey man please help what do i do its says

amdgpu-pro-20.45-1188099-ubuntu-20.04.tar.xz ... FAILED

==> ERROR: One or more files did not pass the validity check! :: Unable to build amdgpu-core-meta - makepkg exited with code: 1

Ashark commented on 2021-01-19 07:42 (UTC) (edited on 2021-01-26 01:23 (UTC) by Ashark)

In the future pkgrel I want to make libgl to be activated on demand with progl prefix. However, there are some files inside, which I do not know yet if I can safely drop. Namely:

  • amdrc (in /etc/amd) - I think it should stay there
  • amdapfxx.blb (in /etc/amd) - probably some firmware? I tried to open it in text editor, it contains lots of readable text with application names. It is probably some optimisations per application?
  • (in /opt/amdgpu-pro/lib/xorg/modules/extensions) - probably, this thing causes failing X to start when installed. Probably, intended for use with specific version of X on Ubuntu. But probably, someone would want to use ag-pro on entire X.
  • how to handle file 10-amdgpu-pro.conf (in /opt/amdgpu/share/drirc.d). It have xml config for dri driver. Also, need to find out if ag pro can work with libglvnd.

KatStuffs commented on 2021-01-17 01:52 (UTC) (edited on 2021-01-17 01:52 (UTC) by KatStuffs)

Has any had luck passing this driver off as an environment variable like described in the wiki?

$ LD_LIBRARY_PATH="$PACKAGEPATH/opt/amdgpu-pro/lib/x86_64-linux-gnu:${LD_LIBRARY_PATH}" LIBGL_DRIVERS_PATH="$PACKAGEPATH/usr/lib/x86_64-linux-gnu/dri/" dri_driver="amdgpu" command

Ashark commented on 2021-01-16 23:42 (UTC)

@Akrai thanks for adding example to the wiki. I have checked, seems like amf works ok even without opencl-amd, so I just removed that dependency.

Akrai commented on 2021-01-15 20:53 (UTC)

Oh you're right, vulkan-driver is already satisfied with amdvlk, no issues uninstalling it. But ffmpeg throws this error when trying to encode without it:

[h264_amf @ 0x56452d8d3d40] DLL failed to open Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

So yeah, i have to keep amf-amdgpu-pro i guess.

Yo should remove opencl-amdgpu-pro-icd as deps as it doesn't exist right?

Ashark commented on 2021-01-15 20:29 (UTC)

@Akrai amf-amdgpu-pro just contains, but I do not know for what it is. By the way, steam does not require vulkan-amdgpu-pro, it just require vulkan-driver, which could be open.

Akrai commented on 2021-01-15 20:16 (UTC)

Yeah, ffmpeg fails if i remove vulkan-amdgpu-pro, which also removed amdgpu-core-meta and amdgpu-pro-core-meta but those two seems irrelevant. So what does the amf-amdgpu-pro package does? I have zero idea, as I have it uninstalled right now and ffmpeg encodes just fine

Akrai commented on 2021-01-15 20:14 (UTC)

I was trying to encode videos through GPU a month ago and so with the very few information of AMF encoding in linux available in the internet I achieved it. I thought I had to use the amdgpu-pro package, as I thought I had to link the ICD file that the amdgpu-pro provides (in the vulkan-amdgpu-pro one, using VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json) as a parameter in ffmpeg.

Now that you asked I just checked and it works to encode without linking that ICD file, so... yeah. As there is no info out there to know for sure what i really need to encode using AMF, i'm not really sure but it looks like i don't need at all any amdgpu-pro packages... Also, I can't really test to encode uninstalling amdgpu-pro as steam requires vulkan-amdgpu-pro, which is the package which provides that ICD file and so maybe if i uninstalled it then ffmpeg could not use h264_amf encoder, but i cannot test it. I could force remove it, for the test...

In fact i'm gonna do it real quick just to check

Ashark commented on 2021-01-15 19:47 (UTC)

@Akrai thanks, I missed that. Probably yes, I do not remember what is inside for now. Maybe it should be replaced by generic icd loader dependency, if it requires opencl. I will try to figure that out a bit later. By the way, are you using AMF? If yes, could you describe it here ?

Akrai commented on 2021-01-15 19:32 (UTC)

So opencl-amdgpu-pro-icd dependency should be removed from amf-amdgpu-pro, right?

Ashark commented on 2020-12-07 18:59 (UTC) (edited on 2021-01-01 20:16 (UTC) by Ashark)

Yeah, I know that 20.45 is now available for my rx 580 gpu. The problem is that I had no success installing it even in kubuntu 20.04.1! amdgpu-dkms package failed to install. It is strange, because they should support ubuntu in the first place. I have also tried with CentOS 8 stream, but also had no success. Need further experiments.

Edit 20210101: they have released 20.45-1188099 that fixes the issue with amdgpu-dkms. I have successfully installed ./amdgpu-install --pro --opencl=legacy,rocr --no-32 but the problem is that onboarding screen is blank and when I drag an image to timeline, dr crashes after a second. Need further experiments.

Ashark commented on 2020-11-23 21:41 (UTC)

I am glad to say that linux gpu reset bug was eliminated by gnif's project vendor-reset. See

Now it should be much easier to test amdgpu-pro repackaging.

kode54 commented on 2020-11-21 01:37 (UTC)

Uh, yeah, searches don't ordinarily look for base packages, only the sub-packages they build.

e8hffff commented on 2020-11-20 11:20 (UTC)

This AUR package is being hidden from both website and Octopi searches.

sperg512 commented on 2020-11-20 00:16 (UTC)

@Recompiler until, and if, Ashark updates this to 20.45 (or someone else) you're probably better off using my opencl-amd package (shameless self-promotion) as it's currently up-to-date, and Blender works on my Vega 10. Though we have been noticing some GPUs have problems and are trying to see if we missed any libraries. To anyone seeing this, you could help too :)

Though helping us out with that would probably speed up these packages getting updated as well. So yeah, mutually beneficial

Recompiler commented on 2020-11-19 23:46 (UTC)

Blender crashes when I select my GPU with OpenCL. I have a Radeon RX Vega 10 so it technically should work. Any thoughts?

naetherm commented on 2020-11-19 11:08 (UTC)


Ashark commented on 2020-11-19 07:48 (UTC) (edited on 2020-11-19 08:29 (UTC) by Ashark)

@sperg512 ~~Where did you see 20.45? On the web site I only see 20.40.~~ I see, it is only available for several gpus, but not mine.

Ashark commented on 2020-11-19 07:13 (UTC)

I had success of running DR by placing files to the separate dir and changing environment variables, as was shown in previous comments. I thought that it may be a good start for creating such a specific package. And then run applications something like this: progl-run davinci-resolve. I will take a look at the weekends.

sperg512 commented on 2020-11-19 02:35 (UTC)

@apaz I was gonna keep it after 20.40, but after 20.45 introduced a massive set of changes to the file list of the official tarball, I'm not even gonna try. Maybe somebody could replace the opencl packages with opencl-amd?

Ashark commented on 2020-11-02 10:12 (UTC)

@apaz In the repo I have made a nice readme, describing info on how to update a pkgbuild

As for video editors, I really like a magnetic timeline feature, because it so much convenient and applicable for my type of videos (linux tutorials). When recording, I just can resay a mistaked sentence, and then just cut unneeded while previewing. Final Cut has its own drawbacks (macos with its buttons mess, un), DR has its own (no text box for titles). Unfortunately, no one else video editor provides this feature. Thanks for the list. I would like to try Olive.

apaz commented on 2020-11-02 09:13 (UTC)

@Ashark I am sorry about this, I hope someone will be able to keep the driver. Do you think it's okay to make a request on the forum to find a substitute?

[As for video editing on Linux I recommend you (from the most complete and difficult to the easiest): Cinelerra-GG Infinity Kdenlive Shotcut and Olive editor Openshot]

kvaps commented on 2020-10-30 23:41 (UTC)

Hi, I have a segfault when starting Xorg with amdgpu-pro 20.30:

[   140.049] (EE) 
[   140.049] (EE) Backtrace:
[   140.049] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x53) [0x55f3d22ccbd3]
[   140.049] (EE) 1: /usr/lib/Xorg (0x55f3d2186000+0x151a15) [0x55f3d22d7a15]
[   140.049] (EE) 2: /usr/lib/ (0x7fca33c49000+0x3d6a0) [0x7fca33c866a0]
[   140.049] (EE) 3: /usr/lib/ (amdgpu_bo_export+0xb6) [0x7fca34169e86]
[   140.049] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/ (0x7fc9e0a0a000+0x17c8c7a) [0x7fc9e21d2c7a]
[   140.049] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/ (0x7fc9e0a0a000+0x1636393) [0x7fc9e2040393]
[   140.049] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/ (0x7fc9e0a0a000+0x164bc0d) [0x7fc9e2055c0d]
[   140.049] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/ (0x7fc9e0a0a000+0x1369d0f) [0x7fc9e1d73d0f]
[   140.049] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/ (eglCreateImageKHR+0x483) [0x7fc9e1e3e473]
[   140.049] (EE) 9: /usr/lib/xorg/modules/ (glamor_egl_create_textured_pixmap_from_gbm_bo+0xb6) [0x7fca32ebeae6]
[   140.049] (EE) 10: /usr/lib/xorg/modules/drivers/ (0x7fca34172000+0xe538) [0x7fca34180538]
[   140.049] (EE) 11: /usr/lib/Xorg (0x55f3d2186000+0x1937fb) [0x55f3d23197fb]
[   140.049] (EE) 12: /usr/lib/Xorg (0x55f3d2186000+0x39511) [0x55f3d21bf511]
[   140.049] (EE) 13: /usr/lib/ (__libc_start_main+0xf2) [0x7fca33c71152]
[   140.049] (EE) 14: /usr/lib/Xorg (_start+0x2e) [0x55f3d21c05ae]
[   140.049] (EE) 
[   140.049] (EE) Segmentation fault at address 0x10
[   140.049] (EE) 
Fatal server error:
[   140.049] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   140.049] (EE) 
[   140.049] (EE) 

previus version 19.30 from 370d39c6 is working fine!

image28 commented on 2020-10-26 07:49 (UTC) (edited on 2020-10-26 07:49 (UTC) by image28)

pkgbuild is now tested and working with some kink's and only on LTS kernel Read the readme on my github link, as it can break your system currently, will be fixing that when I have time.

gardotd426 commented on 2020-10-23 17:23 (UTC)

@apaz no, they're just saying they updated to the newest release. It will still have any issues it had previously.

Really the only parts from this that should ever be installed system-wide on Arch are vulkan-amdgpu-pro (and lib32-vulkan-amdgpu-pro) and the opencl packages.

apaz commented on 2020-10-23 14:23 (UTC)

@image28 I can't test now because I have video editing projects in progress... Maybe I didn't understand, are you saying that now amgpu-pro install and work (with your PKGBUILD) without the problems that prevented their use?

image28 commented on 2020-10-21 16:47 (UTC)

Updated my PKGBUILD installer to 20.40 ( still a work in progress towards simplifying package maintenance ). Currently untested will test today if I have time ( but it does build on my system ).

gardotd426 commented on 2020-10-16 20:31 (UTC) (edited on 2020-10-16 20:32 (UTC) by gardotd426)

@mbma. Yeah installing the pro drivers system-wide isn't an option on Arch. It breaks the system.

The only thing I can tell you is that you must be missing something, because it worked fflawlessly for me.

Here's what I have in the $LD_LIBRARY_PATH folder:


dri is a directory, the rest are files from the pro packages.

And then here is what's in the dri folder, which is the LIBGL_DRIVERS_PATH location:

And that's it. Put all those files from the first list in folderA, then in folderB, then you can even test it real quick with LD_LIBRARY_PATH=/path/to/folderA LIBGL_DRIVERS_PATH=/path/to/folderB dri_driver=amdgpu /opt/resolve/bin/resolve. It should work, and then you can just turn that into a script or a little shell command or whatever you want.

gardotd426 commented on 2020-10-16 20:31 (UTC)

@mbma. Yeah installing the pro drivers system-wide isn't an option on Arch. It breaks the system.

The only thing I can tell you is that you must be missing something, because it worked fflawlessly for me.

Here's what I have in the $LD_LIBRARY_PATH folder:


dri is a directory, the rest are files from the pro packages.

And then here is what's in the dri folder, which is the LIBGL_DRIVERS_PATH location:

And that's it. Put all those files from the first list in folderA, then in folderB, then you can even test it real quick with LD_LIBRARY_PATH=/path/to/folderA LIBGL_DRIVERS_PATH=/path/to/folderb dri_driver=amdgpu /opt/resolve/bin/resolve. It should work, and then you can just turn that into a script or a little shell command or whatever you want.

mbma commented on 2020-10-16 20:25 (UTC)

@gardotd426 i've tried the suggest solution to run resolve to no avail. I also found a similar workarround on the wiki

Resolve starts but then halts complaining it can't find any gpu. Any suggestions on that?

I can run resolve if i install the amdgpu-pro packages system wide, but run into other problems when booting the system.

Ashark commented on 2020-10-03 22:24 (UTC)

Version 20.40 is released:

kode54 commented on 2020-09-29 01:41 (UTC)

@paulsun You can git checkout the old revision of this AUR package that builds 19.30, it should still work. Of course, even then, the libGL stuff barely works.

psun256 commented on 2020-09-28 16:57 (UTC)

If I were to use 19.30 instead of 20.30 (for some reason its more stable for me, on 20.30 there are random flickers at times), do I just use extract_deb on these files?

package_amdgpu-pro-libgl () { pkgdesc="AMDGPU Pro OpenGL driver" license=('custom: AMDGPU-PRO EULA') provides=('libgl') depends=("amdgpu-pro-core-meta=${major}_${minor}-${pkgrel}" "gcc-libs" "glibc" "libx11" "libxcb" "libxdamage" "libxext" "libxfixes" "libxxf86vm") backup=(etc/gbm/gbm.conf)

extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libegl1-amdgpu-pro_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgbm1-amdgpu-pro_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgbm1-amdgpu-pro-base_${major}-${minor}_all.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgl1-amdgpu-pro-appprofiles_${major}-${minor}_all.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgl1-amdgpu-pro-dri_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgl1-amdgpu-pro-ext-hwe_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgl1-amdgpu-pro-glx_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libglapi1-amdgpu-pro_${major}-${minor}_amd64.deb
extract_deb "${srcdir}"/amdgpu-pro-${major}-${minor}-ubuntu-18.04/libgles2-amdgpu-pro_${major}-${minor}_amd64.deb

# extra_commands:
mv "${pkgdir}"/opt/amdgpu-pro/lib/xorg/modules/extensions/ "${pkgdir}"/opt/amdgpu-pro/lib/xorg/modules/extensions/


So just those 9 files?

uberben commented on 2020-09-26 17:13 (UTC)

@gardotd426 - can you share the location of your .desktop file and the changes you made? I've tried a few variations on what I think it is supposed to look like but can't seem to get any changes to do anything. I'm new to editing .desktop files so I'm sure I'm missing something simple.

hdi commented on 2020-09-20 17:11 (UTC)

@Ashark I love you man, I installed the 19.30 and now everything working as it should, no more black screen, thank you

Ashark commented on 2020-09-20 16:39 (UTC)

@hdi Yes, you can see the changes history. The link is in the top right corner.

hdi commented on 2020-09-20 13:37 (UTC)

@gardotd426 thanks for the guide. I feel so stupid that I can't understand this. My system was working fine with previous amdgpu-pro-libgl 19.30 that I installed from the Manjaro package manager AUR, but I think the developer removed 19.30 and updated with the 20.30. My question is that, is there any way to downgrade or find the old amdgpu-pro-libgl 19.30 from AUR archive??? is there any archive somewhere?

gardotd426 commented on 2020-09-20 03:09 (UTC)

@hdi, that's the problem.

You can't use AMDGPU-PRO's libgl on Arch. Not installed system-wide, anyway.

I'm assuming you need it for DaVinci Resolve? Considering that's literally the only thing that you should need it for...

If that's the case, then you can just extract the lib files into another directory and use a script to export the proper variables and then launch DaVinci Resolve, meanwhile the rest of your system is using the regular amdgpu and mesa drivers.

Just add something like this to your ~/.bashrc or ~/.zshrc:

progl() {
  export LD_LIBRARY_PATH="/home/$USER/pro/drivers:${LD_LIBRARY_PATH}"
  export LIBGL_DRIVERS_PATH="/home/$USER/pro/drivers/dri"
  export dri_driver="amdgpu"

And then make sure ~/pro/drivers contains,,,,,,,, and from the necessary PRO .debs, as well as a directory called dri/ containing from the .deb package.

Then you launch Davinci resolve from the terminal by running progl first, hitting enter, then running DaVinci Resolve, or you could just add the exact same envvars to the beginning of the Exec= line in the .desktop file for DaVinci Resolve. Both work, I've already tried it.

I'm not sure about orca, you probably need to just install that system-wide.

But that's your only option if you insist on using Arch (or anything based on it). If you want to be able to just install the drivers system-wide, you have to use a supported distribution such as Ubuntu LTS or RHEL.

hdi commented on 2020-09-19 12:44 (UTC)

@gardotd426 I don't need a full package I just need these two 1. amdgpu-pro-libgl 19.30 2. amdgpu-pro-orca 19.30

gardotd426 commented on 2020-09-19 12:11 (UTC)

@hdi if you are that unfamiliar with the terminal, then you absolutely shouldn't be messing with the Pro drivers.

Either way, you can't install the full pro drivers system-wide on Arch (or Manjaro). Also, Manjaro is not supported here.

I'm not sure what you think you need the full Pro stack for, but I'd just about guarantee you just think you need them for some reason, and you actually don't.

But yeah, a) the full pro stack cannot be installed system-wide on Arch or any Arch-based distros (you'll get a black screen), b) Manjaro is not supported in any fashion on AUR package threads, and c) you likely don't need the full pro drivers.

hdi commented on 2020-09-19 11:39 (UTC) (edited on 2020-09-19 11:46 (UTC) by hdi)

Hi every one here. I have Manjaro installed on my PC, my gpu is AMD RX480, 8GB and I use my system for Davinci Resolve 16. Since I updated to AMDGPU-PRO 20.30, I get black screen. I don't want headache I just need the previous drive it was amdgpu-pro 19.30, is there any possible way I get that? I searched AUR website, it seems that one is disappeared from the web. Can anyone help? I'm not familiar with terminal so much so I can't build one from the AMD website.

Thanks for your help

Ashark commented on 2020-08-27 19:42 (UTC)

@gardotd426 -

gardotd426 commented on 2020-08-26 23:23 (UTC)

@Ashark, so, I'm confused about move_libdir in the PKGBUILD.

It doesn't work at all. Packages still git built with files in /usr/lib/x86_64-linux-gnu, /usr/lib32/i686-linux-gnu, etc. Nothing gets moved anywhere, so that little snippet does nothing.

amdgpu-pro-libgl is one example. The resulting Arch package has in /usr/lib/x86_64-linux-gnu/dri/

Ashark commented on 2020-08-26 00:41 (UTC)

@quadronick, so you need to remove roct-amdgpu-pro before upgrading.

kode54 commented on 2020-08-25 23:52 (UTC)

It's not a broken dependency. It's a sub-package that's no longer supported, because AMDGPU-Pro no longer includes it.

quadronick commented on 2020-08-25 08:57 (UTC) (edited on 2020-08-25 09:07 (UTC) by quadronick)

➜ aura -Aux                                                  
[sudo] password for quad: 
aura >>= Fetching package information...
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
amdgpu-core-meta             :: 19.30_934563-1 -> 20.30_1109583-1
amdgpu-pro-core-meta         :: 19.30_934563-1 -> 20.30_1109583-1
amf-amdgpu-pro               :: 19.30_934563-1 -> 20.30_1109583-1
hip-amdgpu-pro               :: 19.30_934563-1 -> 20.30_1109583-1
lib32-opencl-amdgpu-pro-orca :: 19.30_934563-1 -> 20.30_1109583-1
lib32-vulkan-amdgpu-pro      :: 19.30_934563-1 -> 20.30_1109583-1
opencl-amdgpu-pro-comgr      :: 19.30_934563-1 -> 20.30_1109583-1
opencl-amdgpu-pro-dev        :: 19.30_934563-1 -> 20.30_1109583-1
opencl-amdgpu-pro-orca       :: 19.30_934563-1 -> 20.30_1109583-1
opencl-amdgpu-pro-pal        :: 19.30_934563-1 -> 20.30_1109583-1
vulkan-amdgpu-pro            :: 19.30_934563-1 -> 20.30_1109583-1

aura >>= Saved package state.
aura >>= Determining dependencies...
aura >>= AUR Packages:
aura >>= Continue? [Y/n] 

==> Finished making: amdgpu-pro-installer 20.30_1109583-1 (Tue 25 Aug 2020 11:41:53 AM MSK) loading packages... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing amdgpu-pro-core-meta (20.30_1109583-1) breaks dependency 'amdgpu-pro-core-meta=19.30_934563-1' required by roct-amdgpu-pro

Idk guys if it's your package's error or not. But I suggest broken dependencies inside your meta-project or something.

Ashark commented on 2020-08-14 13:09 (UTC)

@gardotd426 Could you actually successfully open a project? I have tried your method, DR started normally and showed a project selector window. But when I click on one of the projects, DR crashes. Also, I am interested what is libGLESv2 and and why did not you used them in your method?

codiflow commented on 2020-08-13 14:55 (UTC) (edited on 2020-08-13 21:54 (UTC) by codiflow)

Great tutorial from @gardotd426 thanks for that.

You can get the archive with all relevant files from Chaotic AUR:

Just use the following command tar -I zstd -xvf amdgpu-pro-libgl-20.30_1109583-1-x86_64.pkg.tar.zst to expand the files.

After running progl ; /opt/resolve/bin/resolve I could run "DaVinci Resolve 16" without any problem and without replacing my open source drivers by the proprietary ones.

GFX: ATI Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]

OS: Manjaro

EDIT: If you want you can also use the workaround stated here:

Just install pacman -S amdgpu-pro-libgl before launching DaVinci Resolve and uninstall it with pacman -R amdgpu-core-meta amdgpu-pro-core-meta amdgpu-pro-libgl after you're done.

If it doesn't show any video preview inside of DaVinci Resolve and literally every video is blank / black theres one main cause: Davinci Resolve doesn't support .mp4 files within the Linux version... Source

At the end of this list you can find all supported codecs – not many but better than nothing.

gardotd426 commented on 2020-08-10 08:24 (UTC) (edited on 2020-08-10 08:26 (UTC) by gardotd426)

Note to anyone wanting to actually use this full stack: It can't be done on Arch Linux, you will experience X crashes. However....

If anyone is wanting to use the OpenGL driver from this in order to run DaVinci Resolve, that CAN be done, and quite easily actually.

Install opencl-amd for the proprietary standalone opencl driver. This also allows you to use OpenCL for things like Blender. But for DaVinci Resolve specifically, you also need to have the OpenGL driver, but you CANNOT install it systemwide. What you need to do, is put something like this in your .zshrc (or somewhere else where you can easily run it from the terminal):

progl() {
 export LD_LIBRARY_PATH="${HOME}/pro/drivers:${LD_LIBRARY_PATH}"
  export LIBGL_DRIVERS_PATH="${HOME}/pro/drivers/dri"
  export dri_driver="amdgpu"

And then simply extract a few of the packages and put them in ${HOME}/pro/drivers (and ${HOME}/pro/drivers/dri).

Here is the output of ll -R ${HOME}/pro/drivers/

total 1.1M
drwxr-xr-x 2 matt matt  4.0K Aug  3 06:03 dri
lrwxrwxrwx 1 matt matt    11 Aug  3 06:05 ->
-rw-r--r-- 1 matt matt   80K Aug  3 06:05
lrwxrwxrwx 1 matt matt    12 Aug  3 06:02 ->
lrwxrwxrwx 1 matt matt    12 Aug  3 06:02 ->
-rw-r--r-- 1 matt matt 1013K Aug  3 06:02

total 51M
-rw-r--r-- 1 matt matt 51M Aug  3 06:03

amdgpu-pro-libgl-20.30_1109583-1-x86_64.pkg.tar should contain everything you need. Make sure to put the file inside a dri/ directory within the pro/ directory.

I've already tested this, it does allow DaVinci Resolve to open and run. You obviously have to run progl from the terminal first, and then run DaVinci Resolve from that same terminal, but yeah that's it.

You could also just edit the .desktop file for DaVinci Resolve in order to add those envvars to the beginning of the Exec= command.

Ashark commented on 2020-08-09 14:44 (UTC)

@bobolin @licensed fixed in 20.30_1109583-1

licensed commented on 2020-08-07 19:07 (UTC)

@bobolin sabe problem here: error: failed to commit transaction (conflicting files) /opt/amdgpu/share/drirc.d/10-amdgpu-pro.conf exists in both 'amdgpu-pro-libgl' and 'lib32-amdgpu-pro-libgl' Errors occurred, no packages were upgraded. ==> WARNING: Failed to install built package(s). warning: package amdgpu-pro-installer failed to build, skipping

bobolin commented on 2020-08-06 12:05 (UTC) (edited on 2020-08-06 12:05 (UTC) by bobolin)

This PKGBUILD doesn't work.

error: failed to commit transaction (conflicting files) /opt/amdgpu/share/drirc.d/10-amdgpu-pro.conf exists in both 'amdgpu-pro-libgl' and 'lib32-amdgpu-pro-libgl' Errors occurred, no packages were upgraded. ==> WARNING: Failed to install built package(s). warning: package amdgpu-pro-installer failed to build, skipping

ganthore commented on 2020-07-30 04:28 (UTC)

@gardotd426 ...aaaand I now I finally understand the root of the problem per your criticism. Seriously, I was like "WAT, I read the comments, what's he on about??"

Anyway, my initial Google search for amdgpu-pro-installer dropped me on page 5 of the comments for some silly reason. That shows me for trusting stuff on the first click.

ganthore commented on 2020-07-30 04:15 (UTC)

@gardotd426 I did read prior comments. This response was specifically aimed at the very recent 20.20 upgrade, not older versions where people tried to force upgrades by manually editing the PKGBUILD to stuff pre 20.20. Note that the last 19.30* stuff was working fine.

By working fine, I mean Davinci Reslove still worked. Gutting this entire stack and attempting to run off the opencl-amdgpu package results in instant crashing.

For now, I'm just reverting to 370d39c63ddc using the 19.30* stuff so I can continue editing videos.

gardotd426 commented on 2020-07-29 08:29 (UTC)

Lord, I looked into debtap, and it's a complete dumpster fire unless you're just flat converting .debs. Using it to create PKGBUILDs is a nightmare, it'll flat-out fail if the package doesn't contain a ./usr/bin directory (so if it's a package without any binaries, like a lib package, or something that goes in /opt or /etc), because of the way they wrote the script.

Someone filed a bug report on the github for it, and the dude didn't read it, said "if you don't have a /usr/bin, your installation is broken, you need to reinstall," and closed the issue - seriously. When it's actually the script itself that's broken.

That sucks, I was super excited to find a script that would create PKGBUILDs from .deb packages. It does seem to work fine for flat-out conversion from .deb to .pkg.tar though, so there's that.

gardotd426 commented on 2020-07-29 05:58 (UTC)


"It was because of strange behavior of debtap. Previously, there was libgcc1 dependency, which was converted to None by debtap. But current version has libgcc-s1 dependency, which is converted to gcc by debtap."

Yeah I've always used dpkg-deb -c instead of debtap, it doesn't pull dependencies, and it takes more work, but it also doesn't cause broken stuff to get added. I just run dpkg-deb -c package.deb and get a list of the file list, then in the PKGBUILD I have the command to move those to the .pkg, and figure out the dependencies some other way. Unfortunately there's no real good solution, I wish we had better dependency conversion tools/databases, where you could search for a dependency on Debian/Ubuntu and find it's alternative on Arch or wherever else.

gardotd426 commented on 2020-07-29 05:52 (UTC)

@ganthore read the previous comments before posting, please.

Both of your issues have already been discussed.

The dependencies missing are an error, they're not supposed to be in the PKGBUILD, and you can't use the full AMDGPU PRO stack on Arch Linux anyway, only the standalone bits (so the OpenCL driver, the vulkan drivers, etc., but not the libgl driver or the full stack).

ganthore commented on 2020-07-29 03:36 (UTC)

libgl1 and lib32-gcc have no deps available in aur and results with the following error before installation:

❯ makepkg -si --skippgpcheck --skipchecksums --nocheck --ignorearch ==> WARNING: The package group has already been built, installing existing packages... ==> Installing amdgpu-pro-installer package group with pacman -U... loading packages... resolving dependencies... warning: cannot resolve "libgl1", a dependency of "amf-amdgpu-pro" warning: cannot resolve "lib32-gcc", a dependency of "lib32-amdgpu-pro-libgl" warning: cannot resolve "lib32-gcc", a dependency of "lib32-opencl-amdgpu-pro-orca" warning: cannot resolve "lib32-gcc", a dependency of "lib32-vulkan-amdgpu-pro" :: The following packages cannot be upgraded due to unresolvable dependencies: amf-amdgpu-pro lib32-amdgpu-pro-libgl lib32-opencl-amdgpu-pro-orca lib32-vulkan-amdgpu-pro

I'm also noticing a black screen after force upgrading. I expect SDDM to load. Using an RX580. Removing the packages allows SDDM to load correctly.

apaz commented on 2020-07-28 14:14 (UTC)

"DaVinci Resolve doesn't work with just the OpenCL driver? I wasn't aware it required the OpenGL driver as well."

DaVinci Resolve needs his specific OpenGL profile (under license?). This is only present in amdgpu-pro and not in amdgpu.

Ashark commented on 2020-07-28 13:25 (UTC)

It's just a matter of removing lib32-gcc from the dependencies

I have also noticed, that it has some mess with detecting hwe vs non-hwe version, so I should fix that as well.

I'm not sure why it was added, it wasn't there before.

It was because of strange behavior of debtap. Previously, there was libgcc1 dependency, which was converted to None by debtap. But current version has libgcc-s1 dependency, which is converted to gcc by debtap.

gardotd426 commented on 2020-07-28 02:39 (UTC)

@kode54 I actually tried that a while back, wouldn't work, but you'd think it would. It might be because I didn't install the full stack and just the libgl, vulkan, and opencl components.

I wish there was a way to make the full stack work on Arch, but it seems like it's just flat-out incompatible, which is rare to find (though usually when you do find it, it's proprietary).

kode54 commented on 2020-07-28 00:02 (UTC)

In that case, a dirty trick you can do, if you're feeling particularly nutty:

You can log into your desktop environment, then install the amdgpu pro libgl packages, and then all successively launched apps will use those libgl drivers.

You then have to remove them before you can log back into another session, or before you restart your desktop manager, if you use one.

gardotd426 commented on 2020-07-27 23:31 (UTC)

Yeah unfortunately the opencl package is enough for stuff like Blender, but DR needs libgl too.

Also, the vulkan-amdgpu-pro and lib32-vulkan-amdgpu-pro are similarly standalone.

kode54 commented on 2020-07-27 23:20 (UTC)

@gardotd426, DaVinci Resolve doesn't work with just the OpenCL driver? I wasn't aware it required the OpenGL driver as well.

Anyone following this repository, it isn't really necessary to install all of the packages of this kit for some programs. Sometimes, all you need is the OpenCL driver for your card (Orca for the RX 480, for instance) and the core packages which install the library search paths for everything.

Ashark commented on 2020-07-27 19:40 (UTC)

@gardotd426, I will fix it, but a bit later.

gardotd426 commented on 2020-07-27 16:03 (UTC)

@uberben yeah the libgl pro drivers haven't worked on Arch in quite a while. Basically if you have an AMD GPU, you can't use Davinci Resolve on Arch Linux, you have to use one of the distros that's officially supported by the AMD PRO drivers.

@Ashark please, fix the broken dependency for lib32-vulkan-amdgpu-pro, it's been a few days now and no response. It's just a matter of removing lib32-gcc from the dependencies (it's also listed under the dependencies elsewhere in the PKGBUILD), as the package does not exist. I'm not sure why it was added, it wasn't there before.

uberben commented on 2020-07-27 14:18 (UTC)

I'm experiencing similar issues as others here. If amdgpu-pro-libgl is installed at boot, Xorg segfaults while trying to start GDM. If I remove the package I can get into Gnome fine, but Davinci Resolve fails to start. Re-installing this package while in Gnome allows DR to launch, but GDM fails to launch again on reboot.

I'm using an RX 480. Let me know if there is anything I can do to help diagnose the issue further.

gardotd426 commented on 2020-07-25 07:52 (UTC) (edited on 2020-07-25 07:53 (UTC) by gardotd426)

I'm not sure where to go from here, the AUR doesn't allow for reporting broken packages, only out of date ones (which this isn't), orphaned ones (which this doesn't seem to be) and requests for deletion (which I don't want to see). I'll just reiterate again that this package is definitely broken, you can see the big red letters under dependencies because there's no such package as lib32-gcc. You can't install a package if it lists dependencies that don't exist... Obviously I was able to upgrade by pulling down the PKGBUILD and removing the offending dependencies (it's listed as a dep for multiple packages in the PKGBUILD), but you're not supposed to have to do that.

gardotd426 commented on 2020-07-24 11:46 (UTC)

@Ashark you done goofed.

There's no such package as lib32-gcc, so no one can install this package (or upgrade if it was already installed).

Ashark commented on 2020-07-24 02:56 (UTC)

@All, Do anyone have a laptop with integrated AMD graphics? Could you please test it with this driver? I wanted to cover this configuration in script.

MrTBuddy commented on 2020-07-20 13:33 (UTC)

Hi and sorry for the late answer. I was busy the last days. Tonight i will try to build the first package and try installation. I'll get back to you as soon as I know more

Ashark commented on 2020-07-10 23:42 (UTC)

apaz, the whole project of the PKGBUILD generator is based on parsing deb files, not rpm. The reason is that Ubuntu uses more recent kernel than CentOS. So, it is more chances that ubuntu's version driver will work with Arch's kernel.

apaz commented on 2020-07-10 15:00 (UTC)

An idea from an incompetent: since not only the amd driver has changed, but also Ubuntu 20.04 compared to the previous LTS. Maybe it's better to use as a basis for pkgbuild, the driver for RedHat/CentOS? After all for DaVinci Resolve is the OS with more support, judging by the BlackMagic forum.

Ashark commented on 2020-07-10 07:04 (UTC) (edited on 2020-07-18 02:41 (UTC) by Ashark)

MrTBuddy, thank you, appreciated. I just recently got access to machine with AMD GPU, so I also could test it. What I just did is downloaded the archive =)

There is some strange thing, that DR starts working right after installing amdgpu-pro-libgl. But my machine stucks at graphical target after rebooting. So I guess there should be a way how to launch dr with amdgpu pro libraries, and mask them for the rest of the system. However, I currently do not know exactly how to achieve that.

MrTBuddy commented on 2020-07-10 05:25 (UTC)

Hi everyone. I have taken care of the matter and am trying to update the package. However, the new driver package from AMD has received many changes and a lot has to be adapted. I will report back when I have shot my installation. ;-)

lsrzj commented on 2020-06-21 13:51 (UTC) (edited on 2020-06-21 13:54 (UTC) by lsrzj)

SDDM is crashing if amdgpu pro is installed and gives a coredump. The symptom is a black screen with SDDM's cursor, no greeter. Here is the content of the coredump

       PID: 53487 (sddm-greeter)
       UID: 975 (sddm)
       GID: 975 (sddm)
       Signal: 6 (ABRT)
       Timestamp: Sun 2020-06-21 10:34:57 -03 (12min ago)
       Command Line: /usr/bin/sddm-greeter --socket /tmp/sddm-:0-ccIAmU
       Executable: /usr/bin/sddm-greeter
       Control Group: /user.slice/user-975.slice/session-c4.scope
       Unit: session-c4.scope
       Slice: user-975.slice
       Session: c4
       Owner UID: 975 (sddm)
       Boot ID: c300040f9ec648e69d0ea823fd9d32bb
       Machine ID: 53272113067949b081473dfe28d80f1a
       Hostname: lenovo-pc
       Storage: /var/lib/systemd/coredump/core.sddm-greeter.975.c300040f9ec648e69d0ea823fd9d32bb.53487.1592746497000000000000.lz4 (inaccessible)
       Message: Process 53487 (sddm-greeter) of user 975 dumped core.

            Stack trace of thread 53487:
            #0  0x00007fa8140e7355 raise ( + 0x3c355)
            #1  0x00007fa8140d0853 abort ( + 0x25853)
            #2  0x00007fa8144f99ac _ZNK14QMessageLogger5fatalEPKcz ( + 0x909ac)
            #3  0x00007fa8101f3293 n/a ( + 0x7293)
            #4  0x00007fa8101f379f n/a ( + 0x779f)
            #5  0x00007fa814b3cd9e _ZN14QOpenGLContext6createEv ( + 0x182d9e)
            #6  0x00007fa8101f6808 n/a ( + 0xa808)
            #7  0x00007fa8101f6f39 n/a ( + 0xaf39)
            #8  0x00007fa8159359c5 _ZN13QSGRenderLoop8instanceEv ( + 0x1d39c5)
            #9  0x00007fa8159b85ee _ZN19QQuickWindowPrivate4initEP12QQuickWindowP19QQuickRenderControl ( + 0x2565ee)
            #10 0x00007fa815a23500 _ZN10QQuickViewC1EP7QWindow ( + 0x2c1500)
            #11 0x000055ed70b57f25 _ZN4SDDM10GreeterApp16addViewForScreenEP7QScreen (sddm-greeter + 0x38f25)
            #12 0x000055ed70b58c7c _ZN4SDDM10GreeterApp7startupEv (sddm-greeter + 0x39c7c)
            #13 0x00007fa814747fef _ZN7QObject5eventEP6QEvent ( + 0x2defef)
            #14 0x00007fa81471b69a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent ( + 0x2b269a)
            #15 0x00007fa81471e183 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData ( + 0x2b5183)
            #16 0x00007fa814774bd4 n/a ( + 0x30bbd4)
            #17 0x00007fa812dc543c g_main_context_dispatch ( + 0x5243c)
            #18 0x00007fa812e12fa9 n/a ( + 0x9ffa9)
            #19 0x00007fa812dc4221 g_main_context_iteration ( + 0x51221)
            #20 0x00007fa814774211 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE ( + 0x30b211)
            #21 0x00007fa81471a01c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE ( + 0x2b101c)
            #22 0x00007fa8147224a4 _ZN16QCoreApplication4execEv ( + 0x2b94a4)
            #23 0x000055ed70b38c05 main (sddm-greeter + 0x19c05)
            #24 0x00007fa8140d2002 __libc_start_main ( + 0x27002)
            #25 0x000055ed70b38f3e _start (sddm-greeter + 0x19f3e)

            Stack trace of thread 53488:
            #0  0x00007fa8141a005f __poll ( + 0xf505f)
            #1  0x00007fa81574463b n/a ( + 0xc63b)
            #2  0x00007fa81574637b xcb_wait_for_event ( + 0xe37b)
            #3  0x00007fa810e1ac51 n/a ( + 0x5dc51)
            #4  0x00007fa814536e0f n/a ( + 0xcde0f)
            #5  0x00007fa813d45422 start_thread ( + 0x9422)
            #6  0x00007fa8141aabf3 __clone ( + 0xffbf3)

            Stack trace of thread 53489:
            #0  0x00007fa8141a005f __poll ( + 0xf505f)
            #1  0x00007fa812e12f38 n/a ( + 0x9ff38)
            #2  0x00007fa812dc4221 g_main_context_iteration ( + 0x51221)
            #3  0x00007fa814774211 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE ( + 0x30b211)
            #4  0x00007fa81471a01c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE ( + 0x2b101c)
            #5  0x00007fa814535c32 _ZN7QThread4execEv ( + 0xccc32)
            #6  0x00007fa810d4e098 n/a ( + 0x17098)
            #7  0x00007fa814536e0f n/a ( + 0xcde0f)
            #8  0x00007fa813d45422 start_thread ( + 0x9422)
            #9  0x00007fa8141aabf3 __clone ( + 0xffbf3)

lucasrizzini commented on 2020-06-10 15:55 (UTC)

Will anyone update this?  

kode54 commented on 2020-05-16 22:19 (UTC)

@Arsen6331 Installing the libGL subpackages is known to cause issues with Xorg, as well as Wayland compositors. It is unknown if they will ever work outside of the supported distributions.

Arsen6331 commented on 2020-05-16 21:35 (UTC)

Installing @hedgepigdaniel PKGBUILD makes Xorg coredump.

panospolychr commented on 2020-04-27 15:12 (UTC)

@kode54 ok thanks but now we will need PKGBUILD for libgbm because amdgpu_drv won't load.

kode54 commented on 2020-04-26 02:47 (UTC)

@panospolychr: You need to drop @hedgepigdaniel's PKGBUILD into the full Git clone of this AUR package, as there are included source files.

panospolychr commented on 2020-04-24 09:56 (UTC)

@hedgepigdaniel I tried to make amdgpu-pro 20.10 packages using your PKGBUILD but i'm getting this message "==> ERROR: install file (amdgpu-core-meta.install) does not exist or is not a regular file."

kode54 commented on 2020-04-20 01:24 (UTC)

Would there be any point to supporting the DKMS packages contained within? One of them contains a different version of the AMDGPU kernel module, while the other contains its own copy of AMD's firmware blobs.

ThomasZeGerman commented on 2020-04-19 15:42 (UTC)

installing this package makes my sddm coredump when it tries to create a opengl context

hedgepigdaniel commented on 2020-04-18 07:24 (UTC)

@kode54 No one has pushed anything out, hence why this package is out of date, and even if they had, they would have no responsibility at all to you.

For the record, AMF video encoding works for me with the PKGBUILD I posted, but installing the libgl packages broke GDM.

kode54 commented on 2020-04-18 07:11 (UTC)

Verified the the 20.10.1048557 does not have working libGL or ORCA OpenCL on my RX 480. Does anyone even test these things before attempting to push them out?

hedgepigdaniel commented on 2020-04-18 05:28 (UTC)

Here's and updated PKGBUILD (modified from @neatherm's one) for the released (not preview) 20.10 version:

kode54 commented on 2020-03-29 09:07 (UTC)

Yeah, I'm gonna call crap on the 20.10 EPB. Any attempt to use Blender to render using it, and my whole GPU locks up the PCIe bus. If I don't quickly switch to a TTY to kill Blender, my desktop will just lock up, period.

The 19.50 Orca driver works fine on my RX 480, though.

kode54 commented on 2020-03-29 04:58 (UTC) (edited on 2020-03-29 05:00 (UTC) by kode54)

How many of the packages have you installed? I only installed:


Using an RX 480. I’ve also kind of stopped using Linux for now, since within 20 minutes of booting I now get a pcie bus error with my gpu and kernel panic.

naetherm commented on 2020-03-28 05:55 (UTC)

@kode54: Really? I'm also using gdm without any problems.

kode54 commented on 2020-03-27 06:52 (UTC)

@naetherm I still can't make the libgl packages work with gdm, logging out of my desktop after installing them results in gdm crashing itself. The Vulkan drivers work, as do the Orca OpenCL drivers.

naetherm commented on 2020-03-26 06:39 (UTC)

In the last days AMD released an early preview of 20.10 drivers, available here:

I've updated the PKGBUILD of this package. Installation is working fine for me. Available here:

But be careful when trying: Maybe I've missed something or have overlooked something.

kode54 commented on 2020-03-26 01:11 (UTC)

Naetherm's PKGBUILD needed a bit of modification. Also, in my personal setup, I've removed the PKG_EXT override, since zstd compression has very little overhead on the process compared to the old default of xz.

I still can't make my desktop manager work or desktop log in with the libGL packages installed, so I've just decided to not bother with those for now.

apaz commented on 2020-03-02 09:16 (UTC)

In Ashark's PKGBUILD I noticed that the /19.50/ directory is missing in the source path. Could this be what is compromising the installation? Naetherm's PKGBUILD has it. Another difference is: backup=(etc/amd/amdapfxx.blb) Which in Naetherm is: backup=(etc/gbm/gbm.conf) Why the difference?

hedgepigdaniel commented on 2020-02-20 13:05 (UTC)

for what it's worth, @naetherm 's patched PKGBUILD worked fine for my purpose which was to use the AMFh.264 encoder in ffmpeg. 19.30 did not work on my 5600XT (encoded video was black).

Posich commented on 2020-02-08 04:07 (UTC) (edited on 2020-02-08 04:35 (UTC) by Posich)

19.50 won't work for me. Tried a few things but troubleshooting is witch-craft at best to me.

I had to modify the PKGBUILD you posted to get pacman to allow the install:


package_lib32-amdgpu-pro-libGL () {
# extra_commands:

I added:

rm "${pkgdir}"/opt/amdgpu/share/drirc.d/10-amdgpu-pro.conf

Otherwise it came into conflict with the non-lib32 version because they both try to install that file.

Also have to delete some library symlink under /opt that's left behind after uninstalling the 19.30 packages. I forget which lib, pacman names it when I try installing with 'pacman -U *.pkg.tar'

After installation I did 'systemctl disable sddm' before rebooting so I'd get a terminal, which I'm sure isn't nmecessary but my luck with things like this tends to lean to catastrophe so I wanted to boot to a terminal for safety.

'systemctl start sddm' resulted in a crash. The only Xorg log I know to check(like I said, it's witchcraft to me), is /var/log/Xorg.0.log which the relevant bit seems to be(I'm running two GPUs BTW, the onboard intel and a Radeon RX 5700XT for a dual monitor setup):

[    29.547] (II) Initializing extension DRI2
[    29.549] (EE) intel(G0): sna_mode_shutdown_crtc: invalid state found on pipe 0, disabling CRTC:45
[    29.555] (EE) 
[    29.555] (EE) Backtrace:
[    29.555] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x4d) [0x556359ded76d]
[    29.555] (EE) 1: /usr/lib/Xorg (0x556359d3a000+0xa9cf8) [0x556359de3cf8]
[    29.555] (EE) 2: /usr/lib/ (0x7f331f5b7000+0x3bfb0) [0x7f331f5f2fb0]
[    29.555] (EE) 3: /usr/lib/ (amdgpu_bo_export+0x9e) [0x7f331e46204e]
[    29.555] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/ (0x7f32cca39000+0x1637b53) [0x7f32ce070b53]
[    29.555] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/ (0x7f32cca39000+0x13ab833) [0x7f32cdde4833]
[    29.555] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/ (0x7f32cca39000+0x13bd7dd) [0x7f32cddf67dd]
[    29.555] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/ (0x7f32cca39000+0x12317af) [0x7f32cdc6a7af]
[    29.555] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/ (eglCreateImageKHR+0x483) [0x7f32cdd33f33]
[    29.555] (EE) 9: /usr/lib/xorg/modules/ (glamor_egl_create_textured_pixmap_from_gbm_bo+0x90) [0x7f331b3934b0]
[    29.555] (EE) 10: /usr/lib/xorg/modules/drivers/ (0x7f331f780000+0x1bd7e) [0x7f331f79bd7e]
[    29.555] (EE) 11: /usr/lib/xorg/modules/drivers/ (0x7f331f780000+0xee30) [0x7f331f78ee30]
[    29.555] (EE) 12: /usr/lib/Xorg (0x556359d3a000+0x67e9b) [0x556359da1e9b]
[    29.555] (EE) 13: /usr/lib/Xorg (0x556359d3a000+0x385b8) [0x556359d725b8]
[    29.555] (EE) 14: /usr/lib/ (__libc_start_main+0xf3) [0x7f331f5de153]
[    29.555] (EE) 15: /usr/lib/Xorg (_start+0x2e) [0x556359d733be]
[    29.555] (EE) 
[    29.555] (EE) Segmentation fault at address 0x10
[    29.555] (EE) 
Fatal server error:
[    29.555] (EE) Caught signal 11 (Segmentation fault). Server aborting
[    29.555] (EE) 
[    29.555] (EE) 
Please consult the The X.Org Foundation support 
     at <>
 for help. 
[    29.555] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    29.555] (EE) 
[    29.555] (II) AIGLX: Suspending AIGLX clients for VT switch
[    29.610] (EE) Server terminated with error (1). Closing log file.

The full log is at

Sorry if that's not very helpful. I used to be better at tracking down issues like this but ADD doesn't let me stay on one hobby for very long and I forgot most of what I knew back then. :(

Let me know if there's any more info I could provide.

apaz commented on 2020-02-04 16:50 (UTC)

It's not working for me either, it doesn't start XOrg and I have to switch to the shell. Many errors "display not recognized" (and sddm), but without being able to determine the exact cause.

Ashark commented on 2020-02-04 09:40 (UTC)

@apaz, install files are in the same repository. At the moment, they are not different from the same files in AUR. But anyway, 19.50 version is not working for me.

apaz commented on 2020-02-04 09:19 (UTC)

Trying to install amdgpu-pro 19.50, it locks immediately with the following error:

$ makepkg -si ERROR: install file (amdgpu-core-meta.install) does not exist or is not a regular file.

My system: chipset: x570 cpu: amd 3700x gpu: amd rx 5700 xt Tried with both mesa and mesa-git Uninstalled opencl and vulkan before trying to install amdgpu-pro.

Ashark commented on 2020-01-18 18:55 (UTC)

nyanmisaka, yes, of course uninstallation will solve the X problem =) I mean I do not know how to make amdgpu-pro 19.50 to work properly.

nyanmisaka commented on 2020-01-18 11:25 (UTC)

Uninstall *amdgpu-pro-libgl from this 19.50 package may resolve the X problem.

Ashark commented on 2020-01-17 21:25 (UTC)

I have made an attempt to update to 19.50, but it is not working for me. Here it is:

After installing and rebooting, my X could not be loaded. I do not know what is the problem. If you have suggestions, please advise.

Ashark commented on 2020-01-11 23:13 (UTC)

Yes, I am planning to update. But I currently have some problems in real life. I have already seen changes in brief. They have omitted most 32 bit packages, renamed roct as you said, and omitted gbm1 packages. If you wish, you could try to update it and test it on your own, I have created update instructions in readme. Otherwise, wait until I make an update.

naetherm commented on 2020-01-11 12:29 (UTC)

Are you working on an upgrade for 19.50? I did some work regarding such an upgrade but don't know I everything is correct.

Mainly the libraries roct-amdgpu-pro were renamed to hsakmt-roct-amdgpu-pro and some version updates. I don't know how you would deal with additional libraries like libdrm2, glamor, etc. In the current version those libraries are left out.

The PKGBUILD can be found here:

Ashark commented on 2019-12-09 20:52 (UTC) (edited on 2022-03-07 22:43 (UTC) by Ashark)

PKGBUILD generator is located here:

AMDGPU PRO wiki page:

New versions will appear here:

commented on 2019-12-01 12:42 (UTC)

I had restored my system after booting in bash mode and deleting all these packages... its so strange how does this breaks my display manager SDDM while it uses only my primary Intel GPU....

commented on 2019-12-01 08:34 (UTC)

This broke my system. I only see a black screen with a mouse pointer moving.

Ashark commented on 2019-11-30 21:53 (UTC)

Updated to 19.30_934563-1

TomCatT commented on 2019-10-18 18:30 (UTC)

Before I found out about a different script for 19.04, I had to install 18.04 just test out amdgpu on Ubuntu.

If I install on Manjaro it'll work but it breaks Vulkan. Out of the box, the Radeon VII renders really slow.

@Ashark - Still, thank you for all that you have done. I'll continue to test it out some more because DKMS gives me errors too.

(TimeShift helps out a lot if something goes wrong)

freefreeno commented on 2019-10-18 18:20 (UTC)

@Ashark I have a black screen with moving mouse pointer. I can get to dell splash screen only. Can we please see if your script works in Kbuntu 19.10 and advise me what to install first before I try to install the graphics. Ubuntu 18.04 runs like a champ with 0 errors so I have to do something. Thanks for all the help.

freefreeno commented on 2019-10-18 07:16 (UTC)

@ Ashark so I see at the bottom of the page about the black screen.I believe this is what happened to me when I tried it so now I really have no idea if I should try it again or not but I believe I will. I have a switch to disable switchable graphics in Bios but I am worried about heating problems. I use my PC a lot. And like you I see no info on the other packages.

freefreeno commented on 2019-10-18 07:01 (UTC)

@Ashark And thank you for sure. let me ask you since the PC came with Ubuntu would I be better off in Ubuntu. I really don't care for Ubuntu but for for the sake having the same packages what is your opinion?? I would be I guess trying Kubuntu 19.10 or .04 because my wifi is too new for KDE neon installer or Kubuntu lts.

Ashark commented on 2019-10-18 05:50 (UTC)


freefreeno commented on 2019-10-18 05:28 (UTC) (edited on 2019-10-18 05:31 (UTC) by freefreeno)

@Ashark And that would so greatly appreciated because for someone like me that has only ever had Intel up until this point I am feeling a little confused. I have used Arch for 2 years and when I got this new AMD Pro card for some reason I can install Arch base and make it thru the first reboot with no problem but when I install plasma desktop as I have done a million times I just get a black screen. I am on manjaro now because of it.I am sure I am missing something probably about the drivers but I am not sure. I tried 4 times before I gave up so I did try. Any help or wiki edits to help would be greatly appreciated.I have been contemplating all day moving to Kubuntu 19.04 or 19.10 because Ubuntu came oem on the laptop but it is gnome and I don't use gnome. I am stuck. I have a ton or errors in the logs and with the OEM Ubuntu had 0 errors. Also I normally enable early KMS on intel but I am not sure whether I can do that or not now either.

Ashark commented on 2019-10-18 05:16 (UTC)

@freefreeno I have just read your comment on my youtube video. I think I will edit the AMDGPU PRO page to contain more extensive information, but I do not know all details to be honest.

freefreeno commented on 2019-10-18 05:12 (UTC)

Can someone please tell me if this and the lib32-amdgpu-pro-libgl are the only two packages to install to get this up and going. I have intel driver and the normal amdgpu already but the wiki just states to install these two and that is it.It would really be of help to just to pin a comment here with all the packages needed and whether they will automatically install or if we need to install things first and afterwards. Also do we need to be in the video group like in Ubuntu? One more thing is having xf86-video-intel required or can we run just the modesetting driver and xf86-video-amdgpu then the the pro diver on top. I have a new laptop with AMD Radeon PRO and this is the only reason I am wanting to install this. Please help clarify if you don't mind. If you have the PRO graphics card installing the PRO driver is recommended correct ???

Ashark commented on 2019-10-05 17:06 (UTC)

@aDogCalledSpot Can you provide exact actions, so I could reproduce?

aDogCalledSpot commented on 2019-10-05 16:50 (UTC)

I get the following error message multiple times when trying to install on Arch with kernel 5.3.1

==> ERROR: install file (amdgpu-pro-core-meta.install) does not exist or is not a regular file.

Kepos commented on 2019-08-28 15:23 (UTC)

@Ashark Did not get what you are trying to point me to, sorry. But, I got it running on myself lately. Checked Kernel first, as I knew the driver only works with higher then 4.15-Kernel, but I have 5.2.9 installed. Then I tried to install vulkaninfo ( which brought up a conflict between 'mesa-demo' and 'glxinfo'. De-installed 'glxinfo' and so I got vulkaninfo and additionally now the requested vulkan driver up and running.

Ashark commented on 2019-08-25 17:34 (UTC)

@Kepos Sorry, I cannot understand what is your problem. Probably, you have missed to read vulkan article on archwiki.

Kepos commented on 2019-08-25 16:40 (UTC)

The installation worked without any issue with Arcolinux Deepin edition. Unfortunately, I can't find Vulkan support and also Steam's Proton doesn't work correctly without. Mesa + Vulkan was pre-installed, then I installed the above snap. Amdgpu-pro has built-in Vulkan support. Did I miss something?

Ashark commented on 2019-08-17 17:55 (UTC)

@tigr72 force remove it: pacman -Rdd libdrm-amdgpu

tigr72 commented on 2019-08-17 16:14 (UTC)

dependencies could not be satisfied: installing amd gpu-core-meta (19.30_855429-1) breaks the 'amd gpu-core-meta=19.30_838629-1' dependency required by lib32-libdrm-amdgpu installing amd gpu-core-meta (19.30_855429-1) breaks the 'amd gpu-core-meta=19.30_838629-1' dependency required by libdrm-amdgpu

Ashark commented on 2019-08-16 02:14 (UTC) (edited on 2019-08-17 08:47 (UTC) by Ashark)

@lod you are right. They have released 19.30-855429 for all supported distributions and gpus. Here is a link to release notes page:

Ashark commented on 2019-07-11 15:36 (UTC)

@tfla this is ok. They renamed a hip package, so did I.

tfla commented on 2019-07-10 11:30 (UTC) (edited on 2019-07-10 11:31 (UTC) by tfla)

I needed to pacman -R opencl-amdgpu-pro-hip before updating to 19.30_838629-1, also I get this warning for every package after the first:

warning: amdgpu-core-meta-19.30_838629-1 is up to date -- reinstalling
warning: amdgpu-pro-core-meta-19.30_838629-1 is up to date -- reinstalling
warning: amdgpu-pro-libgl-19.30_838629-1 is up to date -- reinstalling
warning: amf-amdgpu-pro-19.30_838629-1 is up to date -- reinstalling
warning: hip-amdgpu-pro-19.30_838629-1 is up to date -- reinstalling
warning: lib32-amdgpu-pro-libgl-19.30_838629-1 is up to date -- reinstalling
warning: lib32-libdrm-amdgpu-19.30_838629-1 is up to date -- reinstalling
warning: lib32-opencl-amdgpu-pro-orca-19.30_838629-1 is up to date -- reinstalling
warning: lib32-vulkan-amdgpu-pro-19.30_838629-1 is up to date -- reinstalling
warning: libdrm-amdgpu-19.30_838629-1 is up to date -- reinstalling
warning: opencl-amdgpu-pro-comgr-19.30_838629-1 is up to date -- reinstalling
warning: opencl-amdgpu-pro-dev-19.30_838629-1 is up to date -- reinstalling
warning: opencl-amdgpu-pro-orca-19.30_838629-1 is up to date -- reinstalling
warning: opencl-amdgpu-pro-pal-19.30_838629-1 is up to date -- reinstalling
warning: roct-amdgpu-pro-19.30_838629-1 is up to date -- reinstalling
warning: roct-amdgpu-pro-dev-19.30_838629-1 is up to date -- reinstalling
warning: vulkan-amdgpu-pro-19.30_838629-1 is up to date -- reinstalling

Ashark commented on 2019-07-08 23:36 (UTC)

@PedroHLC This is to not compress packages after building. You can remove it if you like.

PedroHLC commented on 2019-07-08 23:24 (UTC)

Why the PKGEXT=".pkg.tar"?

lod commented on 2019-07-08 21:24 (UTC)

It's probably just for day1 support. I think, we will get a new version soon'ish.

Ashark commented on 2019-07-08 21:20 (UTC)

@lod, oh, I see it now, thanks. And also for some reason it is only released for ubuntu (I mean there are no versions for CentOS/RHEL/SLED/SLES). Anyway, I want to see if that is true.

lod commented on 2019-07-08 21:15 (UTC) (edited on 2019-07-08 21:16 (UTC) by lod)

copy&paste from there site:

AMD Radeon™ Product Family Compatibility

This Radeon™ Software for Linux® release is only compatible with the Radeon RX 5700 Series of cards – no other products are supported.

Ashark commented on 2019-07-08 21:11 (UTC) (edited on 2019-07-08 21:12 (UTC) by Ashark)

@lod, what makes you think it support only navi?

lod commented on 2019-07-08 21:08 (UTC) (edited on 2019-07-08 21:13 (UTC) by lod)

It's written right on the AMD site. I only copied the text

And choosing vega or older brings you right to 19.20.

Ashark commented on 2019-07-08 19:10 (UTC)

@lod I think you are not correct. At least I still can see legacy (orca) opencl implementation there, which means it supports gcn4- gpus.

lod commented on 2019-07-08 16:54 (UTC) (edited on 2019-07-08 16:59 (UTC) by lod)

This Radeon™ Software for Linux® release is only compatible with the Radeon RX 5700 Series of cards – no other products are supported.

There is no need to flag this out of date yet.

Ashark commented on 2019-07-08 13:51 (UTC)

@takov751 thanks for notification. I will mark the package base as outdated for now.

takov751 commented on 2019-07-08 09:10 (UTC)

there is a new version with rx 5700 support

Ashark commented on 2019-06-28 16:08 (UTC)

@vario makepkg -si will install all packages provided by this Package Base. Also, those errors of unresolved dependencies should be gone since you are using -s option for makepkg. Try to install needed opencl package first and see if it helps for your task.

vario commented on 2019-06-28 15:57 (UTC)

I'm very confused. The git clone URL is the same for all the components and that is what I used for "makepkg -si". How do I install only the bits I want?

Ashark commented on 2019-06-28 10:44 (UTC)

@vario If you need only OpenCL part, then why are you trying to install lib32-amdgpu-pro-libgl? Btw, could you test if Davinci resolve works for you? I ask because I do not have iGPU AMD hardware. For testing you need to install amdgpu-pro-libgl and also an opencl implementation (I guess opencl-amdgpu-pro-orca for your iGPU).

vario commented on 2019-06-27 12:46 (UTC) (edited on 2019-06-27 14:04 (UTC) by vario)

I'm getting some errors when trying to install. I am running GNOME & Wayland on a Ryzen5 2400G with opencl-mesa installed for GPU computing with boinc. Some boinc stuff is crashing the PC so I thought I'd try with this opencl as well.

loading packages...
resolving dependencies...
warning: cannot resolve "lib32-libx11", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxcb", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxdamage", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxext", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxfixes", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxshmfence", a dependency of "lib32-amdgpu-pro-libgl"
warning: cannot resolve "lib32-libxxf86vm", a dependency of "lib32-amdgpu-pro-libgl"
:: The following package cannot be upgraded due to unresolvable dependencies:

:: Do you want to skip the above package for this upgrade? [y/N] n
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'lib32-libx11' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxcb' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxdamage' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxext' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxfixes' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxshmfence' required by lib32-amdgpu-pro-libgl
:: unable to satisfy dependency 'lib32-libxxf86vm' required by lib32-amdgpu-pro-libgl
==> WARNING: Failed to install built package(s).

I only want the OpenCL libraries from AMD and to carry on with AMDGPU from the kernel (I don't have a PRO graphics card) - is this possible ?

Ashark commented on 2019-06-18 12:41 (UTC)

Good news. I got it working already. But I still need to realize if I could safely omit remaining open components and to map dependencies properly.

davidossahdez commented on 2019-06-13 18:32 (UTC)

@ashark May I suggest Natron. It is available in the AUR and requires OpenGL 2.0 or higher. You can see the system requirements below the download links

Ashark commented on 2019-06-12 21:40 (UTC)

19.20 is out.

Ashark commented on 2019-06-11 15:58 (UTC)

I have heard that some CAD applications require GL extensions, but I do not know which exactly. I also thought that it may be a windows application running with wine.

y6ep3 commented on 2019-06-11 15:52 (UTC)

@ashark you want to test? May be some windows over wine game?

Ashark commented on 2019-06-09 23:00 (UTC)

@adelpozoman I see, thank you. But what about OpenGL? At gentoo wiki it was mentioned about UCSF chimera, but looks that is is not true anymore. And the only such software I know for now is Davinci Resolve.

adelpozoman commented on 2019-06-09 22:54 (UTC)

@ashark Blender requires propietary OpenCl

Ashark commented on 2019-05-14 12:59 (UTC)

Can anybody suggest an application that requires proprietary OpenGL implementation?

kuasha420 commented on 2019-04-28 13:06 (UTC)

@Ashark thanks man you are a saint

Ashark commented on 2019-04-24 18:34 (UTC)

I am currently working on it. I hope I make it in a week and it will work.

kuasha420 commented on 2019-04-24 18:32 (UTC)

I wish AMD just fucking supported arch but that's never gonna happen. I also don't have the know-how's to patch it myself. :(

Ashark commented on 2019-04-20 21:35 (UTC)

19.10 is out.

IhaveAcatAndDog commented on 2019-03-09 16:10 (UTC)

Hi Ashark, I have patch for 18.50, but it's not fully completed for 32 bit libs yet, and I'm testing it now. Please contact me, so I will provide it to you "as is" for review and future improvement and maintenance.

For 18.50: dkms driver is working with linux 4.16.9-1 and xorg version 1.19.6.

Ashark commented on 2019-03-06 07:51 (UTC)

@kuasha420, yes, but later. I am now busy with another project (exploring solution for After I finish with it, i will switch back to repacking amd driver. As for now, you can try to make it yourself and send me a patch.

kuasha420 commented on 2019-03-06 07:45 (UTC)

Will it ever get fixed for 18.50 and newer?

Ashark commented on 2019-02-17 06:50 (UTC)

@kode54 Of course, that need to be updated to 18.50. I am not so familar with amd drivers yet. There is also some new stuff there (f.e. vulkan drivers), which I should repack and test. I wanted to test amd's proprietary drivers with davinci-resolve. Have not done it yet. Patch is wellcome. I can remove binfmt-support from depends list for now (but also I need to test current version).

kode54 commented on 2019-02-17 06:42 (UTC)

Can you people not read? That dependency should have been removed, because systemd already provides the necessary functionality, so that package is redundant.

Also, shouldn’t this be moving toward the 18.50 release, with yet another kernel requirement?

aviallon commented on 2019-02-02 20:23 (UTC)

Hello, added back the binfmt-support package :D

serdarsaglam commented on 2019-01-31 20:20 (UTC) (edited on 2019-01-31 20:26 (UTC) by serdarsaglam)

Hi binfmt-support not found can't install


Ashark commented on 2019-01-21 02:22 (UTC)

@GI_Jack I know. As of comment 2018-10-11 06:08, try to just drop that. I am now trying to make working gpu pasthrough configuration so I could easily test drivers in a virtual environment. If you are interested, please join. I have a problem of a secondary passthrough. See this:

GI_Jack commented on 2019-01-21 02:17 (UTC)

binfmt-support missing dep

Ashark commented on 2019-01-18 00:27 (UTC)

Yes, this package is out of date now. I just prepared it for further updates in a way that it won't clutter pkgbuild's diff with version upgrades. It was maintained by Corngood, he is not interested in this package anymore, so now I got maintaining of it. The plan is the following: - Return Travis ci back - Explore deb packages which are in amd's archive - Repack them to pkgbuild using If you are interested, I invite you to join.

rokero commented on 2019-01-17 21:34 (UTC)

the package is out date,

Olympus593 commented on 2018-10-14 16:49 (UTC)

will this work with GCN 1 cards?

jamespharvey20 commented on 2018-10-11 03:08 (UTC)

Regarding dependency "binfmt-support", it was deleted on 2/28/2018. See

This is because systemd-binfmt replaces its functionality.

Previous comments saying they couldn't find "binfmt-support" on the AUR, but with a link that got to its files will no longer work. I asked about how those files were still accessible but searching for "binfmt-support" didn't find anything at and those files were deleted. If that messes anything up, sorry about that, wasn't my intention.

That said, I'm assuming the dependency of "binfmt-support" can just be removed, since "systemd" is in "base". I haven't tried it, and probably won't be, because downgrading kernels is a no-go for me.

If I'm right, perhaps a 17.40.492261-2 could be released, removing it as the only change.

jamespharvey20 commented on 2018-10-11 03:02 (UTC)

@ illogical123 - I could be wrong, but if I'm understanding this right, isn't AMDVLK really only going to supersede AMDGPU-PRO-VULKAN, not all of AMDGPU-PRO? So, AMDGPU, mesa-libgl, opencl-mesa, and xf86-video-amdgpu would still be used? To me, if that's the case, I can't call AMDGPU-PRO dead like some of those links are. (For Vulkan gaming specifically, sure, perhaps, and Vulkan is only going to get more and more prevalent.)

illogical123 commented on 2018-09-02 19:43 (UTC)

For those eagerly waiting for a never version of AMDGPU-PRO:

"... the current impression from AMD is that AMDVLK is intended to supersede AMDGPU-PRO for Vulkan gaming on Linux"

see also:

psihei4 commented on 2018-09-01 12:40 (UTC)

It's work for PS4 PRO (CUH 7016B)?

bjo commented on 2018-08-23 12:45 (UTC)

I've asked Corngood and he would like to handle the release process when someone makes a PR or might hand over the package to somebody who would like to adopt it.

ModYokosuka commented on 2018-08-03 23:36 (UTC)

I took a stab at upgrading this package at one point. In the process I determined the open source drivers were good enough and stopped using it.

Enverex commented on 2018-08-03 22:42 (UTC)

I assume this is abandoned given that it's now several versions and over half a year out of date?

parkervcp commented on 2018-06-20 20:04 (UTC)

18.20 was released today. What is the potential on updating?

Charadon commented on 2018-05-15 02:22 (UTC)

18.10 has been released, and the benchmarks have been a little impressive. Any possibility for this to be updated?

Tralen commented on 2018-04-23 19:07 (UTC)

The main file is failing checksum validation.

Necrobuffalo commented on 2018-04-12 21:35 (UTC)

I am not able to install amdgpu-pro because it can not resolve this dependency (binfmt-support).

error: can not find the git package needed to handle git sources

Can someone help me?

rawsh commented on 2018-04-04 17:22 (UTC)

I'm having a binfmt support issue as well. I've installed the git version (which is the only one I could find in the aur) but it does not provide the package this wants

hotaru commented on 2018-01-21 02:30 (UTC) (edited on 2018-01-21 02:37 (UTC) by hotaru)

it looks like binfmt-support (listed as a dependency of the amdgpu-pro package) doesn't exist.

EDIT: binfmt-support doesn't show up on, but I managed to find it at

derdigge commented on 2017-12-30 10:41 (UTC)

I tried the package from aur and git, mentioned in pinned comment. I cant install them. cannot resolve "amdgpu-pro-libdrm=17.40.492261-1", a dependency of "xf86-video-amdgpu-pro"

but the packages are made and there. cant find a typo in PKGBUILD

full paste:

pls help

nathan-osman commented on 2017-12-24 06:27 (UTC)

I tried @Noctivivans PKGBUILD with the other files from the archlinuxcn repo. The amdgpu-pro kernel module wouldn't compile with 4.14 or even 4.13, so I tried downgrading the kernel to 4.10 and it succeeded. However, the system then refused to boot, freezing early in the boot process. Single user mode did the same thing so I was forced to recover with a LiveCD.

Noctivivans commented on 2017-12-22 22:43 (UTC) (edited on 2017-12-22 23:29 (UTC) by Noctivivans)

I was able to install version from archlinuxcn PKGBUILD after enabling archlinuxcn repo and fixing some file conflicts in PKGBUILD (fixed version here: I successfully booted system with linux-lts kernel, but I am not sure how to check if pro features are really enabled (my card is not fully supported yet anyway).

Btw, even archlinuxcn PKGBUILD is outdated - I've found more recent driver version here: direct link (requires page above as referer):

Rosen commented on 2017-12-17 11:30 (UTC)

@ozmartian are you sure?

==> Making package: amdgpu-pro-installer 17.40.483984-1 (нд дек 17 11:29:43 GMT 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... [sudo] password for rosen: <br> error: target not found: lib32-libomxil-bellagio error: target not found: lib32-mesa-noglvnd-nogbm error: target not found: lib32-ncurses5-compat-libs error: target not found: mesa-noglvnd-nogbm error: target not found: ncurses5-compat-libs ==> ERROR: 'pacman' failed to install missing dependencies.

ozmartian commented on 2017-12-14 03:41 (UTC)

you can grab the archlinuxcn PKGBUILD from GitHub via:

$ makepkg -is (to build pkg and install + check dependencies)

znmeb commented on 2017-12-04 23:05 (UTC)

This software doesn't even work on Ubuntu 16.04.3 LTS, which AMD supposedly supports!! See

I couldn't even make it work on 16.04.2. I've pretty much given up on AMD.

Svenstaro commented on 2017-12-04 23:00 (UTC)

@Corngood, are you still maintaining this? Otherwise, I'll orphan this package in a bit.

Rosen commented on 2017-11-23 20:34 (UTC)

archlinuxcn do not have such a driver!

Unboxious commented on 2017-11-15 04:23 (UTC) (edited on 2017-11-15 04:24 (UTC) by Unboxious)

@heavysink It still doesn't seem to be working for me, so I ended up downloading the individual files from the github page. I'm getting errors such as, "/etc/xdg/gstomx.conf exists in both 'amdgpu-pro-gst-omx' and 'lib32-amdgpu-pro-gst-omx'". There are 4 other files which conflict on the 32-bit and 64-bit versions. Would it help if I listed those, or is that enough info?

heavysink commented on 2017-11-07 16:17 (UTC)

@Reize Oh gosh I forgot to put amdgpu pro into the configuration file in ArchlinuxCN. Doing it now. My bad.

Raize commented on 2017-11-06 20:29 (UTC)

The 17.40 amdgpu-pro packages in ArchlinuxCN repo no longer seem to exist? Can someone please make a 17.40 package. I've spent a whole weekend trying but it's just beyond me.

Renfield commented on 2017-11-02 11:07 (UTC)

There should not be a problem installing the libraries in /opt/amdgpu-pro/lib/x86_64-linux-gnu/, because it is listed in /etc/ Despite this, I do see a problem with qdirstat being unable to compile, not finding libGL. I think, though, that this conversation should probably be moved to a GitHub issue against archlinuxcn, as we are not talking about this specific package.

riddicc commented on 2017-11-02 06:38 (UTC)

@heavysink: all the libraries were in /opt/amdgpu-pro/lib, but my box expected them in /usr/lib/... and usr/lib/xorg/modules/... maybe i forgot to install something?

laichiaheng commented on 2017-11-01 07:21 (UTC)


heavysink commented on 2017-10-31 18:00 (UTC)

@riddicc: which symlinks? I might have to change something in the PKGBUILD file on archlinuxcn.

riddicc commented on 2017-10-25 12:40 (UTC)

@heavysink: thx for that amdgpu-pro-17.40 package on it supports OpenGL quite good... but: it is slower than 17.30 on Ubuntu 16: 29fps instead of 35fps. it is unable to switch to 2560x1080@60 (just like amdgpu), but amdgpu-pro 17.30 on Ubuntu can do it. somehow i had to add manually some symlinks from /opt to /usr/lib... or is it just my box? :)

heavysink commented on 2017-10-14 19:04 (UTC)

I have included amdgpu-pro 17.30 in ArchlinuxCN repository. It is compatible with my 4.13.6 kernel and xorg 1.19.5. (I am using lightdm and cinnamon) 1. The libgbm provided by mesa is incompatible with amdgpu-pro so I have to package mesa without libgbm (mesa-noglvnd-nogbm). 2. The libglamor shipped with amdgpu-pro is causing problems for Xorg, so I removed it from the package and used the glamor libraries shipped with xorg-server instead. 3. I didn't install amdgpu-pro-dkms (which will fail to build on 4.13.6 and taint the LTS-4.9.56 kernel). 4. I didn't modify the mkinitcpio.conf. 5. I have added a x11 config file (which includes Device and Screen0) in the package to make the driver happy. It turns out to work very well for me. To add the repo: [archlinuxcn] Server =$arch As the packages are signed, archlinuxcn-keyring package must be installed before installing the driver.

nmset commented on 2017-10-13 20:01 (UTC) (edited on 2017-10-13 20:01 (UTC) by nmset)

@ vS0uz4 Not ffmpeg, but ffmpeg2.8 (a vlc requirement).

vS0uz4 commented on 2017-10-13 18:30 (UTC)

@nmset Briefly, I have to downgrade ffmpeg and maybe xorg. I will do the tests and give feedback

nmset commented on 2017-10-13 15:48 (UTC) (edited on 2017-10-13 15:51 (UTC) by nmset)

@vS0uz4 You could downgrade ffmpeg2.8 to 2.8.12-4. ffmpeg2.8 2.8.13-1 crashes X on my laptop (Kaveri + Topaz) and my desktop (RX 480) too. Moreover, xorg 1.19.4-1 fails on my desktop but runs on my laptop. xorg 1.19.3-3 works on my desktop. So there's hardware and software compatibility issues.

vS0uz4 commented on 2017-10-13 14:26 (UTC)

@nmset Thank you! Anyway, it's not working. It generates the package, install it, but when it will start X, it crashes. I'm using a Dell Inspiron 5547 notebook (5000 series), with AMD Radeon R7 M260 graphics card. I have not yet been able to run the graphical driver in Arch Linux.

nmset commented on 2017-10-13 09:43 (UTC)

@vS0uz4 Yep, I noticed. *.so libraries in those directories are not symbolic links to *.so.<version>, and ldconfig complains. I do with it as it's functionally harmless up to now.

vS0uz4 commented on 2017-10-13 01:29 (UTC)

@nmset your PKGBUILD generate this errors: (1/1) instalando amdgpu-pro [#######################################################################################] 100% ldconfig: /opt/amdgpu-pro-32/lib/xorg/modules/extensions/ is not a symbolic link ldconfig: /opt/amdgpu-pro/lib/xorg/modules/extensions/ is not a symbolic link :: Executando hooks pós-transação... (1/1) Arming ConditionNeedsUpdate... is not a symbolic link???

vS0uz4 commented on 2017-10-12 20:50 (UTC)

Does this package have any forecast when it will receive an update?

Corngood commented on 2017-09-16 16:12 (UTC)

If anyone's interested in helping with the 17.30 upgrade, there's a PR at: It builds valid packages, but it still needs work and testing.

nmset commented on 2017-09-10 11:44 (UTC)

@Darkhogg If you don't mind using a non-conventional but functional PKGBUILD, here is mine again :

Darkhogg commented on 2017-09-10 09:34 (UTC)

The maintainer of this package is not likely to keep it up to date, as he no longer uses Arch Linux, as stated in a comment thread on GitHub:

md2prof commented on 2017-08-29 00:31 (UTC)

I believe the released update by AMD to 17.30 will bring 4.10 kernel and Xorg 1.19 support. Any estimation when an update to these packages might be available?

nmset commented on 2017-08-18 21:01 (UTC)

Just FYI : AMD released amdgpu-pro 17.30-465504 that works with Xorg 1.19 with kernel 4.12.6 (the DKMS package is ignored).

awkwardtechdude commented on 2017-08-08 04:45 (UTC)

Will this be updated to 17.20?

hollunder commented on 2017-07-11 05:45 (UTC)

Building this stuff is quite a clusterfuck. Does someone have a list of what to build/install and in which order? Apparently pacman -Rdd libglvnd install mesa-noglvnd before everything else because building that does not work with the amdpro-libdrm.

Vi0L0 commented on 2017-07-03 18:37 (UTC)

@nileshmoodley: I should update pkgs today, but the workaround is very simple: pacman -Rdd libglvnd before installing mesa-noglvnd

nileshmoodley commented on 2017-07-03 17:33 (UTC) (edited on 2017-07-03 17:33 (UTC) by nileshmoodley)

I am unable to install mesa-noglvnd as there are file conflicts which are owned by libglvnd. That's the hang-up for me right now in getting this package to work. I have posted comments on that AUR package to please resolve this issue.

hollunder commented on 2017-07-02 13:19 (UTC)

When I try to downgrade xorg-server I get the following error: warning: cannot resolve "xf86-input-driver", a dependency of "xorg-server" Any idea what to install to provide this?

rsa commented on 2017-06-28 02:35 (UTC)

Latest version (17.20) seems to work properly with Linux > 4.9, not sure about Xorg. I couldn't fix the PKGBUILD to work.

marcoms commented on 2017-06-02 23:34 (UTC)

I managed to downgrade xorg using vi0l0's `xorg118` repo, and linux using the `downgrade` utility, but then I realised mesa-noglvnd was required also. Is it expected to compile mesa to install amdgpu-pro each time?

EndlessEden commented on 2017-05-22 11:11 (UTC)

Issue with mesa-noglvnd- builds against libdrm(2.4.66), one used by AMDGPU-PRO is libdrm(2.4.0), which means compatibility issues with Xorg as well.

znmeb commented on 2017-05-05 21:08 (UTC) (edited on 2017-05-05 21:12 (UTC) by znmeb)

Looks like I need to downgrade the kernel and xorg server first :-( That looks like a nightmare - I couldn't make the AMD GPU stuff work on the Ubuntu 16.04.2 LTS that AMD claims to support either.

Corngood commented on 2017-05-05 18:02 (UTC)

@znmeb Got any more info about which dependencies are failing?

Corngood commented on 2017-05-05 18:01 (UTC)

@gregf Is this consistent? I just ran a build and it pulled down the correct tarball from AMD. Maybe try removing the file?

commented on 2017-05-05 15:14 (UTC)

:: Retrieving package(s)... :: Checking amdgpu-pro-dkms integrity... ==> Making package: amdgpu-pro-installer 17.10.401251-2 (Fri May 5 11:13:52 EDT 2017) ==> Retrieving sources... -> Found amdgpu-pro-17.10-401251.tar.xz -> Found 0001-disable-firmware-copy.patch -> Found 0002-linux-4.9-fixes.patch -> Found 0003-Change-seq_printf-format-for-64-bit-context.patch -> Found 0004-fix-warnings-for-Werror.patch -> Found 0005-add-archlinux-as-build-option.patch ==> Validating source files with sha256sums... amdgpu-pro-17.10-401251.tar.xz ... FAILED 0001-disable-firmware-copy.patch ... Passed 0002-linux-4.9-fixes.patch ... Passed 0003-Change-seq_printf-format-for-64-bit-context.patch ... Passed 0004-fix-warnings-for-Werror.patch ... Passed 0005-add-archlinux-as-build-option.patch ... Passed ==> ERROR: One or more files did not pass the validity check!

znmeb commented on 2017-05-05 09:12 (UTC)

I'm trying to install this on a freshly built Arch system - it's hitting a bunch of unresolved dependencies: :: The following packages cannot be upgraded due to unresolvable dependencies: amdgpu-pro amdgpu-pro-libgl amdgpu-pro-vdpau lib32-amdgpu-pro lib32-amdgpu-pro-libgl lib32-amdgpu-pro-vdpau xf86-video-amdgpu-pro

Corngood commented on 2017-04-08 22:39 (UTC)

I've pushed an update with 17.10. Let me know if you have any problems (preferably with an issue on github). Unfortunately it still requires xorg 1.18 and linux 4.8/4.9.

laichiaheng commented on 2017-03-30 10:29 (UTC)

Can't wait for it to be available for xorg-server1.19 and linux4.10

Kant commented on 2017-03-23 02:14 (UTC)

I've found a mirror of the file: found here: checksum is the same as the pkgbuild, so it seems legit :-D

Kant commented on 2017-03-22 23:40 (UTC)

however I try to download amdgpu-pro-16.60-379184.tar.xz (the apt version), I end up with a 13.6 MB file which is broken. Does anyone have the complete version and can mirror it?

vltr commented on 2017-03-20 18:03 (UTC)

@nmset ok, thanks for the info! so, amdgpu-pro is to be kernel version independent but walking alongside xorg 1.18 ... i wonder if this is just related to the abi version or the xorg version itself ... of course, if this doesn't sound too much bs* from my part, heh.

nmset commented on 2017-03-20 14:54 (UTC)

@vltr No, I'm running xorg 1.18. We are hooked to the Ubuntu clock. They are supposed to release 17.04 with xorg 1.19 and hopefully, amdgpu-pro devs may upgrade their development workstations some time later.

vltr commented on 2017-03-20 14:00 (UTC)

thanks, @nmset! it's a interesting PKGBUILD. i've seen some other stuff on github, too, that may help get some of the "issues" of this package solved. i have no time to see this atm, but i'll hook into it when possible. thanks for sharing your "alien" PKGBUILD file. just for curiosity sakes, are you running xorg 1.19 also? cheers! :)

simon_herbert commented on 2017-03-20 05:18 (UTC) (edited on 2017-03-20 05:18 (UTC) by simon_herbert)

@Kant the link does seem to be right, but I had to download via my browser from

Kant commented on 2017-03-20 01:58 (UTC)

The download link for amdgpu-pro-16.60-379184.tar.xz does not seem to be working correctly, does anyone have a mirror?

nmset commented on 2017-03-19 17:07 (UTC)

@vltr I'm afraid the issue you are referring to may point to two things : DKMS I don't know how to resolve this and I don't try to. INSTALLING I still use my alien dirty PKGBUILD adapted to nowadays :

vltr commented on 2017-03-19 15:41 (UTC) (edited on 2017-03-19 15:45 (UTC) by vltr)

@nmset: I totally agree with you. To put into the right context, I gave that "tip" in case of using dkms modules -- at the time I wrote the comment, it didn't worked with any 4.10.x kernels (out-of-the-box). Any tips regarding this issue? :)

zxvfxwing commented on 2017-03-18 17:30 (UTC)

@Gelmo I'm to lazy to retry install. I wanted to know if with amdgpu-pro I can setup my monitor to 144Hz. atm with xf86 I'm stuck at 120Hz :/

Gelmo commented on 2017-03-18 05:32 (UTC)

@zxvfxwing check the Xorg and/or lightdm logs when you're at that black screen. You should be able to switch to another tty (ctrl+alt+F2 maybe) and login without X, and navigate to /var/log. If it keeps switching you back to the other screen, it's trying to restart X/lightdm; disable then stop the service from tty2.

zxvfxwing commented on 2017-03-17 12:21 (UTC)

I downgraded to xorg-server 1.18 & 4.9 kernel, but nothing to do. At boot I'm stuck on a black screen with a white "_" at topleft corner. I gess lightdm.service doesn't want to start for some reason. When ctrl+z to xorg119 and 4.10 everything works fine. Any suggestions ?

nmset commented on 2017-03-15 14:47 (UTC)

@vltr I'm using amdgpu-pro with kernel 4.10 and 4.11-rc1. One goal of amdgpu-pro was to separate userspace and kernelspace binaries. I don't think one should downgrade the kernel package.

vltr commented on 2017-03-15 13:51 (UTC)

@simon_herbert: in order to use amdgpu-pro, *you have to downgrade some packages*, like xorg-server to version 1.18 and your linux-kernel to 4.8 or 4.9, for some reasons: ABI compatibility, header compatibility, etc. _In my machine_, here's a list of what I have downgraded in order to install amdgpu-pro properly (see final notes at the end): * xorg-server (1.18.4-1) * xorg-server-common (1.18.4-1) * xorg-server-devel (1.18.4-1) * xorg-server-xvfb (1.18.4-1) * xorg-server-xwayland (1.18.4-1) * xf86-input-libinput (0.20.0-1) * xf86-input-evdev (2.10.2-1) * xf86-input-keyboard (1.8.1-2) * xf86-input-mouse (1.9.2-1) * xf86-input-void (1.4.1-2) * xf86-video-fbdev (0.4.4-5) * xf86-video-vesa (2.3.4-2) * mesa (12.0.3-4) * mesa-libgl (12.0.3-4) * lib32-mesa (12.0.3-4) * lib32-mesa-libgl (12.0.3-4) * linux-ck-piledriver (4.9.13-1) ¹ * linux-ck-piledriver-headers (4.9.13-1) ¹ [1] I use the ck patchset in my system, you can simply install linux-lts kernel if you want. Other than that, it's all about your own settings. Final notes: - You can download older packages from the archive: - You should install lib32-libomxil-bellagio from AUR: - You should also install lib32-ncurses5-compat-libs from AUR: - amdgpu-pro installation should have a wiki page of it's own! :)

simon_herbert commented on 2017-03-12 20:03 (UTC)

Trying to install amdgpu-pro through yaourt, and already manually installed missing packages, I'm stuck with it saying that "lib32-mesa: removing lib32-libglvnd deletes needed package from "lib32-libglvnd"" "mesa: removing libglvnd deletes needed package from "libglvnd"" What can I do to repair this?

Vi0L0 commented on 2017-03-11 18:37 (UTC)

Don't know if and how recent update in mesa/xorg-server/libglvnd did touch amdgpu-pro, but it touched catalyst badly ;) If it also touched amfgpu-pro then mayb it will be useful?: for now I've added mesa packages of 17.0.1-1 version to [catalyst]* and [catalyst-stable] - simply copied from archive: 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. * [catalyst] Server =$arch

francoism90 commented on 2017-03-08 21:35 (UTC)

Any luck with AMD R270? I'm unable to start any X-session after downgrading to 1.18 and using linux 4.9. After upgrading to the latest xorg-server, all seems to work fine, but of coures I'm unable to use amdgpu-pro.

Berg commented on 2017-02-27 15:38 (UTC) (edited on 2017-02-27 15:41 (UTC) by Berg)

Thanks! To maintainer: depends ncurses5-compat-libs, libomxil-bellagio, lib32-libomxil-bellagio and lib32-ncurses5-compat-libs. It has to be set manually, or install is failed

nmset commented on 2017-02-27 09:46 (UTC)

@Berg : To remove, I would # switch to a terminal # systemctl stop sddm #whatever display manager # pacman -Rdd amdgpu-pro amdgpu-pro-dkms amdgpu-pro-libdrm amdgpu-pro-libgl amdgpu-pro-opencl amdgpu-pro-vdpau amdgpu-pro-vulkan lib32-amdgpu-pro lib32-amdgpu-pro-libdrm lib32-amdgpu-pro-libgl lib32-amdgpu-pro-opencl lib32-amdgpu-pro-vdpau lib32-amdgpu-pro-vulkan xf86-video-amdgpu-pro # pacman -Sy xf86-video-amdgpu mesa-libgl ocl-icd lib32-mesa-libgl lib32-ocl-icd # systemctl poweroff Now I have not tried it, but it should get you back to stock libraries.

Berg commented on 2017-02-26 15:53 (UTC)

And how to remove it with unfortunate result of the installation? Installation is fine, but on my R7 240 this driver gives the garbage and terrible artefacts at the screen Plasma 5.9.2 Something like this user: Or you know how we can fix this bug?

g00dx commented on 2017-02-21 07:59 (UTC) (edited on 2017-02-21 09:24 (UTC) by g00dx)

@Vi0L0: Your repo worked great to downgrade. I use xfce4 so I've not tested with gnome or cinnamon. Thanks! Right out of the box I could not get Vulkan to work. I'm still messing around with drivers and settings. Thanks for putting this together. I'll mess around a bit to see if I can find out why Vulkan is not working. *Edit* I got Vulkan working by removing amdgpu from KMS and now it works on both of my kernels. 4.9 and 4.5. Also got a significant FPS increase. Here are some benchmarks I put together using the talos principle, if anyone is interested I can post my full xorg and talos logs.

Vi0L0 commented on 2017-02-19 21:18 (UTC)

just thought that repo with xserver 1.18 related packages could be useful: [xorg118] Server =$arch Didn't test it though with this package as atm I don't have time to fight with libgles/libegl conflicts :/. If you got proposition of a package which could be included in the repo - let me know.

Gelmo commented on 2017-02-16 22:18 (UTC)

@hpstg Make sure you're using a version of GDM which works with 1.18

hpstg commented on 2017-02-16 17:48 (UTC)

The driver installs ok once reverted to Xorg 1.18, using the Arch Linux Archive. The issue is that the GDM login screen is completely garbled, with wrong fonts and placement of some controls.

Gelmo commented on 2017-02-14 23:37 (UTC)

@parkerlreed -

awkwardtechdude commented on 2017-02-13 14:14 (UTC)

I use an aur package called agetpkg-git, a script for the arch packages time machine. Anybody else getting performance hits with the last update? I've gone from around 60 fps in War Thunder to under 30.

parkerlreed commented on 2017-02-13 03:43 (UTC)

Anybody have an easy way to downgrade all the relevant Xorg packages? I haven't been able to come up with a list that works together.

ztx commented on 2017-02-10 01:03 (UTC) (edited on 2017-02-12 00:16 (UTC) by ztx)

I'm trying to install compiz after amdgpu-pro, but it can't find libdrm. It also failing to find libgl, so i installed mesa-libgl instead of amdgpu-pro-libgl, but i can't do the same for libdrm. What should i do? I cannot find any info on that. UPD: after a lot of time spent on google and trying different solutions i just gave up and created symlink to amdgpu-pro's libGl (Yes, i don't have 'mesa-libgl' installed anymore, but i have 'mesa' package installed though. And i completely reinstalled amdgpu-pro once again). And that didn't help. I have no idea what to do. Of cource, that is not only 'compiz' compiling problem, - anything related to GL, GLES and DRM (at least) will eventually fail compilation process, which is a huge problem for me, considering 'amdgpu-pro' has best performance among all video drivers in my case. Please, help.. UPD-2: Recreated symlinks, works for libGL. But not for libdrm, unfortunately. Finds libEGL, but not drm. Mistake with symlinks once again, probably. Still i want to know why do i have to manually create symlinks, it donsn't seem like a very safe thing to do.

JontySR commented on 2017-02-07 20:47 (UTC)

@Corngood Yeah, I have twice now, but there are serious graphical glitches, mainly to do with corrupted text and letters missing, so it's pretty unusable for me on an HD 7850. I don't know how to correctly go back to the amdgpu driver if this can't be fixed either, although I may just be dumb of course. I'll put a screenshot in the issue. Thanks

Corngood commented on 2017-02-07 20:25 (UTC)

@Stonewall @JontySR I opened an issue: In the meantime, are you able to install it with makepkg?

JontySR commented on 2017-02-07 19:58 (UTC)

Hey, @Stonewall beat me to it by a minute. xD

JontySR commented on 2017-02-07 19:57 (UTC)

@Corngood Awesome job. One problem I'm having is when I pacaur -S amdgpu-pro, I get: :: resolving dependencies... :: dependency cycle detected (amdgpu-pro=16.60.379184-1 amdgpu-pro-dkms=16.60.379184-1 amdgpu-pro-libdrm=16.60.379184-1 amdgpu-pro-opencl=16.60.379184-1 amdgpu-pro-vdpau=16.60.379184-1 amdgpu-pro-vulkan=16.60.379184-1 lib32-amdgpu-pro=16.60.379184-1 lib32-amdgpu-pro-libdrm=16.60.379184-1 lib32-amdgpu-pro-opencl=16.60.379184-1 lib32-amdgpu-pro-vdpau=16.60.379184-1 lib32-amdgpu-pro-vulkan=16.60.379184-1 xf86-video-amdgpu-pro=16.60.379184-1) I managed to install it with makepkg -si from the git clone earlier, but I uninstalled because all the text was glitchy corrupt-looking, and wanted to reinstall, seeing if I could get round this dependency cycle as well.

Stonewall commented on 2017-02-07 19:56 (UTC)

Now it get this stonewall@axiom ~ % pacaur -S amdgpu-pro :: Package amdgpu-pro not found in repositories, trying AUR... :: resolving dependencies... :: dependency cycle detected (amdgpu-pro=16.60.379184-1 amdgpu-pro-dkms=16.60.379184-1 amdgpu-pro-libdrm=16.60.379184-1 amdgpu-pro-opencl=16.60.379184-1 amdgpu-pro-vdpau=16.60.379184-1 amdgpu-pro-vulkan=16.60.379184-1 lib32-amdgpu-pro=16.60.379184-1 lib32-amdgpu-pro-libdrm=16.60.379184-1 lib32-amdgpu-pro-opencl=16.60.379184-1 lib32-amdgpu-pro-vdpau=16.60.379184-1 lib32-amdgpu-pro-vulkan=16.60.379184-1 lib32-ncurses5-compat-libs>=6 ncurses5-compat-libs>=6 xf86-video-amdgpu-pro=16.60.379184-1) 1 stonewall@axiom ~ %

parkerlreed commented on 2017-02-07 19:00 (UTC)

@Stonewall it's just amdgpu-pro The installer package is part of the PKGBUILD

Stonewall commented on 2017-02-07 18:48 (UTC)

Anyone know why I can't find this pacage with pacaur? stonewall@axiom ~ % pacaur -S amdgpu-pro-installer :( :: Package amdgpu-pro-installer not found in repositories, trying AUR... :: resolving dependencies... :: no results found for amdgpu-pro-installer 1 stonewall@axiom ~ %

Corngood commented on 2017-02-07 16:07 (UTC)

@parkerlreed It's working with 4.8 and 4.9. It's broken with 4.4, and probably will be broken with 4.10. I wouldn't bother installing this without the dkms driver.

parkerlreed commented on 2017-02-07 16:04 (UTC)

What's the status of the DKMS module? (What kernels does it currently work with)

Corngood commented on 2017-02-07 13:09 (UTC)

16.60 is here. Big thanks to @brainpower for doing all the hard work, and to everyone who came by the PR to help test it. Please test and let us know about any issues.

commented on 2017-01-25 11:37 (UTC)

Hi, Any chances you can update the package to 16.40? Because this one is pretty old and it seems to require linux 4.7. Thanks.

xier commented on 2017-01-24 14:50 (UTC) now has prebuilt in case someone wants to try 16.50. No guarantee it works for others though (personal backup repo).

Corngood commented on 2017-01-09 14:22 (UTC)

@pew yeah, github would be best

darkbasic commented on 2017-01-09 11:34 (UTC)

What about filing a bug report on github?

pew commented on 2017-01-09 06:56 (UTC)

Hi, is there any place like and irc channel or active forum thread for discussing this package? I have some questions but I don't want to fill up the comments with stuff that isn't relevant to most people. If nothing already exists, I'm chilling on #amdgpu-pro on oftc.

darkbasic commented on 2017-01-02 15:05 (UTC)

Yes, downgrade xorg to 1.18

Renfield commented on 2017-01-02 13:52 (UTC) (edited on 2017-01-02 13:53 (UTC) by Renfield)

Thanks DarkBasic. I'm always missing things, and I missed nmset's comment further below that contains the PKGBUILD. I managed to build a 16.50 package using that, but then when I boot into it, the Xorg log mentions incompatible ABIs. I suspect, looking at your comment in the Phoronix benchmark post, that my problem here is that I'm running Xorg 1.19.

Corngood commented on 2017-01-02 01:56 (UTC)

IMO the most promising path forward is this PR: If someone can take that, update it for 16.50 using the patches I made for NixOS, and test it, I'll merge it and update AUR. 16.40 -> 16.50 didn't take much work on NixOS, so it shouldn't be a big job. If anyone's interested in doing this, we can coordinate on github and I'll help as much as possible. Cheers

darkbasic commented on 2017-01-02 00:56 (UTC)

To use my patches you will have to know what you're doing first... You can start by having a look at this post:

Renfield commented on 2017-01-01 23:33 (UTC)

Is anyone supporting this? I tried adding the patch files darkbasic linked to into the package directory that I'm building this from, but it still tries to download 16.30. How do I get it to download and use 16.50?

Renfield commented on 2016-12-31 20:27 (UTC)

I've just got a Radeon RX 480. makepkg fails: ==> Validating source files with sha256sums... amdgpu-pro_16.30.3-315407.tar.xz ... FAILED ==> ERROR: One or more files did not pass the validity check! I have tried twice to be sure it wasn't just really a corrupted download.

darkbasic commented on 2016-12-29 12:06 (UTC)

Here is the link to the DKMS patches for amdgpu-pro 16.50: They should work up to 4.7, but I only tested 4.4 and 4.7. If you are interested you can find some fresh benchmarks here: Avoid using recent kernels with amdgpu-pro because they don't perform well, I suggest you to use linux from 4.4 up to 4.7. nmset's package is a bit rough but works fine, unfortunately I didn't have enough time to properly update the 16.30 one.

nmset commented on 2016-12-23 08:28 (UTC)

@parkerlreed : I guess there's no volunteer to take on this maintenance, I just can't as I tinker a lot as a hobby only.

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 Good luck.

daren 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 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.

marcio commented on 2016-12-10 23:38 (UTC)

@nmset I'm having some trouble trying to get amdgpu-pro working with RX 480. After reboot gdm do not start and on journalctl I have that output: tks

nmset commented on 2016-12-09 13:58 (UTC)

@Corngood : regarding conformance, it does not use standard locations (/usr/lib...) as I don't want to mess up a system if things go wrong. This forces to declare other library locations in /etc/, and optionally a long list of LD_LIBRARY_PATH variable, which gets not very clean, though it works. It doesn't always use quoted variables as I observed that unpacking the DEB packages would fail otherwise. And it's not clear how to get a direct download link from AMD's website on every release.

Corngood commented on 2016-12-09 13:42 (UTC)

@nmset go for it. I haven't had time to do any work on arch lately, so I'm happy to take any contributions, or even hand over maintainership if someone wants to take it on. What's non-conformant about your script?

nmset commented on 2016-12-09 10:01 (UTC) (edited on 2016-12-09 13:30 (UTC) by nmset)

Here is a 32/64-bit PKGBUILD for 16.50 : @Corngood : I don't have any intent to hijack your repository, I just don't have any other outlet to share a PKGBUILD that doesn't conform to AUR standards. If you feel I should stop linking here, I'll do so.

LiberteCzech commented on 2016-12-09 06:18 (UTC)

AMDGPU-PRO 16.50 released. GCN 1.0 enable by default by DKMS.

nmset commented on 2016-12-08 09:42 (UTC)

@Lopo : >there is nothing to do Your system is up to date. >:: imagemagick: requires opencl-icd-loader An acceptable sacrifice for many probably.

Lopo commented on 2016-12-08 08:45 (UTC)

@nmset pacman -Syu --ignore ocl-icd :: Synchronizing package databases... core is up to date extra is up to date community is up to date archlinuxfr is up to date :: Starting full system upgrade... resolving dependencies... warning: ignoring package ocl-icd-2.2.9-2 warning: cannot resolve "opencl-icd-loader", a dependency of "imagemagick" :: The following package cannot be upgraded due to unresolvable dependencies: imagemagick :: Do you want to skip the above package for this upgrade? [y/N] N error: failed to prepare transaction (could not satisfy dependencies) :: imagemagick: requires opencl-icd-loader Y looking for conflicting packages... there is nothing to do

viennaa commented on 2016-12-07 08:34 (UTC) (edited on 2016-12-07 08:35 (UTC) by viennaa)

Is there a way to build the 16.30 version against a kernel? On my 4.8.12 it always fails to build DKMS. If you manage to build it on a specific kernel version, please share.

tranqtech commented on 2016-12-07 05:15 (UTC)

@nmset Managed to install with your pkbuild, but if there's no 32-bit libs for your build is there a known way to get steam working?

commented on 2016-12-05 12:32 (UTC)

@nmset ok

nmset commented on 2016-12-05 08:27 (UTC)

@Paullux : The PKGBUILD I linked does not install 32-bit libraries at all. On further testing, I could not get an X session if I co-install the 32-bit libraries.

commented on 2016-12-04 17:27 (UTC)

@nmset The 32 bits applications (like 'steam' and 'the lord of the rings online' with wine) doesn't work with your PKGBUILD (there is artefact).

nmset commented on 2016-12-03 17:28 (UTC)

@Lopo : I guess you should use [pacman -Syu --ignore ocl-icd], as amdgpu-pro here uses its own ocl libraries.

Lopo commented on 2016-12-03 15:50 (UTC)

==> Package upgrade only (new release): extra/imagemagick 1 -> 2 ==> New package : extra/ocl-icd 2.2.9-1 (required by imagemagick) . . looking for conflicting packages... :: ocl-icd and amdgpu-pro-libopencl-dev are in conflict (libcl). Remove amdgpu-pro-libopencl-dev? [y/N] for N: error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: ocl-icd and amdgpu-pro-libopencl-dev are in conflict for Y: error: failed to prepare transaction (could not satisfy dependencies) :: amdgpu-pro-computing: removing amdgpu-pro-libopencl-dev breaks dependency 'amdgpu-pro-libopencl-dev='

commented on 2016-12-01 14:28 (UTC)

I'm seeing some graphics glitches with the OS-drivers from the main repo : But I wouldn't want to land in a situation where I'm worse off. (1) So does this package build without issues with the current version? (3) Does this package give me control over the fan speed, or does it maybe control the fan speed itself?

nmset commented on 2016-11-30 08:30 (UTC)

@Stonewall : Here is how I do that : Please read the header comments.

Stonewall commented on 2016-11-29 23:11 (UTC)

Hey @nmset could you give a little more information on how you are getting this to working?

WildyLion commented on 2016-11-23 13:33 (UTC)

Can somebody please share a new PKGBUILD for 16.40? Also it seems one should run linux-lts for the time being to avoid slowdowns.

joshua5201 commented on 2016-11-20 16:23 (UTC)

Thank you @nmset, I'm currently using RX480, too. I'll try it. Will this be merged into the package's repository?

nmset commented on 2016-11-20 15:59 (UTC)

I've been patching 16.40 DKMS against linux 4.9.0-rc5. It builds after applying the 14 available patches, plus the following patch applied as 0015 : has to be modified, discarding the last lines that delete a/amd/backport/symbols. My final impression is that it's useless to use the DKMS package. glmark2 score has not changed at all. Worse, this older driver does not activate powerplay on my Topaz discrete GPU, and the laptop becomes hot and noisy. dmesg reveals '[drm] Initialized amdgpu 3.2.0 20150101' with the DKMS build, while the 4.9.0-rc5 module's version is 3.8.0. @Paullux : The DKMS package is not an obligation. As I said below, I'm using 16.40 with a dirty PKGBUILD on my laptop having Kaveri+Topaz, and on my desktop with RX480. I avoided 4.8.x because 4.9 stable will be out soon.

commented on 2016-11-20 15:15 (UTC)

The driver needs DKMS to work...

joshua5201 commented on 2016-11-20 13:48 (UTC)

Does anyone succeed to make OpenCL work on kernel 4.8? The display manager doesn't boot if I install all packages except dkms (dkms doesn't build). Or on what version of kernel this package will work? If none, I think I should start to try patching this package.. Isn't this an userspace driver? I am wondering why we need dkms here.

Corngood commented on 2016-11-19 02:56 (UTC)

I'm sorry this package hasn't got any attention lately. Partly due to the struggle of dealing with many kernel/xorg configs and proprietary drivers, I've been working almost exclusively on NixOS (which I can't praise highly enough). I will happily take PRs if anyone can get 16.40 working. The patches needed for linux-4.8 should be very similar to what's in NixOS: Also the history there should help explain how things have moved around in 16.40.

commented on 2016-11-18 17:33 (UTC)

I tried to work package, I forked the reposery of lhl on github. I am stopping because there is error with dkms, and i don't know how to resolve this. I have change PKGBUILD and one of patchs to BUILD and try to install the driver. To obtain this : If someone want to continue or say me if i mistaked somethings. The error is : ==> dkms install amdgpu-pro-16.40/348864 -k 4.8.8-2-ARCH /var/lib/dkms/amdgpu-pro-16.40/348864/build/ ligne 26: amd/backport/symbols: Aucun fichier ou dossier de ce type Error! Bad return status for module build on kernel: 4.8.8-2-ARCH (x86_64)

nirei commented on 2016-11-15 22:36 (UTC)

Might be of interest to you guys:

aaronp commented on 2016-11-15 04:34 (UTC)

Do you know if it'a possible to use amdgpu-pro for opencl and vulkan but mesa for OpenGL?

lhl commented on 2016-11-07 09:34 (UTC)

It looks like there were a lot of changes of the deb package names - including the complete removal of the computing package? I'm primarily interested in the OpenCL drivers, so just trying to modify the PKGBUILD to work. I've grabbed corngood's Nix patches and was slogging my way through, but hit a bit of a roadblock w/ the computing package:

nmset commented on 2016-11-07 08:56 (UTC)

>Has anyone gotten 16.40 to work? I've installed it with a quick and dirty PKGBUILD adapted from the one available here. I have not noticed perceptible differences (laptop with Kaveri + Topaz, desktop with Ellesmere). I am not using the dkms stuff packed in the 16.40 release. glmark2 score dropped by 5% on my laptop(570) with respect to 16.30, but without amdgpu-pro, glmark2 is 650 ! On my desktop, glmark2 score is about the same with 16.30 and 16.40 (1950).

lhl commented on 2016-11-07 08:32 (UTC)

Has anyone gotten 16.40 to work? I tried out benklett's 16.40 fork but it failing patching for me (and unfortunately seems to have extensive PKGBUILD changes)

NogradThGin commented on 2016-10-30 16:03 (UTC)

Driver 16.40 just came out.

nmset commented on 2016-10-22 18:22 (UTC)

Just for information : Using linux-4.9.0-rc1-git : On Kabini, amdgpu +/- pro works well, with the lockup with video file playback. On Oland Pro, amdgpu +/- pro fails to launch a GUI.

nmset commented on 2016-10-21 20:34 (UTC)

I tested against linux-4.9.0-rc1-git. Unlike with linux-4.8.2, both amdgpu and work nicely. I did not try for hours. amdgpu-pro-dkms does not compile and seems not mandatory. Lockups still happen while reading videos. CIK and SI have been enabled. All this on my Kaveri+Topaz laptop. Will try with Kabini and Oland next.

jdubs commented on 2016-10-21 04:04 (UTC)

I have the exact same error as nmset. I will also attempt to downgrade the kernel and try again.

nmset commented on 2016-10-20 17:56 (UTC)

amdgpu-pro-16.30.3 does not compile on linux-4.8.2. I guess it should be expected as there is not 4.8 patch in this package. Here are the reported errors : According to web available information, amdgpu-pro ought to be the userspace part of the kernel amdgpu module. But this package does try to compile another kernel module. What am I missing ? As a sidenote, linux 4.8.2 amdgpu module (not pro) constantly crashes the system (Kaveri + Topaz) with a lot of AMD-VI reported errors, no way for me catch them. Both work well with linux 4.7.6, apart from the lockup with video playback mentioned below.

mikaelbrun commented on 2016-10-20 15:29 (UTC)

@ViOLO: 1: It was just backgroundinfo why I considered changing to amdgpu-pro 2: I didn't see the update in the wiki Last time I checked it was experimental for 4.8. That is why I was confused I guess. Today I can't be a volounteer, but I can try to install kernel 4.9 on a second disk and try to help out.

Vi0L0 commented on 2016-10-20 13:49 (UTC) (edited on 2016-10-20 13:52 (UTC) by Vi0L0)

@mikaelbrun: 1. i believe it's not the place for commenting catalyst-test pkg, but fyi i have updated it more than 2 weeks ago to cover 4.8 kernel support, you probably only have to update it. 2. afaik AMDGPU-PRO is not compatible with SI, experimental SI support was just added to AMDGPU in kernel 4.9 (release candidate atm) Amarildo [1] have tested -PRO on his SI card, and he catched segfaults [1] It would be good anyway to confirm that experimental SI support in 4.9 kernel is not working with -PRO driver - aby volunteer? :)

mikaelbrun commented on 2016-10-20 13:37 (UTC)

I currently have the catalyst-test driver installed on my computer. I now see that the linux 4.8.2-1 kernel has been released, and this gives me a conflict when I want to update (catalyst-test needs linux < 4.8). My graphics card is a radeon R9 280x, which is SOUTHERN ISLAND (isn't it?). Is the new kernel compatible with this card and AMDGPU-PRO out of the box? The information I have found is confusing to me. I don't want to make big changes to my system if it gives me alot of extra work. :-)

nmset commented on 2016-10-18 20:34 (UTC) (edited on 2016-10-18 20:34 (UTC) by nmset)

@Corngood : libvdpau is installed on my system, and I can't remove it as many packages depend on it. But I noticed no lockup with ffplay. VLC, mplayer and dragon will always lockup my laptop before even the first frame is displayed.

Vi0L0 commented on 2016-10-18 19:16 (UTC)

@Corngood: i also had stability issues with amdgpu-pro, hard lockups where even hardware reset button didn't help (sic!). My longest session stayed for ~2hours. Lockups appeared in random situations - in games, movies, web browsers, text editors, with compositing enabled and disabled. I checked many kernels and iirc amd-staging-4.7 (from agd5f's git) was best because it was freezing desktop envronment, not whole pc so i could reboot it safely (`systemctl restart sddm` then was causing complete lockup again). Even dkms version of the module was worse than this amd-staging-4.7. I'm on 290x so also hawaii and thats why i'm so much surprised when you telling you are not experiencing these lockups. As for me it is the worst amd driver because of those lockups and also the first one on which gl-cl sharing is working completelly fine, heh :). Oh well, I will patiently wait for newer version to check it out, meanwhile I'm on amdgpu and gotta tell that it's really nice!

Corngood commented on 2016-10-18 18:12 (UTC)

@nmset - I assume you are trying to use VDPAU? I've had stability problems with VDPAU on HAWAII, but just corruption in the video and the video player stopping, no system lock ups.

Vi0L0 commented on 2016-10-18 06:47 (UTC) (edited on 2016-10-18 06:53 (UTC) by Vi0L0)

I believe my GNOME 3.22 "fix" should also work on amdgpu-pro: Like said there still no luck with gdm, at least on catalyst but since amdgpu-pro shares code with catalyst it could be also touched - anyhow it's another story + I believe it's easier to switch dm than de

nmset commented on 2016-10-15 14:15 (UTC)

I just can't play any video file with amdgpu-pro, with any DE, any video file format and any player. The system totally freezes on playback and there's no choice but a hard reboot. There are no problems with a 3D application I use. My laptop : Linux hp2.domain 4.7.4-1-ARCH #1 SMP PREEMPT Thu Sep 15 15:24:29 CEST 2016 x86_64 GNU/Linux 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6 Graphics] 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360] (rev ff) X.Org X Server 1.18.4 Now I intend to buy an RX480 card for a desktop PC, which will require amdgpu/pro. I wish to know if someone has experienced such system freeze during video playback with this card, before buying. Thank you.

commented on 2016-10-15 12:18 (UTC)

Since I Updated my system (Arch64bit) there 4 days, i can't start gnome, i have just dark screen with mouse cursor. The Update was Gnome 3.20 to 3.22 and Wayland. So i must uninstalled AMDGPU-PRO and reinstall AMDGPU (the free driver) to start Xorg and/or Gnome.

flubba86 commented on 2016-10-14 01:25 (UTC)

@s1kx - Oh, hey thats me. Glad my patch worked for you, and you were able to create a working package using it. I came across this page while trying to get amdgpu-pro working on Linux 4.8 in Ubuntu, and was surprised to see my username mentioned.

Corngood commented on 2016-09-27 20:23 (UTC)

@nmset Yeah, you should just be able to remove everything with amdgpu-pro in the name, and then you'll probably want to install install xf86-video-amdgpu and mesa.

nmset commented on 2016-09-27 20:20 (UTC)

How do we uninstall amdgpu-pro to switch back to amdgpu ? Do we just remove the individual packages ? Anything else to do ? Thanks.

s1kx commented on 2016-09-12 03:05 (UTC)

Thanks for your work on this package. I had trouble getting it to run at first today with Linux 4.7 and a RX 480, because I would boot into a black screen with just a cursor. After some debugging, I found that the problem was with lightdm and cinnamon, because they use COGL and there is a compatibility problem with the AMDGPU-PRO libgl drivers. There is a patch by flubba86 on the Phoronix forums for COGL, which made everything work! I have created an AUR package called cogl-amdgpu-pro for anyone with the same problem.

Corngood commented on 2016-08-29 16:40 (UTC)

Updated to Firmwares and DKMS driver are now installed by default. I suggest installing them both or neither. Using the DKMS driver fixes the fence errors in Vulkan (e.g. in Vulkan smoketest). I have had some problems with hibernation on HAWAII, and I get some IO_PAGE_FAULT around when the module is loaded at boot. Please let me know how it works for you.

oi_wtf commented on 2016-08-25 22:11 (UTC)


Corngood commented on 2016-08-25 17:19 (UTC)

@oi_wtf - Thanks. Could you post an issue on github?

oi_wtf commented on 2016-08-25 16:54 (UTC)

When installing, pacman complains: xserver-xorg-video-amdgpu-pro: /usr/lib/xorg/modules/drivers/ exists => So it should probably conflict xf86-video-amdgpu

Corngood commented on 2016-08-25 16:37 (UTC)

I'm not sure. They're talking about merging stuff into linux-4.8, but this is the dkms driver released directly from AMD, which is sort of developed independently. It does seem to have a bunch of HW support that's not in linux-4.7 though, so you could either grep for SI things or just try to run it.

okabekudo commented on 2016-08-25 16:09 (UTC)

Does this include the patch for GCN 1.0 SI cards? That means this:

Corngood commented on 2016-08-24 15:52 (UTC)

I made a branch which enables firmware and the dkms driver by default. It turns out you need the dkms driver for Vulkan to work properly (possibly other things). You can grab it from if you want to try it out. I'd like to get some feedback before releasing it. I need to set the kernel param 'amdgpu.dal=0', or the kernel crashes on Xorg start. I will make that the default when I release it, unless someone finds that DAL works on certain GPUs (I'm using a 290).

kdb424 commented on 2016-08-24 15:45 (UTC) (edited on 2016-08-26 03:07 (UTC) by kdb424)

Was having issues with polaris before. Working on an RX 470 Nitro 4GB with this and the tips on past 3 of this thread. EDIT: Steam coredumps. No clue. Not going to bother posting logs unless someone else is having the issue. 3D works great in unigine-heaven and in everything else I need. Launching steamapps manually works, just not steam itself.

Tower commented on 2016-08-22 16:09 (UTC)

Thanks Null32, can confirm that installing linux-mainline (linux kernel 4.8 rc3) has sorted out the issues in Plasma. R9 380 here.

NogradThGin commented on 2016-08-22 01:06 (UTC) (edited on 2016-08-22 01:08 (UTC) by NogradThGin)

Hello, personnaly I have this error: Screen 0 deleted because of no matching config section. on Kernel 4.7.2 linux-ck with all AMDGPU options enabled in kernel config Technically the R9 390 is supported by AMDGPU-Pro (according to AMD site). But i can't get it to work. Also if i build all package DKMS doesn't succeed to install. (Sorry for bad english)

Null32 commented on 2016-08-21 19:44 (UTC) (edited on 2016-08-21 20:54 (UTC) by Null32)

RX 470 here. With this driver Plasma keeps showing wrong/black icons and crashing from time to time, it gets impossible to use after a while. There were no problems at all with the opensource driver. Steam works perfectly after removing some of the libraries that it includes, I'm getting much more stable framerates on TF2 now. With the opensource drivers it would make the whole system freeze randomly. EDIT: Installed linux-mainline and set the rendering backend to OpenGL 3.1, the Plasma problem seems to be gone now.

Jhackler commented on 2016-08-21 14:56 (UTC)

anyone know if the issue causing this not to work under gnome shell is fixed yet?

kdb424 commented on 2016-08-20 06:31 (UTC)

Can confirm that it works on my RX 470. Having some major issues after installing this. PlayOnLinux is reporting missing 64bit openGL libs, many games such as openarena, xonotic, and others aren't launching. Steam works with many hacks, as do some games such as portal, but at a lower framerate and choppier than the open source drivers. I have gotten openCL to work with folding at home, which failed on the open drivers. I'll put in a more proper report later, but wanted to let people know the state of what I got to work here, as opposed to just putting issues elsewhere.

mcirillo commented on 2016-08-18 17:31 (UTC)

Just bought an R9 Nano - anyone using this card?

Corngood commented on 2016-08-06 23:07 (UTC)

Updated to The package structure is identical, and I don't seem to have any problems. Any success stories for polaris yet?

Corngood commented on 2016-08-06 14:15 (UTC)

@DevilX You'll have to remove the xf86-video-amdgpu package. I'll add a conflict for it in the next release. Let me know if you have any other package conflicts.

DevilX commented on 2016-08-06 10:13 (UTC)

I get the following error: Fehler: file owned by 'xf86-video-amdgpu' and 'xserver-xorg-video-amdgpu-pro': 'usr/lib/xorg/modules/drivers/'

Corngood commented on 2016-08-06 03:26 (UTC) - moves some libraries out of debian paths into /usr/lib and /usr/lib32 - should fix -lGL - should fix vdpau This is a pretty big change to the library layout, so keep around a copy of the previous packages and be prepared to boot in text mode to revert. Let me know how it goes.

headkase commented on 2016-08-01 17:50 (UTC)

@conihorse - To keep it all in one place please comment on the issue here:

conihorse commented on 2016-07-31 20:03 (UTC) (edited on 2016-07-31 20:04 (UTC) by conihorse)

@headkase - Trying to compile baka-mplayer and I'm also having the same issue (I think?) with OpenGL headers/includes: "/usr/bin/ld: cannot find -lGL".

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, 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/ / 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... 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) - 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: 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.

ecloud commented on 2016-07-05 18:57 (UTC)

@corngood Like I said, I tried it both ways. Usually without xorg.conf since it is not normally needed. No, I don't see any specific info about the card being detected; when I modprobe amdgpu, I get only this appended to dmesg [ 1505.897630] [drm] Initialized drm 1.1.0 20060810 [ 1505.918023] [drm] amdgpu kernel modesetting enabled. The RX 480 is very new, and full open-source support is supoosedly on track for the 4.7.0 release. I was hoping to simply use amdgpu-pro in the meantime, but maybe something is missing from this 4.6.3 kernel? Did they need to modify the Ubuntu kernel to support the amdgpu-pro drivers? I guess I'll try the 4.7rc6 from aur. I already tried building a custom kernel myself from git, but am not having much luck with that either; of course I tried to get by without an initrd in that case. I'm not sure which console driver should be used with amdgpu. Simple, or VESA, or radeon, or something else? About the 4.7 changes, Mesa changes etc.:

Corngood commented on 2016-07-04 21:04 (UTC)

@ecloud So you get the same 'Screen deleted' error without your xorg conf? My config has nothing in /etc/ and just: /usr/share/X11/xorg.conf.d/01-amdgpu-pro.conf /usr/share/X11/xorg.conf.d/10-evdev.conf /usr/share/X11/xorg.conf.d/10-quirks.conf Is yours the same? Is KMS actually working (changing video modes at boot) for text mode? Shorly after "[drm] amdgpu kernel modesetting enabled." I get: [drm] initializing kernel modesetting (HAWAII 0x1002:0x67B1 0x174B:0xE289 0x00). Do you see the equivalent?

ecloud commented on 2016-07-04 20:40 (UTC)

I just got an RX 480. I've got 4.6.3-1-ARCH and dmesg shows this [ 1.838630] [drm] Initialized drm 1.1.0 20060810 [ 1.844828] [drm] amdgpu kernel modesetting enabled. and the amdgpu module gets auto-loaded. The console works OK. When I run startx I get this in the Xorg log: [ 3273.692] (II) [KMS] drm report modesetting isn't supported. [ 3273.692] (EE) Screen 0 deleted because of no matching config section. [ 3273.692] (II) UnloadModule: "amdgpu" [ 3273.692] (EE) Device(s) detected, but none match those in the config file. [ 3273.692] (EE) Fatal server error: [ 3273.692] (EE) no screens found(EE) regardless if I have xorg.conf (I tried to write one) or not. Xorg -configure puts this into the log [ 3555.491] (II) [KMS] drm report modesetting isn't supported. [ 3555.598] Number of created screens does not match number of detected devices. Configuration failed. My (optional) xorg.conf or xorg.conf.d/20-amdgpu.conf looks like this Section "ServerLayout" Identifier "layout" Screen 0 "scr0" 0 0 EndSection Section "Device" Identifier "AMD" Driver "amdgpu" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "monitor0" EndSection Section "Screen" Identifier "scr0" Device "AMD" Monitor "monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1200" EndSubSection EndSection Any ideas what to try next?

Tower commented on 2016-07-02 18:56 (UTC) (edited on 2016-07-02 18:56 (UTC) by Tower)

I was getting flickering issues in KDE Plasma, I thought it a minor issue but since removing xf86-video-vmware (was attempting to try gnome, happy accident that I couldn't get gnome working and switched back to KDE) . 99% of the flickering has disappeared it seems - needs more testing to be sure, but looks promising so far.

Corngood commented on 2016-07-02 18:38 (UTC)

@dedxi It sounds like you're back to using the open source driver, which at least suggests the package conflicts are working. If you want to try it again, I suggest installing all the amdgpu-pro packages except the dkms one, reboot your system, then run: `ldconfig -p | grep` It should show only the amdgpu-pro drivers for both 64 and 32 bit. Test glxgears (or something else) to verify 64-bit GL is working, then test steam for 32-bit GL. If you still have problems, I'd suspect something in Xorg config or some problem with the kernel module. You can always email me or open an issue on github if you want to discuss it in more depth.

Corngood commented on 2016-07-02 18:27 (UTC) (edited on 2017-12-24 00:50 (UTC) by Corngood)

This is a generated PKGBUILD. The full source is available at:

Feel free to post issues and send PRs.

*** linux 4.9 with KALLSYMS_ALL=y is required

*** mesa-noglvnd is required The mesa package in Arch now includes the glvnd libGL, which conflicts with the AMDGPU-PRO libGL. You'll need to replace mesa with mesa-noglvnd.

Corngood commented on 2016-07-02 18:25 (UTC)

@ivan.kolmychek The missing issues page was just an oversight from when I forked it, but it's there now. I switched to wget because I couldn't get curl's up-to-date check to work with the referrer url required by the amd server. Obviously there's a missing 'makedepends' on wget, so I'll make sure to add that.

dedxi commented on 2016-07-02 18:09 (UTC)

I was wrong before, there were some errors when installing via Packer and some sub-packages were not installed properly. Reinstalled via Yaourt with no errors and then steam didn't work at all - with or without any of the workarounds listed in the wiki. It gave the line 756 segfault error as if I was running it with STEAM_RUNTIME=0, but I wasn't (tried =0 and =1 and got the same error). To answer your questions, the original output of `pacman -Qo /usr/lib32/` (when steam worked with LD_PRELOAD) was: "/usr/lib32/ is owned by lib32-mesa-libgl 11.2.2-1" With the package properly installed, output is: "error: failed to read file '/usr/lib32/': No such file or directory" And I verified I have the latest version installed - "aur/amdgpu-pro [installed]" I ended up re-installing lib32-mesa-libgl (removing the corresponding amdgpu-pro package) and now steam is working without LD_PRELOAD. Now the output of "pacman -Qo /usr/lib32/" is "/usr/lib32/ is owned by lib32-mesa-libgl 11.2.2-1" again.

ivan.kolmychek commented on 2016-07-02 16:09 (UTC) (edited on 2016-07-02 16:10 (UTC) by ivan.kolmychek)

@Corngood Also, the wiki page ( says "visit for *issues* or pull requests.", and there is no "issues" tab in that repo. Is that on purpose? If it is, 1) where should users go for issues and 2) should we change the text in wiki?

ivan.kolmychek commented on 2016-07-02 16:08 (UTC) (edited on 2016-07-02 16:13 (UTC) by ivan.kolmychek)

@Corngood just found out the 'extra/wget' is not installed by default, but 'core/curl' is. I was kind of surprised too, but still - can we use the curl instead? This is a minor change but it may work more reliably as curl is installed out-of-the-box with regular arch installation, while wget is still needed to be installed manually. (Update, just in case: no, it's not a problem for me, I've installed the wget right away this time when I found that it was missing on that system, so it's more like a tiny suggestion for minor improvement :))

Corngood commented on 2016-07-02 01:16 (UTC)

@dedxi - Glad to hear it's working, but you shouldn't need LD_PRELOAD unless there's a conflicting Could you try `pacman -Qo /usr/lib32/` (assuming it exists)? Also could you verify that you have amdgpu-pro It's the first one which declares a conflict with other libgl packages.

dedxi commented on 2016-07-02 00:59 (UTC)

Works for me as well without dkms. Steam gave me a "libGL error: unable to load driver:" after installing, but works now with the "LD_PRELOAD='...'" workaround recommended in the wiki. Even wine games seem to be running well. Thanks Corngood.

Tower commented on 2016-07-01 15:58 (UTC)

Seems to be running well for me, didn't bother with the dkms package either. Steam is behaving too, really awesome.

Corngood commented on 2016-06-30 10:54 (UTC)

@Uranai - I suggest not even installing the dkms package. I think it only works with ancient kernels. I'm thinking of just removing it from the PKGBUILD.

Uranai commented on 2016-06-30 09:06 (UTC)

I finally tried to install this package but it gives me an error when DKMS tries to build the module Kernel preparation unnecessary for this kernel. Skipping... Running the pre_build script: grep: /boot/ No such file or directory Building module: cleaning build area... make KERNELRELEASE=4.6.3-1-ARCH -C /usr/lib/modules/4.6.3-1-ARCH/build M=/var/lib/dkms/amdgpu-pro-16.30.3/306809/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 4.6.3-1-ARCH (x86_64) Consult /var/lib/dkms/amdgpu-pro-16.30.3/306809/build/make.log for more information.

Corngood commented on 2016-06-30 04:16 (UTC)

Updated to 16.30.3 - Interdependencies are now to the exact version. Take care when updating, but from now on it shouldn't allow you to mix versions. - Now provides/conflicts libgl and lib32-libgl. This will prompt removal of e.g. mesa libgl. Steam now works without any hacks. Let me know how it goes.

Corngood commented on 2016-06-16 17:49 (UTC)

@nirei Vulkan 'works' for me on a R9 290 (HAWAII), which is CIK, but I've only tried a few sdk samples and my own stuff which is still very primitive. Agreed about the provides/conflicts. That's definitely on my TODO list, but I've been too busy to do it this week. Personally I think it should at least symlink the libs into /usr/lib and /usr/lib32 (if not just install them there) instead of messing with ld.conf. Then it would make sense to provide and conflict with "libgl". Still, why is your mesa getting removed? I currently have it installed along side amdgpu-pro and it's just superseded via ld.conf.

nirei commented on 2016-06-16 17:07 (UTC)

@Corngood The updated package works for me. X works fine and OpenGL/OpenCL do their job. Vulkan runs into a floating point exception when initializing depth buffers. (This also happens on Ubuntu with the amdgpu-pro userspace and kernel driver). Does Vulkan work for somebody on a CIK GPU? (I have a Kabini "AMD Radeon HD 7700 Series", aka "Radeon HD 8330") I think it would be really nice to add "provides" and "conflicts" information to the packages. Right now pacman pulls mesa-libgl on every update (and then i remove it again) because it doesnt know that libgl is provided by the amdgpu-pro package...

2xsaiko commented on 2016-06-15 11:45 (UTC) (edited on 2016-06-15 14:25 (UTC) by 2xsaiko)

@Corngood I just noticed I did not have lib32-amdgpu-pro-* installed. Massive derp :D EDIT: Yep, it works now. Thanks for the tip!

2xsaiko commented on 2016-06-14 13:19 (UTC) (edited on 2016-06-14 13:21 (UTC) by 2xsaiko)

How would I do that? I'm gonna try this: strace env LD_LIBRARY_PATH=/usr/lib/i386-linux-gnu/amdgpu-pro/ /bin/steam | grep /usr/lib/i386-linux-gnu/amdgpu-pro/ :D EDIT: nothing shows up. please note I'm running steam with STEAM_RUNTIME=0, maybe that has something to do with it

Corngood commented on 2016-06-14 12:01 (UTC)

@HyperLink That looks exactly like what I get if I don't specify LD_LIBRARY_PATH (so it loads mesa). You should double check that the steam process is actually loading /usr/lib/i386-linux-gnu/amdgpu-pro/

Corngood commented on 2016-06-14 11:59 (UTC)

@gfurst - I just had a look for benchmarks and it seems like performance is all over the place, unfortunately: You might be better off using catalyst on your GPU. Personally I've been doing vulkan development, so I don't have a choice.

2xsaiko commented on 2016-06-14 11:40 (UTC)

@Corngood Your steam fix works, but my Steam window is distorted. I only have this problem with steam. here is a picture ->

gfurst commented on 2016-06-14 04:35 (UTC)

Hey guys, thanks for providing the package, I'm to say I've successfully installed the driver, using a r7 260X card, with a enabled kernel and etc. Unfortunately it seems that for my card the driver is resulting in a really worse performance than it was with radeon. Though there isn't much of a solid test to compare it to, mainly the games I've tried are Soma and Metro Redux, both of which seems to perform remarkably better in windows. Now it seems that even a mainly 2d game like Prison Architect is slowed down. So anyway, surprisingly there isn't much configuration need, but I'm at a loss for config options, like a xorg.conf or something, any clues? Can one still use amdgpu module using the radeon driver?

Corngood commented on 2016-06-14 01:16 (UTC) (edited on 2016-06-14 01:18 (UTC) by Corngood)

@eddie Great work tracking that down. Thanks. FYI for anyone trying to get steam running: > LD_LIBRARY_PATH=/usr/lib/i386-linux-gnu/amdgpu-pro/ steam Steam does some fiddling with LD_LIBRARY_PATH which overrides ld.conf and ends up loading mesa.

eddie commented on 2016-06-12 03:55 (UTC)

@Corngood The issue @Jhackler is experiencing is something I ran into yesterday when installing these packages. Gnome Shell uses cogl for GL operations while requesting a GL 3.x forward-compatible context. Meanwhile, cogl is prepending shaders with #version 120 in this case, which is equivalent to GLSL 1.20 or GL 2.1. It would seem that other driver vendors are lenient about this, but AMD's GL implementation doesn't like it, so Gnome Shell's shaders fail to compile, hence the black screen @Jhackler sees (while being able to see the mouse and perform actions). I patched cogl locally but there's been a bug in cogl's Bugzilla since last October (last updated in February): Assuming they remain unable to resolve it, I'll likely just end up switching desktop environments.

Jhackler commented on 2016-06-11 19:40 (UTC) Second one is the x output Lightdm displays right but once I log in it arranges my displays correctly like gnome does and stays black with the gnome mouse. I can run commands from the gnome without seeing anything :/ (another edit) the amdgpu powerplay I tried running with it turned off since I assume unlike the pure opensource driver it is not needed. however same results.

Jhackler commented on 2016-06-11 18:44 (UTC) (edited on 2016-06-11 19:22 (UTC) by Jhackler)

Ok I will do that here in a moment with the mainline kernel. Sent it in email when I noticed it was not an automated message from aur.

Corngood commented on 2016-06-11 18:32 (UTC)

@jhackler Could you boot into multi-user, try `startx` and pastebin the Xorg log? Also could you post the output of `ldconfig -p | grep`? It should show the AMD libGL first.

Jhackler commented on 2016-06-11 18:26 (UTC)

Sorry last post till response. I could be checking wrong becuase it is behaving like the wayland (non x) boot option used to before I black listed the radeon driver. You can email me a if you want to keep comments clear

Corngood commented on 2016-06-11 18:24 (UTC)

@lahwaacz specified custom license

Jhackler commented on 2016-06-11 18:22 (UTC)

Amdgpu is loaded radeon is not cannot boot multi user target on main kernel. Libudev.so1 cannot open shared object file which was the problem with both kernels till reistalling systemd and libsystemd.

Jhackler commented on 2016-06-11 18:09 (UTC)

Lsmod |grep amdpu show entries nothing for radeon when grep for radeon

lahwaacz commented on 2016-06-11 18:09 (UTC)

@Corngood: The PKGBUILD still does not specify the license:

Jhackler commented on 2016-06-11 18:04 (UTC)

R9 380 the regular kernel broke when the mailine upgraded to 3.7 rc2 recently which forced me to reistall system d for anything to work. Radeon is blacklisted and has been for a while. I will attempt lsmod is a second once I restore my system back to state mentioned below.

Corngood commented on 2016-06-11 17:51 (UTC)

Also on my phone at the moment, so bear with me. Sounds like you have X, but no GL. Which GPU do you have? What happens with the regular kernel? Can it boot into Could you check lsmod output to see if amdgpu is loaded, and make sure radeon is not?

Jhackler commented on 2016-06-11 16:25 (UTC) (edited on 2016-06-11 16:26 (UTC) by Jhackler)

Oddly enough I cant seem to submit an issue on the github from my phone. I am using the mainline kernel, and regular kernel is not booting. After installing this light dm displays I log in and black screen. However gnome is clearly runing because alt f2 r then enter flickers the screen as if screen is restarting. Mouse displays over black :/

Corngood commented on 2016-06-09 02:00 (UTC)

I've updated this package to the version from my PR. If you have any problems, post here or on

Corngood commented on 2016-06-08 01:30 (UTC)

@thewisenoob - Did you try my PR, or just the original AUR package?

thewisenoob commented on 2016-06-03 07:03 (UTC)

I had successfully gotten amdgpu working after compiling Linux with support for my R9 290X. It worked after blacklisting radeon. Once I installed this, X wouldn't start. I tried removing it and X won't start still because of the same error. I get a bunch of file owned by 2 things errors now too when using yaourt. All of them are amdgpu related.

thewisenoob commented on 2016-06-03 06:40 (UTC)

I get a module mismatch error when I run startx after installing this. Any idea why that is? Does it have to do with this package being out of date?

Corngood commented on 2016-06-01 02:07 (UTC)

@nirei: I've updated to 16.20.3, and vulkan has been working for me.

nirei commented on 2016-05-31 16:46 (UTC)

I got the 16.15.2 version working with CIK via this PKGBUILD: . That PKGBUILD basically extracts the whole driver package into one directory and symlinks paths to libs to match where the Arch system expects them. This works on a patched 4.5 and 4.6 kernel. No DKMS module needed. For example, the following symlinks are set for the file from the driver package: > /usr/lib/dri/ -> /usr/lib/x86_64-linux-gnu/dri/ and > /usr/lib/xorg/modules/dri/ -> /usr/lib/x86_64-linux-gnu/dri/ I don't know which of the two symlinks gets used, but throwing in a hand full of such symlinks sure helped to get the AMDGPU-PRO OpenGL, OpenCL and Vulkan parts get running on Arch. The same PKGBUILD also works for the 16.20.3 version of the driver (simply adjusting pkgver and _amdver), but i run into errors with the Vulkan lib when running Vulkan applications. OpenGL acceleration from the AMD driver seems to work fine.

Themaister commented on 2016-05-30 20:09 (UTC) (edited on 2016-05-30 20:17 (UTC) by Themaister)

I saw that a DKMS module was installed, but do I need to do something special to have it actually compile? I'm using 4.5.4 with CIK config added in my kernel build. Has anyone got this to work on CIK at all?

Corngood commented on 2016-05-30 17:07 (UTC) (edited on 2016-05-30 17:21 (UTC) by Corngood)

I'm really not sure why you're having so much trouble. Have you looked through strace or LD_DEBUG=all for loading of any incorrect libraries (mesa)? Maybe just remove mesa and see what breaks then? Perhaps you're on to something with that ioctl, which would imply a kernel problem. Are you using kernel 4.5.4+CIK? Have you tried building the dkms module, or using 4.6/4.7? Edit: actually from what I can tell 0 is ok for that ioctl.

Themaister commented on 2016-05-30 16:03 (UTC)

Another interesting thing is that using LD_LIBRARY_PATH I can get glxinfo to return 4.5 core context from amdgpu-pro's GL implementation while in plain amdgpu Xorg. glxgears "runs", but it's completely corrupted. Probably due to mismatch in how the GLX implementation does things ...

Themaister commented on 2016-05-30 14:05 (UTC)

I got a paste of what happens right before "accel disabled": It calls DRM_IOCTL_GET_CLIENT and returns 0. I'm not sure if this means error or not in this case.

Themaister commented on 2016-05-30 13:10 (UTC)

Installed the amdgpu package from LiberteCzech. I still cannot get GLX. Same error. I cannot understand what is possibly blocking GLX here. I've rerouted every .so I can see in ldconfig. What "works" is to use Mesa's xf86-video-amdgpu thing, and LD_LIBRARY_PATH for apps which use Vulkan. Then amdgpu-pro "works". I cannot get a window, but off-screen stuff can run to some extent.

lahwaacz commented on 2016-05-28 09:52 (UTC)

The PKGBUILD does not specify the license:

Corngood commented on 2016-05-27 03:15 (UTC)

My PR is also now updated to 16.20.3. It needed a couple of changes to the generator to deal with new dependencies, but it appears to be working. @Themaister looks like the surface extension is fixed in this version.

storma commented on 2016-05-25 12:58 (UTC)

@LiberteCzech I made the same changes as you did and it works fine. Needed the tweaks from below to get it running though.

LiberteCzech commented on 2016-05-25 09:10 (UTC)

Here is the latest driver. I used the corngood and LEW21 work. If you have time, you can try and let you know if it works. I did not have time to test it yet.

Corngood commented on 2016-05-19 21:54 (UTC) (edited on 2016-05-19 21:56 (UTC) by Corngood)

Mine looks similar to yours (I also get the (EE) about the hybrid driver) up until: [ 78.193] (II) LoadModule: "dri2" [ 78.193] (II) Module "dri2" already built-in [ 78.198] (II) glamor: OpenGL accelerated driver based. [ 78.284] (II) glamor: EGL version 1.4: Where yours says: [ 557.285] (II) AMDGPU(0): GPU accel disabled or not working, using shadowfb for KMS Maybe check if EGL is correct: $ ldconfig -p | grep libEGL (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/amdgpu-pro/ The only active xorg.conf files I have are: /usr/share/X11/xorg.conf.d/01-amdgpu-pro.conf /usr/share/X11/xorg.conf.d/10-evdev.conf /usr/share/X11/xorg.conf.d/10-quirks.conf So maybe get rid of any others in there or in /etc/. After that I'd probably use LD_DEBUG and strace to figure out what it's doing before it prints those messages. Then maybe build a debug xorg-server. I'm using xorg-server 1.18.3-1 and kernel 4.5.4 w/ CIK. I assume you are on similar versions and on x86_64? Edit: also I'm on HAWAII, not BONAIRE.

Themaister commented on 2016-05-19 08:42 (UTC) (edited on 2016-05-19 09:46 (UTC) by Themaister)

Hm, still doesn't work. Here's a paste of Xorg.0.log. I'm using a GCN 1.1 card with CIK enabled in kernel if that helps. ldconfig is pointing to the right place. It seems like it's failing something, trying fall back to software which doesn't work. Plain MESA with AMDGPU is working however.

Corngood commented on 2016-05-18 15:02 (UTC)

Sounds like the problem I had before I had set up properly. Maybe 'ldconfig -p | grep' and make sure it's finding the amdgpu-pro one rather than mesa? You could try the PKGBUILD from my pull request as it fixes the

Themaister commented on 2016-05-18 14:57 (UTC)

I'm also struggling to get GLX working at all. Either I get a segfault if I enable DRI3 or I don't get GLX at all ... Do you need to do something special to get GLX working?

Corngood commented on 2016-05-18 14:16 (UTC)

@libercv Yeah, I noticed that when I went through and fixed up the PKGBUILD. Now it makes a link for the ld and modprobe configs. PR is up at if anyone wants to take a look. @Themaister Yeah, I have that problem too. It was broken by this change in the loader: which was merged in 1.0.8. If I use 1.0.6 I get the extension, and it seems to work fine. It's a bug in the AMD vulkan ICD, which only reports VK_KHR_swapchain and VK_KHR_xbc_surface. I guess it worked by accident before that loader change. I tried reporting it on, but I'm still waiting for my post to be approved. If anyone has a better way of reporting bugs to them, let me know.

Themaister commented on 2016-05-18 14:07 (UTC)

For some reason, VK_KHR_surface is missing for me (VK_KHR_xcb_surface is present though). Anyone else having same issue?

libercv commented on 2016-05-18 10:38 (UTC)

Thanks a lot @Corngood, it works!!! Just one minor change. I copied /usr/lib/amdgpu-pro/ld.conf to /etc/ instead of creating a link to gbm. I couldn't make it work with the symbolic link, but the file already includes the path to gbm.

Corngood commented on 2016-05-17 21:24 (UTC)

@jhackler I'll try to fix up the PKGBUILD to do all this stuff when I get a chance, but for now: - Before you do this, consider making a snapshot or backup, and I suggest 'systemctl set-default multi-user' to avoid having to touch your kernel args to stop Xorg from running in case something goes wrong.. - 380 is GCN 1.2 I think, so you _should_ get the amdgpu driver if you - Update your kernel (I used 4.5.4) - Blacklist the radeon driver (put "blacklist radeon" in /etc/modprobe.d/blacklist-radeon.conf) - Reboot and verify amdgpu is loaded (lsmod | grep amdgpu) - At this point if you have mesa installed you should have a working system with GL, etc. If you are in text mode, 'systemctl isolate graphical' to start X, and if you want, run glxgears or something to verify - 'systemctl isolate multi-user' to quit Xorg if you launched it - Make sure you don't have anything driver specific in /etc/X11/xorg.conf, /etc/X11/xorg.conf.d/*, or /usr/share/X11/xorg.conf.d/* - Install this AUR package (e.g. 'pacaur -S --force amdgpu-pro') - I'm not sure if --force works with pacaur, but the point is to force overwrite the conflicting firmware files. If not, install it with 'pacman -S --force'. - 'sudo ln -s amdgpu-pro/gbm/ /usr/lib/x86_64-linux-gnu/' - Alternatively you _might_ be able to make the ink in the amdgpu-pro dir, or add gbm/ to ld.conf, but this is what I did. Without it, Xorg wouldn't start. - 'sudo ln -sf 1.18 /usr/lib/x86_64-linux-gnu/amdgpu-pro/xorg' - The package ships with a symlink to the Xorg 1.15 driver, so you need this if you have an up to date 'xorg-server'. - create /etc/ with: ============== /usr/lib/x86_64-linux-gnu/amdgpu-pro /usr/lib/i386-linux-gnu/amdgpu-pro ============== - `sudo ldconfig` - Now you should be able to 'systemctl isolate graphical' and have everything working. - Steam does some shenanigans with the LD path, so I have to run it with "LD_LIBRARY_PATH=/usr/lib/i386-linux-gnu/amdgpu-pro/ steam". This could be fixed by including top level symlinks to libGL etc. If you have any problems feel free to email me. I wrote this from memory, so I could have forgot something. I'm going to go see how much of this I can fix in the PKGBUILD, which should make the process less painful.

Jhackler commented on 2016-05-17 09:11 (UTC)

Corngood If you don't mind, and have the time, could you post slightly more detailed instructions on how you did this, just so I can test it on my r9 380? If not I will eventually go through and figure it out myself or wait for a package update :/.

Corngood commented on 2016-05-15 19:39 (UTC)

It works! I just didn't have the amdgpu-pro libs in After adding the path, Xorg starts, GL works, Vulkan works. I haven't tested lib32 GL, VDPAU etc, but it's good enough for me to keep working on my vulkan projects after moving from NV to AMD. Also I tried it both on linux 4.2 + amdgpu-pro-dkms, and 4.5.4 + CIK. 4.2 doesn't detect my screens properly, but 4.5 does. I haven't noticed any other differences. So I guess the only real problems with this package on latest Arch are: - xorg 1.18 symlink - symlink ? - entry - firmware conflicts Then for people with GCN < 1.2 chips, getting the correct kernel (4.5.4 with CIK option or whatever GCN 1.0 patches AMD released in the last couple of days).

Corngood commented on 2016-05-14 16:32 (UTC)

Has anyone actually got this to work? I'm just going through the process now on my R9 290. I made some notes: - install amdgpu-pro - firmware conflict (mentioned below). I just overwrote with the amdgpu images from this package - built kernel 4.5.3 with CIK - downgraded to xorg 1.15 - crash in Xorg at GLX init - upgrade to xorg 1.18 - symlink xorg driver 1.18 (mentioned below) - similar crash in Xorg - build kernel 4.2 without amdgpu - install amdgpu-pro-dkms - OS_VERSION problem with /etc/os-release, fixed by defaulting OS_VERSION to 0.0 in the Makefile - -Wno- some warnings to make it compile with -Werror - /boot/[uname] is needed, so copied that from my kernel build - dkms module seems to load ok, but I still get a similar crash in Xorg - build debug Xorg - Xorg log now shows the signal handler as the crash stack - running in gdb shows this stack for the segfault: So it's a crash during dlopen() of (calling 0), for which I have no symbols. I couldn't find anything relevant in strace or the xorg log before the crash. P.S. Thanks for packaging this. I probably wouldn't have bothered to try if it didn't exist.

nirei commented on 2016-04-02 14:43 (UTC)

@silakka The xserver-xorg-video-amdgpu-pro package provides drivers for Xorg versions 1.15 up to 1.18. In the package the default Xorg version is set to 1.15 via a softlink pointing to the directory with the 1.15 drivers. You can see that on startup Xorg loads the driver from the correct path, but the softlink it uses along that path simpy points to a driver version too old for you Xorg. From your Xorg.log: >> (II) Loading /usr/lib/x86_64-linux-gnu/amdgpu-pro/xorg/modules/drivers/ The amdgpu-pro directory looks like this: drwxr-xr-x 3 sergej users 4096 17. Mär 03:31 1.15 drwxr-xr-x 3 sergej users 4096 17. Mär 03:31 1.16 drwxr-xr-x 3 sergej users 4096 17. Mär 03:31 1.17 drwxr-xr-x 3 sergej users 4096 17. Mär 03:31 1.18 lrwxrwxrwx 1 sergej users 4 17. Mär 03:31 xorg -> 1.15 To set the correct link you can do the following: > cd /usr/lib/x86_64-linux-gnu/amdgpu-pro/ > rm xorg > ln -s 1.18 xorg But even after this amdgpu-pro probably still won't work. Looks like AMDs release only works on older kernels where the amdgpu-pro DKMS modules can be compiled successfully.

LEW21 commented on 2016-03-31 11:35 (UTC)

Looks like the firmware package is going to be useless when the next linux-firmware will be released:

LEW21 commented on 2016-03-29 14:55 (UTC)

Looks like the xserver-xorg-video-amdgpu-pro module requires older You may want to use Arch's xf86-video-amdgpu instead - however I have no idea if it will work with pro's GL drivers.

silakka commented on 2016-03-29 11:40 (UTC)

I did install and overwrite, but Xorg didn't start and not sure what's the issue. Xorg.log:

LEW21 commented on 2016-03-29 11:02 (UTC)

About firmware files? Yeah, I guess you can try to ignore the amdgpu-pro-firmware package, and run it with the firmware from linux-firmware. Or, alternatively, overwrite the files - and later simply reinstall linux-firmware to get the old ones back.

silakka commented on 2016-03-29 10:43 (UTC)

Complains about files already existing in filesystem, not brave enough to force install :(

silakka commented on 2016-03-29 10:37 (UTC)

I have a supported card (R9 Nano), going to test.

LEW21 commented on 2016-03-28 23:00 (UTC)

Note: I don't have any idea if it works. Unfortunately, upstream AMDGPU does not work on my Athlon 5350, and I don't have time to compile the AMDGPU PRO's kernel modules, as they work only with Linux 4.2, and the chances that they will fix the problem are small. Pull requests welcome at