Werner

Nobody I guess. We don't deal with Android.

Try this: Remove armbian-bsp-cli-orangepi5-plus-legacy and install armbian-bsp-cli-orangepi5-plus-vendor legacy is deprecated

moved to tvboxes

If there is a "pi" user present the image is fake.

I don't know. Maybe the 4 amps the original PSU provides are sufficient in theory but the voltage breaks down early leading into issues. You could get one of these cheap usb voltage meter thingies if you don't have a proper multimeter at hand. If voltage breaks below 4.9 to 5V issues are to be expected.

May not be enough. It seems like you run a full fledged DE on it which also means you most likely have peripherals connected like mouse, keyboard and so on. I have an 5+ with NVMe here as well and runs stable. No desktop though. Also I use an industrial grade PSU for all my SBCs that doesn't break down easily and can be adjusted to compensate for losses across connectors and wiring.

moved to off-topic we neither deal with windows, chrome os nor android.

Try adding legacy as kernel target to the board config of your desire and use BRANCH=legacy then. If something doesn't work you are on your own since this is not supported.

https://docs.armbian.com/Release_Changelog/

https://forum.armbian.com/topic/45248-wireguard-borking-system

Odd. I have an OPi5 with nvme and vendor kernel as well and it survives reboots. It is not up to date though. Also cannot check on which version it is atm.

Upgraded in which way? Jammy? or earlier Armbian release?

ah. good old omv annoyance. Known to mess up the system....

Are you sure you tried this with "wireguard-tools" package and not with plain "wireguard"?

If there is no pre-made OMV image you can create your own just like mentioned under DIY at the very first post of this topic. Also check the few posts after for copying the necessary extension if necessary.

Can you share full logs? Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Do you have an old OPi3 or the LTS variant? They differ in network chip on the pcb. Please verify you are using the correct image for your board.

Just guessing. Sometimes armbian-install seem to fail to populate /boot or the UUID of the nvme is wrong. Try this: clear mtd and nvme, boot from fresh image from microsd, maybe remove emmc if not needed. Do armbian-install and let it move OS to nvme and flash spi. Do not reboot. Mount the nvme again somewhere and check if /boot is populated. If not, copy everything manually from microsd/boot to nvme/boot, then use lsblk or similar command to get the uuid of the nvme and edit the freshly copied armbianEnv.txt to match the uuid. If /boot on nvme is populated already make sure the uuid is correct. Then shutdown, unplug, remove sd and power up again. For best chances debugging boot issues set verbosity to 7 in armbianEnv.txt and check the video at https://debug.armbian.de

I still believe a simple "apt-get install --no-install-recommends wireguard-tools" does the trick as well but I have no option to test this atm.

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.

Besides archive there will be old-archive available on a just a few mirrors. However this is not ready yet.

I think so, yes. As mentioned Armbian kernel comes with wireguard module pre-installed so nothing besides the userspace tools is required IIRC.

Ah yeah, now I know. You are installing with recommends which might include wireguard and wireguard-dkms packages which have dependency on stock Debian/Ubuntu kernel which then will be installed and render your system unbootable.

Without proper logs this hard to track down. Try to grab some actual logs when you get a chance: https://debug.armbian.de Wireguard is - kernel-wise at least - nowadays included in all Armbian images. However it might be necessary to install userspace tools separately (i.e. apt install --no-install-recommends wireguard-tools), especially on minimal images.