On 08/27/2015 08:37 AM, Pete Travis wrote:
efibootmgr acts on the firmware boot menu. The firmware boots grub, which lives on the efi system partition (It's a file on a vfat filesystem, not code in an MBR). grub gives you a menu and boots the kernel.
ubuntu was the last OS installed, and it created a grub.cfg file, /boot/grub/grub.cfg . so I boot back into fedora, but I have to edit the grub menu to use the newest kernel, which isn't listed.
This means that both ubuntu and fedora can have a grub binary installed, each with a config file. Figure out which one you are booting first. If it's the ubuntu grub, this is all expected and you need to manually update the associated grub.cfg (not the binary, just the config file!) If it's Fedora, also manually update, but also look into where the kernel failed to update grub.cfg.
TL;DR: What is the actual full command you used when invoking grub2-mkconfig ?
well I see 2 grub.cfg files , ls -l /boot/grub2/grub.cfg -rw-r--r-- 1 root root 12189 Aug 27 06:39 /boot/grub2/grub.cfg [root@pauls-desktop backups]# ls -l /boot/efi/EFI/fedora/grub.cfg -rwx------ 1 root root 12189 Aug 27 06:40 /boot/efi/EFI/fedora/grub.cfg
I did the command grub2-mkconfig twice, to update both of those files.. so now how do I get the efibootmgr to recognize/use one of those files??
# df -h|grep efi /dev/sda8 95M 9.5M 86M 11% /boot/efi