laibsch

this has now regressed to a generic # bluetoothctl list Controller AA:AA:AA:AA:AA:AA banana [default]

I am not using WOL on any of my devices, I have no personal experience with the software on the Helios or any other platform.

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?