Werner

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.

Seems missing in kernel config. Feel free to send a PR and enable the module.

./compile.sh BOARD=orangepizero3 BRANCH=current RELEASE=trixie BUILD_MINIMAL=yes KERNEL_CONFIGURE=no https://docs.armbian.com/Developer-Guide_Build-Preparation/ replace BRANCH with edge if you prefer more recent kernel. replace RELEASE with noble if you prefer Ubuntu flavour. remove BUILD_MINIMAL=yes to get the choice to build a standard cli image instead of minimal/iot.

Hi, difficult task since there is no support for the whole chip family in the framework yet, but first steps are here:https://github.com/armbian/build/pull/8364 I suggest to start by getting familiar with the framework and how the mentioned pending pr it put together. moved

Switch to edge or vendor kernel (latter either with panthor overlay or proprietary mali blobs). current is a bad choice for desktop usage.

Not planned but should be possible. A good start would be to copy the mentioend 2f and extract the device tree from official image and add it to vendor kernel source. If you're lucky that's all what's needed to get it to work.

moved to offtopic. not using Armbian. If you need support with that image, ask at the place where you downloaded from.

RTL8211F is the interesting label.