I looked this up before buying the GPU, and I read that it should “just work” on Debian stable (Bookworm, 12). Well, it doesn’t “just work” for me. :(

clinfo returns two fatal errors:

fatal error: cannot open file '/usr/lib/clc/gfx1100-amdgcn-mesa-mesa3d.bc': No such file or directory

fatal error: cannot open file '/usr/lib/clc/gfx1030-amdgcn-mesa-mesa3d.bc': No such file or directory

I get similar errors when trying to run OpenCL-based programs.

I’m running a backported kernel, 6.6.13, and the latest Bookworm-supported mesa-opencl-icd, 22.3.6. From what I’ve found online, this should work, though Mesa 23.x is recommended. Is it safe/sane to install Mesa from Debian Trixie (testing)?

I’ve also seen references to AMD’s official proprietary drivers. They do not officially support Debian, but can/should I run the Ubuntu installer anyway?

I’m hoping to get this up and running without any drastic measures like distro hopping. That said, if “upgrade to Testing or Unstable” is the simplest approach, I am willing to entertain the idea.

Thanks in advance for any help you can offer.

  • hersh@literature.cafeOP
    link
    fedilink
    arrow-up
    3
    ·
    6 months ago

    Update: I upgraded to Sid. Unfortunately, mesa-opencl-icd depends on libclc-17, which uninstalls -18. So I can’t get OpenCL working while the correct libclc is installed.

    No idea where to go from here. I’ll probably restore my Bookworm snapshot, since I don’t want to be on Sid if it doesn’t solve this problem.

    • bloodfart@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      6 months ago

      you ought to be able to specify the version to install of libclc after mesa-opencl-icd is installed, you could instead force the newer libclc 18 with dpkg. you can also create a vile mutant install by adding sid backports or repository to your perfectly fine stable install. here are some resources to help you destroy your system

      e: i was hoping that last sentence would be clearly four links because of underlining but that’s not working, here it is in cursed haiku format:

      here are

      some resources

      to help you

      destroy your system

      • hersh@literature.cafeOP
        link
        fedilink
        arrow-up
        2
        ·
        6 months ago

        IT WORKS NOW! I will need time to run additional tests, but the gist of my solution was:

        1. Backport llvm-18 from sid following the guide you linked at https://wiki.debian.org/SimpleBackportCreation

        2. After compiling and installing all those deb files, I then installed the “jammy” version of amdgpu-install_6.0.60002-1.deb from https://www.amd.com/en/support/linux-drivers

        3. Downloaded the latest kernel sources from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git, and simply copied all the files from its lib/firmware/amdgpu folder into my system’s /lib/firmware/amdgpu. Got that idea from https://discussion.fedoraproject.org/t/amdgpu-doesnt-seem-to-function-with-navi-31-rx-7900-xtx/72647

        4. sudo update-initramfs -u && sudo reboot

        I’m not totally sure it step 3 was sane or necessary. Perhaps the missing piece before that was that I needed to manually update my initramfs? I’ve tried like a million things at this point and my system is dirty, so I will probably roll back to my snapshot from before all of this and attempt to re-do it with the minimal steps, when I have time.

        Anyway, I was able to run a real-world OpenCL benchmark, and it’s crazy-fast compared to my old GTX 1080. Actually a bigger difference than I expected. Like 6x.

        THANKS FOR THE HELP!

      • hersh@literature.cafeOP
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago

        Thanks for the links! I’ve never attempted making my own backport before. I’ll give it a shot. I might also try re-upgrading to sid to see if I can wrangle it a little differently. Maybe I don’t actually need mesa-opencl-ics if I’m installing AMD’s installer afterwards anyway. At least, I found something to that effect in a different but similar discussion.