Igor

I am using defaults. /etc/sysctl.conf Yes, this is fine.

ttyS0 is serial console. You can't use that for anything else, try ttyS1

Plug something on and see what's going on. Perhaps it's just an SD card ...

Regarding building - perhaps necessary patches doesn't go trough well. This is nothing unusual. I will try to build and adopt patches when released or if bored NAND support will be here soon, also on u-boot. 1. I heard it's possible but not by default or without some hacking. 2. You need to boot with SD that support NAND and change the NAND kernel. a. no b. don't know

You mean like a Cubietruck emulator on PC or running a virtual machine on Cubietruck?

You are doing properly ... just there is one issue which I need to fix. It doesn't build the kernel because it already exits ... so delete the .deb files which goes with this kernel and it will proceed with compilation. Those parameters are about to be slightly redesigned ... waiting for time & energy

You might run into one known bug. If you are trying to install image with kernel 4.x and you don't use latest Armbian image, system might not boot if you had and old kernel before ... which is quite common and almost sure with yours. http://forum.armbian.com/index.php/topic/64-cubietruck-hangs-at-boot-with-debian-38-wheezy-404/

You don't find modules because they don't exists. Support is build into kernel. That's why you see those devices. With kernel which you use it was confirmed as working. On new one, linux-sun7i, there were some changes in this driver. I don't have proper equipment at my reach to test and confirm.

Most (working) things are enabled.

I am looking forward for details - just make a post and we can pin it. My hostapd build tool is here: https://github.com/igorpecovnik/hostapd ... as you can see not much extra on the top of official. I haven't compile hostapd for a while so something might be missing, sure. I'll check & fix. ADD: I just try and it compile without a problem on a fresh image. Both variants. If you are using SSD slow write speed is not a problem any more. Ramlog is a good addon for SD card scenarios.

No no, legacy kernel (3.4.109) has full working audio, even I2S on some boards. Audio features just haven't reach mainline kernel (www.kernel.org) yet.

If you seek for a solid / better / audiophile sound you should go for external DAC anyway I know you probably don't want that, so just use legacy kernel until then. It's working good enough. Check here - 4.3 is about to be out. I guess a month, two. www.kernel.org

Have no idea why is this happening Better wait for NAND support on mainline kernel. I heard it's already done but not implemented yet. If problem happen there it won't be a problem to fix it since there are a lot of people working on it. On the other hand no one is taking care on legacy kernel any more ... except minor things. I am using 3T but on SATA and it works fine With Lime2 and legacy kernel.

No on-board audio devices yet People, who are working on this, wrote that this will be / is planned for next major kernel release (4.4) http://linux-sunxi.org/Linux_mainlining_effort

Orange Pi PC and all other boards containing H3 chip are not supported by Armbian. I can add that this is true for any other distribution. Nevertheless there are few ROMs based on buggy 3.4.39 Android kernel which is not supported by Allwinner nor community. I recently looked upon the one and only kernel and u-boot source. All I can say is that we need a lot of work & I haven seen much motivation doing this. Not by myself nor others. Factory image build procedure is dirty and with help of some AW binaries. Building really sucks and results are also very poor. I won't say never but dunno when.

I am thinking how to reduce the number of different builds. It takes a lot of time to build them (whole day), even I already made a lot of cache optimizations and have a decent HW. This is the main problem. I do sometime build with vanilla, so it's working fine ... except audio and video acceleration. 2nd option is to upgrade. It should work fine.

Check a script.bin and play with those settings too. Kernel might be just fine.

The only issue regarding USB (that i remember now) is related to OTG port. Are you using it?

Huh. In latest image I changed the wireless driver but ... I also can't confirm nor deny if connection to open network is working properly on all options. It's possible that we are facing with a bug. On which image / kernel are you doing this? We have three different kernels and different wireless drivers.

Ha? You cut the power or you did a proper shutdown? I don't understand what are you doing wrong. SD card / hardware problem? This is a proper boot procedure ...

If you still have a running system, than you don't need to use that procedure but directly: apt-get install linux-image-next-sunxi linux-headers-next-sunxi linux-firmware-image-next-sunxi apt-get install linux-trusty-root-cubietruck apt-get install linux-u-boot-next-cubietruck

Check this: http://forum.armbian.com/index.php/topic/258-1-wire-on-a20-lime2-or-som

Ign is when there is no change. That's ok. The problem might be, that your package base is corrupted ... or simply it does not update because there are no packages to update. In this case you need to install them manually / with this script. Without (install) log I hard to tell what went wrong.

No, I only change was in (proper) configuration. Regarding W1 ... check also if you have those settings in your DTB. https://github.com/patrykk/linux-udoo/commit/697c08d940f67b61690a66a7ec4cdc3ac7f42535 In another words - make sure you upgrade DTB package too.

Yes, likely.