Ask Your Question

Fedora 28 Fails to Install on X399 With New BIOS

asked 2018-09-07 19:53:26 -0600

rfield gravatar image

This one is driving me crazy! I have 6 machines with identical hardware at the office. All have Asrock X399 'Fatality Professional Gaming' motherboards. The only hardware difference is that two have been upgraded from Threadripper 1950X to Threadripper 2990MX CPUs. All machines have nVidia 1080TI GPUs. The attempted Fedora 28 Workstation installation is via UEFI (although this fails on legacy USB as well).

All but one of the machines are running the newest BIOS (v3.3), while one is still running v1.3. All eventually need the newest BIOS so that they can be upgraded to Threadripper 2990MXs, which cannot run on the older BIOS.

The issue is that none of the v3.3 BIOS machines (regardless of which CPU is in them) can run the Fedora live USB installer, although it works flawlessly on the v1.3 BIOS machine. I have tried low graphics mode, "noapic", "nomodeset" (independently from low graphics mode), and "acpi=off". None work. I have changed all the BIOS settings I can think of, and have tried matching all BIOS settings to the v1.3 machine.

The error generally seems to be something along the lines of 'failed to start udev', although I'm not sure how to tell more specifically.

Again, while in BIOS v1.3 I can install Fedora 28 Workstation with no errors or issues at all. All machines can install and run Windows fine, although on the BIOS v3.3 machines Fedora, CentOS, and Ubuntu have all failed to install (although for some reason Ubuntu MATE worked in one instance). I also cannot use a cloned drive from the v1.3 machine that does work - it will never get past boot, also for udevd issues.

Any ideas or help?

edit retag flag offensive close merge delete


A few ideas to start with:

Try Netinstall version. It is just a minimal part of Fedora, all other updated packages are downloaded from network.

Install F27 first and then upgrade afterwards

Try all together: noapic nolapic acpi=off pci=noacpi


keep us updated.

ed209 gravatar imageed209 ( 2018-09-08 04:57:51 -0600 )edit

Try running one of updated F28 ISO's:

There are also test images for upcoming F29:

Also check whether it works on default BIOS settings.

ozeszty gravatar imageozeszty ( 2018-09-08 06:13:02 -0600 )edit

Note that F29 is in pre-beta state, I've had no issues with it, but I have no idea how it'll behave on your workstation.

ozeszty gravatar imageozeszty ( 2018-09-08 06:27:25 -0600 )edit

Thanks! I knew you folks would have some ideas I hadn't tried yet. I'll try all of these and keep you informed.

rfield gravatar imagerfield ( 2018-09-08 11:50:31 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-09-08 15:04:01 -0600

ozeszty gravatar image

It looks like this bug:

So it's best to report it and pressure Asrock to release updated BIOS with that fixed. In-kernel workaround will probably take some time to reach stable version.

Theoretically system installed with older BIOS should boot up on newer one, but with some delay.

edit flag offensive delete link more


That could be it. I have contacted Asrock in regards to the issue, and they have been spectacularly useless so far.

rfield gravatar imagerfield ( 2018-09-09 18:25:26 -0600 )edit

That also seems consistent with comments in this bug report ;) Maybe they can provide you with some beta BIOS with newer microcode from AMD.

ozeszty gravatar imageozeszty ( 2018-09-10 03:53:58 -0600 )edit

Question Tools


Asked: 2018-09-07 19:53:26 -0600

Seen: 359 times

Last updated: Sep 08 '18