On Wed, Feb 27, 2019 at 3:44 AM Patrick Dupre <pdupre(a)gmx.com&gt; wrote: This shouldn't happen if you did an EFI install but I did a conversion and my grub.cfg was not being updated. It turned out to be a symlink that had to be updated in /etc... # ll /etc/grub2.cfg lrwxrwxrwx. 1 root root 31 Dec 17 12:48 /etc/grub2.cfg -> ../boot/efi/EFI/fedora/grub.cfg Thanks, Richard

On Wed, Feb 27, 2019 at 10:44 AM Patrick Dupre <pdupre(a)gmx.com&gt; wrote: You need to have a "/etc/grub2-efi.cfg to ../boot/efi/EFI/fedora/grub.cfg" symlink for "/boot/efi/EFI/fedora/grub.cfg" to be updated because "/usr/sbin/new-kernel-pkg" has grub2EfiConfig=$(readlink -f /etc/grub2-efi.cfg 2>/dev/null) ... if [ -n "$cfgGrub2Efi" ]; then ... ARGS="--grub2 -c $grub2EfiConfig --efi \ --add-kernel=$kernelImage $DEVTREE $INITRD \ --copy-default --title \"$title\$debugtitle\" \ ${mbkernel:+--add-multiboot=\"$mbkernel\"} \ ${mbargs:+--mbargs=\"$mbargs\"} \ --args=\"root=$rootdevice $kernargs \$debugargs\" \ --remove-kernel=\"TITLE=$title\$debugtitle\"" rungrubby --debug ${ARGS} rungrubby ${ARGS} $makedefault ... fi