1. Please describe the problem: Kernel does not get installed to /boot. 2. What is the Version-Release number of the kernel: 5.17.2-300.fc36.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : This started with whatever kernel was current when I upgraded to f36 beta. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install or reinstall kernel(-core). 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes. Running transaction Preparing : 1/1 Installing : kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1. 1/3 Running scriptlet: kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1. 1/3 Installing : kernel-modules-5.18.0-0.rc1.20220408git1831fed559732 2/3 Running scriptlet: kernel-modules-5.18.0-0.rc1.20220408git1831fed559732 2/3 Installing : kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc 3/3 Running scriptlet: kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1. 3/3 kdump: kernel 5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 doesn't exist Running scriptlet: kernel-modules-5.18.0-0.rc1.20220408git1831fed559732 3/3 Running scriptlet: kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc 3/3 Verifying : kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc 1/3 Verifying : kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1. 2/3 Verifying : kernel-modules-5.18.0-0.rc1.20220408git1831fed559732 3/3 Installed: kernel-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 kernel-core-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 kernel-modules-5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 Complete! [root@kibble ~]# ls /boot config-5.16.17-200.fc35.x86_64 efi elf-memtest86+-5.31 extlinux grub2 initramfs-0-rescue-313a6d6ebb9a489b92971a3db1877fe0.img initramfs-5.16.17-200.fc35.x86_64.img initrd-plymouth.img loader lost+found memtest86+-5.31 symvers-5.16.17-200.fc35.x86_64.gz System.map-5.16.17-200.fc35.x86_64 vmlinuz-0-rescue-313a6d6ebb9a489b92971a3db1877fe0 vmlinuz-5.16.17-200.fc35.x86_64 [root@kibble ~]# 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
I upgraded from f35 to f36 beta using the fedora-upgrade script.
The kernel-install script handles this, which is a part of systemd. A few people seem to have run into this on using the dnf upgrade method (myself included on one system). Can you please check /boot/efi/<machine-id> and see if the kernels were installed there? Also of interest, do you know what version of Fedora this system was originally installed on?
The kernel was indeed installed to /boot/efi/<machine-id>. Is /etc/machine-id the source of truth for that value? My collection of backgrounds packages would suggest this system started life on f23.
*** This bug has been marked as a duplicate of bug 2071034 ***