Hello, fellow H96 musers. I've just acquired a 4G/32G H96 Max V56, and tried to flash an image that works on an earlier 8G/64G H96 Max V56, using the appropriate 4G booloader rather than the one I used for the 8G. The HAOS image boots fine, but everything about the Ethernet and WiFi must be wrong, as I have no networking hardware configured. I'm curious to know if there are differences between the 4G/32G board and the 8G/64G, other than eMMC size, that might account for the above outcome? There was some early mention of 'type 1' and 'type 2' 4G/32G boards early on in this thread. Could I be using an inappropriate device tree source configuration for my 4G/32G board? If that's not it, then the only other thing I can think of, is that the 4G/32G board I recently acquired has different WiFi/Bluetooth and Ethernet chips fitted, and the drivers from my 8G/64G build aren't suited? 8G/64G H96 Max V56 PCB: LP6E27116A0 Wifi/BT: HC16335, S3144335 Ethernet: Realtek, RTL8211 4G/32G H96 Max V56 PCB: LS6E28533A0 Wifi/BT: SKI.WB800D80S.1_D40, 2023AP20230(M) Ethernet: Maxio, MAE0621A-02C Thoughts, board type clarification, or driver suggestions, anyone? GBEM 👽

In fact, image boot very well with minimal change. (dtb change and something about virtual console) It' s after 🥲

They are not empty. You need to go one level deeper: https://armbian.nardol.ovh/dl/tinkerboard/archive/ BTW, try https://github.com/armbian/imager It will be much easier.

I though some older images worked ... here you are on your own. Compare device tree from cubox and this hardware and repeate this on modern kernel, and apply difference. Just an idea. Sadly, no simple solution such as download and play.

https://fi.mirror.armbian.de/archive/tinkerboard/archive/