What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Ubuntu Desktop on Arm and RISC-V is not the same installation moved between two chip families. Ubuntu publishes separate arm64 and riscv64 architectures, with different instruction-set baselines, board images, firmware requirements, and desktop-support status. Arm64 has a documented ARMv8-A baseline. RISC-V used the RVA20 profile through Ubuntu 25.04 and moves to RVA23 from Ubuntu 25.10 onward. Before installing, match the exact board revision, Ubuntu release, image type, and supported boot path; a CPU that meets an ISA profile is not automatically a supported desktop computer.
What is the difference between Ubuntu on ARM and RISC-V?
Arm and RISC-V are different instruction-set architectures (ISAs), the contracts that define which machine instructions a processor understands. Ubuntu therefore builds different packages and images for each one. Canonical labels the 64-bit Arm architecture arm64 (also called ARM64, ARMv8, or AArch64) and the 64-bit RISC-V architecture riscv64. A binary compiled for one architecture is not a drop-in binary for the other.
As an Amazon Associate I earn from qualifying purchases.
The practical difference is broader than the instruction names. A desktop installation also depends on a board’s firmware, bootloader, graphics device, kernel support, memory, storage, and the Ubuntu image that Canonical or a board community has prepared. Two boards using the same ISA can consequently provide very different Ubuntu experiences.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| Question | Arm64 | Riscv64 |
|---|---|---|
| Ubuntu architecture label | arm64 / AArch64 |
riscv64 |
| Documented compatibility floor | ARMv8-A, with no optional extensions required; VFPv4 and NEON are assumed | RVA20 for Ubuntu 20.04–25.04; RVA23 for Ubuntu 25.10 and newer |
| Package and image compatibility | Arm64 packages and images | Riscv64 packages and images; Arm64 packages cannot be substituted |
| Hardware choice | Many devices, but support still varies by model and firmware | A smaller, board-specific set documented by Canonical and communities |
| Desktop status in the cited QEMU guide | Not addressed by that guide | Experimental, unsupported Desktop images; GNOME startup can exceed 30 minutes under emulation |
| Comparable performance result | Not established by Canonical’s cited documentation; results require matched hardware tests | |
Canonical’s architecture definitions and release floors are documented in Supported architectures. They describe minimum architectural features, not processor speed, battery life, graphics capability, or application availability.
#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
How the ISA baselines affect Ubuntu releases
Arm64: the ARMv8-A floor
Ubuntu’s documented Arm64 baseline is ARMv8-A without requiring optional extensions. The architecture documentation also assumes VFPv4 floating-point support and NEON SIMD instructions. A particular Arm system can implement newer ARM features, but Ubuntu’s baseline is intended to keep Arm64 binaries compatible across systems that meet those requirements.
RISC-V: RVA20 through 25.04
Ubuntu 20.04 through Ubuntu 25.04 use the RVA20 profile as the documented riscv64 baseline. A board with an older or non-conforming RISC-V implementation may fail to boot a generic image even if it is described informally as “64-bit RISC-V.” Check the processor’s implemented profile rather than relying on the marketing name.
RVA23 from Ubuntu 25.10
Canonical states that Ubuntu 25.10 and later use RVA23. The profile bundles required instruction extensions so software can target a known feature set instead of probing every implementation independently. This is a compatibility rule, not a performance rating.
Ubuntu 26.04 LTS release notes make the requirement more specific: the RISC-V build supports hardware implementing RVA23S64. The same notes say Ubuntu 24.04 LTS continues to support earlier RVA20 cores. The release notes recorded that, in April 2026, no RVA23S64 hardware was available and QEMU was the only supported RISC-V platform at that time. That was a dated statement, not an October 2026 inventory; hardware availability can change, so consult the current board documentation before purchasing or upgrading. See the Ubuntu 26.04 summary for LTS users.
| Ubuntu release | RISC-V profile documented by Canonical | Planning implication |
|---|---|---|
| 20.04 through 25.04 | RVA20 | Older RVA20 boards may remain candidates, subject to board image and support status |
| 25.10 | RVA23 | Verify that the board implements the required RVA23 profile and that a 25.10 image exists |
| 26.04 LTS | RVA23S64 | Check the exact profile and the release’s board/platform support before upgrading |
| 24.04 LTS | Supports earlier RVA20 cores | May be the safer release for an RVA20 board when a supported image is available |
Canonical summarizes the transition as: “Ubuntu 24.04 LTS supports the RVA20 profile while from 25.10 onwards (including 26.04 LTS) we will support RVA23.”
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
Can Ubuntu Desktop run on RISC-V?
Yes, but the answer depends on whether you mean emulation or a particular physical board. Canonical publishes RISC-V images and board instructions, yet its QEMU documentation labels the RISC-V Desktop images experimental and unsupported. That status should not be read as broad official Desktop support for every RISC-V computer.
Running a desktop image in QEMU
The official Install Ubuntu on QEMU (RISC-V) guide includes an “Experimental Desktop images” section. It warns that the images are “in no way supported” and that GNOME can take more than 30 minutes to load in the documented emulated configuration. The guide suggests a Xubuntu Minimal image with the XFCE desktop as a more suitable way to test a graphical environment in emulation.
For Ubuntu 25.10 and newer, the guide requires QEMU 10.1 or later to emulate the rva23s64 CPU option. Earlier QEMU versions can run Ubuntu 25.04 and earlier without that option. Emulation startup time is a property of that QEMU setup; it is not a benchmark of physical RISC-V hardware against Arm.
Using a physical RISC-V board
A physical board can offer a better test environment, but only when Canonical or the board community provides a matching image, boot method, kernel, and hardware workarounds. Even then, “boots Ubuntu” does not necessarily mean “has a supported GNOME Desktop image.” Some boards are intended for server, command-line, or development use.
Which RISC-V boards support Ubuntu?
Canonical’s Ubuntu supported boards index lists RISC-V examples such as:
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
- Allwinner Nezha D1
- Milk-V Mars
- Pine64 Star64
- SiFive HiFive Unmatched
- StarFive VisionFive family
- QEMU as an emulated platform
Each entry is supposed to identify supported variants, available Ubuntu images, installation instructions, and known limitations. Presence on the index does not establish that every Ubuntu release, board revision, or Desktop image is available. Read the individual entry for the exact model and release you intend to use.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCanonical’s broader Ubuntu hardware support documentation explains that non-PC installations, including single-board computers, often need board-specific images and boot procedures. It distinguishes supported and community-supported hardware and records limitations that a generic PC installation guide does not cover.
How to choose an Ubuntu release for an old RISC-V board
An older board may continue to run an older Ubuntu release while failing the profile requirement of a newer one. Use this process before downloading an image:
- Identify the exact board and revision. Record the model, revision or memory variant, processor, and boot media. “VisionFive” or “Star64” alone may cover multiple revisions.
- Confirm the processor profile. Determine whether the CPU implements RVA20 or RVA23/RVA23S64. Do not infer this from the word “RISC-V” on the product page.
- Choose the release deliberately. For a board limited to RVA20, investigate an image based on a release that supports RVA20, such as 24.04 LTS, provided the board page lists it. A 25.10 or 26.04 image may require RVA23.
- Open the board’s Canonical entry. Check the listed image type, installation method, supported storage, bootloader requirements, and known limitations.
- Verify desktop availability. Look for an explicit Desktop image or desktop installation procedure. If only server or minimal images are listed, plan on adding a lightweight desktop only when the board’s graphics stack supports it.
- Check firmware and peripherals. Confirm U-Boot or other firmware requirements, display output, network interface, storage controller, and USB support. Missing drivers can make a nominally compatible installation unusable.
- Keep a recovery path. Have the original image, serial-console access, and a known-good boot medium available before overwriting storage.
This workflow prevents a common mistake: treating the ISA profile as a complete hardware compatibility guarantee.
Is Ubuntu on RISC-V the same as Ubuntu on ARM?
The distribution’s package-management model and desktop concepts are familiar, but the binaries, kernel builds, boot images, and hardware enablement are architecture-specific. On an Arm computer you install arm64 packages; on a RISC-V computer you install riscv64 packages. A software vendor must publish a native build for the target architecture or you must use a compatibility layer, interpreter, container, or emulation. Those alternatives can have their own feature and performance limits.
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
Repositories may not contain identical application versions or optional components on both architectures. A package being present for Arm64 does not prove that the same package, plugin, firmware blob, or accelerated multimedia path exists for RISC-V. Check the package’s architecture metadata and the application’s own support statement.
Desktop interface versus hardware integration
GNOME, KDE Plasma, XFCE, and other desktops can look familiar across architectures because the user interface is largely shared. The difficult parts are below the shell: GPU acceleration, display drivers, suspend and resume, Wi-Fi firmware, audio, camera support, video codecs, and browser media acceleration. These are properties of the particular board and release, not of the RISC-V name alone.
What RISC-V’s open design does—and does not—tell you
Canonical describes RISC-V as “an open standard instruction set architecture (ISA).” An ISA standard can be implemented by different companies or projects. Implementations may be open or closed, licensed as intellectual property, or developed in-house. Therefore, “RISC-V” does not mean that every processor design, firmware package, or board is open source.
RISC-V is extensible: implementations can include optional instruction sets, while profiles such as RVA20 and RVA23 group required features to make compatibility more predictable. Canonical says Ubuntu has supported RISC-V since 2021 and works with partners on qualified images. Openness and extensibility explain the ecosystem’s structure; they do not establish that RISC-V hardware is faster, cheaper, more efficient, more secure, or better supported than Arm.
Arm64 versus RISC-V: a practical comparison
| Evaluation axis | What to check on Arm64 | What to check on RISC-V |
|---|---|---|
| CPU compatibility | ARMv8-A baseline, plus the board’s actual extensions | RVA20, RVA23, or RVA23S64 requirement for the selected release |
| Ubuntu image | Correct arm64 image for the board or computer | Correct riscv64 image; generic PC media may not boot a board |
| Firmware | UEFI, vendor firmware, or board-specific bootloader | Often board-specific bootloader, device tree, and firmware sequence |
| Graphics | Model-specific GPU driver and acceleration support | Model-specific GPU driver; verify whether acceleration is usable at all |
| Application binaries | Look for arm64 builds | Look for riscv64 builds; availability can differ by application |
| Release upgrades | Usually governed by the board’s image and support lifecycle | Also constrained by changing ISA floors, especially the RVA23 transition |
| Performance and battery life | No matched Arm-versus-RISC-V Ubuntu Desktop result is established in the cited sources; test the exact devices | |
| Support status | Varies by device and vendor | Varies by board; QEMU Desktop images in the cited guide are experimental and unsupported |
Common installation failures and how to diagnose them
The image refuses to boot
First check that the image architecture matches the board: riscv64 for RISC-V or arm64 for 64-bit Arm. Then verify the board revision and boot medium against its Canonical entry. A profile mismatch, wrong device tree, unsupported bootloader, or incorrect storage image can all produce an apparently dead board.
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.
The release requires an instruction profile the CPU lacks
An RVA20 board cannot satisfy an RVA23-only image. Select a release and image whose documented floor matches the processor, or replace the board with one implementing the newer profile. Do not attempt to “fix” an ISA mismatch by changing desktop packages.
The system boots but has no graphical desktop
Determine whether you installed a server or minimal image. If the board page does not list a Desktop image, the absence may be intentional. Check display output, kernel graphics support, and acceleration status before installing a heavier desktop. In QEMU, use the guide’s suggested XFCE-based minimal approach for experimentation rather than assuming GNOME’s slow startup indicates a hardware fault.
GNOME appears frozen in QEMU
The QEMU guide specifically warns that GNOME can take more than 30 minutes to load in its documented emulated setup. Allow for that limitation, inspect the emulator’s CPU option and memory allocation, or switch to the suggested Xubuntu Minimal/XFCE image. This warning does not predict startup time on a physical board.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →A familiar application is missing
Search the package repository for the target architecture and check the application’s upstream release policy. If there is no native RISC-V build, an alternative package or source build may exist, but compatibility and acceleration are application-specific. Avoid assuming an Arm binary will run unchanged.
When is RISC-V suitable for everyday Ubuntu Desktop use?
Good fit: learning and board development
RISC-V is a reasonable choice when your goal is kernel work, firmware development, ISA experimentation, package building, or learning how board bring-up works. The architecture’s profiles and board documentation give you concrete compatibility targets, while serial consoles and board-specific images make low-level debugging possible.
Conditional fit: a lightweight personal desktop
A lightweight desktop may be practical on a physical board with a supported image, working display driver, sufficient memory, and the applications you need. Confirm those items on the exact board page before treating the system as a daily computer. A board listed for Ubuntu does not automatically provide a polished workstation experience.
Safer choice: a mainstream productivity machine
If you require predictable suspend, hardware video decode, proprietary applications, broad peripheral support, and long-tested desktop updates, choose a computer with an explicitly supported Ubuntu Desktop image and verify the device’s hardware support. The ISA label alone cannot provide that assurance, whether the machine is Arm64 or RISC-V.
A pre-install checklist
- Write down the exact board model, revision, RAM size, and storage type.
- Confirm whether the processor meets the selected Ubuntu release’s Arm64 or RISC-V baseline.
- Use the architecture-correct image:
arm64orriscv64. - Read the board’s image, boot, and limitations sections in Canonical’s index.
- Verify whether the image is supported Desktop, server, minimal, community-supported, or experimental.
- Check display, GPU acceleration, networking, audio, and firmware support for the release.
- For QEMU and Ubuntu 25.10 or newer, use QEMU 10.1 or later for
rva23s64emulation. - Keep recovery media and serial-console access available.
- Plan application installation around native architecture packages, not assumptions based on Arm availability.
Bottom line for choosing between Arm64 and RISC-V
Ubuntu on Arm64 and Ubuntu on RISC-V share the Ubuntu userland and release process, but they are separate platform targets. Arm64 uses the ARMv8-A baseline; RISC-V moves from RVA20 to RVA23 beginning with Ubuntu 25.10, with Ubuntu 26.04 requiring RVA23S64 according to its release notes. Select by exact board, release, profile, image, firmware, and driver support. Treat QEMU’s RISC-V Desktop images as experimental, and do not infer speed, battery life, or application parity from ISA openness. For a reliable decision, start with Canonical’s supported-board entry for the hardware you actually plan to use, then verify the release-specific requirements before downloading anything.
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.
