[Bug 1178340] New: [yast] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support)
https://bugzilla.suse.com/show_bug.cgi?id=1178340 Bug ID: 1178340 Summary: [yast] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: jslaby@suse.com QA Contact: jsrain@suse.com CC: glin@suse.com, jens@krieger-juhnke.de, jlee@suse.com, jslaby@suse.com, mbenes@suse.com, mchang@suse.com, tiwai@suse.com Blocks: 1172292 Found By: --- Blocker: --- +++ 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 Actual Results: The installation medium is not listed in the boot menu. Expected Results: 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). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c1 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |snwint@suse.com Flags| |needinfo?(snwint@suse.com) --- Comment #1 from Josef Reidinger <jreidinger@suse.com> --- Steffen - please evaluate how hard it will be as it is about installation medium. If not trivial, then maybe jira entry is needed? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c3 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schubi@suse.com --- Comment #3 from Stefan Schubert <schubi@suse.com> --- Steffen ping :-) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c5 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(snwint@suse.com) | --- Comment #5 from Steffen Winterfeldt <snwint@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c6 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |jslaby@suse.com --- Comment #6 from Stefan Schubert <schubi@suse.com> --- Thanks, Steffen. So, Jiri please open a Jira entry in order to discuss and coordinate this feature. Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c8 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jslaby@suse.com |yast2-maintainers@suse.de --- Comment #8 from Jiri Slaby <jslaby@suse.com> --- (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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 https://bugzilla.suse.com/show_bug.cgi?id=1178340#c9 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE --- Comment #9 from Stefan Schubert <schubi@suse.com> --- (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 ! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1178340 roke beedell <rokejulianlockhart+1674683091@outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rokejulianlockhart+16746830 | |91@outlook.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com