Igor

Yes, your board will receive full updates. Currently, we are at kernel 4.9.y but this NEXT is about to be upgraded to 4.14.y when its time. You don't need to change anything.

I upload new images, tested today. Except for those few noted issues, board performs nice.

Perhaps here: https://docs.armbian.com/User-Guide_Allwinner_overlays/

You need to update u-boot as well.

Problems were detected when upgrading from 4.9 to 4.14 ... kernel 4.9 is just fine for and has UAS support.

Wireless chips on those boards are mostly low performance - all are 1T1R and N at best. It's probably enough for streaming video under optimal conditions. You have to pick 3rd party USB wifi module carefully since kernel 3.4.y is very old and most of the modern ones won't work there. A20 boards are not really the best choice for KODI so I would rather pick something else. A big step forward are already (cheap) H3 boards with dedicated Openelec or some Amlogics on a bit expensive side.

Because 4.14.y has issues - some people ended up in a boot loop - which is not resolved yet.

Do apt update and upgrade. I added a new version of armbian-config to the stable repository ... try once again @y52 might have the same problem.

Armbian doesn't provide a kernel that is long time deprecated. We use the latest and there https://github.com/MarvellEmbeddedProcessors/linux-marvell.git branch linux-4.4.52-armada-17.10 ... there is only one DTB file which works. As is. We recommend using 4.14.y kernel and not (lower quality) factory kernel. Can't replicate on the latest build. I download default 4.4.y, switch to NEXT 4.14.y and back to 4.4.y Working as expected, logs: http://ix.io/1agA This menu can be missing if you froze kernel upgrades, severely change the system or in case of network failure.

Kernel changing is super simple. Go to armbian-config -> system -> "Switch to alternative kernels". Switching between default and next should be safe, but it was not tested yet on all variants and it's good that you didn't make any changes to the boot scripts.

Yes, but you need to develop them first. Bootlin will develop required video codecs for 30.000 euros but it's not done yet. Then some changes to video driver might be needed, then implementation and debug ... few more months in the most optimistic scenario. This WLAN - when it works - is probably too slow for multimedia.

And it is stable. Wifi is another area ... we do our best but and this used to work somehow in the past ... probably its a problem with a wrong firmware since nothing else hasn't been changed. As soon as we get a working video acceleration and 3D on a modern kernel, this kernels is gone. That functionality is the only reason we keep it for download.

You can use modern kernel where wifi is operational.

If you use our build and you upgrade/change kernel via armbian-config you don't need to worry about that. https://github.com/armbian/build/blob/development/config/bootscripts/boot-espressobin.cmd#L22-L23 Mainline uses different DT name (armada-3720- espressobin.dtb) and it could be aligned once but now is as is. Mainline kernels have much higher quality standards than vendor kernels which are usually full of dirty tricks and quick patches. Usually, vendor kernels have more special advantages but I think there are no more reasons (advantages) to stay on a kernel 4.4.y anymore.

What is consing? You have a kernel version in a filename. "default" = old kernel, which is 4.4.something for this board "next" = new kernel, which is 4.14.something for this board If you want to upgrade your default 4.4 to 4.14 you need to switch branches. Manually or with armbian-config.

We promote 4.14.y simply because it is a better choice now. Click on area rounded with red color ... to see other (older) choices.

Correct. There is no NAND support in the modern kernel. You use it only with old kernel builds ... Jessie and Xenial. Kernel 3.4.y is too old for Bionic or Stretch.

With a clean image. Not via upgrade. Well, even I think I fixed something, this might not always be true. Sometimes some vital part is somehow lost in the commit phase. Will check. The same. I am not sure everything already works as expected. I haven't check any upgrades yet except installing a desktop on top of the latest CLI image. I agree. Let's plan this for next.

Are you holding a boot key? Images should work. I'll check them again when I am back to the office.

The modern kernel has a different way of setting hw features. Use armbian-config and/or read this: https://docs.armbian.com/User-Guide_Allwinner_overlays/

Blacklist in-kernel driver and search around for more recent known to work drivers (sources), install headers and compile the module. Repeat until you find a working one. When you find a good working one, we can once replace them with those shipped with the kernel. Ideally: send a patch against kernel source.

Yes, video out is not yet supported.

You have to boot the board first. Usually, it's not just kernel and u-boot, but up to few other (pre)loaders. Packages optimization is a fairly simple task. If our default package base is a too much, use PACKAGE_LIST_RM parameter when building an image to remove what you might not need. https://github.com/armbian/build/blob/development/lib/configuration.sh#L219-L222

Our build system downloads most used compilers but to tell you which exactly is appropriate for Hikey board u-boot/kernel sources ... no idea. You can try to play around this way: 1. Define a board config https://github.com/armbian/build/tree/development/config/boards 2. Define a source config https://github.com/armbian/build/tree/development/config/sources Check this example for RK3328 ... https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L32-L43 default branch, kernel 4.4.y need to have a version higher or equal than 6.3 KERNEL_USE_GCC='> 6.3' while kernel dev branch 4.17.y needs KERNEL_USE_GCC='> 7.0' ... u-boot and atf have their own settings. We know that This board is aarch64 (https://github.com/armbian/build/blob/development/config/sources/rk3328.conf#L1) and this way systems knows which compiler to choose. Sometimes trial and error is the fastest way. We use those: I hope you will find those hints useful.

Well, you need to start with an image. If you start with CLI, you should have more desktop install options now. If not ... then I need to run rebuild again. Desktop versions should be installed by default. That's good. Uninstalling should be possible from armbian-config menu ... but BT icon could remain there. On your 1280x1024 monitor? Well, probably it doesn't have this resolution and pick 1st appropriate one. Still better than having some complete invalid. Anything is possible but do we need to mess up with changing this? It can look ugly if not done properly. Yes, I noticed those problems but dunno what's the problem atm.