Werner

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

You can force output to terminal when using -U instead of -u with armbianmonitor. Copy everything to a paste service like paste.debian.net or paste.armbian.de when paste.armbian.com doesn't cut it

Hi, this is not how it works. Any changes you do to the source cache are void once build starts to ensure they are clean. For customizing the config I suggest to either use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } KERNEL_CONFIGURE=yes so you will be asked for modifications or use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } kernel-config code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; build command to output a custom kernel config file without building. For modifying the sources use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } kernel-patch or boot-patch commands. This will pause the process once all given patches were applied and asks you to do modifications to the source (from a different terminal window or whatever method you'd prefer). When being done it will compare and create proper patch files from your modifications. This and more you can read in the docs: https://docs.armbian.com/Developer-Guide_Overview/

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.

https://forum.armbian.com/topic/6617-the-purpose-of-this-subforum/#comment-50149

https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel

We cannot support 3rd party OS. State your questions here: https://github.com/Joshua-Riek/ubuntu-rockchip/issues Armbian Though it is not uncrashable. Because no distro could every be, especially for this soc. Basically all distros available using the same vendor bsp, some are even built around Armbians modified sources (just like Joshuas images).

Check the video, there are a few mentions of good uart chips. I don't remember.

AFAIK NAND support never made it upstream. Therefore its support was lost when getting rid of stone-age 3.14.y bsp kernel. Either life without NAND or dig deep in the archives to find a very old image that still has this old kernel.