Igor

Quite the opposite. It's completely irrelevant what do you want. It's a trade for the time which is the far most expensive resource and for example, the one which I want to spend with my kids. Can your problem match this level? No. Can you buy time? No. I put this price tag/stupid answer, to keep people away from sending technical questions on email / PM. Is it possible for us to provide free one to one technical support for tens of thousands of users? It's mission impossible. A public forum is the best what is possible.

There is a 5V on the clickboard header. IMHO it should be enough to power SSD drive. Double check specs if it's safe. I did it once for testing and the board survived

Try this one: https://github.com/armbian/config

I am getting out if ideas how to stop this. Simply ignoring? Or replying in public with such stupid message? Wrote on mobile

The same message was sent to my PM a few minutes ago and I am really getting pissed off on this kind of abuse. It's 3rd this week

Private consulting starts at 200 EUR / hour. You can use a donate button. Then I'll read what do you want and try to help you.

Another related to this topic. Rockchip VPU driver call for testings.

Some of my thoughts. We are trying to follow those directions. Roughly, very roughly and perhaps we should be more aligned to those plans - especially the date of feature freeze - since I believe some structure helps and this way it's less panic and compromises when the date of actual release come by. But where to draw the line? Can we afford to be strict? Does it make sense that major long term projects are broken to focus on bug hunting and code cleaning? I think currently, there are not enough developers to make two groups - one staying on the edge and the other staying on the stable edge. How many - for such organization - do we actually need for the project as it is today? I saw people on this forum saying: "I want to help", "Can I help", ... Hands up! We need your help. Everything what @Tido already exposed plus armbian-config (https://github.com/armbian/config) also needs extensive testing and code cleaning to be ready on time. I will also find some boards for those who are willing to step forward.

All of them. With Armbian - some 3rd party Linux might not have those screen resolutions. Original Allwinner kernel has only a few of them. Good pick. Exactly. With H3 you have the best chances for success.

That is true and that's why I added links with information with most frequent problems. If you already know everything, why do you ask? Orange pi Zero is the most downloaded image and you are the first one that have problems. What do you expect from me?

There are 100-200 downloads of Opi Zero images every single day only from the main download server. Don't have data for torrent download. There is not a single doubt that the problem is on your side. https://docs.armbian.com/User-Guide_Getting-Started/ https://forum.armbian.com/index.php?/forum/31-sd-card-and-power-supply/ https://www.armbian.com/donate/ Nightly images are of course untested.

@scargill Pete, try this image: https://dl.armbian.com/orangepiplus2e/Ubuntu_xenial_next_nightly.7z It's 4.13.1 (first common image), still considered a testing one, but it works quite well. Go to armbian-config -> Armbian -> Overlays, choose function, press Save and go back. It will prompt for reboot ... It's tested for enabling audio via this menu and it worked after reboot. If you plan to use this image more seriously, freeze kernel update. Also from the menu.

Yes. I use one of those as my primary test device. With cheap HDMI 2 VGA converter. All mentioned boards and kernels which run Armbian support this screen. Get one H3 board, use the legacy kernel and check how can you make use of boards 3D engine (MALI) in the software you are planning to use. Note that those boards use some simple 3D graphics and some hack might be needed like open GL wrapper ... in any case, your best and only way is to proceed with some H3 board. More or less all are supported on Armbian, just go for the one that suits your need best. In term on peripherals and physical dimensions. If you need 3D engine, forget about mainline kernel and more powerful boards. Software support is the key element. Bad or not existing ... you waste your time.

That is alright. We are waiting for 4.13.x kernel to become matured enough. Then we will promote its usage with a big button ... support could burst into flames if we decide to promote unfinished products to end users. Even finished products are hard and costly to support.

https://forum.armbian.com/index.php?/search/&q=AP6212a There were some discussions and AFAIK I made some dirty hack to fix this firmware mess. It looks like it's not working ok.

Download older version and not update. You are using development image which comes without end user support. Hint - DTB file is not in right location: ERROR: Did not find a cmdline Flattened Device Tree

https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver

The answer to this can be either simple or a complex one. I prefer to give simple tips in complex situations like this: start fixing things which you understand today. No idea why, but help to find out why is certainly appreciated. Sources: https://github.com/armbian/config (armbian-config is a separate project) General collaboration info: https://docs.armbian.com/Process_Contribute/ Add: I just realized that you only wanted to test that we could fix it faster It won't help. Especially not in this case. We call for end user testing when it's hard to find troubles.

Not if you install desktop on your own which is most likely the case here.

Well. You switched to DEV kernel, but you actually should switch to BETA repository, where you would get an update for the kernel that you are using and where I made a change. WiFi might not be enabled in DT while drivers should be present in the DEV kernel ... but you are on your own to fix this. Development kernel comes without support since it's rapidly changing. If you are not able to fix such troubles, go back to legacy and switch to beta/nightly repository.

We are not clairvoyant or mind readers Please describe your setup as best as possible so we know what your operating environment is like. 1. Logs, when you can boot the board: armbianmonitor -u (paste URL to your forum post) 2. If your board does not boot, provide a log from serial console or at least make and attach a picture, where it stops. 3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem.

There is no GRUB on ARM boards. /boot/armbianEnv.txt Change those two parameters and reboot: verbosity=9 console=display

I have plenty of top quality dead SD cards around. Trying with another SD card is the first step.

https://github.com/armbian/build/commit/a24cc926db053b5a8a0c7fb891724dff24bd3809 Now you have two options - build a kernel on your own or wait for tomorrow auto build - around 20 hours from now. You need to switch into beta.armbian.com repository to get that update. P.S. Welcome

If you need this feature "today" adding a patch to the build system might be a better and faster way.