Werner

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

You probably have to replace base-files package.

Depending on your location this might not be anything that can be fixed on Armbian side. If this happens on any mirror, the issue is either your setup or ISP blocking access.

Tried this way? https://docs.armbian.com/User-Guide_Autoconfig/

How to debug boot issues: https://debug.armbian.de

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

Provide full logs

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

vendor kernel has rknpu enabled by default. edge will receive initial support for it (called Rocket then) with 6.17 iirc.

moved to tvboxes

Then you should stay with edge for now. current will only receive critical and security fixes due to its LTS nature.

moved

There is only amd64 download as far as I can see. Yes, browser compilation takes crazy amounts of memory and computing time.

There is no official support for offline work. You can try OFFLINE_WORK=yes but no clue if it still works.

./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble ENABLE_EXTENSIONS=mesa-vpu or something like that for an image with this extension built-in. There is no method to install this on a existing system (yet).

https://docs.armbian.com/Process_Contribute/#adding-a-new-board

For those we cannot and will not help. This is a fork which uses the name Armbian without permission and does not contribute to the core development process. Ask at their place for help. For the leftover: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -u would be a good start.

Maybe the mirror isn't good at this time. You can work around by choosing any mirror from this list and add it to your armbian source list: https://docs.armbian.com/Mirrors/

Ah, I misunderstood. I thought does not appear at all anymore but the question was about manual call. Has been answered properly already.

If there is no overlay available you may need to write one by yourself. I'd start by modifying the device tree itself and set the port in question to host and see if this actually works. I think armbian-config comes with a device tree editor. Make sure to make a backup beforehand.

moved to off-topic we dont support 3rd party os.

To 1.) it is only displayed if the first boot assistant is not cancelled before user creation. To 2.) You should find some clues here: https://github.com/armbian/build/tree/main/packages/bsp/common/etc/update-motd.d

Cannot reproduce: root@pihole-v2:~# apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Hit:5 https://github.armbian.com/configng stable InRelease Get:6 https://armbian.atomonetworks.com/apt bookworm InRelease [54.1 kB] Get:7 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils all Packages [10.4 kB] Get:8 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils arm64 Packages [205 kB] Get:9 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils arm64 Contents (deb) [55.9 kB] Get:10 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils all Contents (deb) [36.1 kB] Fetched 362 kB in 3s (143 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@pihole-v2:~# cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop

Hi, there are some pending changes to uefi config, not sure if they would affect you: https://github.com/armbian/build/pull/8377

I assume it is some debugging left-over. Dealing with sbc families and sunxi in particular it is a ongoing fight against regressions and having a debug kernel can help to identify such. It is not ideal having this on end-user sbcs enabled but to limit resources we cannot afford having two current branches with and without debugging. If this is an issue for you, you can always use the build framework to build your own kernel package with adjusted kernel config disabling traces.