Igor

I only tried to compile 4.2 Haven't got a chance to boot it. If kernel is ok than the most problematic part is patching. This cannot work properly for all new versions. I suspect this: https://github.com/igorpecovnik/lib/blob/next/patching.sh#L57 Restore that file from original and try again. BR

We'll get to the bottom of this somehow Sadly I don't have Banana PRO around to recreate exact scenario, only the original one. Until later.

Aha, are you using correct script bin? Is this in place? [sdio_wifi_pro_para] sdio_wifi_pro_used = 1 sdio_wifi_pro_sdc_id = 3 sdio_wifi_pro_mod_sel = 7 ap6xxx_wl_regon = port:PH22<1><default><default><0> ap6xxx_wl_vdd_en = port:PH27<1><default><default><0> [usb_wifi_para] usb_wifi_used = 1 usb_wifi_usbc_num = 2 Do a test with latest build on a separate SD card with only Wifi enabled. Perhaps on board wifi doesn't work together with LCD / I2S ? It's possible.

Google doesn't know ? Best Regards. This configuration thing is something I avoid all the time. The one I saw on raspbian and clones is more or less just a feeling that you are in charge. In reality you can't alter many things. OK, you usually don't need to either. Having a menu where you coud: - expand root (i do this automatic) - change password (is it hard to type passwd) - edit some conf file and save There are plenty much much better configuration tools. For example: - webmin - ajenti Why bother with developing something similar to raspbi config which is not really much useful. And ... Thanks!

OK. All images must work They are tested ... some problems might occur only with Jessie on certain Cubietruck boards as reported.

Huh. Are you sure you are using kernel 3.4.108 ? uname -a In kernel 4.x we have yet another module: brcmfmac

Module name is not apxxxx but bcmdhd They are more or less the same.

This is normal output. Console is set to HDMI by default.

Primary git is not yet updated, new (branch second) is under testing and last fixing ... Set u-boot tag to v2014.04 and it will work. R1 has troubles with current uboot. I haven't got time to look into details.

Just upgrade the u-boot. I assume you already add my repository? (howto: http://forum.armbian.com/index.php/topic/211-kernel-update-procedure-has-been-changed/) apt-get install linux-u-boot-cubietruck reboot I think this is all you need to do and you should be fine.

Perhaps your SD card is bad or file-system corrupted. Try again with fresh install / new SD card.

Hmm. Do you have NAND too? Was there any error during installation. Can you mount image on some linux comp and show the content of /boot/boot.cmd ?

Have you come here with upgrades or you started with clean image? Stability issues are in most cases related to U-boot and board configuration. Board conf hasn't been changed for a while, uboot is changing constantly. There was the same issue with R1 not long time ago. Kernel and distribution doesn't play any role here.

Some releases had stability issues. Which build do you have? Check: /etc/armbian.txt or /root/readme.txt Last one is stable.

It's possible but usually not recommended, especially setting all to Y. http://serverfault.com/questions/116299/automatically-answer-defaults-when-doing-make-oldconfig-on-a-kernel-tree I already add a lot of tuners. Use my new development config: https://github.com/igorpecovnik/lib/blob/second/config/linux-sunxi-next.config (the script branch will be default when I'll be sure everything is going ok)

Yes, they are all re-uploaded. Maybe you download them too fast? (server needs up to one hour for mirroring) Everything is the same but build date must be today. Build date: 31.08.2015 (armbian.txt inside zip) I test some of them.

(TIME) Time out waiting for device dev-ttyS0 device. Kernel 4.x and Jessie. This problems occur one some boards. Dunno why. It's working fine on my Cubietruck. One solution is to power cycle but if this won't help ... choose Wheezy or Trusty, try also to boot bare board, without anything on USB.

The most important problem here is that NAND is not supported in kernel different from 3.4.x ... If this is ok, than download latest system (4.1.6). You will need to boot from SD card, than change boot script parameter from root=/dev/mmcblk0p1 to /dev/sda, copy kernel files /lib/modules/xxxxxxxxxx from SD card to SDA. Boot from hard drive. Add /dev/mmcblk0p1 to your /etc/fstab and mount under /boot Done.

Fixed. Thanks for reporting.

Hey. No, the problem was here at my web page. I am doing something and I didn't notice that one module was failed Thanks. Everything is back again. For NAND restore you will need to do with Phoenix tools. No other way, sorry. (walk around) BR, Igor

Development is very much open so there is a constant interaction between users and developers. I do most of the distribution development, scripting, some kernel / u-boot patching and basic testing. What I miss, community find and it's usually quickly fixed. No special organization ... but I have top authority. Armbian started as an hobby ROM project for Cubitruck two years ago I am open to re-think and change the organization of the project.

Check if XVID codec is supported. I think it's not. Try if sample video is working: http://samplemedia.linaro.org/H264/big_buck_bunny_1080p_H264_AAC_25fps_7200K.MP4

Oh, thanks. True. Anyway, there will be no tar packaged deb files anymore. Everything it is now on the repository apt.armbian.com

At this point upgrade is ready only for advanced users. Repository: apt.armbian.com Key: http://apt.armbian.com/armbian.key Add to sources if not there: deb http://apt.armbian.com $(lsb_release -cs) main Packages naming logic for apt-get install: I. Kernel 3.4: Deprecated linux-u-boot-DEVICE_NAME-default (cubieboard, cubietruck, lime, ...) linux-image-sunxi (all) or linux-image-banana (for boards bananapi, orange, lamobo r1) linux-headers-sunxi or linux-headers-banana (for boards bananapi, orange, lamobo r1) linux-firmware-image-sunxi or linux-firmware-image-banana (for boards bananapi, orange, lamobo r1) linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...) I. Kernel 3.4 sun4i (Allwiner A10) linux-u-boot-DEVICE_NAME-default (cubieboard, lime-a10) linux-image-sun4i linux-headers-sun4i linux-firmware-image-sun4i linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, lime-a10) I. Kernel 3.4 sun7i (Allwiner A20) linux-u-boot-DEVICE_NAME-default (cubieboard, cubietruck, lime, ...) linux-image-sun7i linux-headers-sun7i linux-firmware-image-sun7i linux-$(lsb_release -cs)-root-DEVICE_NAME (cubieboard, cubietruck, lime, ...) II. Mainline stable kernel: linux-u-boot-DEVICE_NAME-next (cubieboard, cubietruck, lime, ...) linux-image-next-sunxi linux-headers-next-sunxi linux-firmware-image-next-sunxi linux-dtb-next-sunxi linux-$(lsb_release -cs)-root-next-DEVICE_NAME (cubieboard, cubietruck, lime, ...) You need to install all packages otherwise you might end up with not booting system. III. Mainline or developement kernel: linux-image-dev-sunxi More info: https://www.armbian.com/kernel/ Beta repository: https://forum.armbian.com/index.php/topic/2422-more-proper-testing-better-armbian-experience/

You need to alter boot script on your SD card /boot/boot.cmd and set from root=/dev/sda1 back to /dev/mmcblk0p1 (on the end of this line add loglevel=9 to get more output from kernel boot) Than you need to recompile boot.cmd to boot.scr. Tools: linux computer with installed uboot tools