legacy boot bug with GRUB 2.06, boot loop/stuck at GRUB loading, -current

Howdy,
It seems that GRUB 2.06 has some issues, at least my machines (real PC, and VPS) that boot in legacy mode. My laptop, which uses EFI seems to be unaffected.

I upgraded the Slackware package, did grub-install with the new package installed, and grub-mkconfig to create a new config (probably unnecessary).

I did a quick look at their bug tracker and this seems to be similar to the issue I am facing:
https://savannah.gnu.org/bugs/?60458

The link also seems to indicate building with -Os fixes it, I might try that later if I find the time.

It seems like a lot of folks here use lilo so it probably won't matter that much, but be warned if you use legacy boot and GRUB. I rolled back to 2.04-2 (2.04-3 has the decompressor too big bug) and reinstalled GRUB, and all is working now. I upgraded the package to 2.06 and did a grub-mkconfig and it still seems to be working. So you can upgrade the package, but you probably don't want to install 2.06 if you are using legacy boot.

Did you try without -O2?

I tried here in Legacy mode with a GPT, no issue. Do you have this issue with a GPT or a DOS partition table?

Originally Posted by Didier Spaier Did you try without -O2?

Not yet, I might try it tomorrow.

Originally Posted by Didier Spaier I tried here in Legacy mode with a GPT, no issue. Do you have this issue with a GPT or a DOS partition table?

Both are GPT. It very well might be specific to my hardware. The real machine is ivy bridge era with an oddball motherboard, and the VPS could be an issue with the provider (maybe hypervisor or something similar)

Both machines reported that grub-install was successful, and the following grub-mkconfig seemed to work without a hitch (other than warning the os-prober is disabled, or something to that effect).

The real machine was boot looping once it hit "GRUB Loading" and the VPS just hung at that message.

Originally Posted by kaott Howdy, It seems that GRUB 2.06 has some issues, at least my machines (real PC, and VPS) that boot in legacy mode. My laptop, which uses EFI seems to be unaffected. I upgraded the Slackware package, did grub-install with the new package installed, and grub-mkconfig to create a new config (probably unnecessary). I did a quick look at their bug tracker and this seems to be similar to the issue I am facing: https://savannah.gnu.org/bugs/?60458 The link also seems to indicate building with -Os fixes it, I might try that later if I find the time. It seems like a lot of folks here use lilo so it probably won't matter that much, but be warned if you use legacy boot and GRUB. I rolled back to 2.04-2 (2.04-3 has the decompressor too big bug) and reinstalled GRUB, and all is working now. I upgraded the package to 2.06 and did a grub-mkconfig and it still seems to be working. So you can upgrade the package, but you probably don't want to install 2.06 if you are using legacy boot.

I confirm the problem here, compiled with -Os, fixes it, here.

Originally Posted by gmgf I confirm the problem here, compiled with -Os, fixes it, here.

I will upload the one having removed -O2 (-Os is the default) to the Slint repos. I observed that this makes the package a little smaller (107M installed vs 112 M, built for platforms i386-pc, i386-efi, x86_64-efi and x86_64-emu.

Also, I have used --enable-stack-protector when configuring for the efi platforms. The security patch which provided this option is among those under the cover letter Multiple GRUB2 vulnerabilities - 2021/03/02 round. Caveat: this is with gcc-5.5 shipped in Slackware64-14.2.

Originally Posted by Didier Spaier I will upload the one having removed -O2 (-Os is the default) to the Slint repos. I observed that this makes the package a little smaller (107M installed vs 112 M, built for platforms i386-pc, i386-efi, x86_64-efi and x86_64-emu. Also, I have used --enable-stack-protector when configuring for the efi platforms. The security patch which provided this option is among those under the cover letter Multiple GRUB2 vulnerabilities - 2021/03/02 round. Caveat: this is with gcc-5.5 shipped in Slacwkare64-14.2.

Right, @Didier, i confirm this, the package is little smaller.

-Os fixed it on the VPS, haven't tried it on the real machine yet (I suspect it will probably fix it)

I had the same problem with the GRUB on legacy BIOS.

Compiling grub with -Os also works for me.

@Didier I'm a bit confused with GRUB 2.06, what do you think is worth installing on a production server with UEFI?
I've stayed at ELILO's for now.
Could I have problems?
Debian and Fedora, for example, are still at 2.04

Originally Posted by teoberi @Didier I'm a bit confused with GRUB 2.06, what do you think is worth installing on a production server with UEFI? I've stayed at ELILO's for now. Could I have problems? Debian and Fedora, for example, are still at 2.04

I don't expect any big issue using GRUB 2.06. Its maintenance is handled in a very professional way.

I confirm the problem with GRUB 2.06, only on slackware current x86 system. Not having problems with EFI and x86_64 slackware64 current.
I fix it recompiling grub packages for both x86 and x86_64 with CFLAGS -Os

Originally Posted by Didier Spaier I don't expect any big issue using GRUB 2.06. Its maintenance is handled in a very professional way.

By professional way do you mean its lead's employer makes sure he's kept super busy with non-GRUB tasks to keep him on his toes? At least in the country I'm in this is what professional employment is, no time to relax or contemplate. I'm glad some of these GNU maintainers can get a good paycheck with the big companies, but it's not any kind of sinecure or patronage from what I can see. Must be anxiety inducing to have demands both from the likes of us and the paying people.