Bug 1210969 - "grub2-reboot uefi-firmware" leaves box unbootable
Summary: "grub2-reboot uefi-firmware" leaves box unbootable
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Bootloader Maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-28 20:01 UTC by greg mott
Modified: 2023-05-14 14:32 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description greg mott 2023-04-28 20:01:24 UTC 
After

grub2-reboot uefi-firmware

grub directly boots the bios without even briefly showing the menu. grub2-reboot did give a warning, but i bravely presumed that after i'd adjusted bios settings i could boot by grabbing the boot menu. But boot_once doesn't show the menu and sets timeout=0, leaving no way to grab the boot menu.

Looks like a design bug to me, why should next_entry/boot_once prevent access to the grub menu? That sets up a classic case of catch 22, can't boot until next_boot is cleared, which can't happen because it can't boot.
Comment 1 greg mott 2023-05-14 14:32:47 UTC 
as mentioned grub2-reboot did give a warning, but (1) the warning is weak, and (2) there's no need to setup an unbootable situation to boot_once into the bios.  grub is clearly capable of modifying grubenv, and, there's no reason boot_once should even temporarily deny access to the grub menu.