Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1330522 - F24 does not boot over UEFI when USB is created using the old liveusb-creator
Summary: F24 does not boot over UEFI when USB is created using the old liveusb-creator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: liveusb-creator
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F24BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2016-04-26 12:07 UTC by Kamil Páral
Modified: 2016-09-20 02:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-29 11:40:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
boot error (132.37 KB, image/jpeg)
2016-04-26 12:07 UTC, Kamil Páral
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1318494 0 unspecified CLOSED fails to create UEFI bootable media by default 2022-05-16 11:32:56 UTC

Internal Links: 1318494

Description Kamil Páral 2016-04-26 12:07:07 UTC
Created attachment 1150902 [details]
boot error

Description of problem:
When I try to create a USB stick using the old liveusb-creator and use Fedora-Workstation-Live-x86_64-24-20160422.n.0.iso to be written, the stick does boot using BIOS, but does not boot using UEFI. The error message says:

> error: file '/images/pxeboot/vmlinuz' not found.

Version-Release number of selected component (if applicable):
liveusb-creator-3.14.2-2.fc23.noarch
liveusb-creator-3.14.2-1.fc22.noarch
(happens on both)
Workstation-Live-x86_64-24-20160422.n.0.iso

How reproducible:
always

Comment 1 Kamil Páral 2016-04-26 12:08:28 UTC
Proposing as a Beta blocker due to:
"Release-blocking live and dedicated installer images must boot when written to optical media of an appropriate size (if applicable) and when written to a USB stick with any of the officially supported methods."
https://fedoraproject.org/wiki/Fedora_24_Beta_Release_Criteria#Release-blocking_images_must_boot

Of course a solution here is to push the new LUC into F22 and F23 before Beta release:
https://bodhi.fedoraproject.org/updates/?packages=liveusb-creator

Comment 2 Kamil Páral 2016-04-26 13:56:55 UTC
This is probably a duplicate of bug 1318494, but I keep it open because I already proposed it as a blocker. We can sort that out once things are pushed stable, which should be any day now.

Comment 3 satellitgo 2016-04-26 23:12:53 UTC
Boots bios and EFI in NUC i5 intel:
Fedora-KDE-Live-x86_64-24-20160424.n.0.iso
8 GB Toshiba USB

3.93.2-1.fc23.noarch.rpm -boots not tested for install [1]

[1] https://fedoraproject.org/wiki/Test_Results:Fedora_24_Branched_20160424.n.0_Installation#USB_media

Comment 4 Kamil Páral 2016-04-27 08:22:48 UTC
liveusb-creator-3.93.3-1.fc22 and liveusb-creator-3.93.3-1.fc23 has been now pushed stable, which solves this bug. But this needs to stay open until the mirror manager stops offering older metadata, according to:
https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Tracking_AcceptedPreviousRelease_blocker_bugs
(of source only on basis that this gets accepted as a previous release blocker).

Comment 5 Kamil Páral 2016-04-29 11:40:31 UTC
INFO    ✔ PASSED All metadata referenced in metalink is sufficiently newer than the time when liveusb-creator-3.93.3-1.fc23 was tagged into f23-updates. All users should be able to receive the update now.
INFO    ✔ PASSED All metadata referenced in metalink is sufficiently newer than the time when liveusb-creator-3.93.3-1.fc22 was tagged into f22-updates. All users should be able to receive the update now.


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