I nailed down that the echo (even of an empty string) has to be before "terminal_output gfxterm". Once it is after the "terminal_output gfxterm" instruction, the menu and background do not shows up.
Note: I also tried "GRUB_TIMEOUT_STYLE=menu" in /etc/default/grub followed by update-grub and it did not help with this issue. Cheers Alban On Sat, 15 Mar 2025 03:51:03 +0100 Alban Browaeys <pra...@yahoo.com> wrote: > Package: grub-efi-amd64 > Version: 2.12-5 > Followup-For: Bug #1051832 > > Dear Maintainer, > I was not having the anything displayed, only grub loading the default > entry in hte background once the timeout of 5 seconds expired. > > After tests, I sorted out that I did not need to add a full videoinfo at > the top of /boot/grub/grub.cfg to get the menu including the grub > background png back. > Add 'echo ""' at the top of the grub.cfg file is enough on my box which > strangely is pretty close to the other reporter of this bug. Ie a Lenovo > Thinkpad Yoga S1 from 2014. Core i7-4500U. I don't believe this bug > triggers on these Lenovo box because they have a slow CPU and about the > storage speed I have a fast Crucial SATA SSD instead of the original > HDD. > So probably a Lenovo EFI graphic bug or Grub being out of spec. > Graphic is > 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) > > > For now I add my empty string echo to /etc/grub.d/00_header. > " > export TEXTDOMAIN=grub > export TEXTDOMAINDIR="${datarootdir}/locale" > > . "$pkgdatadir/grub-mkconfig_lib" > > echo "echo \"\"" > > # Do this as early as possible, since other commands might depend on it. > # (e.g. the `loadfont' command might need lvm or raid modules) > for i in ${GRUB_PRELOAD_MODULES} ; do > echo "insmod $i" > done > " > and all is fine. > With this hack I can use GRUB_GFXMODE=1920x1080x32 > or 1280x1024x32 and get the grub boot menu with background graphics to > show up. > Otherwise the menu only shows up if I uncomment "GRUB_TERMINAL=console" > from /etc/default/grub. > > My root FS is on a btrfs @rootfs subvolume per Debian specs. /boot is > not a separate partition. > > > I had not noticed this grub menu regression for a while since I switched > to systemd-boot on this box as my main boot menu. While migrating SSD I > tested every entries including the grub one and found this issue existed > on my box. > > Could adding this empty string echo to 00_header be acceptable for now? > Could you report this issue upstream? > > Cheers, > Alban > >