Hi @Igor, Thank you for following up on this! In the end, coincidentally I think, I managed to get it to work. I saw that a new armbian package was available via apt. I installed it, and because it included kernel 6.6.61-current-meson64, I saw that when this was being built, one of the steps was to write the headers for ZFS. I restarted my board, and now ZFS works.

I currently only have the 6.8.11 kernel running but here's the output for that. $ uname -a Linux snapclient-living-room 6.8.11-edge-rockchip64 #1 SMP PREEMPT Sat May 25 14:28:41 UTC 2024 aarch64 GNU/Linux $ ls /dev/snd/ by-path controlC0 pcmC0D0c pcmC0D0p seq timer I'll see about getting the output for other kernel versions later.

Thank-you for reply. Sorry for the beginners question, but "How to"? I used armbian-config to move from 6.1.92 to 6.6.44 and I was assuming that 6.6.44 would replace 6.1.92; apparently it did not, as you said in your reply. So how can I make 6.6.44 the new 1 and only new kernel. I currently back to my old image w/ kernel 6.1.92 frozen and Debian Bullseye. I have a complex APP with tons of middleware and 3rd party SW; a fresh new installation would be a PITA.

@Wizzard The boot environment is stored on emmc. So when you boot (enable multiboot via holding the reset button) that is setting certain variables in the u-boot environment and persisting them there (which is on emmc). That is why you only need to press the reset button the first time you boot Armbian or any other distribution. But the way that the distributions setup the boot environment are different (and usually not compatible) - even the Armbian legacy stuff from balbes150 changed how it was done (in incompatible ways) a number of times over the years. So without knowing what has been changed in the u-boot environment that is stored on emmc, it is impossible to really support people. So there is a check in the Armbian code that looks for certain changes that indicate something else has run and then fails the boot.

I retrieved the DTB rk3566-box-demo_x96_x6.dtb in the thread dedicated to the H96 Max and... all the USB ports are ok 🙂 But on the other hand the ethernet port does not work anymore : it is up and the negotiation is done well (1000baseT) but, if what the router emits is well received by the box, the latter does not see what it emits. Strange: if we start with the dtb rk3566-box-demo.dtb and we restart with rk3566-box-demo_x96_x6.dtb (without power cut) ethernet continues to work! It is as if an initialization was missing, present in rk3566-box-demo.dtb, absent in rk3566-box-demo_x96_x6.dtb. I'm trying to find the differences between rk3566-box-demo and rk3566-box-demo_x96_x6 but there are hundreds of them and it's hard to identify the real semantic differences 😞 Any help appreciated... Kernel log :