[Bug 1226727] New: can't install micro os on SoC missing grub2-i386-efi
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 Bug ID: 1226727 Summary: can't install micro os on SoC missing grub2-i386-efi Classification: openSUSE Product: openSUSE Leap Micro Version: 5.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: opensuseidp@ikol.8shield.net QA Contact: jalausuch@suse.com Target Milestone: --- Found By: --- Blocker: --- I can't install micro os on SoC. The installer says it's missing grub2-i386-efi and only find grub2-i386-pc seems to be available. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c1 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Base Assignee|yast2-maintainers@suse.de |screening-team-bugs@suse.de QA Contact|jalausuch@suse.com |qa-bugs@suse.de --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- Which installation method did you use? For an SoC, it was probably the image-based method, right? Bug component "installation" in this product is misleading here in Bugzilla; that would be a YaST-based installation which is very rarely the case. See also bug #1223976. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c2 --- Comment #2 from v bm <opensuseidp@ikol.8shield.net> --- yes, this image; https://download.opensuse.org/tumbleweed/iso/openSUSE-MicroOS-DVD-x86_64-Cur... Where should I report this then? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c3 --- Comment #3 from v bm <opensuseidp@ikol.8shield.net> --- (In reply to Stefan Hundhammer from comment #1)
Which installation method did you use? For an SoC, it was probably the image-based method, right?
Bug component "installation" in this product is misleading here in Bugzilla; that would be a YaST-based installation which is very rarely the case. See also bug #1223976.
sorry just to clarify, I think it is a YaST-based install. I'm new to SUSE but here the steps I follow: 1. burn https://download.opensuse.org/tumbleweed/iso/openSUSE-MicroOS-DVD-x86_64-Cur... into USB 2. boot device using USB 3. have to select manual partition of device's eMMC and create an EFI and a system partition 4. enter installation GUI, follow all the steps until screen the shows at 2:29 in this video https://youtu.be/TICAnBeK028 4. can't advance as I get an error asking for grub2-i386-efi and can only find and select grub2-i386-pc package when clicking "software" and searching for package. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |bootloader-maintainers@suse | |.de -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c4 Benjamin Brunner <bbrunner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags| |needinfo?(fvogt@suse.com) --- Comment #4 from Benjamin Brunner <bbrunner@suse.com> --- This is not really a grub-bug either, after grub2-i386-efi is built but not included in the MicroOS repository. AFAIK, 32bit-EFI is also not supported for MicroOS. Fabian, could you confirm, please? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c5 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuseidp@ikol.8shield.ne | |t Flags|needinfo?(fvogt@suse.com) |needinfo?(opensuseidp@ikol. | |8shield.net) --- Comment #5 from Fabian Vogt <fvogt@suse.com> --- Which system are you installing on? 32bit EFI on 64bit hardware is quite rare. (In reply to Benjamin Brunner from comment #4)
This is not really a grub-bug either, after grub2-i386-efi is built but not included in the MicroOS repository. AFAIK, 32bit-EFI is also not supported for MicroOS.
Fabian, could you confirm, please?
FWICT it's supported by Tumbleweed so I don't see a reason to exclude it from MicroOS. It's likely just missing from the DVD, I made https://build.opensuse.org/request/show/1184289. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c6 --- Comment #6 from v bm <opensuseidp@ikol.8shield.net> --- (In reply to Fabian Vogt from comment #5)
Which system are you installing on? 32bit EFI on 64bit hardware is quite rare.
(In reply to Benjamin Brunner from comment #4)
This is not really a grub-bug either, after grub2-i386-efi is built but not included in the MicroOS repository. AFAIK, 32bit-EFI is also not supported for MicroOS.
Fabian, could you confirm, please?
FWICT it's supported by Tumbleweed so I don't see a reason to exclude it from MicroOS. It's likely just missing from the DVD, I made https://build.opensuse.org/request/show/1184289.
Thanks. I was going to point out the iso boots in the EFI32 and the install runs normally until it can't find grub2-i386-efi, so it seems it knows it's on EFI32 and how to set it up. :) -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c7 --- Comment #7 from Fabian Vogt <fvogt@suse.com> --- Could you please also answer: (In reply to v bm from comment #6)
(In reply to Fabian Vogt from comment #5)
Which system are you installing on? 32bit EFI on 64bit hardware is quite rare.
That would be useful to estimate the relevance of 32bit EFI support in MicroOS. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226727 https://bugzilla.suse.com/show_bug.cgi?id=1226727#c8 --- Comment #8 from v bm <opensuseidp@ikol.8shield.net> --- (In reply to Fabian Vogt from comment #7)
Could you please also answer:
(In reply to v bm from comment #6)
(In reply to Fabian Vogt from comment #5)
Which system are you installing on? 32bit EFI on 64bit hardware is quite rare.
That would be useful to estimate the relevance of 32bit EFI support in MicroOS.
it's an old bauhn mini pc I bought while back. it originally came with Win 8 :) , immediately upgraded to 10 and I later broke trying to install linux (accidentally wiped its "huge" 8GB emmc). I tried SUSE for the first time a couple of months ago, after installing tumbleweed on a laptop, stumbled upon microOS and thought it might allow me to bring my old shitbox to life. What can I say? I like to repurpose stuff, although my best half would say I'm a hoarder and a tightass that won't fork out for a raspberrypi ir something similar for his homelab projects. If I can bring it back to life, I probably put pihole on it as a backup to my main box, see if it works as a domain controller or just set it up as a honey pot. I completely understand if you can't be bothered. I'm not sure how many more crazies are out there, but EFI32 on microOS might save a few machines from going to landfill just yet. FWIW, I still use KDE on ubuntu 24.04 on this (https://forums.whirlpool.net.au/archive/2631080) almost every day :) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com