Bug 1039257

Summary:	RFE : install on 32 bit UEFI systems
Product:	[Fedora] Fedora	Reporter:	Ken <kjh>
Component:	lorax	Assignee:	Brian Lane <bcl>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, bcl, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-16 00:12:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ken 2013-12-07 10:22:27 UTC

Description of problem:

There is no EFI install on 32 bit installers.  I have a Gateway LT41P04u , which has 32 bit UEFI firmware (I tried a workaround by booting the installer on a BIOS machine with "gpt" on the cmdline, and installing grub2-efi later, but it still doesn't work).

It would also be nice if the default auto partition for GPT includes a "BIOS_Boot" partition.  I guess there needs to be 2 grub.cfg files : one at /boot/grub2/grub.cfg , and one at /boot/efi/EFI/fedora/grub.cfg ?

Maybe need mokutil , MokManager.efi , shim.efi as well.

The best would be a way to make a 32 bit UEFI firmware boot a 64 kernel, but I think that's difficult.


Version-Release number of selected component (if applicable):

I tried it on Fedora-20-Beta-i386


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ken 2013-12-13 18:30:02 UTC

I got this to work (Fedora-20-Beta-i386 runs on a 32 bit UEFI secure boot machine).  The only tricky thing is that anaconda sets the "bootable" flag on the "protective MBR", so that causes the UEFI firmware (Insydeh20 BIOS v2.03) to ignore the EFI partition.  When I unset the bootable flag (and copied a modified /boot/grub2/grub.cfg to /boot/efi/EFI/fedora/grub.cfg), then it booted.

I know have a disk that boots on UEFI machines and BIOS machines.

FYI, since there is no shim.efi, on the UEFI machine I had to go into firmware setup UI and "select an UEFI file as trusted for executing" (when this option is selected, users may select all available .efi in FAT32 partitions and add the .efi hash into secure DB).

Fedora rules!

Comment 2 David Shea 2015-04-14 19:12:08 UTC

This is more of a lorax thing, I think.

Comment 3 Fedora End Of Life 2015-05-29 09:56:23 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 Brian Lane 2015-05-29 16:58:44 UTC

Almost there, waiting on new shim - https://github.com/rhinstaller/lorax/pull/16