Just as an update, for anyone who cares. The above setup worked well, but I couldn't help but attempting to get video hardware acceleration in a browser. Since my post above, Armbian support for the Nanopi R6S went platinum (thanks to @Efe Çetin), kernel 7 came out and mesa 26 should provide all that is needed for vaapi/v4l2 support in firefox. Unfortunately, minimal Armbian Debian with kernel 7 combined with mesa 26 looks to be some time away - that would allow me to run sway, and likely with firefox using video decode acceleration. OTOH, vendor kernel at 6.1 doesn't seem to allow sway to run at all. So I tried Armbian Debian 13 minimal with kernel 6.18, which runs sway just fine, but the mesa version is stuck at 25.2 which in the standard Debian package does not by default support the rockchip hardware yet, I think. In addition, there seems to be some incompatibility with the repository provided here (or I am doing something wrong, which I wouldn't deny). Fortunately, looking at the Armbian git files I saw that the standard Armbian Ubuntu Noble with vendor 6.1 and Gnome (KDE version doesn't run well) appears to a) work fine with wayland, and b) automatically uses the Amazingfate (liujianfeng1994) PPA. This provides chromium with video hardware decode support, and I can still set up jellyfin. So at this point, without having to compile everything myself from scratch, this is the best setup from my perspective. Shout out to @Efe Çetin for making it this convenient - which it truly is, even though Gnome isn't my preferred DM.

armbianmonitor picks up the wrong temperature to show as "Tcpu". 19:40:09 1600/1600 MHz 0.63 12% 0% 12% 0% 0% 0% 34.9 °C 0/1 19:40:14 1600/1600 MHz 0.66 12% 0% 12% 0% 0% 0% 34.9 °C 0/1 19:40:19 614/ 614 MHz 0.60 5% 0% 4% 0% 0% 0% 34.9 °C 0/1 19:40:24 614/ 614 MHz 0.56 0% 0% 0% 0% 0% 0% 34.9 °C 0/1 19:40:29 614/ 614 MHz 0.51 0% 0% 0% 0% 0% 0% 34.9 °C 0/1 19:40:34 614/ 614 MHz 0.55 1% 0% 0% 0% 0% 0% 34.9 °C 0/1 19:40:39 1000/1000 MHz 0.51 3% 1% 1% 0% 0% 0% 34.9 °C 0/1 19:40:44 614/ 614 MHz 0.47 0% 0% 0% 0% 0% 0% 34.9 °C 0/1 Time CPU_cl0/CPU_cl1 load %cpu %sys %usr %nice %io %irq Tcpu C.St. 19:40:49 1600/1600 MHz 0.51 12% 3% 8% 0% 0% 0% 34.9 °C 0/1 19:40:54 1600/1600 MHz 0.55 15% 4% 10% 0% 0% 0% 34.9 °C 0/1 19:41:00 1600/1600 MHz 0.58 15% 4% 10% 0% 0% 0% 34.9 °C 0/1 19:41:05 1600/1600 MHz 0.70 15% 4% 10% 0% 0% 0% 34.9 °C 0/1^C Meanwhile in 'sensors': cluster1_thermal-virtual-0 Adapter: Virtual device temp1: +45.0°C nvme-pci-10100 Adapter: PCI adapter Composite: +34.9°C (low = -40.1°C, high = +119.8°C) (crit = +129.8°C) Sensor 1: +42.9°C (low = -40.1°C, high = +139.8°C) Sensor 2: +34.9°C (low = -40.1°C, high = +119.8°C) cluster0_thermal-virtual-0 Adapter: Virtual device temp1: +45.0°C So it shows the NVMe SSD temperature instead.

I have a Orange Pi Zero2W with Armbian. I flashed a SD-card, and then I copy the system and boot to a usb- hdd (sda) and the system boot to sda Want hdd because It write much data and USB 2 don't take mush more speed. But I get a warning about a file-error or something so I run fsck on sda(hdd) that was a systemdisk, but when I run I choose to do it read-only, but anyway it does not boot any more. I think I can take the usb-hdd and run fsck from another computer? I have one system with Ubuntu on a Intel 6 gen, and Raspberry pi 500 and 5. The Pi-machine have raspberry-pi OS and the other Ubuntu 24.04.Does the machine or system have any significans? Or is there another fix to fix so the /boot on SD-card can find sda on USB? /Cheers /Edit. I posted under Orange Pi Zero2, but that was wrong place, and get moved, but at the same time get my thread classed as solved, but the solving was just to get the question on right place. I have also cleared my question a little bit and I can not take away the other.

Thanks Nick A for the A7S image! I've been trying out v0.6.4 using Sway on top of the server image w/ a pair of Viture Luma Pro AR glasses as a display. A few things I noticed: - It seems like a display needs to be plugged in at some point during boot for DP to work, but can be unplugged and replugged afterwards without breaking anything. I'd guess that this is the same issue @qq20739111 noted. - Audio over DP doesn't seem to work, and I don't see any sinks available through pactl. Fwiw, I've at least verified DP audio to work on the vendor image, and Bluetooth audio to work on this one. If it'd be useful, here are some boot logs taken over UART: DP plugged in at boot, display output works - https://paste.armbian.eu/vuvoyufuto.yaml DP plugged in after boot finished, no display output - https://paste.armbian.eu/ohoqorupiy.yaml

Off course do I have Orange Pi Zero2W, as I wrote in the beginning, but I thougt there also was an 2E verion and thoungt that orange pi zero 2 was a "over group" with only diffence ethernet and wifi.