eselarm

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.

Do as Werner says I think, although setting verbosity=7 in armbianEnv.txt will likely show you where it fails

This is "Orange Pi Zero 3 is powered by Allwinner H618 quad-core Cortex-A53 processor: I am a bit surprised that you needed own actions to enable KVM. At least already Debian Bullseye aarch64 had this enabled by default. I used that on RPi3 although that one can run 32-bit kernel then it won't work. I use standard KVM/libvirt/QEMU, no proxmox.

There is Debian Bookworm image as well. That variant should have been there for more than a year. Ubuntu Noble is fairly new, so maybe some issues. Kernel is the same. But vanilla Ubuntu Noble is kernel 6.8, so in theory there might be issues. I use Armbian Debian (kernel 6.6) on my 32-bit NEOs. no issues. I could switch to Noble but is no priority. I use it on a new Rock3A, works fine there. If you feel you can't handle potential issues, use Bookworm.

It tuns out that the failing mmc1 DISCARD is related to the specific SD-card: Silicon Power 16GB CID=9f5449535043432010c464002f012c61 With mainline 6.12.6 kernel about daily this: [Dec27 00:13] mmc1: Card stuck being busy! __mmc_poll_for_busy [ +0.000526] I/O error, dev mmcblk1, sector 2107456 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0 [ +0.001177] mmc_erase: group start error -110, status 0x800 [ +0.540862] dwmmc_rockchip fe2b0000.mmc: Busy; trying anyway [ +0.729908] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ +0.020846] mmc_host mmc1: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0) [ +0.447254] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000000Hz, actual 50000000HZ div = 0) [ +0.124915] dwmmc_rockchip fe2b0000.mmc: Successfully tuned phase to 0 No data corruption, btrfs scrub reported 0 errors. I did dd copy the card to a new 32GB Sandisk card, fixed GPT and now not this kind of errors anymore.

You might have the situation that your Pi sees/has 2x U-Boot, 2x boot.scr Or even more. boot.scr is generated from boot.cmd, look in there how scripting composes the name of your overlay files. Multiple copies and/or versions will create mystery. Take your time and see what is what and where. And connect serial console. It allows you to load dtbo manually, needs a lot of U-boot commands study, I also had to learn myself.

Indeed you need to hook up a 'serial console cable' for cases like this. Some call it 'serial debug cable' or you say 'RS232 logger'. It actually should not be RS232, that is serial but other higher voltage signal levels used for long wires, PCs in the past. It must be TTL level 0V en 3V3. Which pin you need is undocumented for your RockPiS ('Comming soon', cheap board so no good documentation...) https://radxa.com/products/rockpi/pis#techspec I guess you need to take the same pin numbers from the colored header as for RaspberryPi boards and almost all others like for my Rock3A. See what is Rx, Tx, GND. If you look in boot.cmd for your board you could derive what setting you need on the USB side of the cable(in your laptop or so). For Linux laptop controlling my Rock3A I use for example: sudo screen /dev/ttyUSB0 1500000

I see it is from 2021. So a typical case where the board vendor has left its customer. Still Debian10 where in half a year we will have Debian13 already. I also see there is an older version Debian9. So ASUS sold the boards, supplied it with some OS image, did 1 time an update, but that's it. It looks to me that they never made any profit from this SingleBoardComputers business, so not surprising that support ended, that is the hard truth. It is a pity as I remember when it was put on the market, I found it a promising alternative to RaspberryPi and I have several ASUS PC motherboards that already work for 10+ years. But of course people still pay Microsoft. This is more or less the base for expectation level what you can do with the board. You can make some mix of the old ASUS Debian10 image and a newly build more generic Armbian image, but that requires quite some Linux know-how and low-level tools to do. Otherwise, pull the powerplug after shutdown.

Yes thanks for mentioning this. I will need to keep an eye on this as my initial bring-up of the Rock3A also resulted in block errors after 2 days. Was another SD-card (new one). But I did many reboots/trials and 3 different U-Boot versions, 3 different kernel versions, also not to forget various powering options. So cannot really conclude anything from it. Note that I use Btrfs, so already the kernel detects block corruption. Usually that says enough. See also comments inside script: /usr/sbin/fsck.btrfs If a DISCARD command fails (I/O error), it should not corrupt used blocks, unless the SD-card internal firmware makes a total mess of things or due to some wrong administration in fstrim/kernel. I bought this Rock3A for its SPI flash and SATA, so I can put Btrfs+SATA enabled U-Boot in it, then the board itself can boot from Btrfs raid1 profile (SD-card+SATA-HDD), even with SD-card totally failing. So that I could use to detect issues with SD-card (anything, even A2 queing etc if that is the case, I haven't focused on it). And keep it running. But it is easier to raid1 an SD-card partition + an NBD image file on NAS (TFTP boot), I have done that before. Then no changes in default U-Boot needed.

This works.