Werner

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.

unreadable walls of barfed ai stuff

I recommend using "caveman ultra" skill to reduce the barfed out walls of slop

Hm. It MAY not work because the upper layer (patches/u-boot) to say has no patching config for this particular board, but just guessing. Try this way: https://github.com/armbian/build/compare/main...EvilOlaf:build:sunxi-uboot-config-sample patching config ensures recognition of plain dts and defconfigs and copies them into the source tree before compilation. The defconfig I put in there is just a sample.

Yes, must be copied. deb is touched when the expected build output is identical to artifact. force rebuild by adding ARTIFACT_IGNORE_CACHE=yes switch

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

send a pr if you want to have this included

this board is community supported and I assume nobody took the effort to create an overlay for mainline kernel yet. feel free to do so.

do you post anything beyond unreadable slop?

i suggest to open an issue against imager repo on github. but yes, onboard sd readers are sometimes tricky. I believe I had a similar issue with either etcher or usbimager years ago

moved. feel free to send pr

moved lacking proper format for a tutorial broken links foreign language

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

Hi. If those changes are compatible with other hw (for example you are adding a new driver) these changes can be sent to https://github.com/armbian/linux-rockchip If your changes are likely to break other boards, then the better way is to create your own family, hence having independent kernel packages with different name. Example: https://github.com/armbian/build/blob/main/config/boards/recomputer-rk3588-devkit.conf Which refers to https://github.com/armbian/build/blob/main/config/sources/families/seeed-rk3588.conf This will also allow custom kernel config: https://github.com/armbian/build/blob/main/config/kernel/linux-seeed-rk3588-vendor.config It is not ideal to have a individual family for a single board but sometimes the hw is very customized, breaking other implementations, making this necessary.