and grubby,
https://src.fedoraproject.org/rpms/grubby/commits/f37
1 Like
I have had no issues.
My part of this discussion is about the fact that 2 of my desktop systems had that file already there and my laptop did not. All are running fedora 36. I have had no problems with any of them booting. I wondered why there was a difference and the only thing I can remember as a difference is that I know I had run grub2-mkconfig on both desktops at some time in the past, but had never previously done so on the laptop.
Then it seemed curious that my newly installed fedora 37 VM already had that file in place even though I had never run grub2-mkconfig on that system.
The OP seems to have found another error that caused problems for him when /etc/kernel/cmdline either did not exist or had the wrong data. He has not jumped back in but his original post triggered this discussion.
Recapitulation:
OP @fd-user jumped in to report a solution while on the grubby tool still got worked on a fix F36. Several attempts have been made (see coment @vekruse) to fix.
Last but not least after a start-over for F37 the fix got implemented.
The OP mentioned
and might reported while still fixing on F36.
on the start-over for F37 the message to report a bug got removed.
if [[ ! -f /etc/kernel/cmdline ]]; then
echo "No /etc/kernel/cmdline; please report a bug";
I set the Title new to:
Workaround for missing bugfix 0da23ad
the old one:
*This is a Solution* Changed Root Part UUID, /boot/grub2/grub.cfg $kernelopts is Correct, but Fedora Still Uses Old UUID to Generate BLS Boot Entries
was quite clumsy.
1 Like