Werner

zero2 != 2w moved to staging

Even though current is an LTS kernel it probably makes more sense to focus on vendor an edge. vendor because its rockchip bsp and close to being feature-complete. And edge for likely becoming the next LTS kernel which ultimately become current at some point. You can try to see what actually works on current at this time. You can ignore 6.15-6.17 since those patches, if still present, are for archival purposes only and will be remove at some point. In theory it could be re-used but may introduce confusion. If in doubt, copy and rename. Edit: Seems like lots of stuff has been mainlined already. So I suggest shifting your primary focus on edge.

If you need an image without desktop, there is always the build framework which allows you to build any combination of kernel and userspace and desktop you want.

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

Yes, that's correct. Didn't pay attention. Thanks.

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

Have you installed the proprietary mali blobs? https://github.com/tsukumijima/libmali-rockchip/releases/download/v1.9-1-2131373/libmali-valhall-g610-g24p0-gbm_1.9-1_arm64.deb

I think this is wrong. The overlay needs to enabled if there is an m2 sata ssd connected. However in this case we connect a pcie device which connects to a chip that multiplexes the sata devices. tl;dr: try disabling this overlay

Hi, my first step would be comparing the opp nodes in the device trees of both Armbian and any other distro that allows the faster speed. Perhaps the necessary node is just missing.

debug boot issues and provide logs: https://debug.armbian.de

Perhaps package dependencies need to be adjusted so the installation order matches the requirements? Cannot help there though, I have very little insight.

Yes That's on us

Same answer and further reasoning as here:

better in which way? performance? driver support? size? from our pov the better the support conditions, the more likely to recommend. https://www.armbian.com/download/?device_support=Standard support Is one platinum? Go for it? If not, check standard support. If one is in this category, go for it. If not, check further down for community support.

Yes. In the past everything was added as patch. The problem was (and still is for other reasons) that some patches modifying a dt build on top of each other or stuff breaks. Now the dt can be edited directly and using git blame it is documented who edited what for whatever reason. Of course sometimes there is an almost perfect dt upstream that needs minor adjustments. Those can be perfectly fine done with a patch. Also both patches and our dt files only stay for as long as there is no proper equivalent upstream. Once everything is in mainline they are no longer needed.

Agreed. A check if the package is installed (and if not install it beforehand) would be sufficient too. PRs to fix this are highly appreciated. https://github.com/armbian/build/blob/main/packages/bsp/common/usr/bin/armbian-install

I suggest to retry later

I suggest to build desktop images with code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ENABLE_EXTENSIONS=mesa-vpu to have necessary stuff built-in automatically.

We're aware that our documentation isn't great (also about adding new hw: https://docs.armbian.com/Process_Contribute/#adding-a-new-board) but it is hard to find time for such tasks when we're crowded with other stuff already. The file extension defines a boards support status. https://docs.armbian.com/User-Guide_Board-Support-Rules/ Anyone can add .csc boards. For dts files we have dedicated folders to avoid having a patch necessary for them: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.12/dt https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18/dt

Depends on your use case. If you need raw cpu power, better gpu or video processing, Go for RK3588/s based board. If you heavily rely on GPIO and its functions (PWM, I2C,...) go for RPi.

Did you check already merged PRs which were adding new boards? Like https://github.com/armbian/build/pull/8754/files Should give some clues.

I wasn't talking about dmesg logs.

Did you make sure they're actually loaded? Like by checking uboot boot logs via serial console?

There is a minor difference in another node: "phandle = <0x2c2>;" in radxa.dts and phandle = <0x2c3>; No clue if that's the culprit or if there is something on software-side to make fan work.

debug boot issues: https://debug.armbian.de This board is community maintained, therefore Armbian core team does not monitor its status. May be broken, may not. We don't know.