grubby-8.40-72.fc40.aarch64 In a mainline kernel git tree: root@fedora-x13s:~/linux# make install INSTALL /boot grub2-mkrelpath: error: failed to get canonical path of `/boot/vmlinuz-6.6.0-rc4JL_CONFIG_CHANGES+'. dirname: missing operand Try 'dirname --help' for more information. The machine then fails to boot because the kernel wasn't copied to /boot Replacing the symlink change in -72 with the original grubby `installkernel` fixes the problem and now the machine can boot. Reproducible: Always Steps to Reproduce: 1. Git clone mainline kernel 2. copy /boot/config-XXX to kernel 3. make; make modules_install; make install Actual Results: INSTALL /boot grub2-mkrelpath: error: failed to get canonical path of `/boot/vmlinuz-6.6.0-rc4JL_CONFIG_CHANGES+'. dirname: missing operand Try 'dirname --help' for more information. Expected Results: INSTALL /boot grep: warning: stray \ before / kdump: For kernel=/boot/vmlinuz-6.6.0-rc4JL_CONFIG_CHANGES+, crashkernel=1G-4G:256M,4G-64G:320M,64G-:576M now. Please reboot the system for the change to take effet. Note if you don't want kexec-tools to manage the crashkernel kernel parameter, please set auto_reset_crashkernel=no in /etc/kdump.conf. Fixed by reverting to the previous grubby installkernel script.
Maybe I should change the component to systemd.. flip a coin I guess.
Oh, noticed bz#2239008 which sounds like the same thing.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
*** This bug has been marked as a duplicate of bug 2239008 ***