Werner

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.

Updates are published via our own apt repository. Those packages are generated with the same build framework you can find on Github plus some additional scripts which are there as well (probably in a different repo though). Maintainers can trigger an update to publish a new kernel version so end-users can update with a simple apt upgrade.

Wouldn't be the first time that an image for board X just works on board Y because they were close to identical hw wise. Easiest would be to simply try and check if it actually boots and which functions work and which not. Feel free to give feedback in that matter. Armbian does not accept new boards by themselves without funding. However anyone can step up and add support to the framework via pull request. Examples are here: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

Mainline support for rk3588 is far from being feature-complete. 6.10 was moved to current because basic functionality is given and to make room for 6.11 which for once comes with more stuff (maybe ap.... is already there? try edge) mainlined and also might become next LTS kernel. If you need most features to work you have to use vendor kernel for now. Also you can try to port this overlay to mainline: https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr3/arch/arm64/boot/dts/rockchip/overlay/orangepi-5-ap6275p.dts

moved to userspace neither a tutorial nor a review

If armbianmonitor script is not present on your OS it is either VERY old or not a genuine Armbian image. Since Focal is just a few years I guess latter or it has been removed. Anyway grab the script from here, set chmod +x and ./armbianmonitor -u https://raw.githubusercontent.com/armbian/build/dfe8fc39e84f77718a86ab587b6851d872942e91/packages/bsp/common/usr/bin/armbianmonitor

If there is a dedicated image for rock pi 4 se and the board says rock pi 4 se this should be the correct one. How to debug boot issues: https://debug.armbian.de

Using punctuation marks reduces annoyance when reading. Which guides? Which tvbox? vendor? type? soc? specs? which img file? Insufficient information.

You have quite some mix-up in your system. You are running vendor, trying to install something from current (why?) and also still some legacy packages. interferences are expected. I suggest home housekeeping.

Hi, we do not deal with Android and nobody here will be able to answer questions in this direction.

moved. neither a tutorial nor a review. Check if the user you are using has permission to use docker (usermod -aG docker yourusername) Alternatively use PREFER_DOCKER=no

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

Is the emmc soldered on the board? I don't know this board in particular but it might be simply just sit in a socket.

moved to userspace

Do you have any chance to show us debug uart logs when trying to boot those? Check the link above to get a video on how this works if you don't know.

I wonder why these images even exist. AFAIK support has been added by Joshua for vendor only...