Summary: | sys-boot/grub-2.12 fails to bring up menu on some uefi systems and enter setup instead | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ben <blc+gentoo> |
Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | base-system, blc+gentoo, egorr.berd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00371.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ben
2024-02-24 08:30:48 UTC
The linked Arch bug implies this is the same as the issue which we have a news items for? Does it happen after following that? (In reply to Sam James from comment #1) > The linked Arch bug implies this is the same as the issue which we have a > news items for? > > Does it happen after following that? i.e. everybody in there seems to say running grub-install works, which would bring us back to the news item. Ah yeah you got it. It was due to not updating the core image. Oops! Changing too many things at once. It's still a bit wonky, I typed in the command wrong at first, and it ended up causing it to go to firmware setup anyway, i.e. fwsetup --is-supported-by-firmware (instead of just --is-supported) won't give an error, but will reboot and go to setup... Reopening this; I'm going to send a patch upstream to address this. Thanks, I'd suggest them add some command that's not an option to an existing command (with unintended side effects) so a new config would simply give a bad command error instead of getting into a state where it cannot be recovered. Technically if I could get into efishell and used its editor on grub.cfg (which I have on fat32/ESP) I could work around this problem if it happens again. However I don't know if all my EFI machines support efishell. So I had suggested a fix for this on the grub-devel mailing list back in 2022, and it got shot down as "too complex". https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00371.html I'm afraid we are just going to have to live with this. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=597323aae87e1857d2c048dde3450e3c3c0c92c7 commit 597323aae87e1857d2c048dde3450e3c3c0c92c7 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2024-04-11 19:39:11 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2024-04-11 19:40:40 +0000 sys-boot/grub: add workaround for fwsetup issue Bug: https://bugs.gentoo.org/925370 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-boot/grub/files/grub-2.12-fwsetup.patch | 38 ++++++++++++++++++++++ .../{grub-2.12-r3.ebuild => grub-2.12-r4.ebuild} | 1 + 2 files changed, 39 insertions(+) |