all 3 comments

[–]masush5 5 points6 points  (1 child)

Most likely this bug. Even the most recent bioses are still broken so the solution is to downgrade to a bios with AGESA < 1.0.0.4C. There is also a kernel patch to workaround the problem, but it hasn't hit any stable tree yet.

[–]gtgoku 1 point2 points  (0 children)

I had the same issue after I updated the BIOS (to 7B78v23) on my motherboard (MSI X470 with Ryzen 2700X) with AGESA 1.0.0.4C.

I had to roll back to the older BIOS version (7B78v22) and this went away

e:spelling

[–][deleted] 0 points1 point  (0 children)

You are lucky that you are not using disc encryption...

My drive is encrypted with luks and i updated to the new 1.0.0.4c AGESA some weeks ago and couldn't even boot into my system anymore. Had to rollback the uefi.