Arch is the smallest of the major RISC-V Linux distributions, but it’s the most up-to-date — and the one rolling-release enthusiasts who want their RISC-V box to feel like mainline Arch are running in 2026. This article covers what’s officially supported, what works in practice, and what doesn’t.
The short version: Arch RISC-V is a community port, not an archlinux.org architecture. The project — archriscv, maintained by Felix Yan — packages the vast majority of the Arch repos against the RV64GC profile, and runs on a handful of officially supported boards plus a long tail of community-supported ones. The user experience is closest to a “normal Arch box with a slower CPU and a few rough edges” than to “a hobbyist distro that barely runs.”
What “Arch RISC-V” actually is
archlinux.org still ships x86_64 only. The 2024 RFC #0032 “Arch Linux Ports” defined a process for promoting ports to official status, but as of 2026 RISC-V has not been promoted through that process. The port lives at riscv.mirror.pkgbuild.com and archriscv.felixc.at, run by community maintainers. The long-term goal stated by the project is upstreaming patches so riscv64gc can join Arch itself.
The archriscv project is the patch + build infrastructure layer. The actual package builds come from a fork of the standard Arch build system, with a few arch-specific patches. The current primary maintainer is Felix Yan (@felixonmars), an Arch Linux developer. The patch repo is github.com/felixonmars/archriscv-packages (269 stars, 5,288 commits). Support channels are IRC #archlinuxriscv on libera.chat and Matrix #archlinux-riscv:matrix.org. Hardware baseline: RV64GC, lp64d ABI (no soft-float, no RV32).
Officially supported boards in 2026
| Board | SoC | Cores | Status |
|---|---|---|---|
| QEMU virt | (virtual) | configurable | Mainline test target. Boots cleanly. |
| SiFive HiFive Unmatched | FU740 | 4× U74 + E76 | Officially supported. |
| SiFive HiFive Unleashed | FU540 | 4× U54 + E51 | Legacy. Still works but no upstream. |
| Microchip PolarFire SoC Icicle Kit | PolarFire | 5× U54 + E51 | Officially supported. |
| StarFive VisionFive v2 | JH7110 | 4× U74 | The recommended 2026 daily-driver SBC. Best software support. |
| Milk-V Mars | JH7110 | 4× U74 | Same SoC as VF2; uses the same kernel + packages. |
| Allwinner Nezha D1 | D1 (C906) | 1× C906 + E902 | Officially supported. |
| Sipeed LicheePi 4A | TH1520 | 4× C910 + E902 | unsupported repo experimental, kernel pkg linux-th1520 |
| Milk-V Pioneer | Sophgo SG2042 | 64× C920 | unsupported repo experimental, kernel pkg linux-sophgo |
Pine64 Star64 (JH7110, same SoC as VF2) works with the VF2 kernel/pkg set but has no dedicated target. Mango Pi MQ Pro (Allwinner D1/C906) falls under the Nezha D1 supported family. AX45MP cores (C910 etc.) generally need BSP kernels — thead-blacklist.txt excludes them from main builds.
Kernel
The mainline arch kernel is linux 6.12.x tracking upstream. linux-lts is available too. For boards needing BSP kernels, additional packages are available: linux-zen (Zen patchset), linux-revyos (for some Allwinner boards), linux-sophgo (SG2042), linux-th1520 (TH1520). The community VisionFive 2 image from cwt-vf2/archlinux-image-vf2 ships a StarFive BSP-derived kernel at 6.12.18 with the Imagination PowerVR GPU driver wrapper.
Package state
The archriscv port maintains core, extra, and unsupported repos. pacman -Sy works against mirrors. The vast majority of Arch packages build and ship. Out of the box:
- Browsers: Firefox, Chromium, Chrome
- Editors / IDEs: VS Code, JetBrains toolbox, Vim, Neovim, Emacs
- Media: Kodi, OBS Studio, Krita, Blender, GIMP
- Emulators: Dolphin, PCSX2, SNES9x, plus Wine (via box64)
- Office: LibreOffice
- Languages: Python, Node, Ruby, Go, Rust, Java (slow bootstrap on cold cache but works)
- Containers: Docker (works on RISC-V since 2023)
Known gaps:
- Bootstrap chains for GHC, Julia, OpenJDK, Dart, Bun are heavy — the first build can take hours because the bootstrap binary for those toolchains itself needs a working RISC-V host.
- Sophgo SG2042 has its own blacklist (
sg2042-blacklist.txt) excluding packages that don’t yet compile cleanly on its RVV 0.71 vector extension profile. - TH1520 / C910 has
thead-blacklist.txtfor the same reason. - Some packages still tracked in the detailed status page rather than fully up-to-date.
The exact package count is not publicly documented in 2026 — don’t quote a specific number without checking riscv.mirror.pkgbuild.com directly.
Desktop
The closest to a usable 2026 desktop is GNOME on Wayland on a StarFive VisionFive 2 with the PVR (Imagination PowerVR) GPU driver stack. The PVR driver is closed-source — Imagination’s DDK (Driver Development Kit) is a binary blob wrapped by the mesa-pvr-ddk119 package and a community img-gpu-vf2 kernel module. EGL support is at OpenGL ES 1.4 / 2.0 / 3.0 depending on the DDK version; no Vulkan support on JH7110 outside the blob wrapper. KDE Plasma Wayland works with the same PVR stack, slower than GNOME but functional. Weston and Xorg modesetting are also functional.
What is rough:
- GPU acceleration depends on the closed-source Imagination DDK blobs. When the userspace blob and the kernel-side module version mismatch, you get software rendering or a black screen.
- EGL is at 1.4 only for some of the wxWidgets/EGL toolchain builds. Most modern apps need 1.5 or higher; they fall back to software paths.
- HiFive Unmatched and Sophgo SG2042 have no GPU at all. The desktop is unusable on these — use them headless.
- Pine64 Star64 has had IMG-Rogue artifacting reports after some kernel upgrades. Use VisionFive 2 instead if you need a display.
The “daily driver” path: VisionFive 2 + PVR blob + GNOME on Wayland. It works, but the experience is closer to a 2015-era ARM laptop than to a 2025 desktop.
Installation
The upstream archinstall package is arch=(any) — it installs on RISC-V if you boot an Arch RISC-V rootfs. But archinstall is not packaged with RISC-V-specific board profiles or bootloader handling — it’s the generic installer.
The project-recommended path is to flash a prebuilt rootfs image (default credentials root / archriscv) from riscv.mirror.pkgbuild.com. The community cwt-vf2/archlinux-image-vf2 GitHub repository provides a VisionFive 2 image with a custom U-Boot, kernel, GPU driver, and PVR-Mesa wrapper. Booting often requires manual SPL/U-Boot updates and DIP-switch or env-var tweaks — the stock VF2 SPL/U-Boot is too old for current kernels.
The popular community VF2 image is github.com/cwt-vf2/archlinux-image-vf2. There is no project literally called archinstallrisc-v.
Performance expectations
| Core | Examples | Single-thread | Notes |
|---|---|---|---|
| U74 | VisionFive 2, Star64, JH7110 | ~Raspberry Pi 4 / early-Pi-5 territory at 1.5 GHz | In-order, dual-issue |
| C906 | Mango Pi MQ Pro, LicheeRV, Nezha D1 | ~Raspberry Pi 3 | 1 GHz single-core in-order |
| C920 | Sophgo SG2042, Pioneer | Mid-range x86 on parallel workloads, weak single-thread | 2 GHz, out-of-order, 64 cores, RVV 0.71 |
| Cortex-A55 / A76 (for comparison) | Various | A76 is materially faster per-thread than U74; A55 is in the same general class |
If you want a usable Linux desktop in 2026, a $60 VisionFive 2 is in the same class as a $100 Raspberry Pi 5 for desktop performance. The RISC-V advantage is openness of the ISA and (eventually) per-watt scaling — not raw performance yet.
Common pitfalls
- Bootloader: stock VisionFive 2 SPL/U-Boot is too old for current kernels. You must flash updated SPL+U-Boot via
flashcpto/dev/mtd0/mtd2, or usecwt‘su-boot-starfive-vf2pkg. - Missing device tree: you must load
dtb/starfive/jh7110-starfive-visionfive-2-v1.3b.dtbexplicitly from the EFI partition. Wrong DTB = silent no-display. - GPU: the PVR driver is a closed Imagination DDK blob. Mainline
powervrindrm-nextis still maturing. No real Vulkan on JH7110 outside the blob wrapper. - NVMe on VF2 needs the
phy_jh7110_pciemodule in initramfs, not just a late autoload. - AX45MP / C910-based boards (some LicheePi 4A revisions, TH1520 parts) need the BSP kernel, not mainline
linux. - Framebuffer fallback only — no GPU acceleration when the PVR userspace blob mismatches the kernel module version.
- SD card regressions reported after kernel 6.10 on certain VF2 board revisions. Check the cwt project issue tracker before upgrading.
Comparison to other RISC-V distributions
| Distro | Strengths | Weaknesses |
|---|---|---|
| Debian RISC-V | Oldest and largest package set. Official-ish port. Broadest hardware coverage and best community docs. Considered the “reference” RISC-V distro. | Conservative; sometimes lags on the latest packages. |
| Fedora RISC-V | Official Fedora secondary arch. Strong on server / HPC. Used on SG2042 Pioneer boxes at EPCC. | Smaller package set than Debian-RISC-V. |
| openSUSE RISC-V | Tumbleweed has a riscv64 build. | Smaller community and fewer boards. |
| Ubuntu RISC-V | Canonical-supported since 24.04 with riscv64 images for VF2 etc. | Less rolling than Arch. |
| Arch RISC-V | Rolling-release like mainline Arch. Smallest but most up-to-date packages. Weakest board coverage and installer story. | Best fit for Arch enthusiasts and kernel hackers. |
If you want the most “Arch-like Arch on RISC-V”, the answer is archriscv. If you want the most polished installer and the largest package set, the answer is Debian-RISC-V.
The future
RVA23 profile is the 2024 RISC-V profile standardizing the V-ext, hypervisor, vector, crypto, and other extensions. No shipping RISC-V SBC silicon is fully RVA23-compliant yet — most current SBCs are RVA22 or RV64GC. archriscv’s baseline stays RV64GC until silicon catches up.
Server-class: Sophgo SG2042 (C920, RVV 0.71) in the Milk-V Pioneer is the current high-end dev box — 64 cores, 128 GB DDR4, mATX form factor. Next-gen Sophgo SG2044 has been announced as a follow-up, but is not yet a shipping dev board in 2026. The SG2042 + Fedora RISC-V is the closest you can get to “RISC-V as a server-class platform” in 2026.
JH8110 / JH8100: successor SoCs to the JH7110 referenced in 2024-2025 LKML chatter. Not yet generally available as of 2026.
TL;DR
Arch RISC-V (archriscv, community port by Felix Yan) packages the vast majority of the Arch repos against RV64GC and runs on QEMU virt, HiFive Unmatched/Unleashed, PolarFire Icicle, StarFive VisionFive 2 / Milk-V Mars, and Allwinner Nezha D1 officially; LicheePi 4A and SG2042 are unsupported experimental. The VisionFive 2 with the Imagination PVR blob + GNOME on Wayland is the closest thing to a usable 2026 desktop. The kernel is mainline 6.12.x plus per-board BSPs. The installer is a prebuilt rootfs image, not archinstall. Performance is in the Raspberry Pi 4 / 5 class for the U74 boards, weaker on C906, much stronger on the C920 (SG2042). Debian RISC-V has the largest package set; Arch RISC-V has the most up-to-date. RVA23 silicon and JH8100/JH8110 SoCs are not yet shipping in 2026. If you want “RISC-V on a Linux desktop” in 2026, a VisionFive 2 with the cwt community image is the closest you get to “it just works.”
Sources verified July 2026: riscv.mirror.pkgbuild.com (official port homepage); archriscv.felixc.at (mirror); github.com/felixonmars/archriscv-packages (patch repo, 5,288 commits); rfc.archlinux.page/0032-arch-linux-ports (RFC merged May 2024, not yet promoted riscv64); forum.rvspace.org/t/arch-linux-image-for-visionfive-2/1459 (cwt VF2 image thread, kernel 6.12, PVR DDK 1.19 Mesa wrapper, custom U-Boot); milkv.io/pioneer + sophgocommunity/Pioneer_Doc (SG2042 specs); riscv.epcc.ed.ac.uk/documentation/hardware (board reference list). Unverified items: exact 2026 package count (not quoted), Sophgo SG2044 shipping status (not quoted as a fact), formal promotion status of RFC #0032 (still pending).
Comments