@Marvin-03 this trixie img boot on Orange pi 4A?!

Oh, btw your branch throws an APT error around "ntpdate" not having an installation candidate or something. I'm pretty sure there's other issues, but I'm out of the house at this very moment. I would've brought this up on your github project page, but there's no "Issues" tab.

That's nice, I don't have this new board BOM, be free to add the variant, I think board variants are included using a .dtso file for armbian i think we cannot include tirth party drivers, but any changes to .dts could be included into a .dtso file that's a way to enable this variant into mainline armbian

Good evening everyone. I acquired another X96Q TV Box with the same Armbian-H313 processor, but this time with revision V4.0. I flashed an SD card with the following image: Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz Surprisingly, the box booted correctly with this version. However, when I tried to install my server, the system prompted me to perform an update. I ran the following command: sudo apt update && sudo apt upgrade After rebooting, the box remained stuck on the red LEDE. Luckily, I hadn't installed it in the internal memory. Here is a photo of the two cases: Here is a photo of the motherboards of both cases: Here is a photo of the X96Q-Armbian-H313 V4.0 boot screen: Here is a photo of the X96Q-Armbian-H313 V4.1 boot screen: Here is the X96Q-Armbian-H313 V4.0 report file: X96Q-Armbian-H313 V4.0.txt Here is the X96Q-Armbian-H313 V4.1 report file: X96Q-Armbian-H313 V4.1.txt Question: Could the difference between version V4.0 and V4.1 of X96Q explain the incompatibility during installation? And how can this be resolved? I would like to use them as servers. Is there any risk if I reinstall, but this time directly to the case's internal memory? Thank you in advancur help.

I see this on your dts: ethernet-phy@1 { compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22"; But I think should be: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x1>; And try to use the generic driver for ethernet.