Fedora's next release will run on every variant of the Raspberry Pi 5B — with caveats — while buyers of the Compute Module 5 and the Pi 500+ will need to keep waiting. And Fedora 44 users are not locked out, but are told a temporary workaround is needed at boot.
That is the picture Peter Robinson paints in a blog post, summarised by LWN.net. According to Robinson, the upcoming Fedora 45 release will work on all Raspberry Pi Model 5B variants, subject to caveats; the Compute Module 5 and Pi 500+ remain works in progress. On Fedora 44, he notes a temporary boot-time workaround is required — with the implication that keeping the kernel and firmware updated promptly can make it a one-time step rather than a permanent one.
The gap matters because single-board hardware has consistently shipped faster than mainstream distributions can validate it. For anyone choosing a board around a Linux target rather than the other way around, one release cycle of missing support is the difference between a working project and a stalled one.
Support matrix at a glance
| Board | Fedora 45 (upcoming) |
|---|---|
| Raspberry Pi 5B (all variants) | Works, with caveats |
| Compute Module 5 | Work in progress |
| Pi 500+ | Work in progress |
The practical split:
- Pi 5B variants: the mainstream option. Fedora 45 is the target release; Fedora 44 users are not locked out, but must apply the boot workaround Robinson describes.
- Compute Module 5: the embedded variant used in custom carrier-board and edge deployments. Support is explicitly "work in progress" — not blocked, but not ready.
- Pi 500+: the desktop/education-style variant, same status as the CM5.
Analysis: matching board to release
The sections below are editorial guidance drawn from the status table above, not further reporting from the source. The guidance is straightforward: match the board to the release.
- If Fedora is the target OS, a Pi 5B variant is the board to buy now, planning around Fedora 45.
- If the project specifically needs a CM5 (custom carrier boards, embedded deployments) or a Pi 500+, and Fedora is a hard requirement, hold off until that board's status changes — or choose an OS where it is already supported.
- Teams with Fedora 44 deployments should apply the documented workaround now and move to Fedora 45 when it lands rather than relying on the stopgap.
Analysis: before you commit hardware
- "With caveats" is not a clean pass. The specifics sit in Robinson's original post, which should be checked directly before hardware is committed.
- Fedora 45 is still upcoming, so status may shift as launch approaches.
- The Fedora 44 workaround is temporary — do not bake it into long-lived images or provisioning scripts.
- CM5 and Pi 500+ users should plan on waiting; neither board has reached the "works with caveats" stage.
Hardware availability consistently outpaces distribution support in ARM Linux, so board selection and OS selection are increasingly a single decision rather than two.
Source: LWN.net, "Robinson: Raspberry Pi 5 on Fedora." Detail above is drawn from LWN's summary of Peter Robinson's post; see the original for specifics.
Fedora 下一個版本將可在 Raspberry Pi 5B 的所有變體上運行——但附帶若干限制條件——而 Compute Module 5 及 Pi 500+ 的買家則仍需繼續等待。另一方面，Fedora 44 用戶並未被拒諸門外，但被告知開機時需要採用一個臨時的 workaround。
以上是 Peter Robinson 在一篇網誌文章中描繪的情況，並由 LWN.net 作出摘要。根據 Robinson 的說法，即將推出的 Fedora 45 將可在所有 Raspberry Pi Model 5B 變體上運作，但須受若干限制條件所規限；Compute Module 5 及 Pi 500+ 則仍在開發中。在 Fedora 44 方面，他指出開機時需要一個臨時的 workaround——言下之意是，若及時更新 kernel 與 firmware，該步驟可僅需執行一次，而非永久性質。
這個落差並非小事，因為單板硬件的推出速度向來快於主流發行版對其進行驗證的速度。對於那些圍繞 Linux 目標而非倒過來挑選開發板的人來說，缺少支援的一個 release cycle，足以令一個順利運作的項目與一個停滯不前的項目產生天淵之別。
支援矩陣一覽
| 開發板 | Fedora 45（即將推出） |
|---|---|
| Raspberry Pi 5B（所有變體） | 可運作，附帶限制條件 |
| Compute Module 5 | 開發中 |
| Pi 500+ | 開發中 |
實際分野如下：
- Pi 5B 變體：主流之選。Fedora 45 是目標版本；Fedora 44 用戶並未被拒諸門外，但必須套用 Robinson 所述的開機 workaround。
- Compute Module 5：用於自訂 carrier board 及邊緣部署的嵌入式變體。支援狀態明確標示為「開發中」——並未受阻，但尚未就緒。
- Pi 500+：桌面／教育型變體，狀態與 CM5 相同。
分析：按版本選板
以下各節屬編輯分析，取材自上方狀態表，並非來自消息來源的進一步報道。指引十分直接：按版本選板。
- 如果 Fedora 是目標作業系統，現階段應購買 Pi 5B 變體，並以 Fedora 45 為規劃基礎。
- 如果項目確實需要 CM5（自訂 carrier board、嵌入式部署）或 Pi 500+，而 Fedora 又是硬性要求，宜暫緩購買，直至該開發板的狀態改變——或者改用已支援該板的作業系統。
- 持有 Fedora 44 部署的團隊，應立即套用文中所述的 workaround，待 Fedora 45 正式推出後便行升級，而非長期依賴這個權宜之計。
分析：購入硬件之前須知
- 「附帶限制條件」並非毫無問題的通過。具體細節載於 Robinson 的原文，落實購買硬件前應直接查閱。
- Fedora 45 尚未正式推出，因此狀態可能隨發佈日期臨近而有所變動。
- Fedora 44 的 workaround 屬臨時性質——切勿將其嵌入長期使用的 image 或 provisioning 腳本之中。
- CM5 及 Pi 500+ 用戶應做好等待的準備；兩款開發板均未達至「可運作但附帶限制條件」的階段。
在 ARM Linux 生態中，硬件供應向來先行於發行版支援，因此選擇開發板與選擇作業系統，已日益成為一個不可分割的整體決定，而非兩個獨立決定。
資料來源：LWN.net，〈Robinson: Raspberry Pi 5 on Fedora〉。上述內容取材自 LWN 對 Peter Robinson 文章的摘要；詳情請參閱原文。