Werner

Never heard of that spelling "ip_tables". Anyway should be built in: https://github.com/armbian/build/blob/4e027a40d6d38d5e9072577a7e47b110914a843d/config/kernel/linux-qcs6490-edge.config#L421

If that doesn't do it, try the main integration branch which for once combines all branches and for the other is actually meant to be used by megi iirc:https://codeberg.org/megi/linux/commits/branch/orange-pi-6.18

First step is to cleanup and bump the sunxi patchset to 6.18. This is a major blocker. Once that is done. Patches for more recent Allwinner SoCs can be added. I started doing that but it is extremely exhausting. I have no clue how the-going managed to maintain that for that long... must be sort of masochistic or something lol. https://github.com/EvilOlaf/build/tree/sunxi-6.18

Not an Armbian uboot binary. Also we started to drop vendor uboot in favor of mainline.

Perhaps this one? https://www.youtube.com/watch?v=yhZahmbb03Q

I never mentioned any solution. Moving your post to an appropriate location is a forum moderation task and the post was FYI only. I don't have this board nor do I know how to fix it.

moved to the appropriate place

There are none. https://docs.armbian.com/User-Guide_Networking/#networking

moved

Try installing qemu-user-static package via apt

IIRC stuff for rock2a/f was sent to upstream uboot too. Try adding a condition to use mainline uboot as well. You can check various rockchip based boards which also have this in their board config file.

moved

This is part of https://github.com/armbian/build/pull/8777/files And there are no changes at our end. So I assume the issue was introduced in mainline?

moved to staging

moved to tvboxes

just noticed current kernel is broken. I assume because of upstream changes. looks like similar what I've fixed for meson64 6.18-rc7. Got it, will send pr Of course this does not explain why the image wasn't correctly assembled at all... Looking good: https://paste.armbian.de/ohagifufem ls -l|grep Odr -rw-rw-r-- 1 root root 142 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.sha -rw-rw-r-- 1 root root 19751 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.txt -rw-rw-r-- 1 root root 322026836 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.x

Because this is not Armbian. This is a fork which uses the name Armbian without permission. We do not support 3rd party forks.

May I ask why you do this fsck? Is there a problem with the image like not booting?

This is not recommended. https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

Agree. @Igor

While having this sent to mainline would be overall best, the faster approach in the mean time would be to send a patch via PR to this location to have it included into Armbian kernel packages: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18

At this time we do not have plans to support it. However anyone is free to step up and provide support with a pull request. We'll happily review. Perhaps chainxs will do this since they're an active volunteer contributor already

When support for Raspberry Pis has been added there was no model 5 yet. With the intention to only support the flagship the board configuration was added as rpi4b.conf. Since then support was extended across all models from 3 and up. However renaming a board config file is an issue. I already had the idea to address that but gave up on it: https://github.com/armbian/build/pull/7881 tl;dr: rpi4b image will work on all models from 3 to 5. https://www.armbian.com/rpi4b/

Try to select CSC/EOS/TVB or use EXPERT=yes

moved to staging