Igor

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.

Nothing is weird. If you have wlan used by ifup ( /etc/network/interfaces) than network manager can't use them and vice versa. Remove /etc/network/interfaces, reboot and nmtui-conenect will work.

It seems that latest nightly build (4.14.18-sunxi/4.14.18-sunxi64) also works just fine. I am currently heavily stressing out: - Cubietruck - Orange Prime - Orange 2E Uptime: 15 hours 56 minutes 50 seconds If they are still up by the end of the day, I'll push kernel to the repository.

Nevertheless, support preparation can still start. It is a great way to get familiar with the build engine. The first step would be to add: [[ $EXPERT=yes ]] && options+=("bionic" "Ubuntu Bionic 18.04 LTS") after this line and everything else. Then we just wait that deboostrap is fixed upstream or we use some dirty hack in between.

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-connect-to-wireless

There are some problems with the latest update and we are currently investigating them. Read this ... and try the same test with the latest nightly kernel.

One good testing point is latest nightly builds to check if this issue is already fixed. armbian-config -> nightly + reboot

We (armbian developer) don't have the capacity nor wish to provide one to one teaching. Technical support is the best what is possible to get and exists in a very limited form ... the day has 24h and you are not the only person/task which wants something from us. I hope you understand this.

One more trouble. Our hostapd autdetection tool needs network connection. Since this is without this wont work. Manual then. Wrote on mobile