Sombohan

That's what I'm assuming. For the old one 16.04 I've found a apt-get list but now it starts right away after installing with apt-get install git, git clone and sudo ./compile.sh. Where can I find the other needed packages?

Here my log I'll give it a try and reinstall my VM using the mini.iso. Without the dialog and at least build-essential not even the menu appeares.

For testing, I'm trying to build a complete image for my orange pi one. In the old environment, there was no problem with it.

Hi there, I've tried to migrate from my old 16.04 ubuntu build machine to 18.04 regarding the documentation there is no need for extra packages. To get compile.sh running I've added build-essentials, ccache, make & libpython. Now there is a problem with openssl/bio.h. Is there a complete list of packages needed? I've set up my VM using the ubuntu-18.04.1-desktop-amd64.iso image. Is it solely failing by not using the mini.iso? Regards, Sebastian

Hi Abdul, I've tested the functionality. The Zero runs smoothly with Debian 8 if you use the build instructions at the previous thread.

I like to share the things I've learned. I've figured out, that was not the whole story. If a new user checks out the git repository there is an additional step to do. Copy the fix-sdcard-detect-bpi-m2z.patch to your userpatch/u-boot/u-boot-sunxi/ folder. That file should not be influenced by the changes in the git repository. After that small step it is possible to run the build-process and use the image afterwards. It may help some users to get their Banana Pi M2 Zero running.

So for now that means, the support for the zero can be removed at any time because the build toolchain will be updated every time I start it, right?

If I'm right the bananapim2zero is listed as CSC and you say that means "will probably never be"? What makes it relevant to be supported? I've only started this thread do give a smal hint for somebody stuck at this point. I'm trying to get kernel sources matching to the running kernel. The stock image based on armbian does come with the wrong headers by default. By the way, I'm excited how fast a new user will be supported here. That's cool.

Thank you, after I've tried to do some copy&paste with the .patch files. I've found out, that they where already installed. I've come to the expert view at board selection... "Show CSC/WIP/EOS" does the trick! So maybe I haven't read the documentation in depth. But now I can go on.

Ok, I've got the patch but I'm not familiar to patch device trees from where do I have to apply the patch? Directly at the image at the sd-card or somewhere in the build-root?

Hello, I'm trying to build a image using the amazing auto builder supplied by armbian. In the past I've build kernels and modules for linux running at CycloneV-Devices. I don't need graphic support. If I use the image for a M2 Plus there is a initialization issue at mmc: MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Card did not respond to voltage select! mmc_init: -95, time 22 So I'm stuck. Is there a way to get it running by using the auto builder? Using the stock image provided by the manufacturer works. Regards, Sombohan