Igor

Than the problem is elsewhere, things are missing so image is corrupted ... Sometimes the debootstrap process fails, rarely but it does. I don't check this but am thinking to add this check too. You need to remove cache that deboostrap process will run again.

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.

I am working to fix this a little different but it will suit the purpose. If you made a mass to the code and you wan't a fresh source just remove the source directory and it will re-download without a question. The new option will be CLEANUP_LEVEL [0-3], nothing, cleaning compilation, sources, debootstrap And probably I will add a parameter for external kernel config.

If everything was correctly installed the only difference is u-boot and separate boot partition. This can provoke certain troubles but I never heard for such. Double check that you have correct script.bin on (boot) nand1 partition. When you install to nand, script bin from SD card /boot/script.bin is copied there, kernel zImage is converted to uImage and copied there ...

This is the same problem as described here. Apparently the workaround is not working @Jessie. Sometimes the power cycle helps.

Insert SD card into a slot and power the board. First boot takes around 3 minutes than it reboots and you will need to wait another one minute to login. This delay is because system updates package list and creates 128Mb emergency SWAP on the SD card. Did you wait long enough? I haven't notice any problems regarding this script lately. I am using build script daily. Possible problems can be if your host computer is not Ubuntu Trusty 14.04 ... if you are using something else, there is no warranty. Setting fixed size and not shrinking the image is a step back. Try to run script firstrun manually and see what errors do you get. There are differentiates between wheezy and jessie regarding firstrun. With Jessie you get a prompt and script runs further in the background where on Wheezy you need to wait until finish.

Galcore is / if exists / a part of BSP. If it's not here: http://repo.r00t.website/... than no idea where else to look for. I am afraid I can't give you much help on this.

http://forum.armbian.com/index.php/topic/241-first-run-stuck-with-ssh-key-generation-cubietruck-rtc-bug/ Perhaps it's related to this?

Patch is added, so you only need to rebuild or wait for next Armbian build. https://github.com/igorpecovnik/lib/commit/61d76da51584000f564a6e6326a73cc48055aacb

http://www.lemaker.org/forum.php?mod=viewthread&tid=11807&extra=page%3D1&page=2 http://forum.armbian.com/index.php/topic/147-i2s-force-mclk/?hl=sound Help. Request on github or prepared patch against my branch ... For me is just a little more work than replaying to this post but it helps I am having a selection of patches which eventually are merged but until then, they are here: https://github.com/igorpecovnik/lib/tree/second/patch

Perhaps this is solution? https://community.freescale.com/thread/354786

There is one mistery regarding desktop. Ubuntu is currently having this issue on imx boards. I can say that this problem is present on all but it's clearly not working on Cubox, HB and Udoo as well. I build Trusty by mistake. Pick wheezy desktop, issue upgrade and you will be fine. WLAN is as is. Chipset / driver was never brought to perfection. It's working quite stable but performance is not the best. For wide screen I don't have any clue but I send an request to people who might know. There are no video acceleration on desktop but overall desktop performances are very good, the best among boards that are covered by Armbian. Especially Humminboard PRO where you can add SSD.

Yes, I'll add support soon. I am getting one A10 board, then I'll try to fix the kernel. Without an actual hardware is a bit hard.

This scripts is designed to work with images. So it's only an example / idea , not for direct usage in your scenario. I am not sure that bs=512 is enough. It's different for each board architecture so double check. This is how we write it Allwinner: dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8 Yes, armbian has only one ext4 partition.

I2S works with current driver which is from Nikkov. Working is confirmed by some people. (I don't have I2S hw) https://github.com/dan-and/linux-sunxi I am using this repo together with Daniel. He is working mostly on official patches, me unofficial. No idea when things will be merged ... it's one of the small / not urgent tasks. Help is always welcome!

fex2bin and bin2fex are included on all images. Have you compiled image by yourself?

Which kernel are you trying to build? Kernel 3.14... is currently broken. I hope I'll manage to fix it during the week. P.S. Thanks

I am using Nikkov's driver implementation but this part is not merged yet: http://www.cubieforums.com/index.php/topic,1081.msg23222.html#msg23222

Your I2S device is probably not connected to right pins.

You can upgrade basic system but you will fail with special things (gpu-viv-bin) because they exists / works only for wheezy. Remove all those packages and http://repo.jm0.eu./, do update and repeate the process. Than it should go.

OK. I have very little information about those boards at the moment. https://github.com/SolidRun/linux-fslc New kernel 3.14.51 is preparing but I was not able to build it. It's worth to check it.

Perhaps move to Jessie and development version of TVheadend?

remove linux-u-boot-cubietruck linux-image-4.1.2-cubietruck linux-image-next-cubietruck and install linux-u-boot-cubietruck-next reboot and you'll be fine.

https://wiki.debian.org/Bonding If you mean this, than the answer is yes. In all images since some time.

What power supply are you using? If you are running system from nand, than uEnv.txt is taking control. boot.scr and boot.cmd should not be there. Is your /boot (/dev/nand1)? nand1 is boot partition with kernel uImage and uEnv.txt and some other files but not boot.scr and boot.cmd And you have to remove SD card if you want to boot from NAND .. if it's not booting than check BUG/Limitations and proceed with the hint.