Igor

(fat) Boot partition should be big enough. It's for kernel image, device tree and one backup. Regarding problems - i just notice it yesterday while playing with it. This was not manifested in previous build ... C2 kernel still need some basic fixes. If you find a fix regarding HDMI, please share. Thanks!

https://github.com/igorpecovnik/lib/commit/7cae2ca69a31ae49df6f51d0ffec7e81c9f744ef works after this.

Go to toolchains and run: (Make sure you use updated build script) wget -q --show-progress http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/aarch64-linux-gnu/gcc-linaro-4.9-2016.02-x86_64_aarch64-linux-gnu.tar.xz -O - | tar xJ Complete list of tested external compilers, needed for various boards if you build with Xenial. There are some cases where different type of compiler is needed for uboot and kernel. Our system always chooses right one. wget -q --show-progress http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/aarch64-linux-gnu/gcc-linaro-4.9-2016.02-x86_64_aarch64-linux-gnu.tar.xz -O - | tar xJ wget -q --show-progress http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/arm-linux-gnueabihf/gcc-linaro-4.9-2016.02-x86_64_arm-linux-gnueabihf.tar.xz -O - | tar xJ wget -q --show-progress http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/arm-linux-gnueabi/gcc-linaro-4.9-2016.02-x86_64_arm-linux-gnueabi.tar.xz -O - | tar xJ wget -q --show-progress http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/arm-eabi/gcc-linaro-4.9-2016.02-x86_64_arm-eabi.tar.xz -O - | tar xJ wget -q --show-progress http://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz -O - | tar xJ This will be also implemented to the build script asap.

This can take some time since there are lot's of files and it also recompile kernel header on install. If you are using some under average SD card, this can easily takes 30 minutes or more.

Deboostrap goes well ... just few things looks broken. Could be some packages ... sshd is not working service ssh start Starting OpenBSD Secure Shell server: sshdWarning: Fake start-stop-daemon called, doing

I have two build hosts, one was built week ago, one is Xenial, the other is Trusty. Since I added deboostrap to Trusty manually I also downgrade it to Trusty defaults but still ... Wheezy is somehow partially corrupted but it was O.K. few weeks ago. Any ideas what's going on ... before I start digging in?

This module is not a part of a kernel. We build it on the way and since it's not packed it fails out when an upgrade is issued. Feature, which we added, is not done on the proper way yet ... but you can make a module on your own too.

Are you using latest script? I just tested - working normally. cat /etc/apt/sources.list.d/tvheadend.list must result in: deb https://dl.bintray.com/tvheadend/deb wheezy release

I am not sure we have a driver for send in kernel. It exists in A20 kernel for gpio based IR transmitter. I did few tests and it works, but I am not aware of limitations ...

use image from download section and issue an apt-get update / upgrade.

Strange ... Check documentation for "How to unbrick my board"

It is possible that such resolution does not exists in the kernel and needs to be added, tested and issue a kernel update. It's on 2do list (for some time) do add some extra resolutions.

Build script produces kernel and uboot separate, so you can update one by one. Both are deb packaged ... Currently I have no idea what's the problem but I suspect u-boot related troubles. I don't own CB2 but anything else ... Cubietruck, Bananas, Olimex A20 board. All of them are working fine with the same kernel.

This was actually introduced for some other purpose but yes it's usable this way as well. I am slowly preparing on weekly auto build for those who wanted to be on the edge. "5.11-$weeknumber"

Didn't know about that. Thanks! @dony71 Try now.

Remove sources, that you force clean download, and I think it should work.

Check documentation for rescue. I need to take a look what's going on ... http://www.armbian.com/documentation/=> How to unbrick the system?

Add it to the boot script /boot/boot.cmd & convert to boot.scr after you are done.

I'll merge it asap. Thanks too you too. BTW. Now we are extending task to include support for 8189ftv found on latest OPi boards.

Most critical part is your host. What are you using? Any changes to the configuration?

You have some weird user settings? - I made complete rebuild yesterday - I just compile 4.5.5 Host: Xenial with 4.4.0-22-generic Compiler: arm-linux-gnueabihf-gcc (Ubuntu/Linaro 5.3.1-14ubuntu2) 5.3.1 20160413

Kernel 4.6 is development with only basic support at most ... check forum for more info. For developers only. This is the reason why we don't provide downloadable image. Yet. Regarding UARTs in kernel 3.4: http://linux-sunxi.org/Fex_Guide

If you want to see more on serial console, you will need to alter boot scripts. There is nothing wrong. .next is used to boot mainline kernel. If this is set, boot procedure is different. .verbose is used to enable more verbosity in case of troubles . unrecognized fs is because we try to load from other filesystems with one script.

yesterday, v5.11 If I didn't made any mistake, it should be there.

Well, there are few things to clear out - script.bin is a hardware config for legacy kernel (3.4.x). When you change kernel to vanilla, this conf becomes obsolete. Configuration in vanilla kernels is placed in DT. We haven't prepare configuration for Vanilla kernel, but here is a patch: https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sunxi-next/bananapipro_lemaker_lcd.patch.disabled but is untested.