Werner

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

No. This fork uses the name Armbian without permission and they do not contribute to the core development process. Instead they trick you into thinking that you'd get any sort of support here at our place whatsoever.

You are not using Armbian but a fork. Ask where you got the image from. We don't support 3rd party OS.

We don't deal with Android here. Ask vendor or at some place like xda developer forums.

edit /boot/armbianEnv.txt and set verbosity to 7 to get an idea about what happens inside.

This should work too. Debug boot issues: https://debug.armbian.de Related perhaps: https://github.com/armbian/build/pull/8994

Can you provide logs?

Just boot from microsd and then use armbian-install to move image to spi/nvme directly attached?

We don't support 3rd party forks. Ask at the place where you got this OS from.

Because they sell you the hardware only. Their software support is very poorly made since for the price they cannot afford proper software support and - even more important - maintenance. They leave this burden to - mostly unpaid - random developers across the world like us. At least I'd go for a device with Standard Support which the Ultra and Max hasn't: https://www.armbian.com/download/?device_support=Standard support For the raspberry you would need additional hardware (an AI kit I guess). No clue though about how they both perform in comparsion. For RK3588 you have two choices for now: The rockchip bsp implementation and https://github.com/rockchip-linux/rknn-toolkit2. Or using 6.18 kernel using the reverse engineered Rocket driver and latest bleeding edge mesa to get npu access. I personally did not play with either of these options and have no intention to do so for the moment.

Not all possible kernel-userspace combinations are built and/or exposed. If you cannot find what you are looking for, DIY: https://github.com/armbian/build/