Werner

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

3b is not a supported board, therefore mirror does not have up-to-date images. Check 2nd link I provided

There seems to an issue with some boards not showing download links. Until fixed feel free to dig through both mirror and community images: https://fi.mirror.armbian.de/archive/ https://github.com/armbian/community/releases

My guess is that there is some code missing in the board config to make it available. Similar to this: function post_config_uboot_target__extra_configs_for_rock5b_mainline_environment_in_spi() { display_alert "$BOARD" "u-boot configs for ${BOOTBRANCH} u-boot config BRANCH=${BRANCH}" "info" run_host_command_logged scripts/config --set-val CONFIG_ENV_IS_NOWHERE "n" run_host_command_logged scripts/config --set-val CONFIG_ENV_IS_IN_SPI_FLASH "y" run_host_command_logged scripts/config --set-val CONFIG_ENV_SECT_SIZE_AUTO "y" run_host_command_logged scripts/config --set-val CONFIG_ENV_OVERWRITE "y" run_host_command_logged scripts/config --set-val CONFIG_ENV_SIZE "0x20000" run_host_command_logged scripts/config --set-val CONFIG_ENV_OFFSET "0xc00000" } @schwar3kat any chance to have a look?

Because they forked an old version of our framework and replaced "armbian" with "orangepi".

https://fi.mirror.armbian.de/oldarchive/ If its not there, its gone.

Ricardo put some real effort into Rk3528 here :https://github.com/armbian/build/pull/9102 Since the 2A/2F are using the same SoC this should actually help a lot.

Again for the record my suggestion was untested, not much thought about, pieced together in seconds to give somewhere to start.

Try unset or remove ATF related stuff. There is not atf for 3528 yet

There is something to start with. Untested, not even put much thought into it. Try'n'error: https://github.com/armbian/build/compare/main...EvilOlaf:build:rock2f Ignore the rpi4b stuff, accidentially mixed branches.

Interesting. Also because independent from userspace (Bookworm or Trixie) our kernel/firmware package is the very same.

I don't have a rpi4b for comparison here but 5b seems ok: root@localhost's password: 1048576+0 records in 1048576+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 11.4733 s, 93.6 MB/s 2097152+0 records in 2097152+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.72436 s, 227 MB/s root@rpi5b:~# uname -a Linux rpi5b 6.19.0-rc1-edge-bcm2711 #1 SMP PREEMPT Tue Dec 16 21:14:01 UTC 2025 aarch64 GNU/Linux

https://github.com/armbian/build/pull/9094

Hm yes, around line 26785 there should be the overlay folder. Oddly when I tried it was there.

Odd. Should more look like this. Also the first time I hear there is an issue like this. Perhaps retry now since your group is no longer validation but members. https://x.na4.eu/KOTu3/PACoFIsE81.jpg

@JuanEsf sunxi-edge is now on 6.18. You can add your patches for t527 there.

HI, this setting isn't in your account settings but embedded in your profile. https://forum.armbian.com/profile/218842-p3ter There is a button at the bottom left of the "P" what is now your avatar. Also at the bottom right you should have buttons like "Edit Profile" or "Cover Photo".

https://github.com/lanefu/fan-control-rock5b-poe

Wrong serial console set in kernel parameter could be a reason for having not output afterwards, so the suggestion isnt completely off. Though no clue what might be correct here.

No, because as mentioned, we need to wait until the bump to 6.18 is approved and merged. Then the work for more recent AW SoCs can be rebased on top of that.

According to the schematic it seems like pwm is used for that. That would need to be enabled as device tree overlay. https://dl.radxa.com/accessories/25w-poe/radxa_25w_poe_plus_hat_v1.2_schematic.pdf Not sure if there is further/DIY programming necessary to make it work.

This was fixed quite recently:https://github.com/armbian/build/pull/9039 Upgrading uboot package does not automatically rewrite the binaries. It just provides them for manual rewrite. So upgrading this package should not do any harm without actually writing the boot loader.

You're in luck. Major work has been done. https://github.com/armbian/build/pull/9049 Still needs testing Once this is merged 4A and other more recent Allwinner Soc related work can be rebased on top of that.

That would be my best guess too. Check other PRs which add support for boards to get some clues how to achieve. If there are questions, feel free to state.

Set verbosity to 7 in armbianEnv.txt to get an idea about what happens after "Starting kernel..."