Thanks for the hints. Indeed, I didn't read the news regarding grub.
Booting from a rescue system and running grub-install followed by a grub-
mkconfig solved the problem.
Although I do not fully understand why this happend. AFIAK, installing/
updating grub does not update files in /boot nor /boot/efi. And grub-mkconfig
only updates /boot/grub/grub.cfg. And the other files from the grub package are
inside an encrypted system disk, which grub cannot access without getting the
pass phrase. So, why do the EFI files suddenly stop working without having been
changed?
Thanks
Alex
On Freitag, 29. März 2024, 12:00:24 CET hitachi303 wrote:
> Am 29.03.24 um 11:55 schrieb Alexander Puchmayr:
> > Hi,
> >
> > After upgrading two Lenovo Laptops (UEFI, secure boot disabled), grub does
> > not work anymore; instead it says "Welcome to Grub" ... And then
> > immediately boots into bios setup.
> >
> > What did go wrong?
> > I did the usual things:
> > * emerge update world
> > * emerge --config gentoo-kernel
> > * grub-mkconfig -o /boot/grub/grub.cfg
> >
> > Everything went fine without errors, but then the final reboot, only bios
> > setup. And these steps do not alter the efi boot loaders
> >
> > Any ideas? How to get out of this?
> >
> > Alex
>
> Hi,
>
> die you follow the announcement about grub? eselect news read
>
> 2024-02-01-grub-upgrades
> Title GRUB upgrades
> Author Mike Gilbert <flop...@gentoo.org>
> Posted 2024-02-01
> Revision 2
>
> When booting with GRUB, it is important that the core image and modules
> have matching versions. Usually, running grub-install is sufficient to
> ensure this.
>
> On the UEFI platform, grub-install allows the core image to be placed in
> two different locations:
>
> EFI/gentoo/grubx64.efi
> This is the location used by grub-install without options.
>
> EFI/BOOT/BOOTX64.EFI
> This is the location used by grub-install --removable.
>
> On upgrades, it is common for users to mismatch the grub-install options
> they used for the current and previous versions of grub. This will cause
> a stale core image to exist. For example:
>
> /boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image)
> /boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image)
> /boot/grub/x86_64-efi/*.mod (grub 2.12 modules)
>
> Booting this system using BOOTX64.EFI image would likely fail due to a
> symbol mismatch between the core image and modules. [1]
>
> Re-runing grub-install both with and without the --removable option
> should ensure a working GRUB installation.
>
> However, this will clobber any BOOTX64.EFI image provided by other
> loaders. If dual-booting using another boot loader, users must take care
> not to replace BOOTX64.EFI if it is not provided by GRUB.
>
> References:
> [1] https://bugs.gentoo.org/920708
