Igor

We can't start to resolve this: - without any logs or - without possibility to reproduce and catch logs. I don't have eMMC card for XU4

I have no idea what you did wrong at self compiled - most likely you failed at writing stage. For diagnosing the problem, you need to provide build logs and you need to do more tests, not just one. What hardware you have is pretty much irrelevant - just follow the guideline: https://github.com/igorpecovnik/lib#how-to-build-my-own-image-or-kernel

What if you use our prebuild images and other writing tool (Etcher) and some other SD card ? Error only indicates some state of fs corruption while "Warning - bad CRC, using default environment" is normal, ask Google.

Now it depends of the use scenario. Old kernel is also not perfect, has bugs and ... it's old, general support is fading. Mainline kernel is still considered development with H3 chips ... so I would not stand on neither side, while I would recommend mainline kernel for older Allwinner chips, A10 and A20. There, it's clearly a better choice in most use cases, instead of old stock kernel. Soon, here (H3, H5, A64, ...) it will be the same.

https://forum.armbian.com/index.php/topic/3267-eth0-stuck-at-half-duplex-orange-pi-zero/

Read two posts up.

I guess you also doesn't have serial console? We would really like to fix this, instead going back to older schema.

If you want to try, just go ahead, but if it doesn't work you are on your own - pleads for help will be ignored. That's the main difference between supported and unsupported board / kernel.

https://forum.armbian.com/index.php/topic/3267-eth0-stuck-at-half-duplex-orange-pi-zero/ https://www.armbian.com/search_gcse/ half duplex -> first hit

TV module is build in while it's in bad shape and we haven't touch it - it's stock Allwinner. I recently found some related tips on Facebook: https://www.facebook.com/groups/1131759626884432/permalink/1322666627793730/?hc_location=ufi

I also successfully send and receive between Banana Pi running 4.9.7 and Android phone running Android 6.0.1

I have this one: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) and it works fine. I only test keyboard and mouse. Check this: https://wiki.ubuntu.com/HardwareSupportComponentsBluetoothUsbAdapters This one: http://www.dx.com/p/bluetooth-v4-0-csr4-0-usb-dongle-adapter-black-207993#.WJY3tFUrLAQ should also work but haven't test it yet.

There is only one boot on mainline kernel since some time. We optimise a little, there is no need for reboot and more detailed output is to serial console. Login and start using it.

nand-sata-install script is present on the system. Just open a terminal and type. You have to boot from SD card and have eMMC present. Unfortunately this scenario is untested by me so I don't know it it 100% works. It should.

If you want to have picture on the screen, monitor must be attached at the boot time since it performs auto detection. There are problems with some HDMI2DVI adaptors, but we have a solution for this (kernel 3.4.113). It's called h3disp (run as root and read what pops out).

Kernel 4.8.4. You are using developing kernel for which we don't provide any end user support. It's meant for developers and testing. On the download page, there is a big red sign: Warning: nightly downloads are automated untested builds and no end user support is provided for them! If you want audio and microphone with this kernel and addon, which is not officially supported yet, you need to write a driver. There is nothing like "install a driver". http://linux-sunxi.org/Linux_mainlining_effort / here you can see how far things are developed You will have more success with old kernel 3.4.113 ... but even there you might need to play with board configuration (/boot/script.bin) switches. Microphone or audio might be disabled on this board, since by default it doesn't have audio connector.

Check this patch: https://github.com/igorpecovnik/lib/commit/ba3548468ed915f0540729526b16512ee48da7aa You need to add &emac section to your device tree. Nothing more.

Perhaps logram size is too small for your scenario ... disable or debug the ram logging service. systemctl disable log2ram.service

Can you perhaps provide serial console boot log? Unfortunately I don't have any eMMC for XU4 around. Are you trying to boot mainline kernel 4.x ?

There are slim chances of mainline kernel for this board although we have it for Odroid XU4 and I saw some bits for other Samsung chips, while not for this particular one. Even if you could boot it, there will be very limited support. IIRC Odroid XU4, which is one of most popular boards with Samsung chip, doesn't have any multimedia features, not even a HDMI driver in mainline kernel ... here you can expect only worse than that.

Update from old (testing) images might broke, while images works. I just download, burn and boot this image: https://dl.armbian.com/nanopineo/Ubuntu_xenial_dev.7z on my FA Neo. Network works out of the box. If you made a download yesterday, you could accidentally download broken image. I was correcting those images manually during the evening since I figured out, that network was disabled.

Thanks, will be fixed asap.

https://github.com/igorpecovnik/lib/commit/a83a6957f523946096b1009d0fb1e0f06b88f614 Added with patches. I only try if compile.

NanoPi is a good choice but AFAIK CSI camera, if you need that, is not yet supported in modern kernel.

Hardware is dirt cheap while "free" software can cost you some money. Luckily, if you start with Armbian, your basic things are covered - you already saved yourself hundreds of hours and dollars. That's our main advantage - you don't need to start from a pile of junk (Allwinner stock SDK) or spaghetti tutorials. Why? You are wasting time. Forum is more or less inactive and their official support, just not worth the trouble creating forum username. Still better than fixing legacy kernel where those things also doesn't work.