Igor

@Guest_Brezel_* On C2 we use this workaround script to set the screen resolution since it's not working from boot loader - I haven't figured out why: https://github.com/igorpecovnik/lib/blob/master/scripts/c2_init.sh Consider C2 in development phase so things are not working well yet - this is the same for official images / kernel.

Yes, here you put commands what needs to be done. Overwrite interfaces.default with your settings, yes.

We have two kernels, 4.x and 3.4. In 4.x this is not working yet even if you compile by yourself http://linux-sunxi.org/USB_Gadget

Older means kernel 3.4 ? Perhaps here is the problem - our kernel is classical zImage while most others uses uboot uImage style ?

https://github.com/igorpecovnik/lib/blob/master/documentation/geek-faq.md#user-provided-image-customization-script Here you put what needs to be done before image is closed.

We are still in the fixing phase and small things can be done withing this release.

AP should work with this chip ... Just remember some chips needs special treatment -> hostapd-rt instead of hostapd and the config is also slightly changed. I put working examples to /etc/hostapd.conf and /etc/hostapd.conf-rt Onboard chip should work but the quality was never seriously tested so I can't comment more. Just stick to manuals - remember to change network configuration to make use of your router DHCP otherwise you will need to configure additional DHCP server for your AP clients.

It was added to our kernel a week ago and update will be pushed out withing days. https://github.com/igorpecovnik/lib/commit/28d4b146092a052c3d5349b796b4872fa9bf4c89

U-boot has been changed and those errors are already gone.

Dev kernel is not ready yet. There are several issues.

I tried yesterday to build from scratch but kernel 4.5.4 does not boot at all. Strange. This means I would need a bigger time frame to understand what's going on. Until then, use legacy based image, Jessie is recommended - it's most tested / fixed.

If you already exposed Lamobo R1 as an example. One small but important add: networking (on router device ) is not operational without this patch since there is no switch driver in mainline kernel and also Openwrt patches are not working since 4.4

There is newer version of the driver (search forum), which also does not show two devices, but nobody found time to implement it.

Kernel 3.4.x is too old for f2fs ... It's enabled in Vanilla (4.x) kernel but that one is not ready yet for H3 based boards.

https://github.com/igorpecovnik/lib/issues/306

Should I just build it or we do some more fixes?

Read again, we have two different kernels and different limitations. NAND works, but not with Vanilla kernel. I really try not to make confusions. Perhaps we could use different colors do make more contrast ...

First you need to try this: Bugs or limitation NAND install sometime fails. Dirty but working workaround: install Lubuntu to NAND with Phoenix tools and run install again. Shutdown results into reboot under certain conditions. Due to bad PCB placement, there is some crosstalk between Wifi and VGA in certain videomodes (Cubietruck) If things fail, like in your case, you need to use those proprietary Phoenix tools to fix NAND. When this is done, you can install with our tools. Partition or formatting does not break this. And if even this fails, your NAND is broken. It happen.

https://github.com/igorpecovnik/lib/blob/master/documentation/user-faq.md#how-to-set-wireless-access-point https://github.com/igorpecovnik/lib/blob/master/documentation/user-faq.md#how-to-change-network-configuration But don't expect too much from this on board wireless chip.

Something is not o.k. either with our first boot script or your SD card. Will check the script asap.

Is this still present after one reboot?

Where did you install this? Debian Jessie, Wheezy, Trusty, ... ? arm, arm64, amd64, x86 ?

Not possible to power on, only power off and standby/resume. You need to cut / add power. Xenial is not full ready yet. Stick to Jessie.

@chradev What are you building and where?

The script should rebuild cached file system since package base were changed ... i'll check. Walk around: remove cache and it should work.