The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Ubuntu Desktop can run on both Arm64 and 64-bit RISC-V, but they are not interchangeable platforms. Ubuntu publishes separate arm64 and riscv64 packages and images. Whether a graphical desktop actually works depends on the Ubuntu release, the processor profile, the board’s firmware and graphics support, and whether Canonical provides an image for that exact model. Arm64 has a stable ARMv8-A baseline; RISC-V requirements changed from RVA20 to RVA23 for newer releases. Canonical’s documented RISC-V Desktop path in QEMU remains experimental, so architecture support should not be mistaken for broad, supported desktop hardware.
Can Ubuntu Desktop run on RISC-V?
Yes, but the answer has three separate parts: the processor must implement an instruction-set profile that the chosen Ubuntu release accepts; the board must have a compatible kernel, firmware, storage and graphics path; and a supported or intentionally experimental desktop image must exist. A RISC-V board can boot Ubuntu Server while lacking a practical supported GNOME desktop. Conversely, a QEMU image can demonstrate that the userspace boots without representing the performance or hardware support of a physical computer.
Canonical’s hardware-support documentation treats non-PC systems as board-specific projects. Installation methods, image types, boot procedures and limitations are documented per board, rather than promised for every device using the same ISA. The safe question is therefore not “Does Ubuntu support RISC-V?” but “Does this board revision, with this Ubuntu release and image type, have the desktop support I need?”
Architecture support versus desktop support
- Architecture support means Ubuntu can build and publish a kernel, libraries and packages for the CPU target.
- Board support means the firmware, boot chain, storage controller, memory map, peripherals and kernel support are known for a particular model or revision.
- Desktop support additionally requires usable graphics acceleration or display output, input devices, audio and a tested graphical session.
These layers explain why a board can appear in an Ubuntu architecture or board list while still requiring a text-only installation, community work or a different desktop image.
#1 Best Overall
- Flexible MCU Board: Incorporate the ESP32-C3 32-bit RISC-V chip, operating up to 160 MHz, mounted multiple development ports,
- Developer Friendly: Compatible with Arduino IDE, MicroPython, CircuitPython, PlatformIO, ESP IDF, Zephyr, Matter, ESPNow, Meshtastic, WLED, ESPHome, Home Assistant, Ubidots
- Outstanding RF performance: Complete Wi-Fi functions and Bluetooth Low Energy, while supporting communication over 100m with anFL antenna
- Elaborate Power Design: 4 working modes as low as 44 μA in deep sleep mode, while supporting lithium battery charge management
- Thumb-sized Design: 21 x 17.5mm, Seeed Studio XIAO series classic form factor
Arm64 and riscv64 are different instruction sets
Arm and RISC-V describe CPU instruction-set architectures (ISAs), not single processor models. Ubuntu labels 64-bit Arm as arm64, also called ARM64, ARMv8 or AArch64. Its RISC-V target is riscv64, meaning 64-bit RISC-V. Canonical’s supported-architectures documentation lists these as separate package architectures.
| Aspect | Ubuntu arm64 | Ubuntu riscv64 |
|---|---|---|
| ISA family | Arm 64-bit (AArch64/ARMv8) | RISC-V 64-bit |
| Ubuntu package label | arm64 |
riscv64 |
| Binary compatibility | Arm64 binaries require an Arm64 userspace and compatible kernel | RISC-V binaries require a RISC-V userspace and compatible kernel |
| Documented baseline | ARMv8-A, with no optional extensions required; VFPv4 and NEON are assumed | RVA20 for older releases, moving to RVA23 for newer releases |
| What the baseline does not tell you | It is a compatibility floor, not a prediction of speed, graphics quality, battery life, price or application availability | |
An Arm64 executable is not a RISC-V executable. A package must be built for the architecture shown by the repository or image; installing a package compiled for the other ISA is not a supported way to add applications. Projects that ship native builds, source code or architecture-independent formats may support both, but availability must be checked per application.
Ubuntu release requirements: RVA20 versus RVA23
RISC-V compatibility is release-specific. Canonical documents RVA20 as the riscv64 baseline for Ubuntu 20.04 through 25.04, and RVA23 for Ubuntu 25.10 and later. An older board can therefore be acceptable for one Ubuntu release and rejected by a newer one even though both are 64-bit RISC-V.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Ubuntu release | Documented RISC-V floor | Practical implication |
|---|---|---|
| 20.04 through 25.04 | RVA20 | Hardware implementing the earlier profile is the compatibility target, subject to board and image support |
| 24.04 LTS | RVA20 support retained | It remains the LTS option for earlier RVA20-class cores when the board guide provides an image |
| 25.10 and later | RVA23 | A board that only implements the older floor may not boot or be supported |
| 26.04 LTS | RVA23S64 only, according to its release notes | Check the processor profile before attempting an upgrade; an older board cannot be assumed compatible |
Ubuntu’s 26.04 LTS summary says that, at the time of its April 2026 release-note entry, no RVA23S64 hardware was available and QEMU was the only supported RISC-V platform. That statement is historical, not an inventory for October 2026. Hardware availability and board qualification can change, so use the current board page and release notes when selecting a device.
Rank #2
- CH32V003 Development Minimum System Board for Nano RISC-V CH32V003F4U6 Chip TYPE-C USB 22Pin
- on-board 24MHz Crystal oscillator
- Power by TYPE-C USB
Profiles group required instruction-set features so software can target a known minimum. They still say nothing about a board’s memory capacity, display controller, firmware quality or thermal design. A processor can meet the profile and remain unsuitable for a graphical workstation.
Which RISC-V boards support Ubuntu?
Canonical’s supported-board index lists RISC-V examples including the Allwinner Nezha D1, Milk-V Mars, Pine64 Star64, SiFive HiFive Unmatched, the StarFive VisionFive family and QEMU. Each entry is intended to identify supported variants, available Ubuntu images, installation instructions and known limitations.
| Example listed platform | What to verify before buying or installing |
|---|---|
| Allwinner Nezha D1 | Exact board revision, image type, boot medium and whether the selected release supplies a graphical image |
| Milk-V Mars | Supported firmware and kernel path, release-specific image and documented peripheral limitations |
| Pine64 Star64 | Variant listed by Canonical, boot procedure and display support for the intended desktop |
| SiFive HiFive Unmatched | Release image, storage and graphics requirements, plus any limitations in the board guide |
| StarFive VisionFive family | Exact model or revision rather than the family name alone, because images and limitations can differ |
| QEMU RISC-V | Emulator version, selected CPU profile and the experimental status of Desktop images |
Being named on the index does not mean every Ubuntu release, every board revision or every Desktop flavor is available. Do not infer that a listed board meets the newer RVA23 requirement without checking its specifications and the release-specific image page.
Recommended Free Tools
Is Ubuntu on RISC-V the same as Ubuntu on ARM?
The desktop environment can look familiar because Ubuntu’s shell, package tools and applications are designed to be consistent. Underneath, the kernel, boot firmware, binary packages and hardware enablement are architecture- and board-specific. An Arm64 image cannot be written to a RISC-V board, and a RISC-V image is not a fallback Arm image.
Rank #3
- The ESP32-C3 SUPERMINI is positioned as a high-performance, low-power, cost-effective IoT mini development board, suitable for low-power IoT applications and wireless wearable applications
- It is equipped with a rich set of interfaces, including 11 digital I/Os that can be used as PWM pins and 4 analog I/Os that can be used as ADC pins.
- It supports four serial interfaces, including UART, I2C, and SPI.
- The ESP32-C3 features a 32-bit RISC-V CPU, including an FPU (Floating Point Unit) capable of 32-bit single-precision
- Package: 2PCS ESP32-C3 MINI Development Board ESP32 SuperMini ESP32 C3 WiFi Module
Package and application availability
APT selects repositories and package builds for the architecture reported by the system. Check a running installation with:
uname -m
dpkg --print-architectureAn Arm system normally reports an AArch64 machine name and the arm64 Debian architecture; a RISC-V system reports riscv64. These commands do not certify graphics or board support, but they catch the common mistake of using instructions or packages intended for the other ISA.
Native application coverage can differ because each project must publish a build, maintain dependencies and test hardware-specific behavior. If a required application has no native build, investigate whether the publisher provides source, an architecture-independent package or a supported alternative. Do not assume that an Arm download will work on RISC-V simply because both systems run Ubuntu.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Firmware and peripherals
Arm computers often arrive with a vendor-specific boot chain and device-tree support; RISC-V boards can use different firmware, boot media and peripheral implementations. The Ubuntu board guide is more authoritative than a generic tutorial because it records the expected image, boot method and known limitations for that model.
Rank #4
- ESP32-C6 WiFi 6 microcontroller development board adopts ESP32-C6-WROOM-1-N8 module, which is equipped with RISC-V 32-bit single-core processor, up to 160MHz main frequency, built-in 8MB Flash
- Integrates WiFi 6, Bluetooth 5 and and IEEE 802.15.4 (Zigbee 3.0 and Thread) wireless communication, with superior RF performance
- Integrates rich peripherals including SPI, UART, I2C, I2S, LED PWM, SDIO and other interfaces, compatible with the pinout of ESP32-C6-DevKitC-1-N8 development board, more convenient to use and expand a variety of peripheral modules
- Onboard CH343 and CH334 USB HUB chips, supports USB and UART development at the same time via a USB-C port
- Comes with online examples and tutorials for ESP-IDF development environment
What Canonical says RISC-V changes
Canonical describes RISC-V as “an open standard instruction set architecture (ISA)” in its RISC-V explainer. The standard is open, but that does not mean every RISC-V processor or board is open-source. Implementations may be open or closed, licensed as intellectual property, or developed internally by a hardware company.
The ISA is extensible: optional instruction sets and profiles let implementers target different classes of device. Profiles such as RVA23 group required features to make compatibility easier to manage. Canonical states that Ubuntu has supported RISC-V since 2021 and explains that partner-built hardware may need a qualified, board-specific Ubuntu image.
This design changes how you evaluate a purchase. With a familiar Arm computer, the product name may be enough to locate a broad community of images; with RISC-V, the exact CPU profile, firmware and board revision are especially important. Openness alone does not establish a performance, efficiency, security, price or application-parity advantage over Arm.
How to check compatibility before installing
- Choose the Ubuntu release first. Record the exact version and flavor, including whether you need an LTS release or a current interim release. Read its RISC-V architecture requirements before selecting hardware.
- Identify the processor profile. Find the board’s CPU and ISA-profile specification. For newer releases, look for the required RVA23 or RVA23S64 capability rather than relying on the phrase “64-bit RISC-V.”
- Open Canonical’s board entry. Use the supported-board index, select the exact model and revision, and read the image, installation and limitation sections.
- Confirm the image type. Distinguish Server, minimal and Desktop images. A board page may support Ubuntu without offering a supported GNOME desktop image.
- Check the boot path. Verify required firmware, bootloader settings, storage media and console or display connections. A correct ISO cannot compensate for an unsupported boot chain.
- Check graphics and input. Look for documented display output, GPU or framebuffer support, keyboard, mouse and networking requirements. Treat “boots to a shell” as a different result from “usable desktop.”
- Plan a recovery path. Keep the board’s known-good image and firmware instructions available so you can return to the documented release if an upgrade fails.
Installing Ubuntu on a physical RISC-V board
Use the board-specific procedure rather than a generic PC tutorial. A typical supported workflow is:
Best Value
- Ample PSRAM Storage – The development board offers 8MB PSRAM, providing substantial extra memory for handling more complex tasks, large data buffers, and advanced processing.
- Enhanced Multi-Tasking Capability – With the additional 8MB PSRAM, the ESP32-C5-WIFI6-KIT can efficiently manage multiple protocol stacks simultaneously, ensuring smooth operation in multi-tasking IoT environments.
- Support for Medium-Load Applications – The 8MB PSRAM allows the ESP32-C5 to handle medium-load applications more effectively, making it ideal for scenarios requiring real-time data processing or continuous communication.
- Seamless Performance – The increased memory improves the overall performance and responsiveness of the device, particularly when running applications with larger memory footprints or more demanding computations.
- Future-Proof for Complex Projects – With 8MB of PSRAM, developers are better equipped to build scalable, high-performance solutions that support both current and future IoT use cases, offering flexibility for future-proofing designs.
- Download the image linked from the board’s Canonical documentation for the release you selected.
- Prepare the documented boot medium and firmware. Follow the board page’s partitioning and bootloader instructions exactly; RISC-V boards do not share one universal method.
- Connect the console or display path specified by the guide, then boot and watch for firmware or kernel errors.
- Complete the installer or first-boot configuration, including storage, networking and user creation.
- After boot, verify the architecture with
uname -manddpkg --print-architecture, then apply updates from the repository for that release. - Test the hardware you actually need: display modes, acceleration, suspend, audio, networking, USB and storage. Record failures before treating the system as a daily desktop.
If a board guide documents only a server image, installing a desktop metapackage may produce an unsupported combination. Read the stated limitations first and decide whether experimentation is acceptable for your use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Testing Ubuntu RISC-V Desktop in QEMU
Canonical provides a QEMU RISC-V installation guide, but its Desktop section is explicitly experimental and says the images are “in no way supported.” The guide reports that GNOME can take more than 30 minutes to load under its emulated configuration and suggests a Xubuntu Minimal image with XFCE as a more suitable test.
That warning is about GNOME startup in QEMU, not a benchmark of physical RISC-V hardware and not a comparison with an Arm computer. For Ubuntu 25.10 and later, the guide requires QEMU 10.1 or newer to emulate the rva23s64 CPU profile. Earlier QEMU versions can run Ubuntu 25.04 and earlier without that CPU option.
A sensible QEMU test plan
- Install a QEMU version meeting the requirement for the Ubuntu release and CPU profile you intend to test.
- Obtain the RISC-V image referenced by the Ubuntu release or QEMU guide, not an Arm64 image.
- Start with the documented server or minimal configuration to validate boot, storage and networking.
- If you need a graphical test, use the guide’s experimental Desktop instructions and allow for very slow startup under emulation.
- Evaluate package installation and application behavior as a compatibility exercise, not as evidence of physical-device speed, battery life or graphics performance.
Performance, graphics, power and app parity
The official material does not provide a matched Ubuntu Desktop benchmark comparing Arm64 and RISC-V systems. It therefore cannot support a claim that one ISA is faster, slower, more efficient, cheaper or better for battery life. CPU implementation, clocking, memory, storage, GPU drivers, cooling and firmware can dominate the result.
Graphics are particularly board-dependent. The ISA defines how software instructions are encoded; it does not specify a complete display controller or a polished Linux graphics stack for every product. Compare two named devices only when you have comparable tests and documented driver support for the same Ubuntu release and desktop workload.
Application parity also changes over time. Check the architecture of every critical tool, browser, development environment or proprietary client before committing to a RISC-V desktop. A board that is excellent for kernel work or firmware development may not meet a requirement for commercial desktop software.
Choosing between Arm64 and RISC-V
| Your priority | More defensible starting point | Why |
|---|---|---|
| A predictable, supported everyday desktop | An Arm64 computer with a documented Ubuntu image | The Arm64 baseline is established, while RISC-V desktop support varies sharply by board and release |
| Learning ISA design, firmware or board bring-up | A RISC-V development board listed by Canonical | The open standard and profile model make the platform useful for experimentation, provided the board guide is followed |
| Testing Ubuntu’s future RISC-V software stack | QEMU or a board whose exact image is documented | You can isolate userspace compatibility, but QEMU Desktop remains unsupported and slow |
| Reusing an older RISC-V board | The release whose profile floor the board meets | Newer releases may require a profile the board does not implement; verify before upgrading |
| Maximum application choice | Whichever architecture has native builds for your required applications | Package availability is determined per application, not by Ubuntu’s desktop appearance |
Common mistakes and how to avoid them
- “It is 64-bit, so any 64-bit Ubuntu image should work.” Arm64 and riscv64 are different targets, and RISC-V releases impose profile floors. Download the architecture and release-specific image.
- “The board is on the supported list, so GNOME is supported.” Board entries can describe server, minimal or community-supported paths. Confirm the exact Desktop image and limitations.
- “QEMU’s slow GNOME startup proves RISC-V is slow.” The documented 30-plus-minute startup is an emulation-specific caution, not a physical hardware benchmark.
- “RISC-V is open, so every chip is open-source.” The ISA standard is open; implementations can still be proprietary or licensed.
- “A release upgrade is harmless if the old release booted.” Check the new release’s RISC-V profile requirement and the board’s image status before upgrading.
- “A generic PC installation guide is enough.” Follow the board page for firmware, boot media, console, display and known limitations.
The practical verdict
Arm64 and RISC-V provide Ubuntu with two distinct binary targets, not two interchangeable names for the same desktop. Arm64 offers a documented ARMv8-A compatibility floor. RISC-V adds release-dependent RVA20 or RVA23 requirements and a stronger need to match the exact board, firmware and image. Ubuntu Desktop on RISC-V is realistic for carefully selected hardware and for experimentation, while Canonical’s QEMU Desktop path remains unsupported. For an everyday machine, decide from the board’s current release documentation and application requirements; for development and platform exploration, RISC-V can be compelling when those checks pass.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
