Igor

One option is to boot SD image with 3.4.108 ...copy /lib/modules/*********-3-4-108 to nand2 and sda1, convert /boot/zImage to uImage with previously mentioned method and copy to NAND1 ... check uEnv.txt @NAND that it's pointing to proper root. So do step by step. First boot from NAND and rootfs=/dev/nand2 ... than copy modules to HDD and switch rootfs there.

Any recommendations? http://wiki.lamobo.org/index.php/Lamobo_R1S New version is coming out but with Mediatek wifi which is as crappy as Realtek. I think we'll get more cheap (but with a little better hw) router boards soon.

What I can see from log is that you are booting kernel 3.4.107 which makes me think that you haven't used the proper kernel as source. Somehow the conversion from zImage to uImage was not made properly. This is necessary since we use the preinstalled NAND u-boot. I'll recreate the exact scenario in next days to make sure this scenario works.

You need to load alternative driver. It's located in /usr/local/bin insmod rt8192.cu or similar But don't expect too much. Get image with kernel 3.4.108 ... wifi is working better.

Certain things can not be read at kernel 4.x yet or needed manual adjustments. For ambient temperature, illuminance, human detection ... you need external sensors. So, disable it. CPU temperature start to work properly in latest, i think 4.1.2

The chipset is cheap & crap as well the drivers. There are few alternative drivers around but I am not aware if they are any better. I think the driver on 3.4.x works better. BTW: One alternative is located in /usr/local/bin ... blacklist kernel driver and load that one.

I am working on Ubuntu 14.04 with it's defaults. gcc version 4.8.4 / gcc version 4.7.3 Recommended to avoid problems. Perhaps this is related.

Kernel install only kernel (and modules), dtb only dtb, uboot only uboot, headers only header, ... They are not linked together by purpose.

Yes, ignore. Kernel post install script creates a symbolic link to installed kernel. This is not possible on FAT file-system which is on the first NAND partition /boot. I'll fix once that it won't show the error and that that this command will be executed automatically. I am using NAND u-boot as is. All other debs are more or less optional.

Where do you build it? There are troubles on some systems and compilers.

Kernel installation is not yet ready for such scenario. I need to fix it. The only thing you need to do is to convert zImage to uImage (inside /boot) and reboot: mkimage -A arm -O linux -T kernel -C none -a "0x40008000" -e "0x40008000" -n "Linux kernel" -d vmlinuz-3.4.108-cubietruck uImage

I recompile the kernel and image. Lime A10 image with kernel 3.4.108 and HW accelerated MATE desktop Same link: http://mirror.igorpecovnik.com/Lime-a10_Debian_1.0_wheezy_3.4.108.zip

Thanks. 1. I don't need logs. You are right ... I'll fix asap. 2. No ideas at this point. I guess it's not a proper FEX script. I use the one from here. Access to hardware would be nice to conduct more tests. It would be glad to have this working ... some day

Kernel tar pack has it all except rootfs deb package which is anyway not needed in this case. http://mirror.igorpecovnik.com/kernel/3.4.108-cubietruck-default.tar

Lime A10 image with kernel 3.4.108 and HW accelerated MATE desktop http://mirror.igorpecovnik.com/Lime-a10_Debian_1.0_wheezy_3.4.108.zip Lime A10 image with kernel 4.1.2 http://mirror.igorpecovnik.com/Lime-a10_Debian_1.0_wheezy_4.1.2.zip Try when u find time and please report if it's working properly.

There is no community support for Orange Pi 2 with H3 chip. All images that currently exists are build with (the one and only) old and buggy kernel from Allwinner. I hope we will get support within kernel 4.x soon which is the only real solution for this board I guess. http://linux-sunxi.org/Linux_mainlining_effort BTW. Thanks

yes, I was stressing it for more than two weeks and it was stable. u-boot is mandatory, kernel recommended, the rest is optional.

Gr8! I'll add later on. Thanks. How about kernel 3.4.x? Have you try booting that too?

I have some - manage to successfully compile 3.4.106 ... some time ago. http://mirror.igorpecovnik.com/archive/dan%20fix.zip Here are some useful related files. I don't find a compiled binary.

USB sharing is temporally not compiling on kernel 4.x ... on kernel 3.4.x it's working normally. I notified the author. If there is no driver on the image it means I forgot (it happens) to enable it during compilation and you need to compile yourself. It's easy. Our kernel is (rock) stable. There were some stability issues in some 3.4.107 builds but that was single event and actually linked to U-boot (i think). Latest 3.4.108 (and 4.x) kernel are stable. I just finished two weeks burn in stress test and all three boards (Lime, Cubietruck and Banana) were stable. I don't have any info about bugs or memory leak among USB EHCI controller. BTW. Thanks. When you come to Slovenia next time, give me a visit

BTW. RPi monitor might require manual cron install. Check their manual too.

All images are build the same way and I also always sync the clock on host ... which is anyway not relevant I guess. Any ideas for walk around?

This is the DT that I use: https://github.com/igorpecovnik/lib/blob/next/patch/sun7i-a20-lamobo-r1.dts According to the configuration it should work. I was not checking the last R1 build for sata power. Yes, that's the proper way to install u-boot.

You need to install one extra package which is by default in my install. apt-get install bc

Yes, it's a bash shell script. It needs some extra adjustments to gain more accuracy but generally it's usable.