All Activity

You need to look into github changes then, everything is traceable, but certainly not an easy and quick thing to do.

@KhanhDTP, that's great news! Thank you very much for the testing!

What you prefer or think is best. An extra boot partition is more flexible as it is an extra 'boot-stage' sort of, and normal computers that use UEFI anyway need also a FAT formatted bootpartition besides 1 or more rootfs for (multiple) OS. So not a bad approach to have separate boot partition an if on SD-card, is removable, so is flexible in case of trouble and/or testing things.

For that dts file must be changelog somewhere explaining changes. I decompiled both dts files but it is hard for me to decode changes in short time.

Both logs show initial timestamped text, then the same again non-timestamped. That is something fundamentally wrong. You can de-compile and compared DTB files but it might not reveal why it fails. Btrfs might by just un-related. I see in the NOK log a disabling of an LDO, might be on purpose but also because code is just corrupted somehow. I do not have this BPIM2U board, so no way to see if same would happen for me. Hope someone else can reproduce, else use older kernel that does not fail.

Ok. Thanks. dd copie the blob. It has SPI or a little memory, but as I understand it could be a problem, so it easier to use SD as boot-disk.

@humanus Did you build that yourself? I tried Nick's A7A and A7Z images, but they won't boot on the A7S.

logs with verbosity=7 BOOTLOG-NOK.TXT BOOTLOG-OK.TXT

I assume OPi02w has no on-board storage, so it only is the bootcode in ROM, and that reads U-Boot binary blob from fixed sector offset location on the SD-card. It does not even need a MBR-table or GPT and it is not in a partition, so you won't see it. Only if you use dd to read (or write/wipe) that data you will know. See how U-Boot needs to be written for your OPi02w, then you will understand. If the U-Boot is build to initialize the USB and HDD, you do not need /boot partition on the SD-card. But I do not know that. Not all USB-SATA chipset drivers are in U-Boot, so if not, you indeed need a boot partition on de SD-card where kernel initrd DTB are, those should understand USB-SATA chips and so see the rootfs on HDD.

The bootlog-OK.txt shows: [ 10.796728] Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read which is not good at all. I also think you think you still not have set verbosity=7 in armbianEnv.txt, else the both the OK and NOK logs would show more and that is needed as a start for further investigation.

After inspecting the differences between those 2 bootlogs, it looks like it hangs up for some reason when trying to check the root filesystem for errors.

Hey Installed Armbian (Ubuntu-noble) with XFCE desktop on an HDD(sda) from SD-card, so I need to have an SD-card in my orange pi zero 2w. I wonder if I can move /boot to an another smaller SD-card? Or do I also need an "mbr" or someting also there u-boot are? /Cheers

Bootlog with non-working and working dtb file. bootlog-OK.txt bootlog-NOK.txt

I'm using armbian trixie/BSP 6.6.98 by @Nick A with thermal throttling disabled (`step_wise` policy) and with the performance governor (shouldn't matter that much).

That is at least the same base release (2024.01) from U-Boot as my Allwinner H3 boards, but old 32-bit ones. If it would be something like 2017.09 that would point to vendor legacy as older Rockchips might still use that. So I think you would need to look at live kernel logs at power-on and see where it stalls. It might be for example a swap in mmcblk numbers (SD-card v.s. eMMC), just an example. I have also seen many things related to powering as well, or some clock wrong (maybe too high for storage HW, whatever). USB serial console/debug cables cost about 1 euro nowadays, so I once just ordered 10-pack, standard connected one to most SBC's.

root@bpim2u:~# sudo dd if=/dev/mmcblk0 count=32k | strings | grep "U-Boot SPL" U-Boot SPL 2024.01_armbian-2024.01-S866c-P7738-Hadc5-Vc46c-B2eb2-R448a (Feb 20 2026 - 04:58:43 +0000)

rk3588-pcie_bifurcation_2x2-uboot.patchrk3588-pcie_bifurcation_2x2.patch Attached are two patches I've prepared. One for uBoot (to correctly recognize split pcie3x4 to two independent controllers, pcie3x4 and pcie3x2), and one for DT of NanoPC T6. This basically allows you to use trimmed-down bifurcation adapter. The adapter in question must be trimmed down/cut to fit on the back of the board. Tested with 2x NVME, and 1xNVME and QCNFA765 wireless card. I'll post photos later once I'll disconnect the board again from my setup. BEWARE!!! If you'd plan to use more than one ath11k wireless card, you'd need QRTR patch. Since the SBL enums changed in recent kernel 6.18.18+, I am also preparing modified kernel patch (originally for OpenWRT by Hauke Mehrtens and Robert Marko) to allow for more than one ath11k wireless to be installed. Will post later with new patch for it. root@ap-voyager:~# lspci -nn 0000:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0000:01:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0001:10:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0001:11:00.0 Non-Volatile memory controller [0108]: Shenzhen Longsys Electronics Co., Ltd. Lexar NM610 PRO NVME SSD (DRAM-less) [1d97:1202] (rev 01) 0002:20:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0002:21:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0003:31:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0004:40:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0004:41:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) root@ap-voyager:~#

It would save you (and others) a lot of time if you would have a USB serial console/debug cable and with verbosity=7 in armbianEnv.txt I actually only got triggered because of 'Btrfs' in the topic title, but it might be a totally unrelated issue. Also note that besides the kernel provided .dtb file (is in /boot/dtb but and same file is also somewhere in /usr/lib/linux-image-<KVER> ), U-Boot has its own DeviceTree version/variant. Might be older, newer, broken, incomplete, vendor, mainline, patched, custom. So what U-Boot is loaded/used, also is important to know. Extract that info from SD-card where the U-Boot blob is written (sits at fixed sector offset, between partition table and 1st partition). You can look into U-Boot writing scripts to get to know the offset for Allwinner, but something like this is quicker:

thanks, it is settled now, apt-get update behaves normally.

Hello @VBB, those log snippets show no reason why system can freeze. Recompling bcmdhd internal SDIO Wifi driver on kernel updates works as intended. Disabling lightdm and enabling gdm3 is part of the spacemit-gpu-addon.sh you run - gdm3 is the display-manager to use if you want a DM with Wayland (b/c only Wayland works with those closed source GPU stuff). If it's stuck, just rise the loglevel= in /boot/extlinux/extlinux.conf for more output or simply download one of my images and retry running that script (Image -> https://privat-in.de under "Downloads"). HTH // Sven-Ola

thanks, after sudo dpkg --remove-architecture i386 it sped up a little bit, can be marked solved? (it still takes too long, but that may be realted to the sbc or the software installed.) Es wurden 378 kB in 2 min 25 s geholt (2.606 B/s).

dont understand what you mean, was i posting AI? sudo apt-get update on my sbc takes 2min 22sec to complete, and it queries i386 packages, which are not called for, since the sbc is arm64. sudo rm -r /etc/apt/sources.list.d/ armbian-config.sources armbian.sources ubuntu.sources cat /etc/os-release PRETTY_NAME="Armbian 26.2.1 noble" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" PRIVACY_POLICY_URL="https://www.armbian.com" UBUNTU_CODENAME=noble LOGO="armbian-logo" ARMBIAN_PRETTY_NAME="Armbian 26.2.1 noble" uname -a Linux pine64 6.12.58-current-sunxi64 #3 SMP Thu Nov 13 20:34:41 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

meco any update on this? dual NVME also does not work on non vendor kernels as well as second HDMI port.

I am getting closer to resolving this issue ... I took the latest image Armbian_community_26.2.0-trunk.732_Bananapim2ultra_noble_current_6.18.22_xfce_desktop.img.xz, flashed it, and it hung on Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems Removed microsd and replaced file sun8i-r40-bananapi-m2-ultra.dtb in /boot-dtb folder with file supplied with linux-image-6.1.24-sunxi kernel. And do you know what ? It successfully booted up after this change!

@Sergioclr I remember someone was able to get Ethernet working by changing 16 to 0. There's two locations ethernet-phy@16 and reg = <16>; +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +};