Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: With all the necessary changes for the DTBloader change in place I've tried the 20260213 Workstation live iso nightly and it boots fine (as expected). I also did a test install and that mostly works. But no /boot/loader/entries entry get generated for the new kernel. Actually there is no /boot/loader/entries dir at all, which is weird since that is owned by grub-efi-a64, which is installed. As a work around I rebooted into the live USB, created a /sysroot dir and mounted the installed system there including mounting /proc /sys and bind-mounting /dev. And then in that chroot rerun the "kernel install add ..." command from the kernel-uki-dtbloader %posttrans script (copy pasted from the posttrans) script). And that does generate the bls entry, as well as a rescue initrams which was also missing. The regular initramfs was there. Does anaconda disable the kernel posttrans and does some DIY stuff here ? Or maybe this depends on some files generated by anaconda after the transaction, and anconda reruns the script, but skips doing so for the new kernel-uki-dtbloader pkg ? Steps to Reproduce: 1. Boot Fedora-Workstation-Live-44-20260213.n.0.aarch64.iso on aarch64 UEFI system 2. Install 3. Reboot Actual results: grub only shows "Enter firmware setup" menu mounting /boot from live environment show no loader and no loader/entries dir at all Expected results: loader/entries dir is there as well as a bls file for the kernel from the install
FEDORA-2026-32c35c3848 (anaconda-44.21-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-32c35c3848
FEDORA-2026-32c35c3848 (anaconda-44.21-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.