JamesCL

@AurealNix Ready nvme:

@AurealNixThank you, excellent work... boot from eMMC All that's missing is adding support for NVMe

Hi, I'm testing your Linux image on an Orange Pi 4B/4A with an eMMC installed and wanted to share the results. The image correctly detects the eMMC. The kernel recognizes the device as: mmcblk2: mmc2:0001 ISOCOM 58.3 GiB Operating mode: HS200 image : aurealnix-opi4a-debian13-cli-v0.2.img.xz @AurealNix Thank you for your work. Update: During boot, the kernel reports two reserved-memory warnings: OF: reserved mem: Reserved memory: failed to reserve memory for node 'sec-sram1@42350000' OF: reserved mem: Reserved memory: failed to reserve memory for node 'sec-sram2@43000000' The system remains fully functional. OP-TEE and BL31 reserved-memory nodes are present in the device tree, and eMMC HS200 operation has been tested successfully. root@orangepi-4a:~# uname -a Linux orangepi-4a 6.18.38-g59eb61929e89 #49 SMP PREEMPT Thu Jul 16 00:46:12 CEST 2026 aarch64 GNU/Linux root@orangepi-4a:~# free -m total used free shared buff/cache available Mem: 3830 330 95 9 3592 3500 Swap: 0 0 0 root@orangepi-4a:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.6 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@orangepi-4a:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 7.4G 0 disk └─mmcblk0p1 179:1 0 7.4G 0 part / mmcblk2 179:32 0 58.3G 0 disk ├─mmcblk2p1 179:33 0 1.2G 0 part └─mmcblk2p2 179:34 0 57.1G 0 part /mnt/emmc-test mmcblk2boot0 179:64 0 4M 1 disk mmcblk2boot1 179:96 0 4M 1 disk root@orangepi-4a:~# fastfetch _,met$$$$$gg. root@orangepi-4a ,g$$$$$$$$$$$$$$$P. ---------------- ,g$$P"" """Y$$.". OS: Debian GNU/Linux 13 (trixie) aarch64 ,$$P' `$$$. Host: OrangePi 4A ',$$P ,ggs. `$$b: Kernel: Linux 6.18.38-g59eb61929e89 `d$$' ,$P"' . $$$ Uptime: 38 mins $$P d$' , $$P Packages: 299 (dpkg) $$: $$. - ,d$$' Shell: bash 5.2.37 $$; Y$b._ _,d$P' Terminal: /dev/pts/2 Y$$. `.`"Y$$$$P"' CPU: sun55i-t527 (8) @ 1.80 GHz `$$b "-.__ GPU: Allwinner sun55i-a523-mali [Integrated] `Y$$b Memory: 331.41 MiB / 3.74 GiB (9%) `Y$$. Swap: Disabled `$$b. Disk (/): 744.36 MiB / 7.19 GiB (10%) - ext4 `Y$$b. Disk (/mnt/emmc-test): 24.49 GiB / 55.91 GiB (44%) - ext4 `"Y$b._ Local IP (eth0): 192.168.7.12/27 `"""" Locale: en_US.UTF-8 root@orangepi-4a:~#

Is it possible to change the boot order? For my use case, I would like the boot priority to be: eMMC, NVMe, and microSD card. Can this be configured?

@Evgeniy evotronik When I switch from 1 Gbps to 100 Mbps... Ethernet returns to normal.

The eMMC is still not detected. Kernel log: [ 4.621568] mmc2: error -110 whilst initialising MMC card [ 4.627066] mmc2: Failed to initialize a non-removable card Working devices: [ 4.502846] mmc0: new high speed SDXC card at address aaaa [ 4.508907] mmcblk0: mmc0:aaaa SC64G 59.5 GiB [ 4.551951] mmc1: new high speed SDIO card at address 0001 The system boots correctly from the SD card, but the onboard eMMC (mmc2) is not initialized. There are also still Ethernet issues. After connecting through PuTTY, the system sometimes hangs when running dmesg, and the network connection becomes unstable or unresponsive. System information: Thanks

Hi ... Thanks @Evgeniy evotronik. Yesterday I downloaded the image "Armbian_community_26.2.0-trunk.886_Orangepi-4a_trixie_edge_7.0.5_minimal.img.xz", but the Ethernet and eMMC issues are still present. I will apply the Ethernet patch. Thanks again.

I just created a new image and am reporting the following: - On the first boot, I don't have Ethernet (I don't use wireless) and - The eMMC is not detected. Thanks

I am having issues with eMMC detection… The kernel does not detect the eMMC, but apparently U-Boot does. Attached are images.

Hi @sven-ola I downloaded this version, "Armbian-unofficial_26.02.0-trunk_Orangepirv2_trixie_current_6.6.99_minimal.img", and it's working on an SD card without problems... Is it possible for the OPI RV2 to boot from the eMMC with this image? Thanks.

Thanks for your work, @sven-ola. I'm going to try your image. I only need Ethernet (no sound, no wireless, no Bluetooth, and definitely no HDMI). Cheers!

Thanks @JuanEsf

@Ángel Luis Pérez You don't have to apologize because the type of image was very clear in the post where you reported it... it's just a matter of reading 🙂

@Nick AI made the change, but there were no changes in the log

@JuanEsf Ok, I'll try again, connect everything and let you know... Thanks for your work 🙂

@JuanEsf Have this : it gets stuck there : U-Boot 2025.01-armbian-2025.01-S2ebd-Pe2be-H8869-V77e1-Bb703-R448a+ (Feb 24 2025 - 23:31:20 -0300) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: OrangePi 4A DRAM: 4 GiB sunxi_set_gate: (CLK#32) unhandled Core: 52 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 5 ms (906.3 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 156 bytes read in 3 ms (50.8 KiB/s) Load fdt: /boot/dtb/allwinner/sun55i-t527-orangepi-4a.dtb 17256 bytes read in 13 ms (1.3 MiB/s) Working FDT set to 4fa00000 Failed to load '/boot/dtb/allwinner/overlay/sun55i-t527-fixup.scr' 8116855 bytes read in 2781 ms (2.8 MiB/s) 42523136 bytes read in 14555 ms (2.8 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42b40000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8116791 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 49842000, end 49fffa37 ... OK Loading Device Tree to 00000000497d5000, end 0000000049841fff ... OK Working FDT set to 497d5000 Starting kernel ...

@JuanEsf Thanks for the image, I'm going to try it on my opi 4a and I'll let you know. Regards

Is there any armbian image that we can try with the Orange pi 4A ? Many thanks

In my case, my opi5 never worked no matter how many armbian versions I changed. I was disappointed with the SBC and left it lying around for many months... until one day I tried the "trunk" and error... error of versions, one after another... and suddenly I found a particular version... "24.5.0-trunk.276" and it has been working for months without problems... until now... This versión work fine for me: Armbian_24.5.0-trunk.276_Orangepi5_trixie_edge_6.8.1_minimal.img.tar.gz root@orangepi5:~# dpkg -l | grep '^h' hi armbian-bsp-cli-orangepi5-edge 24.11.0-trunk.204 arm64 Armbian CLI BSP for board 'orangepi5' branch 'edge' hi armbian-firmware 24.5.0-trunk.276 all Armbian - Linux firmware hi linux-dtb-edge-rockchip-rk3588 24.5.0-trunk.276 arm64 Armbian Linux edge DTBs in /boot/dtb-6.8.1-edge-rockchip-rk3588 hi linux-image-edge-rockchip-rk3588 24.5.0-trunk.276 arm64 Armbian Linux edge kernel image 6.8.1-edge-rockchip-rk3588 hi linux-u-boot-orangepi5-edge 24.5.0-trunk.276 arm64 Das U-Boot for orangepi5 root@orangepi5:~# apt-mark showhold armbian-bsp-cli-orangepi5-edge armbian-firmware linux-dtb-edge-rockchip-rk3588 linux-image-edge-rockchip-rk3588 linux-u-boot-orangepi5-edge

Hi, in my case... after many problems, I decided to use only nvme on my opi5. Regards cat /proc/cmdline root=UUID=f43263a1-3f44-43aa-bb0b-415ba559deab rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 uname -a Linux orangepi5 6.8.1-edge-rockchip-rk3588 #4 SMP PREEMPT Fri Mar 15 18:19:29 UTC 2024 aarch64 GNU/Linux

for some strange reason the content of armbianEnv.txt (rootdev) is not applied in my opi5, if anyone can help me. Thank !!!

After applying the following changes I was able to obtain the temperatures in my OPI5. https://github.com/htop-dev/htop/pull/1411/files#diff-cd34c934b018d562cd6c276738f8e4ff18638bff20de91ef057e83a425dd68a1 Thank

Hello, I am trying to create a custom uboot using armbian. it's possible? I am using the following command but I cannot generate the "uboot.bin" to save it to the spi: ./compile.sh uboot-config BOARD=orangepi5 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes BUILD_ONLY=u-boot CONFIGURATION=stable KERNEL_CONFIGURE=no KERNEL_ONLY=no PROGRESS_DISPLAY=plain RELEASE=bookworm UBOOT_ONLY=yes Thank.

@Efe Çetin: thank ... now I'm closer uboot recognizes the disk armbian recognizes it, but after a few seconds it disconnects. (the disk is new and I have no problems connecting it to another computer) I attach more information: root@orangepi5:~# dmesg | grep ata [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] Memory: 7453648K/8124416K available (17920K kernel code, 2860K rwdata, 6808K rodata, 5056K init, 755K bss, 277552K reserved, 393216K cma-reserved) [ 0.020108] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [ 0.575618] libata version 3.00 loaded. [ 0.654348] ahci-dwc fe210000.sata: supply ahci not found, using dummy regulator [ 0.654403] ahci-dwc fe210000.sata: supply phy not found, using dummy regulator [ 0.654587] platform fe210000.sata:sata-port@0: supply target not found, using dummy regulator [ 0.654686] ahci-dwc fe210000.sata: PMPn is limited up to 5 ports [ 0.654725] ahci-dwc fe210000.sata: masking port_map 0x1 -> 0x1 [ 0.654736] ahci-dwc fe210000.sata: SSS flag set, parallel bus scan disabled [ 0.654744] ahci-dwc fe210000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode [ 0.654750] ahci-dwc fe210000.sata: flags: ncq sntf stag pm led clo only pmp fbs pio slum part ccc apst [ 0.654760] ahci-dwc fe210000.sata: port 0 is not capable of FBS [ 0.655531] ata1: SATA max UDMA/133 mmio [mem 0xfe210000-0xfe210fff] port 0x100 irq 42 lpm-pol 0 [ 1.124014] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.126188] ata1.00: ATA-11: NT-512 2242, SN14546, max UDMA/133 [ 1.126199] ata1.00: 1000215216 sectors, multi 1: LBA48 NCQ (depth 32) [ 1.128687] ata1.00: configured for UDMA/133 [ 1.872260] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 84,32 bit host data width,256 deep fifo [ 3.537156] EXT4-fs (sdb2): mounted filesystem f43263a1-3f44-43aa-bb0b-415ba559deab ro with writeback data mode. Quota mode: none. [ 5.099156] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). [ 5.761788] systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). [ 32.804419] ata1: SATA link down (SStatus 0 SControl 300) [ 38.139094] ata1: SATA link down (SStatus 0 SControl 300) [ 38.139120] ata1: limiting SATA link speed to <unknown> [ 43.472494] ata1: SATA link down (SStatus 0 SControl 330) [ 43.472521] ata1.00: disable device [ 43.472588] ata1.00: detaching (SCSI 0:0:0:0) root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdb 8:16 1 29.7G 0 disk ├─sdb1 8:17 1 256M 0 part /boot └─sdb2 8:18 1 29.2G 0 part /var/log.hdd / mtdblock0 31:0 0 16M 0 disk zram0 251:0 0 3.8G 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log zram2 251:2 0 0B 0 disk root@orangepi5:~#