MichaIng

On my NanoPi M1 at least this kernel works fine. I also checked that the NanoPi NEO device tree is present. So not sure. If there is any 2nd report,...

I took the new kernel out of the APT repo for now. @mhjessen Oh you use a very old image, or one that was migrated from an original Armbian image?...

From 2017 😍, even before I joined the project. Indeed that time, we did not use own `dietpiEnv.txt` yet. I added this 2022. Hence you can remove `dietpiEnv.txt` entirely in...

Okay that looks all as expected. I was further checking regarding the > 1 GB addresses. And well, I have to admit, sometimes LLMs are incredibly helpful. For Allwinner boards,...

Yeah testing those other images with the same kernel can at least verify that it is not a general kernel issue, but related to bootloader or boot config in combination...

The NanoPi NEO default/debug UART supports 1.5M baud rate?? That is surprising indeed. I mean it will support 115200 as well, so if you connect with a UART adapter and...

> I had the TX and RX swapped inadvertently Typical mistake I forgot to mention: boards assign RX and TX inconsistently, as if sometimes RX means receiver pin for the...

Interesting. While U-Boot gives output at baud rate 115200, the debug port indeed supports 1.5M: I get kernel output and can login, when adjusting the `[email protected]` accordingly, like we do...

Good. So generally it works. Now we do not know yet why it failed originally. You flashed a more recent U-Boot in between, maybe that made the difference. I'll add...

Ah right, with the Armbian `/boot/boot.cmd`, `console=serial` needs to be set in `/boot/armbianEnv.txt` to get kernel output on the serial console. U-Boot however prints to it by default, the cmdline...