Werner

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

moved

moved

forums will receive a major version bump by end of the year. probably including re-arrangement of forums and also sync tags again since there are more to add. What the term "standard support" means: https://docs.armbian.com/contribute/board-support-rules/#standard-support

smells like tvbox

moved. I assume card = sbc?

moved

There are clearly two uboot versions in the log, so one is pulled from something else than sdcard which is the problem. either those or the underlaying ddr blobs don't like each other causing problems. rockchip socs have a fixed boot order which always begins with spi. if a boot loader is found there it will be used. it may not be obvious to the user because it passes basically just on to the next one. However this often causes problems.

wipe spi and retry

https://docs.armbian.com/user-guide/faq/#why-is-my-image-not-listed

Something hadn't changed. I still have no idea what you're talking about. Btw. caveman is a real thing: https://github.com/JuliusBrussee/caveman/blob/main/skills/caveman/SKILL.md

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

bleedingedge is not meant to be used as end-user but for developers only. Use "current" if you prefer stability over breakage.