Thank you

https://github.com/armbian/build/tree/main/config/boards BOARD equals filename (without file extension) from above

Hello Thanks for you answer, I understand the point that if even though M2B & M2U are very close, it does not mean it will work. I really thought it was a simple thing to change "just" to turn off/on the board, as all the rest is perfect. I had a look to https://docs.armbian.com/Developer-Guide_Build-Preparation/ but honestly I am not skilled enough to to this, I did not understand how building it on my PC will make it work on the BananaPi, and the config ./compile.sh build \ BOARD=uefi-x86 \ #bananapim2b does not seem to exist BRANCH=current \ BUILD_DESKTOP=no \ BUILD_MINIMAL=yes \ KERNEL_CONFIGURE=no \ RELEASE=trixie does not help on which string using for my board. Regards

I know this is an old post, but I am desperate and saw you are using v 1.3.2. I have an Orange Pi 5 v 1.3.2 as well and I can't get it to boot. I have been trying a bunch of different OS's, Ubuntu and Ambian versions and it keeps failing. ChatGPT and Gemini both say it is a bad DBT file and then point me to the same version of Ambian to use. None of it seems to work, have you had any luck getting it to work? I haven't tried compiling the OS yet for it, I was hoping there was a stable version out there I could use.

In the world of cheap ARM sbcs you cannot simply use image for board X and assume it works for board Y. It may up to a certain point, even boot, but you have to live with regressions. https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image If there is no pre-made image for a specific board, then you can DIY if it is even supported by the framework. keep in mind, boards in eos or csc status may or may not work. We don't know, we don't pay attention, we don't support.