<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Fedora Bootc on Fedora</title><link>https://fedora.ayshell.dev/tags/fedora-bootc/</link><description>Recent content in Fedora Bootc on Fedora</description><generator>Hugo -- 0.147.5</generator><language>en-us</language><lastBuildDate>Fri, 13 Nov 2026 20:55:27 +0530</lastBuildDate><atom:link href="https://fedora.ayshell.dev/tags/fedora-bootc/index.xml" rel="self" type="application/rss+xml"/><item><title>Fedora 44 bootc on the Raspberry Pi 5: Status Update (Still Partially Supported)</title><link>https://fedora.ayshell.dev/posts/bootc/fedora-bootc-rpi5-report-2/</link><pubDate>Fri, 13 Nov 2026 20:55:27 +0530</pubDate><guid>https://fedora.ayshell.dev/posts/bootc/fedora-bootc-rpi5-report-2/</guid><description>&lt;h1 id="long-story-short">Long Story Short&lt;/h1>
&lt;p>Fedora 44 is a big step up &lt;a href="https://fedora.ayshell.dev/posts/bootc/fedora-bootc-rpi5-report/">from Fedora 42 on the Raspberry Pi 5&lt;/a>. The install process is still the same, and it supports the Pi well. The main limit is still the &lt;a href="https://github.com/worproject/rpi5-uefi">UEFI to VideoCore translation layer&lt;/a>, but the base OS clearly has potential.&lt;/p>
&lt;h1 id="whats-changed-with-fedora-44">What&amp;rsquo;s Changed With Fedora 44&lt;/h1>
&lt;ul>
&lt;li>&lt;a href="https://docs.ayshell.dev/posts/bootc/rpi5-f42/">Same install steps as before&lt;/a>: build &lt;code>disk.raw&lt;/code>, flash it with &lt;code>dd&lt;/code>, add the firmware to the EFI partition, and boot.&lt;/li>
&lt;li>Fedora 44 boots and runs well on the Pi 5.&lt;/li>
&lt;li>The UEFI to VideoCore translation layer &lt;a href="https://github.com/worproject/rpi5-uefi#supported-peripherals-in-uefi">still limits what works&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h1 id="starting-a-hummingbird-image-for-rpi5">Starting a Hummingbird Image for RPi5&lt;/h1>
&lt;p>I started working on a Raspberry Pi 5 compatible Fedora Hummingbird bootc image. The goal is simple: &lt;strong>get hummingbird-bootc running on the Pi 5&lt;/strong>.&lt;/p></description></item><item><title>Getting Fedora bootc to Boot on a Raspberry Pi 5 (and Where It Breaks)</title><link>https://fedora.ayshell.dev/posts/bootc/fedora-bootc-rpi5-report/</link><pubDate>Wed, 21 Oct 2026 11:52:02 +0530</pubDate><guid>https://fedora.ayshell.dev/posts/bootc/fedora-bootc-rpi5-report/</guid><description>&lt;h1 id="long-story-short">Long Story Short&lt;/h1>
&lt;p>I tried running a &lt;strong>Fedora 42 bootc image on a Raspberry Pi 5&lt;/strong>. It’s &lt;em>a partial success&lt;/em>, but I got far enough to learn a lot. The Pi 5 boots and I can log in, but the stock kernel can’t see the Ethernet chip, the Wi-Fi chip, or most other drivers. Only the USB ports work.&lt;/p>
&lt;h1 id="how-i-installed-fedora-42-bootc-into-rpi5">How I Installed Fedora 42 bootc into RPi5?&lt;/h1>
&lt;ol>
&lt;li>Built an ARM64 &lt;code>disk.raw&lt;/code> image with bootc-image-builder from Raspberry Pi 5 itself. (I know QEMU exists, but I couldn&amp;rsquo;t get it working due to my lack of knowledge with QEMU) *&lt;em>shrugs&lt;/em>&lt;/li>
&lt;li>Flashed it on an SD Card with &lt;code>dd&lt;/code>.&lt;/li>
&lt;li>Added the community EDK2 UEFI firmware (&lt;a href="https://github.com/worproject/rpi5-uefi">rpi5-uefi&lt;/a> to the EFI partition, next to the existing &lt;code>EFI/&lt;/code> folder.&lt;/li>
&lt;li>Booted the Pi5 and reached a Fedora 42 Login. (&lt;em>partially successful&lt;/em>).&lt;/li>
&lt;/ol>
&lt;blockquote>
&lt;p>&lt;a href="https://docs.ayshell.dev/posts/bootc/rpi5-f42/">Full guide here&lt;/a>.&lt;/p></description></item></channel></rss>