Werner

If you have patience, CEC may work at some point with mainline kernel. There is not fast solution.

didn't even realize you were on beta repo. Well when you use bleeding edge, you have to be prepared for breakage since it is expected ;).

I'm not sure bit IIRC there should be a 1 second delay which would allow interaction but again, not sure...

We don't deal with android. I suggest to ask at xda developer forums or similar.

Just a wild guess: The code from orangepi wiringpi is old and no longer compatible with newer python which is shipped in Trixie.

No clue

Nothing strange there. The wireguard package comes from trixie which has dependency to debian's own kernel packages. The package cannot know that there is wireguard kernel-wise already in place or even know about Armbian kernel packages. So this is kind of expected. However I think at some point Armbian kernel packages included a apt information that it provides wireguard. Not sure about the status there.

merged. forum tag added.

There is no need to install "wireguard" as all Armbian images come with this kernel module by default. All you need is the userspace tools (if not installed already) from "wireguard-tools". If necessary try installing with "--no-install-recommends".

Different soc and even different soc family. This most likely will not work on h618.

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.