I’m a long time AMD user both my GPU and CPU. I have a powerful enough PSU and a b550m-plus mobo.

I’m looking to do gaming, light AI work, computer programming, running Docker server services.

I have a Radeon 6900xt, but it doesn’t work well with Linux anymore. amdgpu fails to load, and I can only boot by adding nomodeset to my boot entry.

With ArchInstall I even tried reformatting with xfs, ext4, btrfs, without encryption, with and without LVM, selecting both ATI OS drivers for all GPUs, and drivers for AMD gpus, with systemd-boot and grub.

Even Fedora on USB only boots with nomodeset.

Windows seems to boot fine.

I assume it may be a problem with system reading the drivers from the GPU.

I have onboard HDMI for graphics, but I’ve never got it working.

tbh, my 6900XT was too powerful anyways. I do game in 4K with my 55" TV on the highest settings, but it seems I was still barely using the GPUs full potential.

Funny enough, I seem to have had more problems with high end GPUs in the past than low end GPUs.

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    11
    ·
    1 day ago

    amdgpu fails to load

    If you’re referring to the old “amdgpu pro” software, you probably don’t want to be using that. It isn’t necessary for the stuff you want to do, and I’m surprised to learn that it still exists at all — it’s still talked about as if it’s current on the arch wiki. Get rid of that, update the firmware package, run a recent kernel, and then figure out whatever specific thing you actually need for the AI stuff you’re trying to do such as rocm-related things.

    • brucethemoose@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 day ago

      and then figure out whatever specific thing you actually need for the AI stuff you’re trying to do such as rocm-related things.

      For most of this you’d probably want to be running Vulkan anyway. ROCM is mostly slower, at least for quantized text generation.

      • kbal@fedia.io
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        I don’t know, but one possibility to consider is that running amdgpu-pro (or its non-pro counterpart) might’ve done something that stops mesa from working if you didn’t completely undo everything it did.

        • dudesss@lemmy.caOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          1 day ago

          The problem starter with Mesa… Amdgpupro was one of the last thins I tried…