Igor

https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md Untested.

You are obviously using developers/testing/nightly versions where regression is more than expected. Currently, all developers Rockchip kernels are broken to some degree due to severe upstream changes. Check these tips for recovery: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system

Most wireless drivers code is of low quality and it needs fixing that it's possible to build, than sometimes you need to fix it that it works ... Have you ever asked why certain drivers are not already a part of the mainstream kernel? Some drivers are. Because the code is good and compilation works. Even there, problems/regression is possible. There are extremely slim options that something is wrong with the kernel. You can switch to the beta repository and try two other kernels. First updated 4.14.y and 4.17.y and see if you get the same results. If none works ... you still can use old kernel (not recommended) or buy a well working and supported wifi dongle ... or dig into this driver issue on your own.

LEDs and perhaps incompatible monitor are not a proper tool for diagnostic. Again a lot of time was wasted and we don't know anything specifics. Armbian uses mainline u-boot and modern kernel and all others use the same, one and only stock u-boot with old kernel since there are no other options. Your problems are below the operating system. Get a serial console and check Armbian Stretch for One (the exact image which I test and it's 100% working for me) and one other which uses stock firmware. When we will see the actual serial console output, we might know why this problem exists. Also use other SD card .., etc. This image would also be worth trying: https://dl.armbian.com/orangepione/Ubuntu_bionic_dev_nightly.7z It has most recent u-boot 2018.03 and kernel 4.17.y

It's plain simple. 1. Update to the latest nightly build (optional. there this method works 100%) 2. armbian-config -> system -> install minimal desktop | install desktop with a browser

I just test this image: https://dl.armbian.com/orangepione/Debian_stretch_next.7z and it boots straight up. Perhaps you are facing this problem:

Merged. It will be in the nightly images in a few hours from now. Feel free to call for action. Changes are written in the commit header and from that, it can be extracted what we should pay attention most.

For future images: https://github.com/armbian/build/blob/master/lib/distributions.sh#L54-L59

Thank you! But only together we can manage with the complexity If any kernel config changes are needed, we urge people to send PR against build engine. You can find Espressobin, kernel family mvebu64, configurations here: https://github.com/armbian/build/tree/master/config/kernel ... and general howto here: https://docs.armbian.com/Process_Contribute/ Changes lands to the beta.armbian.com package repository in less than 24h if all kernels building succeeded. Try.

Or enabling those: https://github.com/armbian/build/commit/ea4723a445f8167ad7250bb97aed79a43665ee77

Thanks. O.K. I will do few more tests with your changes and then merge in. It was tested well, but we all know how this goes. Let's point out for more profound testing when changes reach beta repository. We need to make sure upgrading won't break, while for new images I am not worried that much. One a bit radical idea, which crossed on my mind - do we actually need a swap file enabled by default? In general, features of the old armhwinfo scripts weren't changed much while the change logic was hopefully met discussion above.

Because our resources are underpowered "to fix everything". There are thousands of such small, add-one-line, issues on the task lists and only a few people are dealing with maintenance. A list is getting bigger and bigger while our resources stand still. All those few people also answer questions, develop new features, test, write documentation, ... And honest appreciations are more or less the only external reward. Thanks!

Then scan at least our documentation and read promoted text on the forum - how to apply for help. There are more than one kernel and more user spaces (Debian Jessie, Stretch, Ubuntu Xenial, Bionic). We deal with a great number of boards, some of them are similar, some have some special features or even hardware bugs or come with different board revisions. To cope with this complexity it is urgent that you supply logs with our tool: armbianmonitor -u This is minimum, that your problem is addressed. Without seeing your system logs, there are more options, which can only confuse you more. Before you do this, use search (ap6210 wifi, access point, bananapi hostapd, ...), and read. In any case, we have no capacity to guide you.

I use this one.

It works - I use one on a daily base - but nobody can't give you the warranty that it works precisely with that one.