Igor

Well, this kernel is how it is. There will be not much fiddling around but you have support for those displays also in the modern kernel. That is your best chance. Unfortunately, this kernel is also not quite ready so other problems might pop out. https://dl.armbian.com/orangepizero/nightly/ (apt upgrade might break your system at this moment so don't) https://docs.armbian.com/User-Guide_Allwinner_overlays/ (you need to enable SPI, so read this) I am not sure if this is all working as it should but its worth trying.

If you want to run hostapd on a certain interface you don't need to disable NetworkManager but add interface or MAC address to unamanaged-devices list: https://github.com/armbian/config/blob/dev/debian-config-jobs#L205-L208

Armbian has already a lot of optimisations regarding writings to SD card but you can go further with having virtual read-only system. Get Ubuntu with kernel 4.9, install overlayroot (from armbian-config) and add hard drive out of your read only section. Some memory will be used, which is not a problem on a board with 2G. And your SD card will live much much longer

Software support is the most important thing, when looking for a new board ... if you want to use it There are boards out there which look good by the numbers / in theory but are useless because support level is bad and will most likely remain that way for ever. Rpi3 is surely a better choice to run Kodi, but if you had chosen some H3 board than you could use it as a media center with Openelec quite decently. This board should act well as a server when support level comes to the user level. Currently, it still has rough edges.

Bad CRC at u-boot is normal behaviour, unrelated to the development stage of H5 kernel. This will be the best way to go for some time or learn how to fix things if they break on update and keep using the latest builds ...

Well, my recipe should work on stable builds, but in beta areas, there is no warranty - it might or not ... things are WIP. Try altering boot device in /boot/armbianEnv.txt or simply pay attention to build log changes https://github.com/armbian/build/commits/master

Fixed. The logic goes this way. It's XU4 template with exceptions. I changed data while for the rest a small rfc was needed since known issues were per family. Now per family can also be overwritten. If you create a file odroidhc1.md in here, it will be presented as "known issues" at HC1 only. Currently, there is none. https://github.com/armbian/documentation/tree/master/docs/known_issues

MALI has nothing to do with video acceleration - is a 3D engine, useful for gaming etc. It's unlikely that will ever hit mainline kernel while video acceleration, which we use is open source. Some day will also work on modern kernel too. Wireless driver on the modern kernel is better for this chip, so you should be able to use it.

option one: edit /etc/apt/sources.list.d/armbian.list and change apt to beta, save, apt update, apt upgrade, reboot option two: armbian-config, switch to beta (nighlty or daily build), reboot Nothing else. If kernel flag is changed in this file: https://github.com/armbian/build/blob/master/config/kernel/linux-sun50i-dev.config then you should notice changes. (this config is responsible for the kernel you are using).

OK, will check Udoo and Cubox in Monday. Cubox is critical since they use pre historic u-boot. Will check if there is working alternative.

If you want to test latest builds, it's also fairly ok to download just any available image for this board, switch to beta repository and update. It will work in most cases.

OK. There is a problem with a wireless driver which is bad quality and nobody is fixing it anymore. Its known to hang at unloading and then watchdog restart the board. If you remove ap6211 from /etc/modules ... power off will work. If you don't need video acceleration functions move rather to a modern kernel, which is a much better overall condition.

Images manually, while deb packages are done daily. https://beta.armbian.com/

Which kernel and what is your configuration? How to do you power your board? Do you have a battery ...

H3disp was moved to armbian-config yesterday as menu driven thingie and can be removed. Wrote on mobile

Can't tell exactly for this case, but it's possible that you will need to start with the different - correct base. Some complex installations don't just work on Debian and Ubuntu at the same time. I can come out with one example (Openmediavaoult - OMV), which works on Debian but not on Ubuntu. At least not out of the box. This is one of the reasons why we provide Debian and Ubuntu base.

You need to update boot loader in any case. Recent eMMC cards have updated bootloader and it works out of the box ... we will provide updating eMMC from armbian-config, but it's not implemented yet. You will need to boot once from SD card with attached eMMC and update boot loader on eMMC from menu (or manually). Than you are done and you can either write IMG to eMMC or install via our nand-sata-install utility. BTW. We solved only low level problem and boot loader, once you have the system running on eMMC is being updated.

There is only one image for now. The one with DEV in the file name. Wrote on mobile

You have a wrong board. Get at least some H3 based board, Orange Pi PC+ and find some HDMI TV. Analogue TV out is bad quality and you need to solder connector. Not something for a beginner. Or get a serial connector and forget about TV.

OMV can be installed from armbian-menu in no time. Perhaps a note about this should be added there? Debian Jessie is a must. Edit: And merging those two recipes might have sense: https://github.com/armbian/config/blob/dev/softy#L282-L316 https://github.com/armbian/build/blob/3845004787d76485be8b53d77a3c776f07f0d472/config/templates/customize-image.sh.template#L34-L205 Some work

I am aware of all those endless possibilities but am not really sure if we will raise much more money if we just add more ways for donations. I am somehow sceptic about. Very sceptic. IMHO the best (and also simple) end user donation way is Paypal, Bitcoin donations (for example) are second best, but they are few hundred / year (half of the amount was made by exchange rate rise) while everything else is just scrapping - if you don't put a lot of efforts into serious money raising project. If getting rich would be a goal, we would not do Armbian in the first place But in any way - more cash helps but also brings more problems and expenses. When there are few people, like we are now, you don't need advanced administration, PR or dedicated project leaders etc. This is a must when upscaled. I think first we need more people, volunteers like us, which perhaps later become a pro, when and if we reach that level or part time which is already possible in some way. Slow development keeps stress level reasonable and nobody need pills or waste amount of beer to keep up Current cash flow covers basic infrastructure costs. Hardware samples (at least boards) are thankfully mostly donated from vendors and I also got few items (in few years) from Amazon wish list (SSD drive, keyboard, WiFi card, SATA controller and few boxes of beer). It's nice to get those gifts and it's nice to get cash donations, but they cover only a small fraction of the work and do not cover a single engineer pay check. Everything that we collect is this way or another reinvested back into the project. The main problem still persists with or without our project: Jumping from here, where donations are simply broken among developers, to professional level seems quite a challenge - from a small group of volunteers without any non-technical worries to a company which has to make money. We are doing this for the sake of fun, to learn something, that some expenses are covered and perhaps once there will be more or we find a better way to fund a project.

Got similar one, also hot like hell ... chip was covered with some nail polish or something. 1st post updated with 2 x 840PRO in RAID0.

First setup ap and than connect to wifi with another adapter ... it used to work for me even on 5 connections and one AP. I am still working on it and bugs are possible ... Wrote on mobile

Then provide your configs to take a look. You can try to use this wizard - https://github.com/armbian/config - it should create everything for you. It's under active development and I still find some issues every day

Yes, check this tutorial and check your board if SPI pins are at the standard location. In most case they are. https://docs.armbian.com/Hardware_Allwinner/#connect-your-lcd-display You need to enable it if not enabled. That's all.