Werner

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

what? armbianmonitor -u

For docker you don't really need armbian-config to install. Just do code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt install docker.io and code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } usermod -aG docker yourusername (if you want as non-root have access to docker). That's it. OPi PC2 is armhf, so 32-bit while it seems that homeassistant requires arm64, so 64bit system. Therefore this won't work.

did you even research what all these switches do? NEWPKG does not even exist, SKIP_EXTERNAL_TOOLCHAINS was removed recently and KERNELBRANCH is ususally a specific tag and EXPERT....well...are you?

moved Cannot reproduce. Download image works just fine https://dl.armbian.com/rpi4b/Noble_current_minimal outdated tag, unsupported

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

moved

We have hundreds of releases and multiple per version per board hard to tell from this which kernel or which exactly i make a wild guess and the kernel you tried is 6.12.y which isn't good for desktop. try 6.1.115 (with mesa-vpu extension, not sure if there are pre-made ones) or 6.18, 6.19 mainline kernel.

Alright, well, such things can happen when attempting to fix a bug and not having hw to test on hand I'll leave it to Cornelius to send a fix since he can directly verify if it works.

Oh great. Then I'll steal borrow your dts and replace the one currently in the framework later

on which kernel did you test?

I tried integrating the suggestion into the actual device tree. Feel free to test: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.64_minimal.img.xz

mirrors/repo are degraded at the moment. We're aware and working on it.

If that worked for you, then you're lucky. For me it did not (other board tested). I guess the files on there have an older state which is still good. Again, as mentioned, repo is being worked on and we're aware of the issues and trying our best to resolve this asap.

I suggest to try kernel-patch build command. Your changes then are compiled into a patch which is then applied to the kernel source before building.

duplicate