cross-posted from: https://lemmy.world/post/39410719

Error when trying to install Bazzite specifically

I get the following error message:

amd_pstate: failed to register with return -19

And there’s more but then the screen turns into a creepy pasta gif looking thing of white and green shifting blocks, except for a few random letters.

But the issue doesn’t happen when I used a Garuda xfce I had laying around I used for an older PC (that was maybe too old for Bazzite?). That went into the installer and live iso environment without issues.

It’s a newish build I’m making for someone as a gift with the following hardware:

Asus Prime B550M-K AM4 microATX Kingston FURY Beast DDR4 3600 MHz AMD Ryzen 5 4500 AM4

And a used Nvidia RTX 3060ti.

I have secure boot off I think (the Asus EZ bios is weird)

Update

I managed to install it using the text installer, but now it does this:

Then blank screen. Ctrl-Alt-F2 gives me a terminal at least and I did just get-logs which gives me the following:

Is this a Wayland issue?

Update 2:

Not a Wayland issue. But tried installing Fedora Kiinoite to rebase it to Bazzite, but Fedora has the same issue Bazzite did when trying to install, only it doesn’t mention the Elf 19 error, and it frezzes allowing me to take a picture:

I really love Bazzite and run it on my own computer, but I’m starting to think it doesn’t really run on older desktop hardware.

  • sp3ctr4l@lemmy.dbzer0.comEnglish
    3·
    16 hours ago

    Ok so, intel gathering:

    https://bbs.archlinux.org/viewtopic.php?id=305924

    Same error for an Arch user, who says (about his HW and situation):

    It’s AMD Ryzen 5 5500U with Radeon Graphics (Integrated), HP Laptop 15-ef2126wm. I have to use IOMMU, otherwise sleep doesn’t work (It get stuck after waking up from sleep, s2idle)

    https://discuss.cachyos.org/t/amd-pstate-failed-to-register-with-return-19/8214/8

    Same amd_pstate 19 error, this time in Cachy OS

    Just ran into this same situation on the same chipset but different board, an Asrock A520M-DHV, but the issue is the same. The latest BIOS from 2025 breaks AMD CPPC and results in both the errors the OP posted as well as no amd_pstate governing (higher core usage, more heat/power, etc.) Downgrading to the last BIOS from 2024 (version 3.52) fixes the issue.

    https://forum.proxmox.com/threads/amd-pstate-driver-steps-and-discussion.118873/

    This may also be relevant.

    So… so far, my guess would be that your motherboard firmware and/or BIOS/UEFI config are having some kind of problem, and maybe possibly it is specific down to either or both the IOMMU and CPPC systems.

    Maybe you can try checking the setting for CPPC? If it is toggled off, try turning it on?

    It seems like this error has been a recurring issue amongst varying systems and varying kinds of Linux… I am not sure from what you’ve written if this is only happening to you with Bazzite…

    … but uh, yeah, it looks like just a lot of MoBos have been having trouble with specifically the AMD CPPC part of their firmware, when running seemingly any kind of Linux.

    I don’t know if this is very helpful or not, but maybe narrowing down to either CPPC or IOMMU could be an idea?

    It at least does make sense that you’re getting hard crashes with graphical glitches, even without a gui… if the CPU itself is fundamentally locking up and being unable to execute commands, that would fit, I would think, with CPPC or IOMMU systems being the culprit.

    • Lumisal@lemmy.worldOPEnglish
      2·
      15 hours ago

      So I’ve tried downgrading bios and disabling CPPC, but neither helped.

      However, that was with Bazzite, not Cachy. I’m not currently as I speak installing Cachy, as that actually loaded into the live iso (seems Arch based distros so far make it through at least, since Garuda also managed to install) - but, it also currently only outputs in 720p. I’ll see if that persists once it’s fully installed, and if it does, I’ll try something else - I’ll try to see if it’s still blurry when using Dvi instead of HDMI.

      • sp3ctr4l@lemmy.dbzer0.comEnglish
        2·
        15 hours ago

        Ok, ok, explain this to me like I have no idea what is going on.

        So, step 1:

        What OS did this hardware originally run?

        Windows… 10? 7? XP?

        Did you ever get comparable like, total screen lockups, hard crashes from it?

        ???

        Step 2:

        What different Linux OS’s have you tried to install on this HW, what happened when you tried to install each one?

        Which ones worked as a LiveBoot, but failed on bare metal, or vice versa?

        Step 3:

        Which of those installs did you try with which MoBo firmware versions, and what BIOS/UEFI settings?

        There are a ton of variables going on here, and… yeah I have no clue what the proverbial spreadsheet from combining steps 2 and 3 would look like.

        The pstate 19 error seemingly always has something to do with CPPC firmware being borked in some kind of way on various MoBo models…

        But you’re saying sometimes you can actually get to a working bare metal install, on Garuda, though only in 720p via DVI?

        • Lumisal@lemmy.worldOPEnglish
          2·
          14 hours ago

          So, step 1:

          What OS did this hardware originally run?

          None - all parts new except the graphics card.

          Step 2:

          What different Linux OS’s have you tried to install on this HW, what happened when you tried to install each one?

          Which ones worked as a LiveBoot, but failed on bare metal, or vice versa?

          Bazzite, Garuda, and currently Cachy.

          Bazzite only worked baremetal, Garuda is stuck at 720p, and Cachy is also stuck at 720p. Changing open source drivers to closed source did not work on Cachy, and the display was glitched. Changing it back didn’t help either.

          Edit: I was typing more but figured out it’s the graphics card that’s bad 🥲

          • sp3ctr4l@lemmy.dbzer0.comEnglish
            2·
            14 hours ago

            Edit: I was typing more but figured out it’s the graphics card that’s bad 🥲

            lol.

            Welp, that probably doesn’t help solve the problem, but … it is identifying the problem.

            Yeah… I’ve been burned too many times buying used GPUs, even managed to get some from Amazon, that had been burnt out on BTC mining, and then (shoddily) repackaged, sold as new.

            Never doing that shit again, not unless I can like, drive over to someone’s house and actually see it working.

            • Lumisal@lemmy.worldOPEnglish
              2·
              14 hours ago

              Well luckily I have an emergency spare 1660 super at least that I know works.

              First time I’ve been burned on a used card. Should have been known that deal was too good to be true this time.

              Still, between the 1660 super and this 3060ti, still cheaper than a new 4050 or 5060 and even AMD stuff of comparable performance. Though the Intel Arcs are around there - if I knew how well they ran on Linux, I’d be willing to give them a try in the future brand new.

              • sp3ctr4l@lemmy.dbzer0.comEnglish
                2·
                14 hours ago

                I am genuienly sorry you had to learn the hard way, but hey, so did I (repeatedly, because I am apparently a moron)… once bitten, twice shy, eh?

                But yeah, if you’re looking for a fairly low spec GPU? Yeah I mean I’m generally more of an AMD fanboy, but the beefier of the Intel cards are doing pretty good for a low budget range.

                I can’t say I have any idea how well they run Linux though, not via direct experience anyway.