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.

    • aksdb@lemmy.worldOP
      0·
      10 months ago

      I did live like this with all my intel/nvidia systems just fine, though. If AMD tends to have bugs like this, they still seem to suffer from the same shitty software development attitude as they did back in the fglrx days… with the added advantage that people from the community can now firefight some of the problems. For a product I paid a few hundred euros for I expect some quality assurance for its driver development - that seems to work with nvidia.

  • loaExMachina@sh.itjust.works
    0·
    10 months ago

    Using amd GX 6600… Mostly going fine, tho I haven’t tried any big heavy games. One thing tho… Everytime I turn on my computer, no display. I reboot it and then ot works fine, but ot never does the first time. One path I’ll investigate is the monitor: my monitors are both older and use DVI or VGA ports, so I have to use converters. I might try and get my hand on a more recent monitor to see if I still get the same problem. But if I do, I’m not even sure where to ask. I don’t even think it’s a linux problem, because I tried removing my drive with linux living one with windows and the problem remains. I also was using mint when the problem started and switched to Arch (btw) since and it doesn’t change a thing.

    • cevn@lemmy.world
      0·
      10 months ago

      I had a similar problem which was resolved by disabling the motherboard integrated graphics in bios settings.

      • loaExMachina@sh.itjust.works
        0·
        10 months ago

        Thank you ! It didn’t seem to work on it’s own, but I also noticed I wasn’t booting in EFI mode, so maybe if I just change my booting partition and combine it with your advice it’ll work…

        • cevn@lemmy.world
          0·
          10 months ago

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

          • loaExMachina@sh.itjust.works
            2·
            8 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·
              8 months ago

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