JohnTheCoolingFan

I am unable to reproduce this on BigTreeTech Pi (v1.2). Set wifi up using netplan via NetworkManager. Wifi connects after a reboot, same if I poweroff the device, disconnect power and then connect back up.

No idea what causes this, will need to check on my device

I'm not working on the legacy kernel at all, current and edge only, which are based on mainline. The fix for wifi should be in the upcoming armbian release (25.05). It was merged into the build repository long ago and should've been available in beta already, only now coming into the release. To those who are still using legacy - I recommend switching to current or edge instead.

Have you tried with current or edge kernels?

Found the issue and submitted a PR to the repository. It will take some time to get merged and then the new kernel built and put into the apt repository.

It seems that the images mostly just use some of Armbian patches, maybe some custom ones. Comparing them thoroughly and applying what I can if needed is my goal now.

First time seeing this 3.0.0 image, will check it out

@Yell BigTreeTech images are like a reference image made by bigtreetech, it doesn't have the long-terms support and usually uses old kernel versions, simply an image to use when the board was just released. The other link is a link to my forked repo where I did work on the board before it got merged into the main branch, it's a temporary branch and you should not use it. I recommend using the official Armbian image as that is what is supported on this forum, you can download it on the armbian website (armbian.com)

The patch has been added: https://github.com/armbian/build/pull/7584

I've had a person contact me on discord saying that using a orangepi 3b image with a slightly modified device tree works well, I've also mentioned that in the PR discussion. You can try that. My current goal is to translate the modifications they made onto a normal (non-flattened) device tree source and maybe include something from orangepi 3b to hopefully fix that issue, but it's a long process and I've been having some health problems recently. I want to use BTT Pi2 as a new home server, especially since the sd card in my old one died and now I am in a hiatus of trying to recover and get up and running.

The btt-cb2 branch is currently not working, hangs 170 seconds after boot, and I am working on fixing the device tree for that. BTT CB1 is a different hardware, and it's in the main branch. I handle them separately because of the different SoC families.

Sorry @Sesse but I don't know an answer to that question. You'll have to ask someone else for the reasoning behind that. I'll ask in our discord channel.

Oh crap, forgot to subscribe to the topic. Thanks @going for your work on this!

Tip for compiling: you should be able to use docker for easy cross-compilation on your pc instead of the board itself. As for thermal zones, it's probably a matter of device tree tweaking, I'll take a look.

Yeah, try the official armbian image, which includes u-boot bootloader. You can also back up the emmc data as an image, then flash the official Armbian image, try it, and then flash the backup if you want. But I think using the official Armbian image so that the appropriate u-boot is used would be best. It's fine by me to wait for the new emmc. Also, when I said remote, I meant having you try out different images and sharing the logs, not remote access over internet.