You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
installer: BIOS works via switch, fresh install is UEFI-only until base ships BIOS payload #102
🤖 Muse Spark 1.3 commenting on behalf of KiKaraage
I switched a legacy-BIOS X230 (GPT, MBR, BIOS GRUB via bootupd) from Bluefin to Utah and back: the switch path works, because the existing bootloader simply loads the new kernel. Rolled back cleanly afterward.
A fresh bootc install to-disk on BIOS is a different story.
Evidence:
The Hummingbird base Containerfile (images/bootc-os/hummingbird/default/Containerfile in gitlab.com/redhat/hummingbird/containers) installs grub2-efi-x64, shim-x64, efibootmgr, and generates bootupd metadata for EFI only (EFI.json).
There is no grub2-pc and no BIOS update payload anywhere in the chain, and Utah adds none. Verified against the Utah Containerfile and contract manifests.
Local bootupctl on the legacy machine reports Boot method: BIOS with only a BIOS component managed.
Acceptance: document that switching an existing install works on BIOS while fresh installs are UEFI-only, until a BIOS payload exists. Links #22; could alternatively go as a comment there.
The documentation and bootloader support model for this issue were superseded by merged commits a567795 (PR #143, defining supported UEFI boot paths and explicitly declaring legacy BIOS/CSM unsupported in README.md and docs/skills/local-testing.md) and 08662a6 (implementing signed shim+GRUB live media). Maintainer @hanthor closed PR #149 as superseded by those commits.
Acceptance was documentation, and it is already there: README.md documents that fresh installs are UEFI-only and legacy BIOS is explicitly unsupported (flash-the-ISO path), while the switch path on BIOS keeps working via the existing bootloader. Closing as satisfied.
Activity
docs(installer): correct BIOS gap cause — no grub2-pc, no BIOS payload
docs(installer): document BIOS switch support vs UEFI-only fresh inst…
docs(installer): correct BIOS gap cause — no grub2-pc, no BIOS payload
repires commentedon Sep 22, 2026
The documentation and bootloader support model for this issue were superseded by merged commits a567795 (PR #143, defining supported UEFI boot paths and explicitly declaring legacy BIOS/CSM unsupported in README.md and docs/skills/local-testing.md) and 08662a6 (implementing signed shim+GRUB live media). Maintainer @hanthor closed PR #149 as superseded by those commits.
— hive: backend=agy
🐝 Hive Agent:
contributor| SHA:unknownhanthor commentedon Oct 10, 2026
Acceptance was documentation, and it is already there: README.md documents that fresh installs are UEFI-only and legacy BIOS is explicitly unsupported (flash-the-ISO path), while the switch path on BIOS keeps working via the existing bootloader. Closing as satisfied.