I’m curious if anyone has had much luck leveraging older AMD hardware to use ROCm, I have an 6700 xt that I’ve just begun inquiring about, and it seems it falls outside of official support.

Right now I intend to pass it through to my Debian Docker VM to support transcoding in some containers in addition to machine learning applications.

  • panda_abyss@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    God after buying an amd machine last year I’m never doing it again.

    What are you trying to use rocm for? Their own guides don’t work.

    • OpticalMoose@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      A couple of years ago, I bought a Radeon laptop, just to see how things were going with ROCm. It worked out ok, but convinced me not to buy a discrete Radeon GPU for my desktop.

      I decided to buy another Nvidia card, and finally start investing in NVDA.

    • despoticruin@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 hours ago

      Their guides specifically call for an exact kernel version, distribution, and hardware. If you are trying to operate outside of the official requirements then it shouldn’t come as a surprise when the official documentation doesn’t work for you.

      • panda_abyss@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 minutes ago

        do you know how insane it is their official guides don’t work with kernel point updates?

        https://github.com/ROCm/ROCm/issues/5824

        This has been an issue for a long time.

        I have to maintain a file of which specific kernel+os+firmware versions I’m on and have downgraded to just to get the most popular ML library in the world to du a matrix multiply.

        I don’t get how this bug gets into production branch, let alone shipped requiring firmware downgrades, on their new line of GPUs/chips. How do they not test their latest hardware with their own firmware?

    • roundup5381@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 hours ago

      mostly it is the hardware I have on hand; first project in mind is ROCm machine learning for immich. after that it’s pretty much trying to understand the technology, I’m sure I’ll come up with something fun.

      • panda_abyss@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 hours ago

        I don’t know how the immich ml works, but if you’re going LLMs stick to llama.cpp.

        going beyond that, I’ve had serious kernel bugs with PyTorch and onnx that are still unresolved. The most popular ML/AI frameworks basically don’t work due to drivers for me.

        Vulkan flows are fine and generally comparable in speed so far, so if there’s a vulkan option try rock first then revert to vulkan.

        • roundup5381@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 hours ago

          thanks for the heads up, in truth I’d probably be headed to vulkan now if it were compatible with immich. I’ll put llama.cpp on my radar.