Hi congrats for the wonderful job with Armbian, i own a banana pro and I've found a great projet for rasp called Dietpi (http://dietpi.com/), Unfortunately the creator hasnt got a Bpro so he is not able to make it for our board, I'm asking if anyone is capable of making this suitable for us? It would be even more awesome, thank you

Thank you. 

Our approach is to provide a stable base system, not to maintain wizards for everything. We provide some basic system configurations - for setting display, to install into NAND / eMMC / USB / SATA, to install Rpi monitor etc ... by default. The rest ...

 

I maintain one after-install script for installing various services: 

https://github.com/igorpecovnik/Debian-micro-home-server

 

This is similar but it is a separate project since you can install this virtually on anything that runs Debian / Ubuntu and clones.

thank you for the answer , I tried ;D

After several crashes, I was able to build an armbian for my banana pi M1.

It works wonderfully! 

I have mounted the image and copied out the kernel (vmlinuz-4.5.3-sunxi) and uInitrd files.

 

However, I am unable to start it with:

 

qemu-system-arm \

  -M vexpress-a9 \

  -kernel vmlinuz-4.5.3-sunxi -initrd uInitrd \

  -append root=/dev/mmcblk0p1 \

  -drive if=sd,cache=unsafe,file=Armbian_5.11_Bananapipro_Debian_jessie_4.5.3.raw \

  -net nic -net tap

 

Being able to update the image from a 'live' system would save me a great deal of time, I think.

 

I am able to run an older bananian image with similar commands.

Do you have any suggestions?

 

thanks,

Regor

I am able to run an older bananian image with similar commands.

Older means kernel 3.4 ?   Perhaps here is the problem - our kernel is classical zImage while most others uses uboot uImage style ?

Yes. Older is 3.2.0-4. I don't understand why I cannot run the zImage. 

Here is the command for the bananian:

 

qemu-system-arm -m 1024M -sd ./LeMedia_v1504.img -M vexpress-a9 -cpu cortex-a9 -kernel vmlinuz-3.2.0-4-vexpress -no-reboot -initrd initrd.img-3.2.0-4-vexpress -append "root=/dev/mmcblk0p2 panic=1 rootfstype=ext4 rw" -net nic,macaddr=52:54:00:fa:ce:13

 

does vmlinuz-3.2.0-4 tell you anything?

Is there something I can do to get it to run in a vm?

 

Thanks,

Regor

file reports:

vmlinuz-4.2.3-sunxi: Linux kernel ARM boot executable zImage (little-endian)

vmlinuz-3.2.0-4-vexpress: Linux kernel ARM boot executable zImage (little-endian)

sorry:

vmlinuz-4.5.3-sunxi: Linux kernel ARM boot executable zImage (little-endian)

 

I am using a newer version. It appears it is not booting, but I wonder if it is booting

and the console under qemu is not set up to report the boot process? 

Actually the difference seems to be the initrd file, not the kernel file:

The jessie build doesn't boot under qemu, but the older bananian image does.

 

The jessie armbian build initrd:

# file: uInitrd: u-boot legacy uImage, uInitrd, Linux/ARM, RAMDisk Image (gzip), 4007052 bytes, Thu May  5 17:27:58 2016, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x3899A90A, Data CRC: 0x0C613615

 

The older - bananian initrd

# file initrd.img-3.2.0-4-vexpress 

initrd.img-3.2.0-4-vexpress: gzip compressed data, from Unix, last modified: Tue Jan 29 16:04:38 2013

 

Any insights?

Regor