As I understand the processes, those two blscfg statements are what controls the kernels displayed and kernel commands issues in the boot menu. As I specified in another thread, when this standard was introduced, I think if F31, I was always using grub2-mkconfig to generate the grub menus and the introduction of the blscfg standard caused the usage of grub2-mkconfig to not make any difference to the menus shown at boot time, and people on this mailing list told me to disable blscfg in /etc/default/grub, which having done that causes grub2-mkconfig to actually work.c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf as it sits now:
title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel
Edited /etc/default/grub to this:
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 rd.l>
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"
# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done
# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done
c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf after running these.
Title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)
version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel
from nano /boot/efi/EFI/fedora/grub.cfg:
===================================================# This section was generated by a script. Do not modify the generated file - all changes
# will be lost the next time file is regenerated. Instead edit the BootLoaderSpec files.
#
# The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and
# populates the boot menu. Please refer to the Boot Loader Specification documentation
# for the files format: https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/.
# The kernelopts variable should be defined in the grubenv file. But to ensure that menu
# entries populated from BootLoaderSpec files that use this variable work correctly even
# without a grubenv file, define a fallback kernelopts variable if this has not been set.
#
# The kernelopts variable in the grubenv file can be modified using the grubby tool or by
# executing the grub2-mkconfig tool. For the latter, the values of the GRUB_CMDLINE_LINUX
# and GRUB_CMDLINE_LINUX_DEFAULT options from /etc/default/grub file are used to set both
# the kernelopts variable in the grubenv file and the fallback kernelopts variable.
if [ -z "${kernelopts}" ]; then
set kernelopts="root=/dev/mapper/fedora_localhost--live-root ro rd.driver.blacklist=nouveau modpro>
fi
insmod blscfg
blscfg
### END /etc/grub.d/10_linux ###
================================================
This is as far as I got with the instructions in your post. I'll finish this later.
Also as I understand it /boot/grub2/grub.cfg is the grub config file used to generate the grub menus for legacy booting, where to get that structure into the mbr you need to issue grub2-install, and, the /boot/efi/EFI/fedora/grub.cfg is what is used for efi booting and in that scenario you do not need to issue grub2-install.
regards,
Steve
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx