Bug 1615668 - Can't Install Fedora 28 on Bios w/ AGESA Code 1.0.0.4C
Summary: Can't Install Fedora 28 on Bios w/ AGESA Code 1.0.0.4C
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: udev
Version: 28
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-14 02:02 UTC by Ryan
Modified: 2019-05-28 22:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:25:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Picture of the screen live USB freezes on and never gets past (95.45 KB, image/jpeg)
2018-08-14 02:02 UTC, Ryan
no flags Details

Description Ryan 2018-08-14 02:02:31 UTC
Created attachment 1475711 [details]
Picture of the screen live USB freezes on and never gets past

Description of problem:
System will not boot from live USB install. Tried several variations of USB drives and Fedora spins including main Fedora 28 Workstation. Error message is 'Failed to start udev Wait for complete device initialization'. Fedora installed prior to Agesa code update from Motherboard manufacturer. No issue installing Ubuntu, Xubuntu, or Mint even after bios update. Only impacts Fedora of the distros tried. 

After research determined likely do to BIOS update by MSI for x470 Pro Carbon.
AGESA Code 1.0.0.4C. Did not have issues prior to this update. Can't roll back BIOS due to hot fix of NVMe included.

Version-Release number of selected component (if applicable):
Tested Fedora 28 Gnome, Xfce, KDE 

How reproducible:
Attempt to boot from live USB drive. Will not get past error above. 

Steps to Reproduce:
1. Boot from USB
2. Wait 2-3 minutes
3. This error pops up and never proceeds past.

Actual results:
Screen remains on error and never proceeds

Expected results:
Install Fedora

Additional info:
Ryzen 7 2700x
MSI X470 Pro Carbon
Bios version 7B78v23
Update AGESA Code 1.0.0.4C

Comment 1 robert.plestenjak 2018-08-21 12:04:09 UTC
Bug confirmed on MSI B350M GAMING PRO motherboard, after AGESA Code 1.0.0.4C BIOS update, booting Fedora 28 install from USB stick fails with same error. Ubuntu 18.06 live USB loaded without problem.

MSI BIOS update that brakes Fedora 28 live USB:

Version
7A39v2H
Release Date
2018-07-23
File Size
10.4 MB
Description
- Update AGESA Code 1.0.0.4C
- Improve memory compatibility.


Reverting BIOS to previous version (7A39v2G, 2018-05-04) enables Fedora 28 live USB stick to load properly and completes installation.

Comment 2 Jason P. 2018-09-10 01:31:08 UTC
Bug confirmed on MSI x470 Gaming Pro Carbon. I just picked up this board yesterday and as part of my standard ritual when installing new hardware, I updated to the latest bios/firmware and couldn't figure out why I was unable to install Fedora and why other distros would take a long time to shutdown. The board I just replaced this one with was still on the older 1.0.0.2c and had no issues. 

System config:
MSI x470 Gaming Pro Carbon
AMD 2700x
Corsair RAM (CMK32GX4M2A2666C16)
MSI Vega 64 card
Samsung evo 960 and 840 ssd

After seeing this Bug report I downgraded to the previous BIOS E7B78AMS.220 (7B78v22 on MSI’s site). I am now able to boot to the liveusb and install Fedora 28

Things I attempted, before finding this report:

Installed Fedora 27 – it worked then upgraded to Fedora 28 resulting in a hang did not gather that info.

Tried booting to Fedora 29 as well. It would not boot either but got a diffrent result just ignored is since it's still beta at this point I was convinced it was my hardware.

Installed Debian 9.5 (kernel 4.9) and Ubuntu 18.04.1 (kernel 4.15.0_33), openSUSE 15 wouldn’t even provide any details just the splash screen. I also tried Manjaro it wouldn’t get past a tlp hang (I think this is related to the Vega video card I have)

Searching for this "AGESA 1.0.0.4c linux" produces several post with othes having the same issus on other board and distros as well.

Comment 3 Ben Cotton 2019-05-02 20:56:15 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 22:25:22 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.