Igor

Hello! Bigger boards = better heat dispersion and (better) voltage control = less (over)heating, better (non microUSB) powering = better stability. H5 is noticable faster than H3 and has better software support than A64 => IMO Opi PC2 should fit your needs.

Anyone familiar how to get into maskrom mode with Neo4 ... and M4? Not exactly critical since eMMC can be removed but nice to know.

http://docs.armbian.com/User-Guide_Armbian-Config/

That is actually a good news

Probably network related troubles.Try again now.

In my two quick tests, I couldn't recreate the problem. It is pretty pointless since this is 3rd time to write you back and you still didn't supply logs. Without logs, a bug is not even filed up. armbianmonitor -u # at the image where this was recognized. Before continue to waste more time, read this: https://forum.armbian.com/topic/6281-board-support-general-discussion-project-aims/?do=findComment&comment=63605

https://github.com/armbian/documentation/commit/c6cfb75f75fa4f096eab5282dee06ad8ad518412 apt update and upgrade and its done.

https://github.com/armbian/build/blob/master/lib/general.sh#L645-L662

There was never a formal team. More like a strong common passion and interest to do something valuable, to push things forward, to help, to show how things should look like. IMO it worked very well until the level of self-fulfillment and happines was high enough and a mountain of problems low enough. People perception on this is very colorful and even among inner circle, we have different views. No matter how good and super the project might be. We have more and more users, while most of them waste our time and energy, contribute nothing and ask for more. This is not sustainable. Armbian might not need major build script or infrastructure development, but both need regular maintenance. We are short already for that. Not hardware, not software but responsibility. If board support is extending and developing, then this will bring solving harder problems which are not possible to be solved by a few people in their free time. This calls for 20-30x size of the budget size. Where from? On the other hand, people expect that "we will solve all the problems they find out". Reality is that our main workforce is basically offline due to overload, mounted problems, life, ... We can talk about how to reshape the project, but first, you need someone that will execute what we brained out. Personally, I need to look on a project from a distance and leave super (hardware) details behind. It might give me an opportunity to better see the problems we have.

I am trying hard to push it away from my personal domain. Surely possible that not properly or right direction.

I didn't have many choices - an urgent matter which didn't turn out well. Until this (and my many other duties) is not upgraded to something more pro, this remains as is. I would gladly not deal with this shit the whole day.

Working on it (moving to another server on the way).

You can try to track here: https://github.com/rockchip-linux/kernel/commits/release-4.4 + https://github.com/armbian/build/commits/master/patch/kernel/rockchip-default Not very human-friendly

Thank you. Fided among this cleanup https://github.com/armbian/build/commit/fd235d6c3467fb5ab735a638db84481927c299d6

Kernel 3.4.y is too old for running Stretch or Bionic hassle free. You need to update a kernel first, while new kernel have different settings and support level (video acceleration is n/a) ...

It was just a suggestion. If we want to get to the bottom of this, this is needed. You don't need to hack a u-boot if you already find the one that works. I assume you did find some older version that works? Than apply apt-halt on that package to prevent it's upgrading and you are done. Of course, this means you might suffer from other u-boot related problems ... Yes, it's complicated.

That is already written and it is used ad hoc or if a person bumps into: https://docs.armbian.com/Process_Contribute/ Instead of telling people what to do. Let's ask people if they want to take responsibility as such: - source code maintainer - adjust kernel configurations, patches, ... help on what we do, - project manager: development and testings overview, samples redistribution - code cleaner - sweeping our build script code round the clock - documentation editor - as a title implies - marketing manager - to help communicate project specific services, new features, changes, ...

... and restart this saga when they eventually upgrade their u-boot. Lol!

No need. It's a general kernel feature. Create a PR for kernel config changes when you figure out what exactly needs to be enabled - I don't know: https://docs.armbian.com/Process_Contribute/

Armbian is mostly ahead of the upstream kernel releases in board specific functions. Up to about one year. Regarding the biggest group (Allwinner), the only change will be that we will remove a few patches and when 4.19.y is sorted out it will become our NEXT for A10/A20/H3/H5/H6/A64 and Armada 3700, Rockchip, Meson, ... almost all supported board as a first or second kernel.

Ooops. I added wrong number. Will be corrected asap. Wrote on mobile

The quickest way is that you add them - we are extremely low on maintenance resources and it can take some time. Here are config files: https://github.com/armbian/build/tree/master/config/kernel

Then we need to solve this a bit different, via post-install script: https://github.com/armbian/build/commit/40e5ce955b39e689a35c05016cbdfcaba5d5f26c

I only adjust console with reality. I don't care where it will be, but it would be nice that we have it at one location on both kernels. Rather wait. You might go in the wrong direction. Work smart not fast. Try older bootloader first: http://apt.armbian.com/pool/main/l/linux-u-boot-tinkerboard-next/ This is the first and most cheap possible solution.

With: apt install linux-headers-next-sunxi you get latest headers from the repository ... but there is not a version 4.14.73 but a bit lower so it's good to start with the same kernel version too or as @chwe suggested.