Announcement

Collapse
No announcement yet.

Radeon ROCm 4.1 Released - Still Without RDNA GPU Support

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

  • #11
    Originally posted by oleid View Post
    Can you confirm that no DKMS driver is required for mainline kernel starting 5.9?
    It depends on the userspace version - we do some testing of release candidate userspace against recent upstream kernels but over time newer kernels are going to be needed. Or is the question specifically for the 4.1 release ?
    Test signature

    Comment


    • #12
      Originally posted by bridgman View Post

      It depends on the userspace version - we do some testing of release candidate userspace against recent upstream kernels but over time newer kernels are going to be needed. Or is the question specifically for the 4.1 release ?
      In general, latest userspace vs latest kernel. I was wondering if the required bits are mostly frozen.

      Comment


      • #13
        Originally posted by phoronix_is_awesome View Post
        ROCm is dead. It is amazing that many years after the release of RDNA 1, AMD still doesn't have ROCm support for it, yet AMD wants to sell a overclocked 192bit RDNA2 chip without compute at Nvidia ampere 256bit GA104 prices by intentionally busting its 8Gb VRAM buffer because it is "designed for gaming at max 1440P settings". What a joke. Milan, as reviewed by anandtech, is also partly a regression in idle power due to subpar IO Hub chip L3 cache design. What a disappointment.
        For information AMD has two architectural lines GCN and RDNA.

        RDNA is for people whom has empty energy drink cans on their desk and the main color lights flashing all over the place.

        GCN is for super computers and servers.
        Last edited by raun0; 24 March 2021, 04:25 AM.

        Comment


        • #14
          I still remember when someone on this forum told me I was wrong that ROCm would take an incredibly long time to come to RDNA, but, hey, here we are

          Comment


          • #15
            Originally posted by sweetsuicide View Post
            I still remember when someone on this forum told me I was wrong that ROCm would take an incredibly long time to come to RDNA, but, hey, here we are
            Please, read my comment above.

            Comment


            • #16
              Originally posted by raun0 View Post

              For information AMD has two architectural lines GCN and RDNA.

              RDNA is for people whom has empty energy drink cans on their desk and the main color lights flashing all over the place.

              GCN is for super computers and servers.
              You mean all those people who had Radeon 7000 series cards, or R9 2x0/3x0 series cards, or RX400 series cards... all of which were GCN?

              I thought it was RDNA for desktops, CDNA for HPC?

              Comment


              • #17
                Originally posted by bridgman View Post

                Good point - I don't think that all the fixes from 20.45 have worked their way into the ROCm release stream yet but we should definitely mention that once the functionality is there.

                It's possible that we may have to work through at least conceptually separating "the upstream for our compute components" from "our datacenter releases" as a pre-requisite since right now the ROCm releases kinda serve as both. That is going to be an increasing problem as we expand support to consumer hardware.

                Thanks !
                Bridgman,

                is there an effort to simplify/streamline the adoption of ROCm for end users?
                Conceptually ROCm/HIP is fascinating and very promising, but it does not compare with the simplicity of installation (and 3rd party support/implementation) of nvidia.

                Years ago I used to do cuda on nvidia,
                Now I am on polaris (arch linux), i just spent 4 days (probably more, between AMD website, git repos, Arch AUR) to try to get pytorch, torchvisiom, torchtext to run.
                Tried from native rocm on arch, to dockers. An ugly mess!

                Finally yesterday night by creating my own pkgbuild (and a lot of kicking and screaming) got all instaleld
                ... to find out that the gpu computing stalls, no errrors, no dmesg -- just trying a jupyter notebook tutorial from torchtext

                How do I debug?
                How do i ask for help? ( I assume first thing will be: arch is not supported, followed by oh, polaris is not officially supported)

                On top of that ROCm 4.1 is out and I have to recompile EVERITHING ....

                Come on. ...

                Comment


                • #18
                  Originally posted by raun0 View Post

                  For information AMD has two architectural lines GCN and RDNA.

                  RDNA is for people whom has empty energy drink cans on their desk and the main color lights flashing all over the place.

                  GCN is for super computers and servers.
                  GCN is Vega/VII and earlier AMDGPU. *DNA are the GPUs released after that. RDNA is for gaming, general purpose and CDNA is for compute.

                  Pretty much all their APUs are GCN and I wouldn't claim those are for super computers and servers.

                  Comment


                  • #19
                    Originally posted by Grinness View Post

                    Bridgman,

                    is there an effort to simplify/streamline the adoption of ROCm for end users?
                    Conceptually ROCm/HIP is fascinating and very promising, but it does not compare with the simplicity of installation (and 3rd party support/implementation) of nvidia.

                    Years ago I used to do cuda on nvidia,
                    Now I am on polaris (arch linux), i just spent 4 days (probably more, between AMD website, git repos, Arch AUR) to try to get pytorch, torchvisiom, torchtext to run.
                    Tried from native rocm on arch, to dockers. An ugly mess!

                    Finally yesterday night by creating my own pkgbuild (and a lot of kicking and screaming) got all instaleld
                    ... to find out that the gpu computing stalls, no errrors, no dmesg -- just trying a jupyter notebook tutorial from torchtext

                    How do I debug?
                    How do i ask for help? ( I assume first thing will be: arch is not supported, followed by oh, polaris is not officially supported)

                    On top of that ROCm 4.1 is out and I have to recompile EVERITHING ....

                    Come on. ...
                    Have you tried the Arch4edu repos with their rocm-arch packages?

                    You shouldn't need to do more than "sudo pacman -S rocm-dev rocm-utils rocm-libs" if bridgman is correct about how it should just work w/o the dkms package with newer kernels.

                    I have a Polaris but no clue on how to run any ROCm stuff cause I've never done that so I can't help much more than that without being point towards some things to try with a tutorial.

                    Comment


                    • #20
                      Originally posted by skeevy420 View Post

                      Have you tried the Arch4edu repos with their rocm-arch packages?

                      You shouldn't need to do more than "sudo pacman -S rocm-dev rocm-utils rocm-libs" if bridgman is correct about how it should just work w/o the dkms package with newer kernels.

                      I have a Polaris but no clue on how to run any ROCm stuff cause I've never done that so I can't help much more than that without being point towards some things to try with a tutorial.
                      Yes, I was looking at it yesterday night (EU timezone)
                      It is fairly old, as the packages are old.
                      After the experience of the latest 4++ days I am tempted to put together my on pkg

                      With regards with pacman command: AMD expressly states to remove old packages before installing ... (on ubuntu/centos/redhat)

                      Comment

                      Working...
                      X