Bugzilla – Bug 1178340
[yast] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support)
Last modified: 2020-11-18 10:49:43 UTC
+++ This bug was initially created as a clone of Bug #1172292 +++
On some devices (In my case a Lenovo Ideapad 100s-11iby) have 64 bit processors, but a 32-bit UEFI, so the 64-bit installation mediums are not recognized by it.
Steps to Reproduce:
1. Grab a device with a 64-bit processor and a 32-bit UEFI
2. Try to boot from a 64-bit installation medium
The installation medium is not listed in the boot menu.
The installation medium is listed correctly, just like on a machine with a 64-bit UEFI.
I did a bit of research, and found out the following:
Fedora has natively supported 32-bit UEFI for 64 bit installs since Fedora 27. There seems to be a a workaround, but this is not very practical for new users, which adds a file from Github (https://github.com/hirotakaster/baytail-bootia32.efi) to the installation medium.
Could the installer detect whether firmware is 32 or 64 bit on x86_64 and install either grub2-i386-efi, or grub2-x86_64-efi respectively. This detection can be done by checking /sys/firmware/efi/fw_platform_size (it contains either 32 or 64).
Steffen - please evaluate how hard it will be as it is about installation medium. If not trivial, then maybe jira entry is needed?
I can comment on the support issue, but ignoring install media issues for now.
The main problem that I see, is that Yast bootloader does not support this configuration. If I tell it to use "grub2-efi" then it wants to install the 64-bit EFI version. Similarly, bootctl (systemd-boot) wants to install 64-bit booting if I try that.
What I have been doing is using Yast bootloader to install MBR booting, even though that cannot work. But at least, if the system is configured for MBR booting, then "grub.cfg" is properly updated after kernel updates and similar. I then install "grub2-i386-efi". After that, I can use "grub2-install" from the root command line, and that does install the proper booting for this system.
Steffen ping :-)
For the install media there is bug 1178338.
I think this bug here is specifically for the yast / installed system part.
The tools would have to check not only the architecture but also take
/sys/firmware/efi/fw_platform_size into account to determine the
package name and the grub target.
yast-bootloader and perl-Bootloader (at least) would need adjustments - not
sure about other places.
There's also the question whether there is/will be a 32 bit shim.
BTW, is there a feature for this? If so, please link it here, if not, I'd suggest
to create one, as this may need coordinated work in a number of places.
So, Jiri please open a Jira entry in order to discuss and coordinate this
feature. Thanks !
Responding to comment #5
>yast-bootloader and perl-Bootloader (at least) would need adjustments - not
sure about other places.
Yes, I think those are the main changes (in addition to the installer). I've been using this setup in a VM for a while, and I have not run into anything else.
>There's also the question whether there is/will be a 32 bit shim.
At present, there isn't one (for openSUSE). It's not up to me to say whether there should be one. Fedora does have a shim for this type of system. And I think "deepin" also has shim support.
At present, OVMF does not have support for secure-boot for mixed-mode systems, so there's no way that I could adequately test shim.
(In reply to Stefan Schubert from comment #6)
> So, Jiri please open a Jira entry in order to discuss and coordinate this
> feature. Thanks !
Done in: PM-2325
(In reply to Jiri Slaby from comment #8)
> (In reply to Stefan Schubert from comment #6)
> > So, Jiri please open a Jira entry in order to discuss and coordinate this
> > feature. Thanks !
> Done in: PM-2325
Thank you Jiri !