Werner

The driver seems to be already included. If I check my kernel (vendor rk35xx) config I see CONFIG_VIDEO_OV13855=y.

Alright, didn't know they are still there. Well as mentioned media won't receive any further updates since all functionally is merged into standard branches. Anyway, Rock64 is rk3399 I think and you should be good to go with mainline kernel, either current which is 6.12.y or edge which is 6.14-rc7 atm. The branches at https://github.com/armbian/linux-rockchip are made from Rockchip BSP code and mostly for rk35xx socs. I don't think there is much work there for rk3399.

moved Where did you get those? media branch has been abandoned for over a year now.

moved

Hi this warning tells you that it is up to you to do a risk assessment if you are fine with the fact, that the device's status is unknown to the Armbian team, that it may break with an upcoming update or never receive an update at all.

Alright. Yes, there seems to be some issue with the naming of the overlays which required editing armbianEnv by hand. It is hard to keep up with the continously changing world of SoCs and kernels where latter, especially on mainline, often even lacking basic overlays since close to nobody deals with this.

As guessed you did not switch to vendor kernel and tried using a vendor kernel overlay with mainline kernel. But glad you figured it out what changes are necessary in order to make it work. Feel free to send the working overlay the build framework so it is included by default. mainline still lacks lots of overlays.

moved

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

These overlays are most likely not made to be used with mainline kernel. I suggest to retry with vendor kernel. Standard overlays for it have been pushed yesterday:https://github.com/armbian/linux-rockchip/pull/345/files

moved

moved, edited

excerpts are useless. Provide full logs with the curl command suggested.

Try oldarchive https://fi.mirror.armbian.de/oldarchive/helios4/archive/

https://github.com/armbian/build/pull/7902 Support is there AS IS. May work, may not. If latter, feel free to fix it and send PRs.

Try it calling by its correct name: armbian-config

Check archive.armbian.com

AFAIK armbianinstall expects an empty eMMC without partitions. This should be easily achievable by overwriting the first few sectors of it. Like dd if=/dev/zero of=/dev/mmcblkX bs=512 count=1 A reboot might be required to make the OS aware of the altered partition table. Then retry installing.

You already did by opening this topic.

Could you check if CONFIG_NLS_ISO8859_2 is enabled in your kernel config? The package is locales I think. That it is not installed tells me you are most likely using a Minimal/IoT image which comes with the absolute bare minimum to have a working system. Designed for advanced users knowing how to install such tools afterwards if needed.

None I am aware of. If you find something feel free to share. Regressions happen all the time.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

since you do not state what exactly you tried the recommendations will probably match those attempts but well, your time. Use armbian-config to enable/disable overlays.

This is how to properly provide logs. Cannot reproduce the issue. Build works just fine: https://paste.armbian.de/otajagegij https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.05.0-trunk_Rock-5b_noble_vendor_6.1.99_gnome_desktop.img.xz My best guess is there is some issue reaching the repository due to firewall/vpn.

Not via armbian-config. This is just a very simply way to do an initial setup. Here is the code that basically happens behind the scenes: https://github.com/armbian/configng/blob/main/tools/modules/software/module_nextcloud.sh So nothing fancy. just a docker run command. I personally prefer using docker-compose.yml instead of endless docker commands. Stuff is well-arranged and after adjusting like mounts down, up and ready to go. As mentioned above for customized installation please refer to the origin of the nextcloud container linuxserver.io. I am pretty sure they have examples for docker compose as well.