On 11/24/19 2:39 AM, Francis.Montagnac(a)inria.fr wrote:
I haven't read all this thread. Just a remark about grub. See below.
On Sat, 23 Nov 2019 21:37:42 -0700 stan via users wrote:
>>>> ran grub2-mkconfig. No entries again in output. It can't find the
>>>> f29 and f30 in /boot.
>> The problem is that installing or reinstalling an f30 kernel does not
>> add the kernel to grub.cfg.
This is normal since you have:
>> cat /etc/default/grub
This generates the following in grub.cfg:
### BEGIN /etc/grub.d/10_linux ###
# The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries
# populates the boot menu. Please refer to the Boot Loader Specification
# for the files format:
### END /etc/grub.d/10_linux ###
The kernels are now defined in /boot/loader/entries/
>> How do I get grub.cfg updated ?
No need to do that thus.
BINGO ! I removed GRUB_ENABLE_BLSCFG=true from /etc/default/grub , ran
grub2-mkconfig, and all the F30 kernels are now in grub.cfg.
No idea how ENABLE_BLSCFG ended up in default/grub. If I have time I'll
file a bug. anaconda should know enough to delete it, especially since
it probably put it there n versions ago.