On Jul 23, 2022, at 23:54, Tim via users <users(a)lists.fedoraproject.org> wrote:
My preference has been a third option:
First hand edit the grub.cfg file that we're not supposed to (because
our changes won't be permanent, the next kernel install will recreate
the whole thing from a different mould), put in my kernel line changes
onto one of the boot choices, and reboot from it to see if they do what
I want (I remove "rhgb" from the kernel parameters).
These days, that tends to be: /boot/efi/EFI/fedora/grub.cfg
And has this symlink to it: /etc/grub2-efi.cfg
Except in the last handful of releases, /boot/efi/EFI/fedora/grub.cfg won’t have any boot
options. Today it just is a simple file to load /boot/grub2/grub.cfg. And THAT file
doesn’t have any specific kernel entries, it just loads blscfg, and the kernel entries are
each defined in a file in /boot/loader/entries/.
There is the default kernel command line defined in the grub.cfg that on a vanilla
install, is referenced in each bootloader spec file in /boot/loader/entries/ but as soon
as you use grubby to change it, the kernel parameters get hard-coded into each file, so
it’s possible to have a different set of kernel options in each file, as well as in the
grub.cfg. Also, if someone has replaced the grub.cfg in EFI with one created by
grub2-mkconfig, there’s now yet another place to get lost adding options.
Then there is the confusion of the /etc/grub2.cfg and /etc/grub2-efi.cfg symlinks. I’ve
seen advice that say to use `sed -i.old ‘s/rhgb quiet//‘ /etc/grub2.cfg` which replaces
the symlink with a real file, making all sorts of things break.
This is why Fedora always suggests using grubby.
--
Jonathan Billings