Announcement

Collapse
No announcement yet.

AMDGPU-PRO is officially unsupported for Ryzen APUs in Linux

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • AMDGPU-PRO is officially unsupported for Ryzen APUs in Linux

    I recently got a Ryzen 2200g for a new compact HTPC in my living room. I had planned to use Lubuntu 16.04.4 with AMDGPU-PRO drivers so that hopefully sound would work over HDMI, but I haven't been able to get the AMDGPU-PRO drivers working with any *buntu distro. I have tried Lubuntu and Ubuntu 16.04.4 and Ubuntu 17.10.1, all of which behave slightly differently but none of which work with the pro driver.

    I raised a support request with AMD to ask them exactly which distro I should be using and they responded stating that Linux is not supported with Ryzen APUs, and to receive support I need to install Windows 10. Here's the relevant quote from the email:

    ... Please be informed that for specified Ryzen APU there is no driver support for any Linux OS. As of now they are limited to Windows 10 OS only. I request you to use the compatible Operating System to get the driver support
    Thanks for contacting AMD
    This isn't a rant, although I am rather disappointed, but I thought I'd start this thread to let others know because I haven't seen this written anywhere else. There is hope though, as the use of the words "As of now" suggests that maybe they will be supported future.

    In the meantime, has anyone had the PRO driver working with a 2200g and ASRock AB350 Gaming-ITX/ac board with any distro? If so I'd love to hear which distro and what is required to get it working.

    Cheers.

  • #2
    Use the latest open source driver. You can test my distribution: https://www.youtube.com/watch?v=fKJ-IatUfis

    Comment


    • #3
      AMDGPU-PRO is not officially supported on any APU products - this is not specific to Raven. That said, we do try to keep AMDGPU-PRO working on APUs at a developer level.

      In general the only reasons for running AMDGPU-PRO on an APU would be (a) for running CAD workstation apps requiring compatibility profiles or (b) running OpenCL. In all other cases the open source drivers are probably the best fit.

      We are continuing to evolve the OpenCL support and hopefully making it easier to use with an otherwise all-open stack.
      Last edited by bridgman; 03-19-2018, 06:53 PM.

      Comment


      • #4
        Thanks for the replies. I think I'll try Lubuntu 16.04 with m-bab's kernel (https://github.com/M-Bab/linux-kernel-amdgpu-binaries). I notice Martin suggests installing the latest blobs too. I haven't done this before. Is it just a case of cloning the repo from https://git.kernel.org/pub/scm/linux...-firmware.git/ and then copying the relevant binary to /lib/firmware?

        Comment


        • #5
          debianxfce - I tried your distro thinking that it might be the easiest option, but the video output went corrupt as soon as it moved off the menu screen. I tried expert graphical install and expert install.

          Comment


          • #6
            Originally posted by khinch View Post
            debianxfce - I tried your distro thinking that it might be the easiest option, but the video output went corrupt as soon as it moved off the menu screen. I tried expert graphical install and expert install.
            Install it to a fast usb memory stick to test it. The partitioner uses whole disk. User https://www.phoronix.com/forums/member/107276-tw78 got my distribution to work with Ryzen 5 2400G. He used UEFI installer not MBR that causes screen corruption with these G chips. With RX560 MBR installer works fine.
            Last edited by debianxfce; 03-24-2018, 08:37 AM.

            Comment


            • #7
              Thanks, I'll try that at the weekend and let you know how I get on. (I don't get much time for projects these days!)

              Between my last post and your reply I also tried Lubuntu 16.04 with M-Bab's kernel, but it lost video as soon as it left the boot menu. I think the kernel completely locked because ALT+SysRq+B didn't respond.

              Comment

              Working...
              X