Igor

By default you are compiling everything. You started properly and first / default options is the safest one (Wheezy) and (defaut 3.4.x) in next screen. If you only need kernel, than alter one more config. option: KERNEL_ONLY="no" - > "yes"

OK, if you are willing to take some experimenting, try older bootloader. http://mirror.igorpecovnik.com/u-boot/linux-u-boot-4.0.4-lime2_1.8_armhf.deb I'll do some tests but the problem is we must wait few weeks for results.

It just hangs, I know. It happened to me too. It's an rear event so it's very hard to catch. I suspect u-boot, because troubles are present in both kernels. Hardware. That's all you have? Nothing on USB?

New kernel (3.4.109 - available soon) is coming with some fixes for wifi driver. This could also be the reason.

Our kernel 3.4.x is not ready for boards with A10 ... I don't have any A10 board to check and fix. I already try few times on theoretical base but failed. Now, you only can compile vanilla kernel 4.x I am planning to fix this. I ordered one (Cubieboard 1) a week ago but it's not here yet. Than I would also need to find some time and fix it ... Use 4.x or wait for a while.

I was using SPI display on 3.4.107 ... it must be something else. BTW. There are two spi patches and I can't tell which one is better. They both works. https://github.com/igorpecovnik/lib/blob/second/configuration.sh#L28 add: -b dan-3.4.104

This source is bind mounted to kernel sources. If it hangs by some reason ... rather reboot and than remove those sources. They will download once again.

That's a fork of my early script Lubuntu flash is needed if this procedure fails, if your NAND come without boot loader, ... It's not possible to achieve this otherwise. Wrote on mobile phone

Than you only can go for 3.4.x at the moment. For WiFi try to build the module or change for supported one. Wrote on mobile phone

You mean in a combination with NAND? Doubt, I don't think it exits. If you need a modern kernel, go for Vanilla, latest stable which is available for download is 4.2 and it's in much better condition than any kernel down to 3.4.108 (latest legacy). All my images are upgradable from 3.4.x to 4.1x and back. Check docs for details. Just remember to upgrade an u-boot not just kernel.

Added to bugs sections. The download page is not determined yet and I haven't come out with a proper solution yet. Main problem is that there are many different downloads and a download link to previous versions (4.2) is also not that bad, but it has to be solved differently. Now is a bit confusing, I agree.

Hmm, damn. I switch U-boot version where I made a config for R1 because it's not existing. Config is virtually the same as Banana with only changes to NIC delay to gain better speed and SATA powering. Than there are some minor changes to kernel which should be o.k., except if the bug is within compiler. Testing, again

If you copy it won't work. Simple as that. zImage kernel type is not supported by that boot loader for which I don't have sources or newer version. Yet. Eventually this will be solved too but now there is no other way.

Ich bin auch sehr froh, dass wir einen Weg gefunden. The only and a small downsize of this method is writing to the card - you also write some unoccupied empty space ... but yes, it's not worth the troubles

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/

You mean FPS in playing video? MALI has nothing to do with it.

Yes, I broke it yesterday ... Fixed. Reboot and refresh build script.

I am stuck here too: cc -MD -MP -MQ device.o -fpic -fvisibility=hidden -Wall -O3 -std=gnu99 -c device.c -o device.o In file included from vdpau_private.h:58:0, from device.c:23: /usr/local/include/csptr/smart_ptr.h:29:21: fatal error: common.h: No such file or directory # include "common.h" ^ compilation terminated. Makefile:43: recipe for target 'device.o' failed make: *** [device.o] Error 1

I don't quite understand. What is not working? You can build it native but fails within chroot?

Aha, ok. There is a solution for this way too. When you are done with your custom installation just enable firstrun back and it will expand to new full size at next run. Execute this: update-rc.d firstrun defaults Than save the image. Your minimal size is the size of your SD card, so it's not that perfect as original solution but if you are using 2G SD card which is almost full you are near to perfect scenario. And you will also gain few extra things: - force to change root password - ssh keys rebuild - package update

You don't get any input or it's distorted? At u-boot, kernel ...? Can you paste the output?

Strange. I am using auto-expand partition script which runs only once - more precisely at first boot. This scripts among other things alter partition table and puts "resize file system" script to the auto start. That script do the actual resizing in second boot since we need to reboot before we can do that. They have meaningful names: firstrun and resize2fs (located in /etc/init.d) If you are using my script to build an image, than this should work out of the box. This feature has been with us for a long time and I don't have a record of malfunctioning. Can you describe precisely how do you build an image - have you done any modifications to the script and which? If things are not working as expected is recommended to remove script /lib to force updates and to start over. I am sure we can work this out. This auto-expand function was exposed by many people as one of the coolest feature ... even it is trivial for advanced users and even "not wanted" by very few.

3.4.107-cubietruck #14 SMP PREEMPT Wed Apr 29 11:57:42 CEST 2015 armv7l GNU/Linux This one is working (?), the last one not. Try this boot loader: http://mirror.igorpecovnik.com/u-boot/linux-u-boot-3.4.107-cubietruck_3.9_armhf.deb for image with kernel 3.4 ... just install and reboot.

You just find a bug. Upgrade if system is on NAND will not go automatic even if there is enough free space, I need to fix it. (nand bootloader doesn't recognize zImage kernel type) Workaround: 1. Remove zImage, uImage, system.map-3.4.108-sunxi and vmlinuz-3.4.-108-sunxi ... located no /boot (/dev/nand1) 2. Run this and pick up the correct board / kernel 3.4: wget -q -O - http://upgrade.armbian.com | bash

http://www.openprinting.org/printers Is it supported by Linux?