AMD Releases BIOS Fix To Motherboard Partners For Booting Newer Linux Distributions

[pal666]

Systemd is the second most important part after the kernel from a distro building blocks and should try the make sure that it will not stop unless it's really something very very very important missing and only in that case shold stop the booting process.

they didn't stop. their cpu operations were returning incorrect results which broke their program. how can you guard your program from some unknown cpu breakage? maybe some future bug will make cpu start substracting values instead of adding randomly, what can you do now when addition is working as intended?

[rene]

so what is precluding you from reading source comment?

nothing, I'm just not interested in systemd and have other, important things to do

[monte84]

Got my Ryzen 7 3800X in today. Running BIOS 7106 for my Crosshair VI Hero X370 and no trouble booting into my Opensuse Tumbleweed install. Systemd version 242.

[rbmorse]

Debian Buster uses 241 and it's fine, too.

[monte84]

Debian Buster uses 241 and it's fine, too.

Yes, Manjaro would not boot for Michael, same for me, they also appear to be on Systemd 242, not sure which sub version, Arch package shows 242-32. Tumbleweed being a rolling release, I was expecting the same problem, but did not have it. I tried booting Manjaro and received the same errors as Michael.

[oibaf]

Workaround is now in Ubuntu 19.04:

systemd (240-6ubuntu5.2) disco; urgency=medium
    [ Jeremy Soller ]
    * random-util: eat up bad RDRAND values seen on AMD CPUs.
      This fixes AMD Ryzen 3000 series failing to boot (LP: #1835809)

[thunder_burn]

I tried booting Manjaro and received the same errors as Michael.

It works with the latest Manjaro 18.1 testing builds for me.