eselarm

I almost never use armbian-config, so don't know if it has options to limit partitions sizes, I think there are, but you will have to look in the script how things are done. But you can boot from SD-card with another independent Armbian installation and from there run a partitions program on the eMMC. Gparted I would say, it should allow you to shrink/resize existing partition and filesystem. An add an extra 1 or more. I usually use gdisk or fdisk/sfdisk via serial console (CLI) and Btrfs as filesystem (not Ext4), so cannot really tell how parted works, but what you want is possible, up to 128 partitions if you want.

I think 6.12.9 is not compatible with the U-Boot versions you used so far. I would try with a 2024.10 mainline U-Boot. I did disable teh SPI flash, see Radxa docs/wiki ( you can also erase it) and then wrote a 2024.10 mainline U-Boot in the boot area of the SD-card. It was from the edge/beta repo a month ago. Currently: root@rock3a:~# apt list| grep rock-3c armbian-bsp-cli-rock-3c-current/noble 25.2.0-trunk.340 arm64 armbian-bsp-cli-rock-3c-edge/noble 25.2.0-trunk.340 arm64 armbian-bsp-cli-rock-3c/noble 25.2.0-trunk.340 arm64 linux-u-boot-rock-3c-current/noble 25.2.0-trunk.340 arm64 linux-u-boot-rock-3c-edge/noble 25.2.0-trunk.340 arm64

What U-Boot version does it run then? I have used also a Radxa version 2023.10 or so pulled as blob from the latest Radxa Rock3A image. Rock3C might be different as especially PCIe is different for RK3568 and RK3566.

You could try: - mainline U-Boot - run rootfs from SD-card and then see if NVMe / PCIe is there and try to mount a filesystem on it. I run OS (edge) from SD-card, so can't tell if NVMe works with >= 6.12.9 I would need to order extra NVMe first.

@asayed Check the usual things like free space etc. And there is a full trace log, I think you have to look into those files. Or just clean/wipe everything and start again, maybe you got some hints/tips/better understanding in the meantime.

Same here for x86-64, but since half a year or so same for aarch64. So I have 2 Ubuntu22 VMs: 1 x86-64 and 1 aarch64. But it turned out that building directly on both RPiOS Bookworm and Armbian Bookworm also works fine. It is mostly compiling Arm kernel and U-Boot, both 32-bit and 64-bit. 32-bit I did via systemd-nspawn of some rootfs-tree clone of a NanoPi-NEO.

A quick look at the shell code makes me think that it is a different purpose compared to how I use virtualization. I use only HW accelerated based virtualization, so -enable-kvm flag is missing, but might be added by virt-install. Also mostly Arm on Arm although I also use x86 on x86 as well. I do not use qcow2, but just flat images or a physical SD-card or NBD or LVM. Before I got my Rock3A, I downloaded the Armbian Noble image for it (was 6.6.62) but put a 6.12 *rk3588 kernel on it as well. With the default Armbian U-Boot for QEMU I could then prepare everything and already 'run' my Rock3A as a VM on NanoPi-R6C like this: taskset --cpu-list 0-3 qemu-system-aarch64 \ -M virt -cpu host -enable-kvm -m 2048 -smp 4 \ -bios u-boot.bin \ -drive if=none,file=rock3a.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1,mac=xx:xx:xx:xx:xx:xx \ -nographic The taskset is needed if host runs 6.1.x vendor kernel and also makes it more realistic w.r.t. speed as then the VM gets 4x Cortex-A55, same as real Rock3A. The 6.12/rk3588 kernel (inside the VM) was needed as that one has all included w.r.t. machine virt (same as vanilla Debian Bookworm kernel). A note is that I later on added Btrfs support to a custom build u-boot for QEMU and converted Ext4 in rock3a.img into Btrfs, but principle is the same. Btrfs offers online shrink and differential snapshots that I use for remote backups. And with a MAC-address equal to the real Rock3A, it is easy flipping between real and VM. Also note is that the following file needs to be created on the host, assuming it uses br0 as base for network I/O: # cat /etc/qemu/bridge.conf allow br0 To use full graphics in VM and for multi-year running VM on my RPi4B, I also use virsh and UEFI. But usually only CLI is needed.

I had to look it up: https://docs.radxa.com/img/rock5itx/rock5itx-system-block-diagram.webp as I was not sure if it was on-chip (RK35xx) or extra. The latter is the case. On a Rock3A I also had success with m.2 e-key port with JMB582, but not used now, instead I use on-chip SATA via overlay. That makes make think that maybe for the Rock5ITX the ASM1164 kernel code is not compiled as module but in-kernel and so maybe there are timing issues in initialization at boot-up. There should not be, but that is what I would look at first as this is PCIe and we know there have been issues with it. If you do not need vendor kernel specifically, you might try 6.12 current/mainline. Also see/check what U-Boot the board boots with.

You could run: sudo apt list | grep linux-image Besides the vanilla Debian/Ubuntu ones, there are Armbian ones: vendor, current, edge In your case your installed U-Boot might be incompatible with kernel 6.1.84, I had that for my Rock3A, I installed mainline U-Boot. If you want all kernels, use http://beta.armbian.com in /etc/apt/sources.list.d/armbian.list Or build yourself from source. The Armbian build runs fine on my NanoPi-R6C Armbian Bookworm

This looks to me as older Debian, older than current/latest RPiOS64 bookworm based. So might use fakeKMS and X11. For efficient and successful modern DE you need KMS, DRM, Wayland and latest MESA and maybe more. W.r.t. labwc that RPIOS64 uses, it worked with Armbian rk3588 6.10.10 kernel. I only ran it for 5 minutes or so as I don't like that former/Pixel DE at all. It is a workaround for old 32-bit RPi boards that can't run GNOME or KDE IMHO, so they need something custom. So it seems to me that you need to port/move the SDR SW from RPi tweaked to more generic arm64 Linux, (with rk35xx additions).

OK contents lost, so again but shorter; Above are all points you should look at; Old U-Boot, likely some failing strange ethernet driver and/or power issue; I would see if the board boot OK with a SPI disabled, NVMe removed from a latest 6.12 Arbian image from SD-card. For my Rock3A from 6.6 to 6.12 I have bypassed boot.src/boot.cmd and armbianEnv.txt, but likely some errors are coming from there. Compare yours with those from fresh latest image I would say.

Look in Radxa Rock3C documentation howto connect a serial console cable. And post U-Boot + as far as it gets here on the forum. Otherwise even you yourself cannot fix it let alone that others can. Or you can download a latest image if that is there with also 6.12.x kernel.

ARM devices do not have something like decades old character buffer 80x25 we know from PC BIOS. It is full graphics and serial console. I lost count on how often I told people to get a USB serial console cable. Especially people used to their iPad WindowsPC Smartphone Tablet RPi seem to be totally unaware that a 2 US dollar cable and setting 'verbosity=7' and removing 'quiet' opens a whole new old world of what the computer board is doing after power on. Some SBCs are even prepared for it; My NanoPi-R6C has an extra USB-C connector for serial console, so just need a USB-C cable to connect to other computer. Better than old 80x25, it allows yo to scroll back and easy copy-paste of text. That is good for fora and getting help.

Small update: As expected, 4+ VLANs work when lan1 is used on my NanoPi-R6C (and with 6.12.6 I had running/installed 3 weeks ago). I basically can work with the limitation on the wan port as for normal planned use-case, I do not need more than 3 VLANs, but any test/trial/experiment is impossible then (I have 9 or more VLANs around in my managed switches). I copied the NM config files to my Rock3A, there is is no problem (but other U-Boot, kernel 6.12.6-edge-rockchip64, Noble instead of Bookworm). I do not understand various details of the patch, for example why is something in the realtek driver needed and not just the STM based MAC driver. I need better understanding first, otherwise I think this is above my skills. It might also be that the Gbit port silicon in the RK3568 is newer than the one in RK3588(S).

I don't know what RK3588S board it is, but you better do it the other way around; I have a NanoPi-R6C and Rock3A, they booth do great in terms of generic KDE6 Desktop with their respective KDE Neon images. GNOME I don't know, but I also guess look at the downloadable images. You need latest MESA and an some other thing, they aren't in vanilla Bookworm, also maybe not in vanilla Noble. That is why the dedicated images are there one can conclude. Also latest/rolling openSUSE Tumbleweed KDE6 Wayland with Armbian 6.12.6*rk3588 works fine. X11 does not work AFAIK. So use the GUI/Desktop images as base, then swap/add kernels. I have 2 or more installed and also manually copied. It takes time to get it a bit flexible (choice at boot time via serial console) but it also depends on what storage/boot devices there are. I only connected the boards to a BENQ 1080p60 LED monitor, via some 2-splitter HDMI-switch (Techhole). 1 side of that splitter is connected to N100 box and I push the switch button when I power on the Rockchip SBC. My Rockchips SoC's work slightly better than RPi3/4 in my experience, that has been a frustrating exercise every now and then (3 years or so) as they cause 1 or the other HDMI monitor not want to detect the Pi. 6.12.6*rk3588 on NanoPi-R6C works great with KDE6 Wayland, i think/assume later *rockchip64 includes all from *3588 as well, maybe just a rename, I have not checked. As long as the SoC is rk35xx it should work is what I would expect. What all does not work is various video codecs, but a rk3588 can decode most in software, same as BCM2712/RPi5 has to do. An as indicated, you might be unlucky with your HDMI monitor, some say only 4K works, but I don't have a 4K monitor.

I have copied the kernel+DTB and regenerated initrd and uInitrd on my Armbian NanoPi-R6C rootfs, set those as boot instead of 6.12.6-current-rockchip-rk3588 Reboot works, but still the limit of 4. And also no network connection as I use bridges and also wan (GMAC 1G) itself counts as VLAN 0 But if I do nmcli con down <a currently unused test VLAN>, there is room for VLAN 0 (done all via serial console), then base LAN connection is there. I have lan1 (realtek 2.5G) unused, workaround would be to use that for the single RJ45 cable connected to the NanoPi-R6C, but plan was/is to use that for other point-to-point link. So I think I will need a closer look and see what could be wrong.

which image did you write to the SD-card ?

Various (newer) Armbian OS images do not have a separate boot partition (anymore). So there is then only 1 partition where also the DTB files are and it is Ext4 formatted, which Windows cannot read. So you need a Linux computer to do DTB file copy. You might encounter another problem, as usually a DTB file is paired with a matching kernel/version, but I do not know your files/version/images, also have no Amlogic box.

The SoC has an ADC AFAIR, but it is used for 'Recovery Key' AFAIR. Look in Radxa PCB schematics to be sure.

I see from: http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_5_Plus#Start_the_Orange_Pi_development_board what you mention: No PD, only 5V. That means that you cannot use a USB-C PD measurement device that shows actual voltage and current being used. But you need normal multimeter etc and maybe some wire soldering. It also means that a 65W PSU that does USB-C PD won't output more than 3A at 5V if it is standards compliant I think. If the OP5+ tends to want to draw more than 3A, the PSU might drop voltage (e.g. even 0), I don't know.

The big questionmark(s) are still then: - can that PSU offer 5A at 5V? - does your OP5+ (and your specific Armbian installation) negotiate 5A at 5V? - or maybe does it negotiate e.g. 15V with 3A ? I got also a 65W laptop type PSU, works fine with tablet/laptop, seen 15V being used. When using with a diskless (headless netboot netroot) RPi4B, it worked, but some undervoltage warnings, that aren't there when I power it with a PSU once bought together with a RPi3B+. So I guess more ripple or so for that 65W PSU and of course RPi4B does not support USB-C PD (only base 5V max 3A).

I think I don't believe that unless you post a similar serial log where we can see what U-Boot, kernel, etc is used. Board is: https://radxa.com/products/rock5/5c I have a RK3588S board running mainline U-Boot 2024.10 and kernel 6.12.6. Is headless (serial console) but if I connect HDMI, it runs KDE6 Wayland really great. I avoid ZFS, but use Linux native Btrfs. All runs from eMMC and/or NVMe. So my advise is, upgrade, maybe first try extra separate latest image from downloads, see if that boots OK. Then merge kernel+U-Boot from that into you non-working setup. That is manually copying things, but then likely no need to re-install everything.

My Rock3A was getting a bit further, so I could benefit from verbosity=7, although it got into trouble somewhere related to NPU (could not draw any conclusion from that anyway). I am looking for an extra RK3588 (not RK3588S) board, maybe OPi5, many options, need more study what is most effective w.r.t. 12V off-grid powering. After I looked into schematics of Rock3A it got more clear to me how I need and want powering. The Rock3A has on-board 5V 8A DC/DC converter, so as suggested somewhere, one can solder some power wires to a DIY USB-C male connector and connect those to something between 9V-20V. So no 'thin wire' problem at least. I should have looked at it before, as now extra RPI5 PSU is not needed now (but good as laptop/tablet charger etc).

I did a quick test based on my december 16th rock3a build tree: /local/s0/armbuild$ sudo btrfs subvolume snapshot rock3a orangepizero3 /local/s0/armbuild$ cd orangepizero3/build /local/s0/armbuild$ ./compile.sh BOARD=orangepizero3 BRANCH=edge kernel-config and also there in the kernel menuconfig Virtualization is not selected, also not the setting 1 level deeper. But when selected, the .config is as expected (like other 64-bit ARMs). My build-host is NanoPi-R6C (RK3588S) running Armbian Bookworm (beta repo, 6.12.6 kernel) where that armbuild folder is 30GB btrfs space on NVMe.

I see that for my 64-bit ARMs (rk3588 rockchip64/rk3568 bcm2711) the kernel configs have the following which allow me to use KVM/libvirtd/QEMU: /local/s0/armbuild/rock3a/build/config/kernel$ grep KVM linux-bcm2711-current.config CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_HAVE_KVM_IRQFD=y CONFIG_HAVE_KVM_IRQ_ROUTING=y CONFIG_HAVE_KVM_DIRTY_RING=y CONFIG_HAVE_KVM_DIRTY_RING_ACQ_REL=y CONFIG_NEED_KVM_DIRTY_RING_WITH_BITMAP=y CONFIG_HAVE_KVM_EVENTFD=y CONFIG_KVM_MMIO=y CONFIG_HAVE_KVM_MSI=y CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y CONFIG_KVM_VFIO=y CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y CONFIG_HAVE_KVM_IRQ_BYPASS=y CONFIG_HAVE_KVM_VCPU_RUN_PID_CHANGE=y CONFIG_KVM_XFER_TO_GUEST_WORK=y CONFIG_KVM_GENERIC_HARDWARE_ENABLING=y CONFIG_KVM=y CONFIG_PTP_1588_CLOCK_KVM=y For 64-bit Allwinner (I only have 32-bit Allwinner SoCs): /local/s0/armbuild/rock3a/build/config/kernel$ grep KVM linux-sunxi64-current.config CONFIG_HAVE_KVM=y CONFIG_PTP_1588_CLOCK_KVM=m I do not know the details, but already KVM IRQ ROUTING needs to be there AFAIR, otherwise hardware accelerated virtualization won't work.