Werner

Example for adding a new board with already existing board family: https://github.com/armbian/build/pull/9456/changes

Maybe. Trunk are untested auto-builds and support for this board is from the community. Its functionality is unknown to the Armbian team. Get serial console logs. This makes investigation way easier.

Feel free to use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=nanopineoplus2notsurehowitsnameis BRANCH=current kernel-config and then build a kernel packages with the adjustments. Once installed and tested, you can PR to these kernel config here: https://github.com/armbian/build/tree/main/config/kernel

I suggest to ask directly at kali forums/chat/whatever they provide. We offer Armbian images with Kali tools pre-installed. However about their usage we cannot help

moved to staging

The max clock is most likely limited via opp table in the dts. H6 should clock up to 1.8ghz, yes, but there might be a reason why this board does not.

Hi, this might be prohibited until you made a few manually approved posting to be moved from Validating to Members group. This measure is necessary to keep the forum clean from spamers who try to spread their bs here on daily basis. So I suggest to stick around for a while, this should resolve itself.

Module name is "ip_tables"

logs are incomplete. dmesg is missing completely which would be the most relevant. moved to staging

https://github.com/armbian/build/blob/b8eab09ef561f2d03956098d26351d323a3b2d7b/config/kernel/linux-meson64-current.config#L355 Check your /lib/modules directory if it is present. It should be.

Why would you use an image for the Zero 3 for the 5B? You cannot simply shove an image for a random board into yours and assume it works...

just tested with a clean image, featuring 6.18.y and works just fine. This may be an issue if your setup is quite old, because at some point upstream changes caused Armbian kernel to break IIRC and this was worked around. The warning is persistent but doesn't actually matter. Please verify that a clean system boots normally.

hard to tell without any logs whatsoever

[ 5.092655] CPU1: failed to come online [ 5.092666] CPU1: failed in unknown state : 0x0 [ 10.217311] CPU2: failed to come online [ 10.217324] CPU2: failed in unknown state : 0x0 [ 15.341948] CPU3: failed to come online [ 15.341961] CPU3: failed in unknown state : 0x0 Yes we're aware of this, since it affects all H5 and H6 devices. We have a few ideas about what could be the cause like added logging (yes, sounds odd but..oh well) or certain ATF version. https://github.com/armbian/build/issues/9555

moved to off-topic since not directly related to armbian.