Fedora Account System
Red Hat Associate
Red Hat Customer
ESP partitions on SD cards created using arm-image-installer from recent Atomic desktop raw images are missing "overlays" directory and all files usually present in root folder (DTBs, RPi firmware, U-Boot, etc.). This prevents booting such SD cards on RPi hardware. Reproducible: Always Steps to Reproduce: 1. Create boot SD card from any recent F45 aarch64 Atomic desktop raw image 2. Mount this card ESP partition and check its contents Actual Results: ESP partition contains "EFI" directory only. Expected Results: ESP partition contains "EFI" and "overlays" directories and RPi firmware and device tree files in root folder. Additional Information: After copying missing files from another image the system booted fine. That would mean that otherwise raw aarch64 images are not missing anything else.
Proposed as a Freeze Exception for 45-final by Fedora user jgroman using the blocker tracking app because: This prevents Atomic desktop raw images from booting on RPi4.
Thanks! Let me info dump a bit here: 1. Fedora Atomic Desktops previously didn't provide raw disk images (or qcow2's), they are new in Fedora 45. 2. Because these systems are ostree-based the files need to be manually copied into the ESP by the image build tooling (`image-builder`). I'm happy to do the second, I created an upstream PR to do so: https://github.com/osbuild/image-builder/pull/2734 However, for this to work the Fedora Atomic Desktops ostree commits need to include the bcm283x-firmware package. They currently don't so I've contacted the Fedora Atomic Desktops Matrix channel to ask if it can be included, if it *does* get included then I can land the above PR and do an upstream release.
+3 in https://forge.fedoraproject.org/quality/blocker-review/issues/2196 , marking accepted FE.
Working on this in https://forge.fedoraproject.org/atomic-desktops/config/pulls/810
For F45: https://forge.fedoraproject.org/atomic-desktops/config/pulls/811
The PR was merged six days ago. Reporter, can you confirm whether this is fixed? Thanks!
Unfortunately the issue does not seem to be fixed even in the latest Silverblue image, ESP partition still contains EFI subdirectory only. Verified also by creating boot sd card using arm-image-installer. ➜ unxz Fedora-Silverblue-Disk-45-20261013.n.0.aarch64.raw.xz ➜ virt-filesystems -a Fedora-Silverblue-Disk-45-20261013.n.0.aarch64.raw --long --all Name Type VFS Label MBR Size Parent /dev/sda1 filesystem vfat ESP - 525033472 - /dev/sda2 filesystem ext4 boot - 2040373248 - /dev/sda3 filesystem ext4 root - 7817916416 - /dev/sda1 partition - - 06 525336576 /dev/sda /dev/sda2 partition - - 83 2147483648 /dev/sda /dev/sda3 partition - - 83 8046772224 /dev/sda /dev/sda device - - - 10737418240 - ➜ virt-ls -la Fedora-Silverblue-Disk-45-20261013.n.0.aarch64.raw -m /dev/sda1 / total 28 drwxr-xr-x 3 root root 16384 Jan 1 1970 . drwxr-xr-x 20 root root 4096 Oct 13 10:48 .. drwxr-xr-x 4 root root 8192 Oct 13 08:48 EFI ------ Correct ESP partition contents should look like this: ➜ virt-ls -la Fedora-Minimal-45-20261009.n.0.aarch64.raw -m /dev/sda1 / total 24244 drwxr-xr-x 4 root root 16384 Jan 1 1970 . drwxr-xr-x 20 root root 4096 Oct 13 10:50 .. drwxr-xr-x 4 root root 4096 Oct 9 08:39 EFI -rwxr-xr-x 1 root root 32539 Sep 8 00:00 bcm2710-rpi-2-b.dtb -rwxr-xr-x 1 root root 35252 Sep 8 00:00 bcm2710-rpi-3-b-plus.dtb -rwxr-xr-x 1 root root 34731 Sep 8 00:00 bcm2710-rpi-3-b.dtb -rwxr-xr-x 1 root root 33720 Sep 8 00:00 bcm2710-rpi-cm0.dtb -rwxr-xr-x 1 root root 32302 Sep 8 00:00 bcm2710-rpi-cm3.dtb -rwxr-xr-x 1 root root 33708 Sep 8 00:00 bcm2710-rpi-zero-2-w.dtb -rwxr-xr-x 1 root root 33708 Sep 8 00:00 bcm2710-rpi-zero-2.dtb -rwxr-xr-x 1 root root 56407 Sep 8 00:00 bcm2711-rpi-4-b.dtb -rwxr-xr-x 1 root root 56411 Sep 8 00:00 bcm2711-rpi-400.dtb -rwxr-xr-x 1 root root 39913 Sep 8 00:00 bcm2711-rpi-cm4-io.dtb -rwxr-xr-x 1 root root 56928 Sep 8 00:00 bcm2711-rpi-cm4.dtb -rwxr-xr-x 1 root root 53824 Sep 8 00:00 bcm2711-rpi-cm4s.dtb -rwxr-xr-x 1 root root 78860 Sep 8 00:00 bcm2712-d-rpi-5-b.dtb -rwxr-xr-x 1 root root 78860 Sep 8 00:00 bcm2712-rpi-5-b.dtb -rwxr-xr-x 1 root root 78816 Sep 8 00:00 bcm2712-rpi-500.dtb -rwxr-xr-x 1 root root 79805 Sep 8 00:00 bcm2712-rpi-cm5-cm4io.dtb -rwxr-xr-x 1 root root 79871 Sep 8 00:00 bcm2712-rpi-cm5-cm5io.dtb -rwxr-xr-x 1 root root 79846 Sep 8 00:00 bcm2712-rpi-cm5l-cm4io.dtb -rwxr-xr-x 1 root root 79912 Sep 8 00:00 bcm2712-rpi-cm5l-cm5io.dtb -rwxr-xr-x 1 root root 78864 Sep 8 00:00 bcm2712d0-rpi-5-b.dtb -rwxr-xr-x 1 root root 52624 Aug 7 11:03 bootcode.bin -rwxr-xr-x 1 root root 2731 Sep 8 00:00 config.txt -rwxr-xr-x 1 root root 7381 Sep 7 20:32 fixup.dat -rwxr-xr-x 1 root root 5512 Sep 7 20:32 fixup4.dat -rwxr-xr-x 1 root root 3282 Sep 7 20:32 fixup4cd.dat -rwxr-xr-x 1 root root 8501 Sep 7 20:32 fixup4db.dat -rwxr-xr-x 1 root root 8501 Sep 7 20:32 fixup4x.dat -rwxr-xr-x 1 root root 3282 Sep 7 20:32 fixup_cd.dat -rwxr-xr-x 1 root root 10348 Sep 7 20:32 fixup_db.dat -rwxr-xr-x 1 root root 10348 Sep 7 20:32 fixup_x.dat drwxr-xr-x 2 root root 36864 Oct 9 08:39 overlays -rwxr-xr-x 1 root root 947704 Sep 8 00:00 rpi-u-boot.bin -rwxr-xr-x 1 root root 3022848 Sep 7 20:32 start.elf -rwxr-xr-x 1 root root 2298560 Sep 7 20:32 start4.elf -rwxr-xr-x 1 root root 844156 Sep 7 20:32 start4cd.elf -rwxr-xr-x 1 root root 3796520 Sep 7 20:32 start4db.elf -rwxr-xr-x 1 root root 3045800 Sep 7 20:32 start4x.elf -rwxr-xr-x 1 root root 844156 Sep 7 20:32 start_cd.elf -rwxr-xr-x 1 root root 4868488 Sep 7 20:32 start_db.elf -rwxr-xr-x 1 root root 3769512 Sep 7 20:32 start_x.elf
This is expected (for now) as I didn't land the image-builder PR (https://github.com/osbuild/image-builder/pull/2734). I'll land that shortly after verifying that everything is appropriate in the commits and land it in an new release under the existing FE.
Ah, sorry, didn't recognize there were two PRs. Yes, please do that, thanks.
FEDORA-2026-51b16b09f1 (image-builder-87.0.0-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-51b16b09f1
FEDORA-2026-51b16b09f1 has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-51b16b09f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-51b16b09f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Verified fixed on F45 RC 1.1 Silverblue aarch64 raw image. SD card created using arm-image-installer boots successfully. ➜ virt-ls -la Fedora-Silverblue-Disk-45-1.1.aarch64.raw -m /dev/sda1 / | wc -l 43
FEDORA-2026-51b16b09f1 (image-builder-87.0.0-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.