Werner

https://debug.armbian.de

unsupported build environment. As per documentation Noble is supported only. there are a few others "whitelisted" known mostly to work in the scripts, Zena hasn't yet. Check if your user has access to docker (usermod -aG docker yourusername) and check if docker run hello-world runs properly.

Probably because nobody had use for those until today. Feel free to send a PR adding whats missing.

https://www.armbian.com/download/ https://github.com/armbian/os/releases https://github.com/armbian/community/releases

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

diy image and you get it immediately

no clue. needs testing. perhaps it just works. kernel sources are the same as rpi os.

There is none. Its csc device. Community supported. You are community

moved

You can set conditions on which branch uses which uboot. Like this: https://github.com/armbian/build/blob/9aa6e1e29ec2d397bbe223bebaa93bd13ef79818/config/boards/orangepi5-max.csc#L21 If the BRANCH is edge, then use mainline uboot, specifically this tag.

You can create an extension including something like unset armbian_kernel_config__force_pa_va_48_bits_on_arm64

Hi While I thiknk your approach should have worked, a quick search revealed that something similar is done for a different family. Perhaps try this way:https://github.com/armbian/build/blob/9aa6e1e29ec2d397bbe223bebaa93bd13ef79818/patch/kernel/archive/filogic-6.16/patches.armbian/0007-build.sh-add-additional-build-script-config-defconfi.patch#L1909

Related answer: https://forum.armbian.com/topic/57601-missing-headers-for-618-kernel/#findComment-232075

There are no header packages for each and every trunk version to save resources. Most simple solution is probably DIY an image with INSTALL_HEADERS=yes to have them shipped with the image.

Feel free to reach out and become a partner: https://www.armbian.com/partners/

https://docs.armbian.com/Developer-Guide_Build-Switches/ Check for ARTIFACT_IGNORE_CACHE diy packages are locally cached. automated packages from the CI are stored online in ghcr. not only this, also the status of build framework internals (like stuff in https://github.com/armbian/build/tree/main/lib/functions) since they also can alter a package. "development" should be sufficient.

You can switch to beta to get faster updates, though they're untested autobuilds, so if something breaks, you have to unbrick yourself.

I like your kind of humor

Should be there. https://github.com/armbian/build/blob/00b6e17abfd859893a39f6445715a3327fed150a/config/kernel/linux-meson64-edge.config#L355 https://cateee.net/lkddb/web-lkddb/IP_NF_IPTABLES.html

Actually not really strange but a measure for spam prevention.

We don't have intention to support this board without funding. However anyone from the community can step up and add support for it.

your sbc has only 100mbit nic

The boot partition presence doesn't depend directly on the Armbian version—it's determined by the board configuration. Some configs enable an extra boot partition, especially for boards using older U-Boot versions that can't boot directly from ext4. As a result, even for the same board and Armbian version, different branches (e.g., legacy, vendor, current, edge) may behave differently. Vendor branch might use an old BSP U-Boot requiring the extra partition while mainline branch uses newer U-Boot that boots straight from ext4.

would you mind sending a pr or even upstream this change?

ah yes, you're right. Well homassistant seems to depend on docker, so if the docker issue is resolved, hass will probably work too. Though no clue what the issue with docker is. Since it is an issue with configng, I suggest to report directly here: https://github.com/armbian/configng/issues Don't forgot to be as verbose as possible when reporting. Will raise chances getting it addressed sooner