RISC-V single-board computer for less than 40 euros

Performance and Use Cases

  • Disagreement on speed: some say the board feels “unbearably slow,” others argue raw CPU is closer to a Pi 4 than Pi 3 for non-SIMD workloads.
  • SIMD (Neon) absence and immature software stack are noted as main performance drawbacks vs ARM.
  • Extra RAM (2–8 GB vs Pi 3’s 512 MB–1 GB) and NVMe via M.2 are highlighted as major practical advantages for builds, dev work, and general usability.
  • Consensus that neither current RISC‑V SBCs nor Raspberry Pis are great full‑time desktops; cheap used x86/Macs are often recommended instead.

Storage Choices and SD Endurance

  • NVMe is praised but some argue SD cards are sufficient for light CLI/dev use, especially with ample RAM caching.
  • Concerns about SD wear are countered with back‑of‑envelope calculations suggesting very high build counts before failure for large cards.

Software, ISA, and Distro Support

  • JH7110’s lack of RVA23 compliance raises future‑compatibility worries, especially with Ubuntu’s decision to target RVA23.
  • Debate over Ubuntu’s stance: some call it premature and exclusionary; others see it as necessary to push vendors toward robust, modern RISC‑V implementations.
  • Fedora and Debian are cited as better fits for current non‑RVA23 hardware.
  • One commenter states that “basically everything works” Linux‑wise, though others fear untested riscv64 paths and subtle bugs.

Ecosystem, Alternatives, and Positioning

  • Orange Pi RV2 is recommended as faster with better software support than this board.
  • Other cheap RISC‑V options (Milk‑V Duo, Banana Pi F3, Pico‑class MCUs) are mentioned, stressing differences between microcontrollers and full SBCs.
  • Discussion on why competitive high‑end RISC‑V cores are rare: integration effort, risk aversion, and the fact that “people buy solutions, not ISAs.”

Hardware Design and Security

  • M.2 (single PCIe lane) is appreciated; lack of full PCIe slots is attributed to signal‑integrity, PCB cost, and validation complexity.
  • Some want boards without onboard flash/wireless for offline security uses.
  • Concerns raised about hidden binary blobs, especially for GPU (IMG BXE) firmware, limiting hobby OS and security‑focused work.

GDPR, Cookie UI, and Ads

  • Thread extensively criticizes the site’s cookie banner: full‑screen, “accept all” prominent, no easy “reject all.”
  • Some argue this violates GDPR guidance requiring symmetric consent options; others say users can just close the tab.
  • Broader frustration with “malicious compliance” cookie UIs and surveillance‑driven ad models; several suggest privacy‑friendly defaults or contextual (non‑tracking) ads instead.