On 7/12/19 17:11, Robert McBroom via users wrote:
On 12/6/19 10:03 PM, Stephen Morris wrote:
On 7/12/19 10:22, Robert McBroom via users wrote:
On 12/6/19 5:41 PM, Samuel Sieb wrote:
On 12/6/19 1:52 PM, Robert McBroom via users wrote:
On 12/6/19 2:06 AM, Anthony F McInerney wrote:
On Thu, 5 Dec 2019 at 19:04, Samuel Sieb <samuel@xxxxxxxx
<mailto:samuel@xxxxxxxx>> wrote:
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> Updated from Fedora 29 to 31 on a legacy system. Kernel
updates no
> longer update grub.cfg to the new kernel. Ran
grub2-mkconfig -o
> /boot/grub2/grub.cfg which finds Windows and Centos 6 but none
of the
> Fedora kernels. /boot is in its own partition and the Centos
kernels
> are in the Centos partition on a second drive. A backup of
windows 7 on
> a usb drive is even found by os-prober. Everything these days
seems to
> point to uefi systems.
grub has been switched to use BLS. Check if you have files in
/boot/loader/entries/.
That's interesting. First i've heard of BLS.
It would seem that runs into a known issue
https://bugzilla.redhat.com/show_bug.cgi?id=1652806
And the way tl;dr is "on BIOS systems you have to run
'grub2-install /dev/sdX'
Not installing grub, getting grub to recognize system entries.
If this is an old install, you might need to update the bootloader
bits that are stored in the mbr. It might too old to support BLS.
That's why if it's not an EFI system, you should run grub2-install
to make sure it's up to date.
Updated with the update to f31.
I'm running F30 in a VM, so in my case even though the motherboard I
have is uefi, fedora is ignoring it and running in legacy mode.
Consequently, because I don't like the BLS results, I run
grub2-mkconfig -o /boot/grub2/grub.cfg to build the cfg file (this
command finds all the fedora kernels quite happily), following by
grub2-install /dev/sda to get the grub boot sequence into the mbr
Because I don't like the BLS results, they look like the results from
grubby which I also hated, I have the following statement in
/etc/default/grub to disable BLS:
GRUB_ENABLE_BLSCFG=false
regards,
Steve
Thanks Steve.
Not knowing about BLS, The variable in /etc/default/grub was left
alone. Changing it the expected behavior returns. Do you find that
the grub install should be run after configuration?
Yes, grub2-mkconfig -o /boot/grub2/grub.cfg writes all the detected
information about the installed kernels and any other detected operating
systems to the specified config file but does not write any information
to the mbr for the legacy boot process to display the grub menu at
startup. As I understand it the install process in not required if
booting in uefi mode.
I'm going to have to do some more changes to /etc/default/grub as the
grub menu appears to be hidden at startup and I'll need to check whether
the timeout is still set to 999.
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
