Each time I try AMD graphics, something is fucked for me. Back with fglrx, fglrx just sucked, so I used Nvidia. Then I had an AMD right around when they finally had opensource drivers, but it was still buggy as hell. So I went with Nvidia again (first a GTX 790, then a GTX 1060). In the meantime I had a new work notebook where I also went with an AMD APU, and had driver crashes for a long time when I was in video calls and it had to decode multiple streams. That thankfully stabilized with Linux 6.4.

Since sooo many people in the community swear by AMD, I thought “dammit, let’s try it again for my new desktop” and got an 7800rx … and I have to reboot ~5 times until I finally make it to a running xserver or wayland session. Apparently I am hit by this problem (at least I hope so). But that doesn’t even read nice … the fix seems to be to revert another fix for powermanagement. So I either have a mostly non-booting card or suboptimal power management.

I start to regret having chosen AMD … again :-/ I seem to be cursed.

  • @c10l
    2•11 months ago

    Run sudo dmesg | grep amdgpu and look for errors.

    You may have a firmware file missing, for instance. If that’s the case, it’s an easy fix - just download the firmware files from the kernel tree and put them wherever your system wants them.

    This is how I do it on Debian but it should be easy enough to adapt to whatever distribution you’re using (it might be exactly the same tbh): https://blog.c10l.cc/09122023-debian-gaming#firmware

    • @aksdbOP
      3•11 months ago

      Thanks for the idea!

      dmesg shows the same errors as in the referenced bug ticket. So I don’t think missing firmware is the issue. I would not be surprised however, if the problem in general is a combination of amdgpu and firmware behavior. (IMO the hardware should not crash as hard as it does, so the firmware seems to be a bit wonky too)