@laibschcoud you take a look at https://github.com/u-boot/u-boot/commit/cae6e8993c8eaed7c520b1046766b658e0f97b90 https://github.com/u-boot/u-boot/commit/aec83261b98eec3a2ca2e9a5a2debea31fcd9d65 https://github.com/u-boot/u-boot/commit/529d24002b6cefb88cd00cef307b8752dbeebfc4 Maybe relevant for the first patch.

Did a fresh install of community Armbian desktop this time, running current 6.12.60 from here. It seems there is no need to compile from scratch if you are using the panel-mipi driver from kungfupanda, I copied my DTS, panel-mipi.bin, etc. from my edge custom compiled installation to the community one and it worked fine after repeating the initramfs process, but I still get a stuck display after a bit, this time on the Armbian loading screen. SSH and Serial console work fine, its just the system stops knowing how to use the display after the initial boot sequence is done, and the kernel hands off the display to X11 / Wayland? This is consistent with how I believe tinydrm works, which is storing the image in memory and displaying new ones from memory if given (which in this case, none are given after a certain stage in the boot process and this hand off to the window manager never happens.) Need to figure out how to tell the system to keep using the drm display. I already tried putting /dev/dri/card0 instead of /dev/fb0 in 99-fbdev.conf, and I've been trying the following extraarg in /boot/armbianEnv.txt to try and get it to work. Screen still pauses halfway through boot messages / loading screen. extraargs=video=SPI-1:480x320@30

go armbian-config - Wait warning message "The current OS (bookworm) is not a officially supported distro!" - Kernel - KER001 Use alternative kernels - Would you like to continue? <Yes> - Show only mainstream kernels on the list? <No> And there the list: then choose "linux-image-edge-sunxi64=25.8.1 v6.15.4 " mainstream kernels: linux-image-current-sunxi64/bookworm 25.8.2 arm64 Armbian Linux current kernel image 6.12.47-current-sunxi64 linux-image-edge-sunxi64/now 26.02.0-trunk arm64 [installed,local] Armbian Linux edge kernel image 6.16.8-edge-sunxi64 linux-image-legacy-sunxi64/bookworm 25.8.2 arm64 Armbian Linux legacy kernel image 6.6.75-legacy-sunxi64 6.16.8: 6.15.4: In the working kernel 6.15.4, the following audio-related modules are loaded: snd_soc_sunxi_machine, snd_soc_sunxi_ahub, snd_soc_sunxi_ahub_dam In the broken kernel 6.16.8, these three modules are completely missing. Only the generic snd_soc_hdmi_codec is present, but it doesn't seem to bind to the hardware correctly without the sunxi-specific modules. I don't know how, but there the list in 6.16.8: tried to activate all dtbs in armbian-config - DTO001 - Manage device tree overlays noghing happend

Well, that makes me wonder how you were able to verify successful flashing with the broken adapters as you were upset we even dared to ask if you did... Maybe reconsider your tone for next time? As it seems the initial request to make sure you had no issues with your storage - one way or the other - were in fact helpful and spot on...

I don't even think this has anything to do with Armbian / Debian / Ubuntu. It's simply someone mucking around too much for their own good and frankly being arrogant about it. Until I see the problem reproduced in a stock setup this is simply PEBKAC as far as I can tell. I mean, for anyone actually willing to read, it's right there: Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. systemd is essentially a monolith, you don't really get to pick and choose for all intends and practical purposes. The choice @Quantum needs to make is whether he wants to have something that works or whether he prefers to be high-and-mighty and run around being condescending to those whose work he uses without paying a dime all the while making outlandish claims. This is a non-issue.