sven-ola

Hi @NHO, copy the Armbian kernel and boot with this: yes probably. You will also need the correct *.dtb in /boot - you need to rename / replace k1*.dtb->x1*.dtb e.g. if you run the original uboot. The GPU probably does not work, since Mesa does / will not support the K1 imagination GPU. You need the Bianbu GPU binaries and userspace tools (...wayland...) that matches them. The spacemit-gpu-addon.sh script (see green [solution] button on top of this page) uses a copied / stripped down version of the Bianbu Repo to install Gnome/Wayland but I doubt that this works under Gentoo Linux.

@rm_ you have a capable platform at hand, why not build edge on your RV2? No docker b/c this is riscv64, but this should work anyhow: git clone https://github.com/armbian/build.git cd build && ./compile.sh BOARD=orangepirv2 BRANCH=edge RELEASE=trixie \ BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_BTF=no KERNEL_GIT=shallow Mine is running, but AFAICR this is under 4h. You may want to place board upright for better ventilation 😉

@c0rnelius thanks for the u-boot-only image. May help to sort things out. Also, the Armbian.com download pages now have downloadable RV2 and R2S images, so I can stop uploading my locally build ones. I grabbed a second NVME and placed it in the RV2 lower 2280 M.2 slot, while my upper 2230 M.2 slot concurrently holds another NVME. There is a minor quirks between U-Boot and Kernel: U-Boot output shows PCIE-0: Link up (Gen2-x2, Bus0) and PCIE-2: Link up (Gen2-x2, Bus2). U-Boot identifies 2280 as Device 0, and 2230 as Device 1. Linux swapped to 2230=/dev/nvme0n1 and 2280=/dev/nvme1n1. Both NVMEs are bootable, i.e the 2280 is booted if present, if not RV2 boots from 2230. A stopped U-Boot shows the following info => nvme info Device 0: Vendor: 0x144d Rev: 1B7QCXE7 Prod: S3EUNX0HB05786X [ 6.900] Type: Hard Disk [ 6.903] Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) [ 6.910] Device 1: Vendor: 0x144d Rev: HPS4NHBV Prod: S774NX0XB34550 [ 6.917] Type: Hard Disk [ 6.920] Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) while the Linux kernel has this: root@orangepirv2:~# df -h / Filesystem Size Used Avail Use% Mounted on /dev/nvme1n1p1 455G 1.7G 448G 1% / root@orangepirv2:~# lspci 0001:00:00.0 PCI bridge: SpacemiT X60 PCIe 2.0 x2 Root Complex (rev 01) 0001:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 0002:00:00.0 PCI bridge: SpacemiT X60 PCIe 2.0 x2 Root Complex (rev 01) 0002:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less) (rev 02) root@orangepirv2:~# hdparm -t /dev/nvme?n1 /dev/nvme0n1: Timing buffered disk reads: 1446 MB in 3.01 seconds = 480.91 MB/sec /dev/nvme1n1: Timing buffered disk reads: 1760 MB in 3.00 seconds = 585.89 MB/sec HTH // Sven-Ola

@rm_ No, SD and NVME are working with Armbian edge 7.1, while USB does not. root@orangepirv2:~# uname -a Linux orangepirv2 7.1.0-rc3-edge-spacemit #3 SMP PREEMPT_DYNAMIC Sun May 10 21:08:09 UTC 2026 riscv64 GNU/Linux root@orangepirv2:~# blkid /dev/nvme0n1p1: LABEL="armbi_root" UUID="fdbd4ab2-2238-4a62-a079-74ff0582c8d2" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="00406d4f-01" /dev/mmcblk0p1: LABEL="armbi_root" UUID="63ee7593-e111-4547-ac2f-6bdb8519ce11" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9ebf8299-01" /dev/zram0: UUID="3be872bc-b408-46c3-8ec9-d27500adc1dd" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="bace3aba-15ea-4833-a7ad-f7d9e39aa0c5" BLOCK_SIZE="4096" TYPE="ext4" root@orangepirv2:~# lsusb root@orangepirv2:~# lspci 0001:00:00.0 PCI bridge: SpacemiT X60 PCIe 2.0 x2 Root Complex (rev 01) 0002:00:00.0 PCI bridge: SpacemiT X60 PCIe 2.0 x2 Root Complex (rev 01) 0002:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less) (rev 02) Anyhow, thanks for the Phoronix link // Sven-Ola

Hi @armfan. From what I am able to extract from the flood of braindumps you have a non-working NVME with 2TB that is not working for some reason. If it really stops sometimes in the middle of u-boot::nvme::init then you may have some power issue with this NVME. For comparison: I placed my NVME in the lower m.2 and booted via MTD the u-boot armbian-installed from the "current" image downloadable from my site. See attached capture file. HTH // Sven-Ola nvme-lower-uboot-may-26-2026.cap

Hello @4A studio. The armbian-config tool may change large parts of the system configuration without a real "undo". I am not sure if I understand your situation correct: Board does not boot. You see UART output but no UART login prompt? Board is booting. But you don't see a live picture on your HDMI monitor?

Hey @armfan. UUID=63ee7593-e111-4547-ac2f-6bdb8519ce11 was read from /boot/extlinux/extlinux.conf which is correct for the edge/7.1.0rc3 image. However, something must be wrong with your SD card if u-boot can read UUID from extlinux.conf, but kernel does not find corresponding file system on the same boot media. This is the expected kernel startup : [ 0.000000] Booting Linux on hartid 0 [ 0.000000] Linux version 7.1.0-rc3-edge-spacemit (build@armbian) (riscv64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU l [ 0.000000] Machine model: OrangePi RV2 [ 0.000000] SBI specification v1.0 detected [ 0.000000] SBI implementation ID=0x1 Version=0x10003 [ 0.000000] SBI IPI extension detected [ 0.000000] SBI RFENCE extension detected [ 0.000000] earlycon: sbi0 at I/O port 0x0 (options '') [ 0.000000] printk: legacy bootconsole [sbi0] enabled Loading, please wait... Starting systemd-udevd version 257.13-1~deb13u1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. HTH // Sven-Ola

While I am here: I have a Mediatek Tri-Band Wifi card installed in my RV2 (label reads MT7922A22M). There's a matching driver in OpenWrt created by Felix and friends. This will take some time until pushed upstream. So, why not make it a DKMS module? That's how things started 🤪 # Grab bleeding edge Wifi from OpenWrt cd /usr/src git clone https://github.com/openwrt/mt76.git mt76-6.18 cd mt76-6.18 # Source code massage (needs OpenWrt kernel patch, missing include) git revert 9a46d8d2 sed '/^#include <linux\/kernel.h>/i#include <linux/version.h>' mt76.h # New DKMS config (with more than one module) cat > dkms.conf << "EOF" PACKAGE_NAME="mt76" PACKAGE_VERSION="6.18" BUILT_MODULE_NAME[0]="mt76" DEST_MODULE_LOCATION[0]="/updates/dkms" BUILT_MODULE_NAME[1]="mt76-connac-lib" DEST_MODULE_LOCATION[1]="/updates/dkms" BUILT_MODULE_NAME[2]="mt792x-lib" DEST_MODULE_LOCATION[2]="/updates/dkms" BUILT_MODULE_NAME[3]="mt7921e" BUILT_MODULE_LOCATION[3]="mt7921" DEST_MODULE_LOCATION[3]="/updates/dkms" BUILT_MODULE_NAME[4]="mt7921-common" BUILT_MODULE_LOCATION[4]="mt7921" DEST_MODULE_LOCATION[4]="/updates/dkms" AUTOINSTALL="yes" MAKE="make -C ${kernel_source_dir} M=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build CONFIG_WLAN_VENDOR_MEDIATEK=y CONFIG_MT76_CORE=m CONFIG_MT76_LEDS=y CONFIG_MT76_CONNAC_LIB=m CONFIG_MT792x_LIB=m CONFIG_MT7921_COMMON=m CONFIG_MT7921E=m " EOF # Add, build, install, and add matching firmware dkms add -m mt76 -v 6.18 dkms build -m mt76 -v 6.18 dkms install -m mt76 -v 6.18 cp -av firmware/ /lib/firmware/updates/mediatek # Give it a try reboot

Hello @mBesar, while I can build images with additional kernel modules, the next "apt-get upgrade" may install a newer kernel that discards such additions. Why not build this on your own? There is already a working DKMS build system on the board for the bcmdhd wifi module. On the next kernel update, DKMS will recompile bcmdhd.ko for the new kernel automatically. Sadly, when I tried this for b2c2-flexcop-usb, it was not too easy to do. Armbian does not provide kernel sources with "apt-source", and the mentioned module itself uses an additional "-i include-dir" during build. So as an example, try to do this on your board: As root: # Change two times "Types: deb deb-src" nano /etc/apt/sources.list.d/debian.sources # Check for avail linux image packages, this time 6.18.5-deb13-parisc apt-get update grep linux-image /var/lib/apt/lists/*Sources|grep 6\\.18|less -S # We are not interested in this image, we just need some source code cd /usr/src apt-get source linux-image-6.18.5+deb13-parisc # Add a new DKMS module (dkms already here b/c bcmdhd wifi driver) mkdir /usr/src/b2c2-flexcop-usb-6.18 cd /usr/src/b2c2-flexcop-usb-6.18 cat > dkms.conf << "EOF" PACKAGE_NAME="b2c2-flexcop-usb" PACKAGE_VERSION="6.18" BUILT_MODULE_NAME[0]="b2c2-flexcop-usb" DEST_MODULE_LOCATION[0]="/updates/dkms" AUTOINSTALL="yes" MAKE="make -C ${kernel_source_dir} M=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build CONFIG_DVB_B2C2_FLEXCOP_USB=m" EOF # What subsys do we need? Says: drivers/media/usb/b2c2, then grab that dir grep DVB_B2C2_FLEXCOP_USB $(find /usr/src/linux-6.18.5 -name Kconfig*) cp -av /usr/src/linux-6.18.5/drivers/media/usb/b2c2/. . # The module Makefile uses an additional include dir. We simply copy them here cp -av /usr/src/linux-6.18.5/drivers/media/common/b2c2/*.h . # Register, build, and install dkms add -m b2c2-flexcop-usb -v 6.18 dkms build -m b2c2-flexcop-usb -v 6.18 dkms install -m b2c2-flexcop-usb -v 6.18 HTH // Sven-Ola

Hi @JamesCL. You cannot change the boot order of the SoC (SD -> eMMC -> MTD / SPI flash), thus i.e. the SD card is always booted if inserted. You can probably change the root file system's UUID, i.e. change the /boot/extlinux/extlinux.conf to give the kernel the command to use eMMC as root file system. HTH // Sven-Ola

@armfan you start mixing instructions from Xunlong, SpacemiT, and Armbian. That will not work probably. The SoC is able to boot from SD, eMMC, and MTD (in that order). With Armbian started, you can use armbian-install to write u-boot to MTD (which is Memory Technology Device aka the kernel device for SPI flash and other flash mem). That Armbian u-boot is able to indirectly boot from NVME. Or via USB but only with manual u-boot commands you can type into the UART console, see discussion on OpiR2S booting in this thread.

Hi @armfan, you can simply change the append root=UUID=(some uuid) in /boot/extlinux/extlinux.conf to suit your needs.

@Curvy Android Try something like fdtoverlays /boot/dtb/spacemit/overlay/k1-uart9.dtbo, this should trigger some u-boot message like: [ 5.621] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 5.672] Retrieving file: /boot/dtb/spacemit/overlay/k1-uart9.dtbo HTH // Sven-Ola

Hi @rm_, I tried my RV2 with current kernel and disabled bcmdhd. For reference, I have uploaded the image to https://privat-in.de under "Downloads". Prevented bcmdhd.ko from loading. There is no such load. I don't think that waiting a couple of hours will change that. Also, I have zero IPI4 irqs, thus you may need to locate the interrupt source, e.g. with lspci and lsusb. Maybe you changed something in the kernel cfg, please compare attached cfg to your /proc/config.gz). HTH // Sven-Ola config.gz

@rm_ On my RV2, there's no such load. Mine waits at the GDM3 login screen (Wayland), it's booted via NVME, no Wifi nor BT configured, and I have a shell via Ethernet. I see a difference in IPI4 dubbed "IRQ work interrupts" which may cause this but I have no clue about the real root cause. There's a patch with comments on that: https://patchew.org/linux/25833c44051f02ea2fd95309652628e2b1607a1e.camel@lenze.com/ , however I have not investigated which of the patches / corrections are in the actual 6.18.26-current-spacemit. I have 53/57° C temp with cat $(find /sys -name temp), I presume yours is higher... interrupts