4 ms·

What did eventually work for me was using the following path: grub2-mkconfig -o /boot/grub2/grub.cfg I'd actually resigned myself to using the rEFInd boot man

What did eventually work for me was using the following path: grub2-mkconfig -o /boot/grub2/grub.cfg I'd actually resigned myself to using the rEFInd boot manager, as I'd used it in the past, and I'd read that others had better luck when implementing dual boot systems with two OS's both using EFI. I had that all working when I decided to to have a closer look at how grub works, and used the path applicable to my system. I didn't even have a grub2.cfg, and I have read today that others have also had this same issue after resizing Mac partitions. I'm just glad it's working as I want now.

cmurf 9y ago
The fact that path works tells me this is a CSM-BIOS installation of Fedora. That is, there is an EFI compatibility support module that presents a faux BIOS firmware to the operating system to make it think it's a computer with BIOS rather than UEFI. On Fedora, the BIOS variant of GRUB puts its files in /boot/grub2; where the UEFI variant of GRUB puts its files in /boot/efi/EFI/fedora/. Did you burn the Fedora installer to optical media? I'm not aware of a way to trigger CSM-BIOS booting with flash media.
- rayascott 9y ago
  I was hoping you hadn't seen this reply of mine. Because it turns out I was wrong. I do have a /boot/grub2 directory. And it has a symlink named 'grubenv' to ../efi/EFI/fedora/grebenv. Grub is actually using /boot/efi/EFI/fedora/grub.cfg. I realised this a few minutes ago when the /boot/grub2/grub.cfg I generated was having no effect on grub, after making a few timeout changes. Is it possible that the grub2-mkconfig only updates the config file if there is a change in the system? I ask because, earlier in the day when I ran your grub2-mkconfig example, it had no effect. But since then I've removed 3 prior kernel versions so I'm guessing that would have caused an update of the config file. Although I'm still unsure as to why grub wouldn't load the config file earlier.

cmurf 9y ago

The fact that path works tells me this is a CSM-BIOS installation of Fedora. That is, there is an EFI compatibility support module that presents a faux BIOS firmware to the operating system to make it think it's a computer with BIOS rather than UEFI. On Fedora, the BIOS variant of GRUB puts its files in /boot/grub2; where the UEFI variant of GRUB puts its files in /boot/efi/EFI/fedora/. Did you burn the Fedora installer to optical media? I'm not aware of a way to trigger CSM-BIOS booting with flash media.

rayascott 9y ago
I was hoping you hadn't seen this reply of mine. Because it turns out I was wrong. I do have a /boot/grub2 directory. And it has a symlink named 'grubenv' to ../efi/EFI/fedora/grebenv. Grub is actually using /boot/efi/EFI/fedora/grub.cfg. I realised this a few minutes ago when the /boot/grub2/grub.cfg I generated was having no effect on grub, after making a few timeout changes. Is it possible that the grub2-mkconfig only updates the config file if there is a change in the system? I ask because, earlier in the day when I ran your grub2-mkconfig example, it had no effect. But since then I've removed 3 prior kernel versions so I'm guessing that would have caused an update of the config file. Although I'm still unsure as to why grub wouldn't load the config file earlier.