Igor

Thanks... I've seen your bugfix on git. Its the same i did and it works.

Hi again,
 
Good news....
 
Using Wheezy 4.1.6, I've updated and upgraded. Once upgraded Linux cubieboard 4.2.2-sunxi is working
 
Up to now everything it's working and fine.
 
Thank you

When I choose mainline and wheezy, I have other options later:
 
Device Drivers --> I2C-Support --> Multiplexer I2C Chip Support: There are 5 Options
 
and
 
Autoselect ancillary drivers (tubers, sensors, i2c, frontends) [*] is under Device Drivers --> Multimedia Support
 
Edit: Now i have a file Armbian_4.4_Bananapi_Debian_wheezy_4.2.1.zip in /output/images which is only 300MB.
When I unzip this file, I have 3 files: imagewriter.exe, Armbian_4.4_Bananapi_Debian_wheezy_4.2.1.raw an armbian.txt. I can unzip the raw file to 0.img. This file is only 900MB. When I write this image on a sd card, the banana pi does not start with it. When I want to open the sdcard in the explorer, it comes a message, that I have to format the card.
 
What is wrong?
 
Edit: It works!!!
 
Edit: I installed tvheadend. There I can choose the Silicon Labs Si2168 under TV Adapter. When I choose the DVB Network, it search the muxes. But it does not find any services.
Does somebody has any idea?

Things has been changed. Everything is now inside repository apt.armbian.com and upgrade is done via apt-get ... lamobo shares legacy kernel with banana, orange, ...
 
More info:
http://forum.armbian.com/index.php/topic/211-kernel-update-procedure-has-been-changed/

Thanks, it's working now.

It worked, thanks a lot!
 
The support and dedication you put into this project is outstanding.

I started to use terminology "Vanilla" which suits www.kernel.org aka mainline kernels. Not exactly correct interpretation but ..

solved,
 
I updated the blog page http://development-annotations.blogspot.it/2015/05/banana-pi-encrypted-sata-disk-bootstrap.html
notes for Bananian 15.08 ( Jessie ) at the end of the page there are relevant actions to enable bootstrap using initial ramdisk.
 
thx again for your directions.

How are you creating on the old system?
 
Try proceeding this way:
fatload mmc 0 0x49000000 /dtb/${fdtfile} fatload mmc 0 0x48000000 initrd fatload mmc 0 0x46000000 zImage bootz 0x46000000 0x48000000 0x49000000 If you are using uImage, some adjustments / converting is needed.
 
If not, check here.

Hello , I find the problem
If I do
bin2fex /boot/bin/lime2.bin >> output.fex nano output.fex fex2bin output.fex >> /boot/bin/lime2.bin I have the errors
 
But if I  do :
bin2fex /boot/bin/lime2.bin >> output.fex nano output.fex fex2bin output.fex >> lime2.bin rm /boot/bin/lime2.bin cp lime2.bin /boot/bin/lime2.bin It is ok , no errors 
thanks for your help
And thank you very much for armbian , great Job !

Hello Igor I tried without success but at the end I found a solution (sort of).
I restored a clean Armbian raw image to my sd and then zeroed it
and used rsync to backup my original sd to the smaller one.
Rsync took less than 2 minutes (2Gb of data on my SD) and I now have a compressed raw of 1.3GB!
 
Not the ideal solution but it's a good compromise at least.
 
Thanks and have a nice day,
V.

Your I2S device is probably not connected to right pins.

DD is direct copy and you can use it almost anywhere.
If you want to speed up the process - shrink data partition on the drive, save only partitions (separate) and expand back. But in this case you are not saving the boot loader. You need to save it separate.

... and I merged this config with default 
+ added firmware.
 
https://github.com/igorpecovnik/lib/commits/second
Next build should work out of the box with this hardware and the rest what has been enabled.
 

I checked other points of a script. Works all but vpn server. Its installation causes errors of Mysql and apache (403 forbidden you don't have permission to access on this server)

Finally I am able to use the DVB-C part of the Astrometa DVB stick (MN88472) with Banana Pi.
 
I made a kernel 4.2.0 wheezy image with Igor's script. In the kernel config I enabled almost everything in
- Device Drivers -> I2C
- Device Drivers -> Multimedia support
- Device Drivers -> Staging drivers -> Multimedia 
 
Here you can find the .config file and my image for download.
 
After you started the banana:
# If you use the image linked above then # (dvb-apps libdigest-sha-perl make gcc git patch patchutils libproc-processtable-perl) are already installed. # apt-get install dvb-apps libdigest-sha-perl make gcc git patch patchutils libproc-processtable-perl apt-get install w-scan cd /lib/firmware wget http://palosaari.fi/linux/v4l-dvb/firmware/MN88472/02/3fbb92e59bd20acedcaa82cfb37b0be3/dvb-demod-mn88472-02.fw reboot # Connect astrometa device AFTER(!!!) boot is complete, system ready # Use scan with the "initial-tuning-data-file" of your TV provider # Mine is the hungarian Digikabel. Check yours in /usr/share/dvb/dvb-c/ or make one for yourself scan -A2 -f1 /usr/share/dvb/dvb-c/hu-Digikabel # or you can use w-scan to find DVB-C transponders for you with this command: w_scan -f c # if you can't find any transponder, try disconnect and reconnect the stick, and run scan or w_scan again Cheers
 
Thanks again for you Igor!

- Finally I changed SDSIZE to 6000, and started everything from the beginning.
- The line 278 in common.sh (BLOCKSIZE=-----) was already the same, what you suggested.
 
The error what I get now is:
[ o.k. ] Shrink partition and image to real size [ 15 % free space ] losetup: /dev/loop0: device is busy tune2fs: Bad magic number in super-block while trying to open /dev/loop0 Couldn't find valid filesystem superblock. tune2fs: Bad magic number in super-block while trying to open /dev/loop0 Couldn't find valid filesystem superblock. tune2fs: Bad magic number in super-block while trying to open /dev/loop0 Couldn't find valid filesystem superblock. /root/lib/common.sh: line 273: (-)*/1024/1024: syntax error: operand expected (error token is ")*/1024/1024") [ ok ] Runtime 114 min Maybe line 275 has a syntax error? I'am not sure, but if i compare
NEWSIZE=${NEWSIZE%.*} to line 268
UNITSIZE="${UNITSIZE//k/}" then I think maybe the quotation marks are missing. I don't know the syntax, that's why I can't decide is it right or not. I know, I know that line 275 is after 273, but I thought I mention to you.
 
I was logged in into LXDE desktop, and used LXterminal to run compile.sh. Now I tried to run it in text mode, and now it works!
 
Just for sure I tested two times!!! If I run compile.sh in text mode, then it is fine! If LXDE loaded then i get the error above...
 
So finally, I can test the final, error free image tonight! I'll send feedback asap! Thanks for your help again Igor!

100% right.
 
The last Legacy-kernel Image (i use Jesse) is working greate as expected.
 
Currently I use PH20/PH21 to MUX4 , while by default they're connected to mux1 for status leds.
 
Hmmm ... its time to trace the board and cut the line.
 
I really appreciate your help.
 
Sincerely
-bino-

Fixed.
 
https://github.com/igorpecovnik/lib/commit/8eb7d85a4d1dbeeda857587e0b4d61b5bfe47c11

:-) I was in the same situation several months before. Lamobo can work perfectly, as both of my lamobo does, but you must: (thanks to Igor, Patcher, Tkaiser etc...)
 
- Operate Lamobo verticaly
- put high profile heatsink to BCM switch (under the harddisk)
- put heatsink to A20
 
If you use ordinary HDD with consumption 500mA, no USB, no WiFi, no HDMI and you have good USB power cable, you don´t need secondary power via battery connector.
 

 
:-) It works )))
 
PM
 
 

No recompiling needed , just reading up on kernel modules ... I added
w1_sunxi w1_gpio w1_therm to File: /etc/modules-load.d/modules.conf


and rebooted
the W1 interface showed up.:
# ls /sys/bus/w1/devices/ 28-0000059a1220 w1_bus_master1 and to read the temperature ( 23.5 deg C ):
# cat /sys/bus/w1/devices/28-0000059a1220/w1_slave 78 01 4b 46 1f ff 08 10 c1 : crc=c1 YES 78 01 4b 46 1f ff 08 10 c1 t=23500 note that you need a 4k7 ish pullup from data to 3V3 for the 1W bus to function properly
some people sugguested using
~# modprobe w1-therm strong_pullup=1 But I have a pullup on the PCB so i did not need to do this
-dd

If I'll look to much into the code I'll solve it but I am anyway looking into (other) code the whole day
 
Step by step, check what's needed and not done. It could also be some very basic. Jessie and Wheezy have different default system packages from which such scripts are depend on.

OK, I see. I guess we (the script) have a problem with setting correct U-boot upon upgrade ...

Hi Igor,
 
this afternoon I made some progress. I now have a service for systemd that should start/stop ramlog appropriately, i.e. before syslog. I do not know wether this is enough, but anyways I'm going to give it a try. I'll let you know in a few minutes...

Oups, I managed to fix it. It's only a permission error. With the root account everything is fine.. I guess I need to apologize. 
I added my user to the audio group.
 
Thanks for the support. Bye