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.

  • cevn@lemmy.world
    2·
    9 months ago

    Mine went back to no display only on boot, so I guess it didnt work for me either :( good luck tho!!

    • loaExMachina
      2·
      9 months ago

      Aw, too bad :( Good luck to you as well, tho! I’ve bookmarked your comment, so I’ll be back to tell you if I find the solution, however long it takes!

    • loaExMachina
      2·
      7 months ago

      I still haven’t found the solution, have you had any luck with yours?

      I tried switching every UEFI setting that seemed to have something to do with booting or gpus, reinstalled gpu bios, upgrading mobo bios, getting a monitor I could plug without a switch… All to no avail.

      Well, I think before upgrading the BIOS, one thing had a slightly different result: Setting the boot mode to UEFI and disabling CSM made it display “no gop (graphic output protocol)” after a few minutes, and it offered to either take me to the uefi settings or loading defaults (which implied going back to CSM), after which it boot this time go back to doing the same thing.

      I don’t think I’ve had this error since the mobo bios upgrade, but still no display unless I reboot, unless the computer had been turned in until recently. I’m kinda out of ideas…

      • cevn@lemmy.world
        2·
        7 months ago

        …unfortunately no… I work around it by knowing what buttons to press but it’s pretty stupid.