Werner

Try with armbian-config -> system -> other

Correct. Ubuntu and Debian userspaces are incompatible.

moved

moved

Maybe the mirror in question was syncing at the moment. If EU works fine other should as well after a bit of waiting.

Also possible but not recommended. https://docs.armbian.com/User-Guide_Getting-Started/#how-to-upgrade-distribution-like-focal-to-jammy-or-bullseye-to-bookworm Keep in mind that Bullseye will continue receive userspace upgrades until "roughly July 2024 to June 2026": https://wiki.debian.org/LTS

Yes. Simply build the kernel for your board, then go to the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } output directory and copy the needed code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } .deb files to your board. Then install them there via code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg -i ...

Search function is your friend

apt repository does not offer 23.05 packages (yet). Risk of break existing installation is too high so shipping is delayed or skipped entirely until 23.08 is released. However you can always use the build framework to create your own set of firmware packages and install them via dpkg. https://github.com/armbian/build/

moved

I did not look at them since I am not a developer. I just gave you the hint that your chances increase when providing proper logs so anybody can volunteer to help.

Cannot reproduce. First thing I did when I received mine was install on NVMe. So verified working. As NicoD mentioned there needs to be a partition created on the nvme beforehand, then armbian-install detects it. Select boot from MTD and let it flash SPI which takes a while. After power off remove sd and power on again. Boots.

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

moved

Repository is unfortunately still behind due to issues we are continuously facing. Two possible workarounds: Use an older release for now (check archive) or use the build framework to create your own image which headers pre-installed.

docs are most likely behind due to lack of maintenance (feel free to contribute!). Docker wants cgroupsv2 which have been introduced in kernel 4.15.y 4.9.y is vendor kernel which might work better but is outdated and unmaintained:https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

merged

Docker needs some kernel stuff that has been introduced after 4.9.y was released. So the only way is to run a more recent kernel which probably does not support all hw features the board has to offer.

moved

You can try to edit /boot/boot.cmd. Search for the line starting with setenv bootargs and add this at the end. Then recompile the boot script with the command mentioned at the end of this file.

No.

We cannot provide images in each and every kernel/userspace constellation for each and every board. Necessary storage and traffic are huge already. You can use the build framework to creat images as needed: https://github.com/armbian/build

No idea what you are talking about. You are aware that this is Armbian forums that handles topics around Armbian, right?

code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg-reconfigure locales to make sure en_US UTF8 is available and set default code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg-reconfigure keyboard-configuration should do the rest

should be here: https://github.com/armbian/os/blob/main/targets/default.conf