Arch Linux User Repository

IF PROBLEM HAPPEN

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

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

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

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

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

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

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

@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 https://github.com/Ashark/davinci-resolve-checker script.

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

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.

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.

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.

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. ;-)

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

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

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

Will anyone update this?  

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