Announcement

Collapse
No announcement yet.

Trying To Run The AMDGPU Driver With A Hawaii GPU On Linux 4.5

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

  • Trying To Run The AMDGPU Driver With A Hawaii GPU On Linux 4.5

    Phoronix: Trying To Run The AMDGPU Driver With A Hawaii GPU On Linux 4.5

    While the AMDGPU DRM driver doesn't enable the necessary Kconfig option by default, it's supposed to be possible to use this new DRM driver with the AMD GCN "Sea Islands" (CIK) graphics cards rather than just Tonga and Fiji when it comes to the currently shipping discrete GPUs...

    http://www.phoronix.com/scan.php?pag...PU-R9-290-Fail

  • #2
    Did the kernel load the correct firmware files? That was the first problem I hit when running the AMDGPU driver on an A10-7800 APU.

    Comment


    • #3
      I had a similar error:
      I think it's trying to initialize PowerPlay which your ASIC does not have.
      Try without powerplay or with this fix: http://cgit.freedesktop.org/~agd5f/l...66db67f2d05c61

      Comment


      • #4
        Originally posted by mathb_81 View Post
        I had a similar error:
        I think it's trying to initialize PowerPlay which your ASIC does not have.
        Try without powerplay or with this fix: http://cgit.freedesktop.org/~agd5f/l...66db67f2d05c61
        Aha, yes, I had left amdgpu.powerplay=1 enabled. Once doing so and rebooting, I got a different error but it pointed clearly to firmware: hawaii_sdma1.bin. So then I downloaded all of the latest Hawaii firmware files from 16 October 2015 into /lib/firmware/radeon and rebooted... Same proiblem. Is there any newer firmware than the 16 Oct for Hawaii? Or some other problem bridgman ?

        http://pastebin.ca/3354345
        Michael Larabel
        https://www.michaellarabel.com/

        Comment


        • #5
          As an R9 290 user, I would be really interested to see this work. I look forward to seeing more results.

          Comment


          • #6
            You are missing hawaii_sdma1.bin. You can find it in the linux firmware tree:
            http://git.kernel.org/cgit/linux/ker...it/tree/radeon

            Comment


            • #7
              Originally posted by agd5f View Post
              You are missing hawaii_sdma1.bin. You can find it in the linux firmware tree:
              http://git.kernel.org/cgit/linux/ker...it/tree/radeon
              Hey Alex, I had grabbed all of them (including sdma1) from http://people.freedesktop.org/~agd5f..._ucode/hawaii/ which looks like it is the same version? Then placed it in /lib/firmware/radeon/, or should it be at /lib/firmware/amdgpu perhaps or something?
              Michael Larabel
              https://www.michaellarabel.com/

              Comment


              • #8
                Originally posted by Michael View Post

                Hey Alex, I had grabbed all of them (including sdma1) from http://people.freedesktop.org/~agd5f..._ucode/hawaii/ which looks like it is the same version? Then placed it in /lib/firmware/radeon/, or should it be at /lib/firmware/amdgpu perhaps or something?
                Should be in /lib/firmware/radeon/. Make sure your initrd is updated if you are using one.

                Comment


                • #9
                  Originally posted by lostdistance View Post
                  Did the kernel load the correct firmware files? That was the first problem I hit when running the AMDGPU driver on an A10-7800 APU.
                  How has your experience been running this way? I have an A10-7850 APU running radeon, and was thinking of trying amdgpu. Then I read somewhere that the backward capability was only in amdgpu for pre-hardware debug and would probably never be touched again, now that the planned hardware was available. They suggested sticking with radeon.

                  Comment


                  • #10
                    Originally posted by phred14 View Post
                    Then I read somewhere that the backward capability was only in amdgpu for pre-hardware debug
                    Not "only" for initial development but that is why it was there in the first place.

                    Originally posted by phred14 View Post
                    and would probably never be touched again, now that the planned hardware was available.
                    Don't think we said this... we were definitely planning to use amdgpu on CI for the hybrid driver (closed source userspace), and we have been pushing updates to the CIK code as well, not just VI.

                    Originally posted by phred14 View Post
                    They suggested sticking with radeon.
                    For open source stack, definitely... since that's where all the test coverage is. If we are able to make amdgpu the default driver in upstream & distro trees then obviously that could change, but at the moment we strongly recommend staying with radeon.
                    Test signature

                    Comment

                    Working...
                    X