Igor

Exactly which image? Kernel version? How long do you wait? First time it takes few minutes. Try another SD card.

If SD is inserted and there is an u-boot on it than it will always start from SD card. Forget about my install procedures. They are only good for fresh start. 1. Create SD card 2. Boot, wait that it finish first boot 3. Login and alter boot scripts to point root to /dev/sda1 4. Copy /lib/modules/ to /dev/sda1 to make sure you have right modules 5. Reboot I think that's all.

If /dev/nand1 is mounted under boot your SD card boot was most likely ignored. I suggest you to forget about NAND and use good/fast SD card for best performance with less troubles as possible.

I am going to add root pwd expiry and setting hwclock to some fixed date, 1.1.2015 to firstrun script? Next build will also come with new uboot 2015.07 which might help with this issue. I don't have those problems so hard to tell.

Power button is not supported by kernel 3.4.108 which is currently the only one where audio features and boot from NAND works. This is common for all distros. Possible solution is by using any A20 board with kernel 4.x and some supported external DAC while boot loader must remain on SD card. Loading system from SSD is possible in any case.

No, if you were booting from NAND and running from SATA before.

If you already have your roofs on sata all you need is to change parameter: from root=/dev/mmcblk0p1 to root=/dev/sda1 inside boot.cmd and conver it to boot.scr.

I am almost out of suggestions. Try two things: - boot from SD and leave everything as is. SATA install yes but not boot from NAND. This part is critical in any case since it's based on some very old boot procedure. - use rather kernel 4.x if you can use with your hardware - change SD card, PSU

Yes I did. It was irrelevant. The problem is that if you are using NAND, you are using NAND uboot. So Uboot is not related - at least not the one on SD card Are you using any "strange" applications?

I think the problem is kernel loading address. Check this (working) boot script: setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt.global_cursor_default=0 quiet ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file} ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 Forget about converting. I think it needs to be zImage.

Which kernel are you using?

You are doing everything O.K. Change console output to serial to see what's going on and where it's stuck. setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=ttymxc1,115200

No, you don't need to recompile kernel, u-boot or download anything. You need to de-compile device tree blob (/boot/imx6q-hummingboard.dtb or /boot/imx6dl-hummingboard.dtb), edit / add, compile back. DTC compiler is within the image. @Moorviper Patches are added to the source.

Yes, I'll simplify this procedure some day. Wrote on mobile phone

Huh, I am a bit confused. Image with kernel 3.4 should work normally but it's possible that you need to use this module: bcmdhd Its from Cubietruck which is practically identical.

And remember to add this boot script: /boot/boot.cmd setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=3 2 ahci_imx.hotplug=1 quiet ext2load mmc 0 0x18000000 /boot/dtb/imx6q-udoo.dtb ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 And convert it to the uboot format: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr And of course adjust according to your conditions. This is for one partition SD card. If you have first FAT than some extra work is needed.

OK, I think the only problem is that architecture name does not match. I think this should help: dpkg --add-architecture armhf

Have you try to install this on my image or some other?

No. Everything is prepared until: "Get driver source & type make ARCH=arm" From there you are on your own. I can guarantee that the driver will work. Install part is also on your own / from the driver if exits. P.S. But there is a driver already on the system: rt2500usb rt2800lib rt2800usb rt2x00lib rt2x00usb

I am having a similar situation but failed to find appropriate / cheap 5Ghz AP. I own three dual band wifi devices (2 x mPCI 1 x USB) and this one is the only one that it (almost?) work. Others, Atheros 9382 doesn't work at all and Intel 7260AC simply does not support AP in 5Ghz. You'll need to ask driver maintainer for additional help & tips: https://github.com/gnab/rtl8812au/issues

You can eliminate one error with upgrade: apt-get update apt-get upgrade reboot

No idea either . I'll take a look. I am fixing the whole build structure. BTW: apt-get update works now . Need some more testing to make sure. sunx-mmc patch caused an build error on 4.1.3 .. huh

Ignore errors, you are running DEV version. Not related. Try loading the driver with: modprobe saa711x Are you running PRO Banana with Wifi or normal one? What you got under lsmod If you want to tweak kernel more I suggest you to establish DEV environment like suggested before.

Not much but look what I did. - latest fresh image 4.1.2 - git clone https://github.com/gnab/rtl8812au - make and load driver - use default hostapd-rt.conf and hostapd-rt binnary - use interfaces.hostapd it works normally. Not tested for 5ghz.. busy @moment.

It's much simpler and faster to add this functionality than teach you step by step how to do it ... even if it's written clearly enough for average Linux user. But problems might occur and this bring more questions. Read forum / FAQ and you'll get much needed info. It's simple but you need to invest some time. Download this image and burn to SD (wait until it's uploaded) http://mirror.igorpecovnik.com/Bananapi_Debian_3.3_wheezy_4.1.3.zip I added support for Philips SAA7111/3/4/5 video decoders You need to use my image for easy update. For rest read FAQ. Some manual work is needed. I never try to compile kernel on device because it's way to slow. I don't know if my tool works without any fixes but in any case you need to download a proper Linux source. And I hope you know limitations of kernels 3.4 vs 4.x ? BTW: most important things are documented on my blog, sunxi wiki, ...