Werner

I am not sure if this isn't a hint from ages ago when boards used phased-out 3.14.y kernel....

Moved to Common issues / peer to peer technical support since it is untested 3rd party hardware

which camera?

Check /etc/default/armbian-zramconfig or whatever the file was called.

Perhaps increase boot verbosity like suggested in the documentation. https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-verbose-boot

Moved to Common issues / peer to peer technical support Duplicate topic has been deleted since it would have been an invalid issue report anyways and posting the same issue in multiple places is considered abusive behavior.

As you may can guess nobody has a second sight to know what is wrong. Having such a thing is absolutely mandatory for debugging boot issues. Thankfully they are quite cheap and can be picked up for just a few bucks.

Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

Feature request declined. https://docs.armbian.com/User-Guide_FAQ/

IIRC Bullseye has been promoted to stable already. Strange...

Best way to debug boot issues is using a serial adapter to get an idea what is happening inside. You cannot rely on HDMI output if available at all.

That is how I always did that...

Hm odd. It seems like overlay support is completely gone or I am blind...

You do not even need to do extra saving via ^O since nano will ask if chances should be saved when trying to exit

There is no dedicated maintainer for this board and if we don't find one within the next few weeks support will be dropped. https://www.armbian.com/newsflash/armbian-needs-your-help/

https://www.armbian.com/newsflash/armbian-needs-your-help/

Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)

Don't hijack random topics. https://www.armbian.com/bugs/

OC is not enabled by default but you can simply enable is via armbian-config.

As long as the mentioned board is officially supported yes. Otherwise common issues/p2p help is the correct place.

Boots fine: http://ix.io/3Bo9 Try different sd card, PSU, cable. Make sure to check armbian.com/bugs That is typical speed for sunxi boards. Rockchip SoCs however using 1,5Mbaud.

For that reason (edge kernel) and missing logs your issue report was invalid anyways so you are lucky that someone answered.

ii linux-dtb-edge-rockchip64 21.11.0-trunk.21 arm64 Armbian Linux DTB, version 5.14.9-rockchip64 edge ii linux-image-edge-rockchip64 21.11.0-trunk.21 arm64 Linux kernel, armbian version 5.14.9-rockchip64 edge Images/kernel packages built from source/nightly are not supported

Considering this a TVbox might not the best choice for you since there would be lots of frustration. If you want an ARM board with well supported SoC I'd recommend something with RK3399 onboard. Yeah it is slightly older and there is a new generation of Rockchips now but remember that development for ARM is still rather slow and it takes several years to get a chip almost fully functional. The Station P1 (which in a nutshell is a T-Firefly RK3399 ROC-PC PLUS board in a fancy case) is working quite well in the meantime and @balbes150 is actively supporting it. Yes, it is also a bit more expensive but you get is what you pay for. Having Debian on it you can use it as PC and installing Kodi will give you TVbox "feeling".

Maybe this is helpful:https://github.com/armbian/sunxi-DT-overlays/blob/master/sun8i-h3/README.sun8i-h3-overlays