Yes, that's the idea I guess. I played around a bit, but could not enable it with the script ... yet.

You don't need that. Most likely unrelated to this problem, but dd does not verify what was written: https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card Did you try booting with defaults? Agree, that's not normal. We are seeing some regressions on Allwinner related Crust support to https://github.com/armbian/build/commit/e76540693522baec079ec7633a918a9168ce130c (responsible for low level power management operations) Nothing obvious, no quick solutions based from what is seen from the logs.

If you build the module in question on the target machine, why do you use stuff like "ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-"? Doesn't make sense when building natively.

Any luck? my tx1 is in the mail.

@Nick AI tried to extract the dts from the working image, cloud you help me find any clues. Thank you. I was able to gain access to the os that works, this is the dmesg: dmesg | grep eth [ 8.550757] libphy: 5020000.eth: probed [ 8.568109] sunxi-gmac 5020000.eth eth0: eth0: Type(8) PHY ID 001cc916 at 0 IRQ poll (5020000.eth-0:00) [ 12.765916] sunxi-gmac 5020000.eth eth0: Link is Up - 1Gbps/Full - flow control off [ 12.775526] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready I also upload the pic of ethernet chip. dts.zip