Werner

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

I suggest to use the "Follow" button instead.

https://debug.armbian.de

Why do you need an old kernel version while this driver is upstreamed into mainline Linux? https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/fbtft?h=staging-testing Build your own image, and use kernel configuration to enable them if not there already.

Maybe latest isn't latest stable but latest beta

At the end of each build, regardless if successful, there is a code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } curl command which uploads the build log to a paste service. Use it and provide us the url.

With code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config you can select available kernels from repo.

moved to off-topic. You are wrong here. We neither deal with phones nor with Android or any of its derivatives.

Please provide full logs

Debug boot issues: https://debug.armbian.de Some folks tend to make things unnecessary complicated

Hi, in order to have a board evicted from stating some requirements must be fulfilled which are listed in the link I mentioned above. Building Armbian is fairly easy. You can find information how to do that in the documentation as well.

Certainly. Here are the requirements: https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support

Just tried the two images under Standard Support button and download works just fine. You can also check directly on mirror: https://fi.mirror.armbian.de/dl/orangepi5-plus/archive/

Try this: verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-pi-s.dtb extraargs=cma=16M rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b rootfstype=ext4 overlays=s0-ext-antenna spi1-spidev spi2-spidev usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u For once the prefix is already set and for the other IIRC it is just overlays instead of fdt_overlays. But not sure. Overall there might be a bug in config-ng with overlays. Just need to verify that manual applying works.

Check if wireguard is present under code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } lsmod Also check your logs (journal, syslog,...) which should tell you something about why things fail.

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

Is the wireguard kernel module available and loaded?

If you use bleeding edge software issues are expected. Try 6.1.y kernel. Also take note that there are two versions of this board on the market. 1.1 has known issues with ethernet. Broken by design. Only fixable by software to a certain extend. Blame vendor.

Debug boot issues: https://debug.armbian.de How Home Assistant is merged while building: https://github.com/armbian/os/blob/main/userpatches/extensions/ha.sh I suggest to try an unmodified image for the S0 and make sure that boots fine.

Sounds like, yes. Model 5 and 5 pro have the SoC in common but nothing else. Therefore discussion about pro in this topic is off-topic anyway.

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.

Did you solder your SPI properly? The 5 pro does not come with by default

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

Defaults are in /etc/skel