laibsch

suggested solution is to move to kernel 6.18

Probably the latter. https://docs.armbian.com/User-Guide_Board-Support-Rules/ has more information. We already have a lot of boards in Armbian. Probably too many from a maintenance POV. Do you simply want to do the work of bringing up your board in Armbian or do you want to become the maintainer of this board going forward? That's an artefact that @Igor may be able to fix. The page should not really exist at this point.

Thank you for testing!

Thank you for sharing these!

well, so it does indeed sound like you DO have network issues on the Odroid N2+. Something related to the network is not working right in noble for you.

People are already helping you. But, they're mostly helping you to help yourself. One thing you can do to make it easier for people to help you is to add the SHARE_LOG build switch to ./compile.sh. That way your build log will be uploaded and you can share the link here.

FWIW, the file in question is available from the mirror. Are you sure you do not have network issues?

ping @chraac, do you have an idea?

That's surprising. All I knew so far was that modules need to be present, either built-in or as dynamically loaded modules. Do you have a reference for this anomaly?

Those are super cheap maybe a dollar if shipped from Asia and an absolute essential tool for debugging. Get yourself one. http://debug.armbian.de

Hello and thank you for the problem report. What solution did orangepi.org provide for you? As you can see, nobody in the Armbian community was interested to step up and support this board and from what I have heard through the grapevine this is because of the poor support that orangepi.org gives to FOSS projects and communities such as armbian.com. Armbian has already pushed another update for Sunxi64. Maybe you are in luck and the problem is already fixed. If not, we are happy to accept a PR once orangepi.org has published a solution.

Thank you for the kind words.

$ grep TARGET config/boards/pine64.conf KERNEL_TARGET="current,edge,legacy" KERNEL_TEST_TARGET="current" So, you can compile either current, edge or legacy for your board. Stick the desired string in the BRANCH switch and off you go. What kernel that is depends on the board or board family and in your case you can check config/sources/families/include/sunxi64_common.inc to find that as of today edge=6.16, current=6.12 and legacy=6.6. So, 6.2 to 6.5 is not an option. But you could always go back to an earlier git state of the build framework or add your own targets. Why do you need those specific kernels?

I think you are looking for the "kernel" build command. Have a look at some of the others as well like kernel-config or dts-check.

Thank you for sharing your findings with the community!

thank you for your work, @Nick A Is this being pushed back to Armbian itself eventually?

Thank you, @Mangix. We bumped u-boot to v2025.10 for Helios, so I would assume those commits are already incorporated, aren't they? I have only looked at commit dates, not actual code.

Well, that makes me wonder how you were able to verify successful flashing with the broken adapters as you were upset we even dared to ask if you did... Maybe reconsider your tone for next time? As it seems the initial request to make sure you had no issues with your storage - one way or the other - were in fact helpful and spot on...

I don't even think this has anything to do with Armbian / Debian / Ubuntu. It's simply someone mucking around too much for their own good and frankly being arrogant about it. Until I see the problem reproduced in a stock setup this is simply PEBKAC as far as I can tell. I mean, for anyone actually willing to read, it's right there: Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. systemd is essentially a monolith, you don't really get to pick and choose for all intends and practical purposes. The choice @Quantum needs to make is whether he wants to have something that works or whether he prefers to be high-and-mighty and run around being condescending to those whose work he uses without paying a dime all the while making outlandish claims. This is a non-issue.

@Learnincurve It is very easy to build only the kernel with the Armbian Build Framework. The result will then appear as output/debs/linux-image*.deb

ping @amazingfate and @prahal

maybe @schmiedelm has an idea?

btrfs on Helios4 is now on by default and there is a uboot-btrfs extension to easily enable this for other boards or even at compile time.

With the latest changes in Armbian and most importantly the update of u-boot to v2025.10 for Helios4, it is now possible to boot SATA and USB from u-boot flashed to SPI NOR flash, with the dip switch set to SPI boot mode. This even includes booting straight from u-boot to btrfs now.

Images shall only be written with imaging tools that validate burning results. This saves you from corrupted SD card contents. Approved Tools: USBImager a lightweight cross-platform imaging tool Balena Etcher an electron / node.js based cross-platform imaging tool (may contain spyware)