Igor

Actually, you only need to update. The stable repository has been updated since some other problems were fixed. apt update & apt upgrade + reboot

@m][sko or anybody. I am adding this board with economy worldwide shipping as an extra motivation for this task It is not a huge task and we will assist in case of troubles. Building has to be reasonably well tested to catch as many upstream (debootsrap) bugs as possible. It is valuable to transform unknown bugs to known one. When Bionic builds and boots with minor problems, the task is done and I send the board out.

I remake image - v5.41 at download - and Bluetooh is up but I was not able to connect my keyboard Can't do anything more atm.

Only one important remark. Kernel 4.14.y is the first modern stable to be for H3 boards and it is the best what exists ATM. Some features are not yet developed and are certainly badly tested. Bugs are possible to be hidden. Even there is a "stable" in the build name, we consider and label all those images testing (at best). Subsequently, there are not many real cases or manuals with this kernel around. Until few weeks, there was only some half-working development builds. I personally don't deal much with IR so I am not aware of the details. This will be also a good source: http://linux-sunxi.org/LIRC

It must reappear on next boot. If not, then this is a bug or systemd related "feature". Try adding service hostapd restart to /etc/rc.local right before "exit 0"

IMO you don't need to touch anything. OMV uses our kernel from repository without changes. Yes, there are more fixes - from our and their side - in our latest. Both are created with our build tools, except Kobol's was made from an unofficial/user-build/development fork, without our direct support.

OK, I'll check.

Since mainline u-boot support is somehow behind for A388 boards, we use board maker's source. They are different for Clearfog and Helios4 but they share the same kernel(s). Suspend & resume is rarely implemented nor needed on those boards. From my head, I don't know how is the situation.

Official OMV for ARM hw is Armbian based. What you look for is enabled by default on both kernels: https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu-next.config#L4104 https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu-default.config#L4617 Rebuilding kernel - if you need: https://docs.armbian.com/Developer-Guide_Build-Preparation/ OMV install: armbian-config -> software -> softy -> OMV or softy -> OMV Debian Jessie base is recommended for stable OMV.

Download image then. We barely can provide support hints, while one to one guidance and teaching is not possible.

It can be very simple: download latest desktop image - it works there out of the box. If you are familiar with scripts and hackings, scrap the commit log and fix your current image.

Where? Thank you!

Trying different cables?

Are your external disk drives self-powered or via USB? Insufficient powering can manifest in such strange ways. In any case I'll try to recreate to see where is the problem.

Did you use a fresh image with a default kernel or you were using some old and you made an upgrade and then switch to NEXT kernel? Can you provide a armbianmonitor -u from the image you did this test upgrade?

(new) repository script update forgot to trigger a mirror update. Fixed now.

.. but sometimes it fails to detect some AP's even after many scans. If that some is yours ... bad luck. It works for some people well enough, but we can't say its reliable.

We and we as community wasted hundreds of hours in an attempt to fix this situation but failed. Forget that this board has wireless. This wifi chip is one of if not the worst ever seen. https://forum.armbian.com/search/?&q=xradio https://forum.armbian.com/search/?&q=orangepi zero wireless We ware thinking to remove the driver entirely since it makes little sense that it is there ...

The system version will not change since updates were made only to the kernel. It's safe to ignore. Also for those who temporally switched to the beta, you just switch back to stable. Kernel will remain "5.41.180208" until it will be updated with a more recent stable version. Switching repository back to stable is important.

If you have a DHCP powered network, you should get an IP and login via SSH. Does that work or you are not getting there? Edit: image you downloaded, boots fine: http://ix.io/FCI (my board is PC+ since I don't have a normal one, which is identical. It only lacks eMMC and wifi)

Not long ago we enabled HDMI on this kernel, while driver itself is still under development. I am not aware of the details and if TV out also works. I have little interest and don't have any equipment around to test this (low-quality) output anyway. People said its barely usable. Since TV support hasn't arrived at the "armbian-config" menu to set it on and off, you need to dig deeper. Check 1st if some of the developers have already made a progress. If you desperately need TV out, use an image with kernel 3.4.113. If you insist to use a modern kernel: Use search Check kernel development status Use search here The kernel is the main thing so it is irrelevant what OS you use. Since you also wasted time on Dietpi - they only rebrand 3rd party work/kernels - a lot of ours, in this case, and provide no updates and no support. TV out is build-in a kernel by default in the legacy 3.4.113 kernel: https://github.com/armbian/build/blob/master/config/kernel/linux-sun8i-default.config#L2798

A stock display settings are set to 720p and if you have some extraordinary display, you need to login via serial or network and then use h3disp utility to set correct one, but first ... strictly follow procedures written in Getting started. SD card and power problems are very common and their symptoms can also show this way. Make sure you use Etcher for writing or check what you write. DD doesn't check and SD media is can be crap. Wait a minute and you should see a login prompt. You need to create a normal username if you want to run a desktop. When you do those things, desktop starts automatically.

Kernel for H3/H5 and A20/A10 has been updated and pushed to the repository. I made 24h severe burn-in testings with three boards: Cubietruck, Orangepi 2E and Orangepi Prime. I did nasty things to them and all are still running.

You need Debian Jessie (for current stable OMV) or Stretch (for OMV development version) based Armbian. Ubuntu is not supported by OMV.

Those were my experiments for testing purposes only. In general, we don't deal with RT kernels. The problem is that you have to use exactly 4.14.y at the moment. Older versions might be completely broken for building - patches are adjusted to 4.14.y and not to 4.13.y - and they miss some important part ... well, even this one is still not completely finished nor (labeled) stable. But it is the best what exists for H3 boards. Simply try adding patches from https://www.kernel.org/pub/linux/kernel/projects/rt/4.14/ to userpatches/kernel/sunxi-next and recompile. User our unmodified build script. And good luck.