The Fedora RISC-V SIG is excited to share that our RISC-V images for Fedora Linux 42 have landed on-time and without delay! If you’ve been watching our progress over the past few releases, you know that staying on schedule is a big deal, especially given our goals of eventually gaining “primary” status for RISC-V as an available Fedora Linux architecture. Previous RISC-V builds of Fedora Linux were released with a small delay compared to the other architectures, but with Fedora Linux 42, we’re right on track.
Today, we’re announcing the general availability of pre-built Fedora Linux 42 images for all our supported boards, QEMU, and container images. You can read more about these images in our previous post and under the Hardware section of the RISC-V team’s wiki. These non-official images are brought to you by the Fedora RISC-V Community.
Big Improvements, Smaller Numbers
Behind the scenes, the data tells an even more exciting story.
One way to measure and compare our efforts over time is by analyzing the number of “unresolved dependencies” in the build root. When a package is built, it typically has access to a repository containing every package built for that Fedora release–we call this the build root. Running the dnf repoclosure procedure against this buildroot by itself allows us to quantify the number of dependencies that are being fulfilled for a given build using a package built for a previous Fedora release.
- In Fedora Linux 40, the RISC-V buildroot had over 6,900 unresolved dependencies.
- Fedora Linux 41 slashed that nearly in half to around 3,800.
- Now, with Fedora Linux 42, we’re down to just 357 unresolved dependencies across 126 packages.
In other words, there are now only 357 subpackages from 126 packages in the RISC-V Koji which were not built directly for Fedora Linux 42 — a nearly 95% decrease in just one year.
That’s not just progress — it’s momentum.
These numbers represent the steady roll toward a complete and clean buildroot for RISC-V in Fedora. Every fix, every patch, and every accepted change brings us closer.
Upstream, Together
Our upstreaming work continues apace, and we want to acknowledge that none of this progress would be possible without the incredible collaboration from maintainers across the Fedora Project and beyond. Thank you to everyone who reviewed, accepted, merged, and built our patches. Your support makes this architecture possible.
We’re also excited about just how many packages build cleanly without special treatment or overlay repositories that need to be cared for. RISC-V is becoming just another architecture, and that’s exactly how it should be.
Get Involved
If you’ve got RISC-V hardware (or want to try it out via QEMU), there’s never been a better time to jump aboard the RISC-V train. Install the image, test your favorite packages, file bugs, and drop by the RISC-V Matrix channel to help us keep this locomotive rolling down the tracks.
Check out the RISC-V wiki page for more information, and we hope to see you on Matrix and helping us shape the future of Fedora Linux on open hardware.
Peter Boy
I really appreciate the RISC V efforts. I hope we get a power efficient device for Fedora Server without all the proprietary hassle we experience with the ARM hardware. Reading the article, we seem to have a real chance to set up a workable Server POC.
Greg Gendron
Will the RISC V effort allow, now or in future, installation on Qualcom Snapdragon systems?
RG
One year ago I managed to install debian on visionfive2. Instructions on doing so included downloading some large tars from a dubious google drive. I see things changed a bit. I was able to follow the instructions from Fedora Docs and now I have a fedora risc5 running on this board. I had to pay attention to properly partition the sd-card, but it was just a bit of trial and error. I still have the problem of drivers for this wifi stick that visionfive2 comes with, because the repo is being discontinued, and I mean the repo is gone, not just archived, but ssh works and for now this is enough. Well done…