Fedora 44 RISC-V widens Linux board support

Fedora 44 RISC-V images add an Omni kernel that boots on 17 boards.

Fedora 44’s new RISC-V images are more than a fresh download: they show how Fedora is trying to cover more boards while upstream Linux catches up. The release includes container, server, and cloud variants, and the Omni kernel now boots on 17 named boards.

Item	Kernel	Image types	Hardware reach
Fedora 44 RISC-V Server	Linux 6.19-based	Server	Vision Five 2, Orange Pi RV, Milk-V Mars
Fedora-Server-Host-Omni	Omni	Server host	17 bootable boards
Fedora 44 RISC-V container	Not stated	Container	Community-contributed alternate image
Fedora 44 RISC-V cloud	Not stated	Cloud	Community-contributed alternate image

1. Fedora 44 RISC-V server images

The server images are the most concrete sign that Fedora 44 RISC-V is ready for real installs, not just experiments. Fedora says these builds use a Linux 6.19-based kernel that stays close to upstream, which matters if you want a system that tracks mainline work without waiting for a long downstream fork.

Fedora also says the server images have been tested on three boards already: the Vision Five 2, Orange Pi RV, and Milk-V Mars. That gives builders a known starting point if they want to bring up a RISC-V machine with a Fedora server stack and fewer surprises during first boot.

• Kernel base: Linux 6.19
• Tested boards: Vision Five 2, Orange Pi RV, Milk-V Mars
• Best fit: users who want a normal server install path

2. Fedora-Server-Host-Omni

The biggest change in this release is the Fedora-Server-Host-Omni image, which replaces the more limited Fedora-Server-Host-Generic path for this branch. Fedora’s goal is simple: keep one kernel build that can boot on more RISC-V boards, even when some hardware support has not fully landed upstream yet.

That makes the Omni kernel a practical compatibility layer for early adopters. It is not about squeezing every board into a perfect upstream profile; it is about getting more systems to boot and stay useful while the surrounding kernel work continues.

• Purpose: broader board support
• Role: host image for Fedora Server
• Approach: supports hardware before all upstream patches are merged

3. The 17-board Omni kernel list

Fedora’s Omni kernel can boot on a notably wide set of boards, and that list is the most useful detail for anyone shopping for RISC-V hardware. The supported lineup includes Banana Pi, Bit-Brick, DeepComputing, Lichee Pi, Milk-V, OrangePi, Pine64, SiFive, SpacemiT, and StarFive systems.

For buyers and testers, the important point is not just the count, but the spread across vendors and board classes. If you are working on a board that is close to one of these families, Fedora 44 gives you a better chance of getting a usable system without waiting on a perfect upstream match.

Bootable boards include: Banana Pi BPI-F3 Bit-Brick K1 DeepComputing fml13v01 Lichee Pi 4A Milk-V Jupiter Milk-V Mars Milk-V Megrez Milk-V Titan OrangePi R2S OrangePi RV OrangePi RV2 Pine64 STARPro64 SiFive HiFive P550 SiFive HiFive Unmatched SpacemiT K3 Pico-ITX StarFive VisionFive 2 StarFive VisionFive 2 Lite

4. Container and cloud variants

Fedora 44 RISC-V is not limited to bare metal. The release also includes container and cloud variants, which matters if you want to test software, spin up a reproducible environment, or move a workload onto RISC-V without committing to a physical board first.

These images are described as community-contributed alternate images, so they are not the same thing as the official Fedora 44 release images from a month earlier. Still, they give developers a way to follow Fedora 44 across more deployment styles, from local experiments to remote infrastructure.

• Container image: useful for app testing and CI
• Cloud image: useful for remote instances and automation
• Status: community-contributed alternate images

5. Why this release matters now

Fedora’s timing is important because RISC-V hardware support is still uneven across Linux distributions. The article notes that current Ubuntu Linux RISC-V builds are limited to the RVA23 profile, which leaves their hardware range much narrower than Fedora’s Omni-based approach.

That does not mean Fedora is done or that every board is equally polished. It does mean Fedora 44 is trying to be the distro you can actually boot on more current RISC-V boards today, rather than the one that waits for every patch to settle first.

How to decide

Pick the Fedora 44 server image if you want a standard Fedora install on a board already tested by the project. Pick the Omni host image if your board is on the edge of support and you care more about booting than strict upstream completeness.

If you are building software instead of a full system, the container and cloud images are the easier entry points. They let you work with Fedora 44 on RISC-V before you commit to a specific board, power setup, or storage image.