On Wed, 2019-10-30 at 01:32 +, Eric Smith wrote:
> Upgrading the BIOS to a version with new AMD Ryzen microcode solved the
> problem.
When replying via HyperKitty please follow long-standing practice and
quote the context as HK doesn't do this by default.
poc
Upgrading the BIOS to a version with new AMD Ryzen microcode solved the problem.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> I had the same problem, I usually buy AMD processors, but I read about
> the problem, I bought an Intel box. Still, the whole boot process
> seemed to take place up, but ended in an infinite loop waiting for
> startup process to end.
I ran into that also with F30, but it's not the same problem
> Questions about F31 should be directed to the Fedora Test list.
Sorry, since F31RC1.9 was approved for release, it hadn't occurred to me to
post to the test list. However, I have done so now.
___
users mailing list -- users@lists.fedoraproject.org
To
I had the same problem, I usually buy AMD processors, but I read about
the problem, I bought an Intel box. Still, the whole boot process
seemed to take place up, but ended in an infinite loop waiting for
startup process to end. I threw in the towel on Fedora and went to
Ubuntu. But ubuntu 19.04
On Sun, 2019-10-27 at 20:22 -0600, Eric Smith wrote:
> I have a new Ryzen 7 3800X system, and since Fedora 30 won't install on
> that, I tried Fedora 31 RC1.9 Workstation Live. That boots up fine, but
> when I try to install to my "disk" (M.2 NVMe), if file system encryption is
> enabled, it hangs
I have a new Ryzen 7 3800X system, and since Fedora 30 won't install on
that, I tried Fedora 31 RC1.9 Workstation Live. That boots up fine, but
when I try to install to my "disk" (M.2 NVMe), if file system encryption is
enabled, it hangs at "Creating luks on /dev/nvme0n1p6". I let it sit there
for
