All Activity

u-boot-rockchip-spi.bin is a firmware. Out of pure curiosity, what is the result of 'pci enum' on the firmware console?

There will be no fix if it is not clear what exactly needs to be fixed I would say. I guess you need to dig deeper yourself. You can build U-Boot independent of Armbian if you want, maybe less reading initially, still the testing/debugging is what matters.

I could not get PCIE to work properly on BSP 6.6 on the A7S, but maybe it was my mistake. For SATA over M.2 to work (in case on m.2 SATA drives), the device need to support this electrically, which I'm not sure if A7x boards do. Sent from my SM-S931B using Tapatalk

U-Boot config looks OK to me. Seems that people seen this issue too, wondering if fix is coming.

My initial testing at the Orange Pi RV2 board detected a list of errors, missing features, driver issues and instabilities: . Not able to run Py5 3D geometry on basis of Jogl, JavaFx3D and Py5 API and packages. The error relates due to missing RISC64 architecture support in the Java APIs and will require platform adjustments for additional drivers. There is yet no GPU acceleration available for this board. Issues: . Missing Wacom tablet driver support at opening of the Ubuntu GNOME environment, the Stylus pen was not detected as pointer device. . Instability at the Firefox Web browser when opening of the start screen. . Chrome browser also shows issues with Google page display. My bypass solution is to use the startpage.com as default entry portal. . Slowness and strange blockings when switching the login to GNOME on Xorg. Xorg mode on Ubuntu. It could give support to the xinput setup commands. I appreciate some guidance how to activate those missing features at the Orange Pi RV2 board. Further test reports are welcome.

Yes that is what it seems. But strange that mainline kernel+DTB gets it right and 2026.04 U-Boot not. You need to look into the build-config of this U-Boot for the OP5 then I think. All PCIe NVME needed for boot might be there, but still other factors might determine fail or success. Maybe timing at power on, some power line or other signal not enabled. You could flash https://github.com/edk2-porting/edk2-rk3588 into SPI and see if you can boot mainline based kernel with that with just SPI and NVME. Maybe other things don't work then, but depends on what the board should do. You need to add or already have an extra EFI type FAT formatted partition with that, usually done manually and also installing grub-efi package and installing all that manually. Also you may want to add loglevel=7 to kernel command line, then you see what is happening after 'Starting kernel'

@210518-nick-a, please tell me about AIPU / Zhouyi driver RemoteProc enabled RPMsg support, are those existing in your kernel or should we add them ?

I am trying to enable the VFD display to show the current time. This board came with AiP1628 chip, will be going the posts to make it working. If you got it already working then kindly share the info. 🙂

@davem, I have similar X88 Pro TV box clone which got "X88PRO-RK3566-4D32-V2.1" written on the PCB. I was struggling to boot the system using SD card since the Android image that came with the box was not allowing. Thanks for sharing about the upgrade tool and modified x96x6.dtb. Without your posts I could not made it to work. I got "Armbian_community_26.2.0-trunk.792_Rk3566-box-demo_trixie_current_6.18.24_minimal.img.xz" successfully writte and booted. Later I have installed KDE based Desktop as well on 64GB Micro SD card. My USB 3.0 (the blue one) is somehow not working, Since I have a USB hub its not a deal breaker. Following are working properly as of now. Summary: Bluetooth - Working On Board LAN - 1000Mbps - Working. WiFI - connected to 2.4 Ghz network - Working. HDMI Display - Working. I have not test HDMI audio though. Sound - No 3.5mm Analog jack in this model. However the sound is working via Bluetooth head phone and Speaker with USB input/power. USB 2.0 - Connected Keyboard, mouse and speaker via USB 2.0 Hub - Working. USB 3.0 - This works fine when we boot in Android - Not working. Toss Link - Though the box got a port in the back, I don't have any device that can be connected - Not Tested. Note: I have windows 11 system as my desktop PC. I could not edit the Micro SD card created using BalenaEtcher. I had to use Ubuntu system in order to prepare the SD card and to edit the boot/armbianEnv.txt with fdtfile=rockchip/rk3566-box-X88PRO20.dtb

Generic aarch64 or x86 image has all needed support for most comon virtual environments. On a side we provide cloud images, optimized to run inside KVM / QEMU virtualized environment - super lean kernel. https://armbian.com/boards/uefi-arm64 https://armbian.com/boards/uefi-x86 Look for cloud kernel images. Here it can only be a problem if host (Orangepi) supports qemu or not. I don't run it here but I think it must just work. There won't be any difference compared to standard Debian / Ubuntu. Armbian is more polished in general, comes with several important improvements. Securing support for virtual targets is relatively easy compared to any custom hardware. And this was done long time ago. We use Armbian UEFI and QCOW2 virtual images to drive our infrastructur and also automated testing, but of course we target KVM / Quemu not Virtualbox. Which anyway can run normal image. Our runners and cloud services mainly run Armbian Noble cloud. Our website (dual core x86 vps): www:/boot:% du -h vmlinuz-6.18.10-cloud-x86 15M vmlinuz-6.18.10-cloud-x86 + 17M for modules (normal image has 150-200M for modules, for things you never need in virtualized environment) Yep, that's the best path for this use case.

Running VirtualBox on Armbian is generally not a good fit for what you’re trying to do. Armbian is primarily designed for ARM-based single-board computers, and VirtualBox is built with x86 hosts in mind and relies on kernel modules that are not well-supported (or sometimes not available at all) on ARM kernels like the one in your chosen Armbian image. Even if you manage to install the package, it’s very likely you’ll run into missing kernel module issues or lack of hardware virtualization support, especially on boards like the Orange Pi 5 Plus. If your goal is to run Home Assistant without containers, a more reliable approach would be to either run Home Assistant OS directly on supported hardware, or use a lightweight hypervisor that works well on ARM (such as KVM/QEMU, if your board and kernel support it). Alternatively, if you specifically want VirtualBox, you’ll have a much smoother experience running it on a standard x86 Debian/Ubuntu system rather than Armbian.

After that kernel boots normally and UART stops printing logs. Kernel, btw v6.18, can see and enumerate NMVe SSD, and mount root. $ lspci 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0004:41:00.0 Non-Volatile memory controller: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1202 (DRAM-less) (rev 01) $ ls /dev/nvme* /dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1 /dev/nvme0n1p2 Not sure what firmware you are referring to. I have u-boot-rockchip-spi.bin flashed to SPI flash by armbian-config, while boot dir (including kernel, dtb, etc.) stays in SD card to workaround booting issue and whole rootfs at NVMe SSD. I still think this U-boot NVMe related issue. Apparently NVMe support in U-Boot is enabled but "nvme scan" failed enumeration.

@Dalibor Pospíšil I haven't tested if the pcie works, maybe others did? But it's a bsp driver so it should. If that works, and if the SATA device has a driver in Linux 6.18, simply enable it in menuconfig and you should be good to go. EDIT: Right, I don't have A7A so I didn't really touch the dts for A7A, there might be a little works needed for it to boot.

@alexc What about SATA support? The a7a board has m.2 pcie where the PentaHAT can be attached (I tested it with a custom sunxi kernel).

IMHO, OP wants to boot OS from NVME while the firmware is stored in the SPI flash, but he is using firmware in which the necessary support is not enabled.

@eli I think I’ve got KVM enabled, but as they discussed previously, it's not a Linux kernel issue, there's some specific u-boot firmware needed. Since I don't think the open source firmware is ready yet, I guess KVM likely is not feasible on A733 for now.

What happens after that? Do you see PCIe getting activated? Is the NVME SSD enumerated? What brand and type of NVME?

I tried u-boot 2026.04 from rolling release, still has same problem: DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot16 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch1 ttot16 channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch2 ttot16 channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch3 ttot16 channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0x1 DQS rds:h6,h1 CH0 RX Vref:28.9%, TX Vref:20.8%,22.8% DQ rds:h5 h1 l0 l0 l1 h1 h1 h2, l0 l0 h1 h2 h1 h2 h1 h4 DQS rds:l0,h1 CH1 RX Vref:29.7%, TX Vref:21.8%,20.8% DQ rds:h4 l0 h3 h5 l1 h6 h1 h2, h1 h6 h3 h7 h1 h2 h2 l1 DQS rds:h1,l0 CH2 RX Vref:32.2%, TX Vref:20.8%,20.8% DQ rds:h3 l0 h5 h2 h1 h6 l0 h1, h1 h4 h3 h1 h1 h3 h5 h4 DQS rds:h1,h1 CH3 RX Vref:29.7%, TX Vref:23.8%,22.8% DQ rds:h1 h1 h1 h4 h4 l0 h1 h1, l0 h3 h7 l1 l0 h3 h1 h3 stride=0x2, ddr_config=0x4 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot12 ch1 ttot12 ch2 ttot12 ch3 ttot12 change to F3: 1560MHz ch0 ttot14 ch1 ttot14 ch2 ttot14 ch3 ttot14 change to F0: 2112MHz ch0 ttot16 ch1 ttot16 ch2 ttot16 ch3 ttot16 out U-Boot SPL 2026.04_armbian-2026.04-S88dc-P9ef2-H95ba-Va0a8-B138f-R448a (Apr 25 2026 - 16:56:23 +0000) Trying to boot from SPI ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x13 INFO: code: 0x88 INFO: ext 32k is not valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE K ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x800000 INFO: SPSR = 0x3c9 U-Boot 2026.04_armbian-2026.04-S88dc-P9ef2-H95ba-Va0a8-B138f-R448a (Apr 25 2026 - 16:56:23 +0000) Model: Xunlong Orange Pi 5 SoC: RK3588S DRAM: 8 GiB Core: 726 devices, 33 uclasses, devicetree: separate MMC: mmc@fe2c0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Xunlong Orange Pi 5 SoC: RK3588S Net: eth0: ethernet@fe1c0000 Hit any key to stop autoboot: 0 <comment: stopped for mannual command > => nvme scan <comment: No NVMe drive found> => boot Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': Card did not respond to voltage select! : -110 Cannot persist EFI variables without system partition Scanning bootdev 'mmc@fe2c0000.bootdev': Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 scanning bus for devices... USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 USB XHCI 1.10 Bus usb@fc800000: 1 USB Device(s) found Bus usb@fc840000: 1 USB Device(s) found Bus usb@fc880000: 1 USB Device(s) found Bus usb@fc8c0000: 1 USB Device(s) found Bus usb@fcd00000: 1 USB Device(s) found Scanning bootdev 'ethernet@fe1c0000.bootdev': ethernet@fe1c0000 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.0.50 (257 ms) missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-2a-1c-db-3c-a0 Using ethernet@fe1c0000 device TFTP from server 192.168.0.1; our IP address is 192.168.0.50 Filename 'pxelinux.cfg/01-02-2a-1c-db-3c-a0'. Load address: 0xe00000 Loading: T T <comment: went through predefined boot devices and stuck at waiting for TFTP server, which doesn't exist> When SD card plugged in, u-boot went through boot devices and found that it is bootable and load OS: DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot16 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch1 ttot16 channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch2 ttot16 channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch3 ttot16 channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0x1 DQS rds:h4,h1 CH0 RX Vref:29.3%, TX Vref:20.8%,21.8% DQ rds:h7 h1 l0 l0 l0 h1 h2 h2, l0 l0 h1 h2 h1 h3 h1 h4 DQS rds:l0,h2 CH1 RX Vref:29.3%, TX Vref:21.8%,20.8% DQ rds:h3 l0 h2 h4 l2 h4 l0 h1, h1 h4 h2 h4 h1 h2 h1 l1 DQS rds:h1,l0 CH2 RX Vref:32.2%, TX Vref:20.8%,20.8% DQ rds:h3 l0 h5 h2 l0 h5 l0 h1, h1 h7 h3 h1 h1 h3 h5 h4 DQS rds:h1,h1 CH3 RX Vref:29.7%, TX Vref:22.8%,22.8% DQ rds:h1 l0 l0 h3 h4 l0 h1 h1, l0 h3 h7 l0 l0 h3 h1 h4 stride=0x2, ddr_config=0x4 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot12 ch1 ttot12 ch2 ttot12 ch3 ttot12 change to F3: 1560MHz ch0 ttot14 ch1 ttot14 ch2 ttot14 ch3 ttot14 change to F0: 2112MHz ch0 ttot16 ch1 ttot16 ch2 ttot16 ch3 ttot16 out U-Boot SPL 2026.04_armbian-2026.04-S88dc-P9ef2-H95ba-Va0a8-B138f-R448a (Apr 25 2026 - 16:56:23 +0000) Trying to boot from SPI ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x13 INFO: code: 0x88 INFO: ext 32k is not valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE K ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x800000 INFO: SPSR = 0x3c9 U-Boot 2026.04_armbian-2026.04-S88dc-P9ef2-H95ba-Va0a8-B138f-R448a (Apr 25 2026 - 16:56:23 +0000) Model: Xunlong Orange Pi 5 SoC: RK3588S DRAM: 8 GiB Core: 726 devices, 33 uclasses, devicetree: separate MMC: mmc@fe2c0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Xunlong Orange Pi 5 SoC: RK3588S Net: eth0: ethernet@fe1c0000 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': Cannot persist EFI variables without system partition 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2c0000.bootdev': 1 script ready mmc 1 mmc@fe2c0000.bootdev.part /boot/boot.scr ** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with script Boot script loaded from mmc 0:1 244 bytes read in 5 ms (46.9 KiB/s) 31493216 bytes read in 2669 ms (11.3 MiB/s) 41200128 bytes read in 3487 ms (11.3 MiB/s) 165243 bytes read in 43 ms (3.7 MiB/s) Working FDT set to 12000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ## Loading init Ramdisk from Legacy Image at 12180000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 31493152 Bytes = 30 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 12000000 Booting using the fdt blob at 0x12000000 Working FDT set to 12000000 Loading Ramdisk to eadf7000, end ecbffc20 ... OK Loading Device Tree to 00000000ece04000, end 00000000ece94fff ... OK Working FDT set to ece04000 [image_setup_libfdt] called [image_setup_libfdt] calling fdt_fixup_ethernet [fdt_fixup_ethernet] called [fdt_fixup_ethernet] alias #0: name='gpio0', path='/pinctrl/gpio@fd8a0000' [fdt_fixup_ethernet] alias #1: name='gpio1', path='/pinctrl/gpio@fec20000' [fdt_fixup_ethernet] alias #2: name='gpio2', path='/pinctrl/gpio@fec30000' [fdt_fixup_ethernet] alias #3: name='gpio3', path='/pinctrl/gpio@fec40000' [fdt_fixup_ethernet] alias #4: name='gpio4', path='/pinctrl/gpio@fec50000' [fdt_fixup_ethernet] alias #5: name='i2c0', path='/i2c@fd880000' [fdt_fixup_ethernet] alias #6: name='i2c1', path='/i2c@fea90000' [fdt_fixup_ethernet] alias #7: name='i2c2', path='/i2c@feaa0000' [fdt_fixup_ethernet] alias #8: name='i2c3', path='/i2c@feab0000' [fdt_fixup_ethernet] alias #9: name='i2c4', path='/i2c@feac0000' [fdt_fixup_ethernet] alias #10: name='i2c5', path='/i2c@fead0000' [fdt_fixup_ethernet] alias #11: name='i2c6', path='/i2c@fec80000' [fdt_fixup_ethernet] alias #12: name='i2c7', path='/i2c@fec90000' [fdt_fixup_ethernet] alias #13: name='i2c8', path='/i2c@feca0000' [fdt_fixup_ethernet] alias #14: name='serial0', path='/serial@fd890000' [fdt_fixup_ethernet] alias #15: name='serial1', path='/serial@feb40000' [fdt_fixup_ethernet] alias #16: name='serial2', path='/serial@feb50000' [fdt_fixup_ethernet] alias #17: name='serial3', path='/serial@feb60000' [fdt_fixup_ethernet] alias #18: name='serial4', path='/serial@feb70000' [fdt_fixup_ethernet] alias #19: name='serial5', path='/serial@feb80000' [fdt_fixup_ethernet] alias #20: name='serial6', path='/serial@feb90000' [fdt_fixup_ethernet] alias #21: name='serial7', path='/serial@feba0000' [fdt_fixup_ethernet] alias #22: name='serial8', path='/serial@febb0000' [fdt_fixup_ethernet] alias #23: name='serial9', path='/serial@febc0000' [fdt_fixup_ethernet] alias #24: name='spi0', path='/spi@feb00000' [fdt_fixup_ethernet] alias #25: name='spi1', path='/spi@feb10000' [fdt_fixup_ethernet] alias #26: name='spi2', path='/spi@feb20000' [fdt_fixup_ethernet] alias #27: name='spi3', path='/spi@feb30000' [fdt_fixup_ethernet] alias #28: name='spi4', path='/spi@fecb0000' [fdt_fixup_ethernet] alias #29: name='ethernet0', path='/ethernet@fe1c0000' [fdt_fixup_ethernet] env var for alias 'ethernet0' is 'ethaddr', value='02:2a:1c:db:3c:a0' [fdt_fixup_ethernet] Patching node '/ethernet@fe1c0000' (offset 40388) with MAC 02:2a:1c:db:3c:a0 [fdt_fixup_ethernet] alias #30: name='mmc0', path='/mmc@fe2c0000' [fdt_fixup_ethernet] SUMMARY: aliases found=31, attempted=1, skipped=0, patched=1 Starting kernel ...

https://blog.aurel32.net/upstream-opensbi-spacemit-k1.html will try dev version of u-boot and openbsi

@alexc Thanks, is KVM supported on this kernel?

Hello, I ruun an Helios4 myself, and I've been struck by the kernel image size issue some time ago. I managed to recover using an old version, but now need to upgrade... I foolishly tried an 'apt update', which obviously end up in a non booting board. I manage to get it boot with the latest version on SD, but can not manage to make it work from SPI... Could you please explain how to get the updated u-boot loaded into SPI ? No try using nand-sata-install I've made make a difference.

Good morning. git clone https://github.com/NickAlilovic/build.git --branch v20251014 ~/build/patch-u-boot/u-boot-aw/150-1dd-x96q-lpddr3-defconfig.patch "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" ~/build/patch-u-boot/u-boot-aw/secure-boot.patch ./compile.sh choice = x96q-lpddr3 2026-04-26_0851h.txt boot sequence, shutdown -r and dmesg Thanks in advance. 2026-04-26_0851h.txt

Hi, For Tanix TX68 to get all USB ports working it was enough to toggle status = "disabled" to "okay" in transpeed-8k618 DTS. (unfortunatelly i cannot spin up an external HDD by it while having soldered 2x18650 UPS, to little amps available) Getting WiFi / BT to work on the other hand is not solved. BT: - modules loaded out of the box, no errors in dmesg after changing something in DTS but hcitool dev/scan show nothing WiFi: - modprobe: ERROR: could not insert 'aic8800_fdrv': No such device - I tried modifying parts of Transpeed DTS to align with vendor Android DTS with no result Probably same issue as on T95Z Plus: I tried its image: https://github.com/LYU4662/t95zplus-h618-build same error. I diffed android DTS between T95Z & TX68 - almost identical tp95_android.dts tx68_android.dts

No, unfortunately, I don't have. I will run your build and, possibly, have all required data by tomorrow morning. Thanks for your prompt answer,

@Sergioclr looks like you are building armbian main branch. You are running the 6.18 kernel but old u-boot 2024.01. I don’t see the AC200/300 patch. Do you still have my build laying around. Can you show me the boot logs.