Igor

This is the only way if you want things moving faster: https://docs.armbian.com/Process_Contribute/#collaborate-on-the-project New kernel, new bugs. At least module packaging is broken on 4.14.y and this needs to be fixed first. Then for H3&H5&A64 we have 100+ patches which might need fine-tuning ...

And how to implement this? For example - user clicks on: https://uk.armbian.com/bananapi/Debian_jessie_next.7z and Nginx randomly redirects to https://dl.armbian.com/bananapi/archive/Armbian_5.31_Bananapi_Debian_jessie_next_4.11.5.7z or https://dl.uk.armbian.com/bananapi/archive/Armbian_5.31_Bananapi_Debian_jessie_next_4.11.5.7z If this is possible to achieve in some trivial way, it is good enough.

Thanks to @pete He is fixing the theme.

Fixed.

When those 100+ patches are rebased on top of 4.14 from kernel.org ... few weeks/a month? Get our 4.13.y ... it has far more support (then upstream kernel) for the board you ask. In both cases, kernel remains flagged as testing while for A10 is stable for some time.

Back in stock. http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=3169&extra=

I just find out one more disturbing problem - search inside PM is not working (at least not for me) but I also made one improvement on Tapatalk module which was upgraded and its apparently less buggy.

https://github.com/armbian/build/commits/master https://github.com/armbian/config/commits/dev Yes, it should be fixed in tomorrows nightly builds. In case you find a bug, add it here: https://github.com/armbian/build/issues/new Issues are not my personal problem

It could update DEV kernel ... but anyway this utility is only for kernel 3.4.y The more recent kernel 4.13.y has EDID auto detection while 4.11.y is already deprecated / EOL - we don't deal with it anymore.

At least this is understandable on the surface - apt-update is running in the background automatically when the board starts the first time.

Remember that 4.13.y kernel is considered testing, a bad driver could hang the board, while the software ... it could also eat memory or something like that?

Thanks. Fixed upstream too. https://github.com/armbian/config/commit/18eab5971fa417e6b80344a4276d583e634c3beb

This still needed?

working on it done

Yes, under ... extras-buildpkgs/ ... than it would be best to do it now.

Probably some armbian-config dependencies must be missing but IIRC you need to start with a new image because overlays need also new boot script. We plan to rebuild images for A10/A20 next week. There this should work and if not, we will try to resolve the problem. Wait.

Try setting this to 0 and remember. You need to reboot twice. And provide full logs: armbianmonitor -u

Each ARM board has its own kernel development ... almost ... and then there is mainline kernel where support is very basic. No video drivers for example ... It is more complicated than this, but this explanation should be good enough to understand the problem. You need to port this driver from that kernel to modern 4.14 kernel and you will have it here. Check if is perhaps already ported to more recent development Raspbian kernels if exists ... in that case, porting should be more simple. We are just a few people and can't support all possible hardware on this planet - we already struggle with a base onboard hardware, which is easy on RPi since it is a simple machine/toy. If you or somebody port that driver, we will include it in the kernel. It might be a half an hour job or weeks. It's possible to build a driver on the board ... but. If things break this means there is some incompatibility with between source code, kernel and compiler. This problem is for you to solve.

OrangePi zero has much more recent kernel 4.13.y and will never get a downgrade to 4.4.y ... Download: https://dl.armbian.com/orangepizero/Ubuntu_xenial_next_nightly.7z

Due - which was set 4 months ago - is approximately next week. The easiest thing is running buildall.sh script at the due date but nobody would be happy with the outcome If you only want to try out, check nightly builds. We plan to rebuild what is stable, while the rest will be put out as automated testing build ... since not ready yet.

Perhaps Armbian? https://www.armbian.com/orange-pi-zero It's Ubuntu based on a kernel 4.13.12 which is still in development mode and the best what you currently find on the planet Earth.

Wait for a new release or update to beta, then use armbian-config to enable/disable desktop.

Try changing CPU governor.

So far you haven't proved anything while I provide you a specific evidence that image from download section works on Orange Pi One. Several hundred thousand happy users (don't worry about popularity) are another proof that you are doing something wrong and you refuse to accept. Act upon documentation, react to our bits of advice, ... Except for stock junk (Android, Lubuntu, Raspbian), most 3rd party distribution and compilations are made on the top of our "distro-developers-junk" work. Why?

This board is not finished - DT does not exist yet. Yesterday I add Nano Pi M1+ and M1 plus2 and I hope I manage to add this later today.