mousavy_mh

Actually I run snapsot from 17 nov and it is working. I even see difference with different thermal compound in different boards.

It works. http://sprunge.us/GcLW At least with the latest build. We fiddled around that part lately and it could be broken ... will be fixed in next small update. ASAP.

Remember. This is open source project running by amateurs and not enterprise-grade service.  Go to GitHub and monitor progress. 
 
We always write major changes to release documentation. 
 

Didn't you notice this?
* packaged versions might be slightly older than in this table!

https://www.armbian.com/logbook/
Prime is in a better shape than Win.

8812au ... and also anything that has Ralink RT5572 or RT3572. Those are not AC but are at least dual band up to 2T2R with good Linux support. I am working on to setup proper testing environment. The current problem is the other side. My router is just 10cm away and I will need to set up another AP. 2.4 band performance is pretty irrelevant in an urban area but our apartment condo has a lot of steel inside walls and it actually works quite well. Except Xradio
 
I have 13 wireless adaptors in a dedicated USB3.0 hub and two more are on the way. The plan is to make some scripts and update the database compatibility/kernel properties. All this setup is early WIP.

I cut out this part of messages from PC2 topic since they are pretty much off topic.
 

And this part is also hard to explain. Some drivers are done badly and simply does not support AP mode. It's common. I am not sure if this is the case with your adapter, but at least its possible. There are many tips around the net, try different drivers or better use adaptors that work. Under specific kernel. If some adaptor works with Raspberry Pi or on PC, there is absolutely no warranty that will work here. Zero. 
 
And do try hostapd with non-realtek hostapd as well. 
 
Check this: 
 

I had same issue on almost same hardware. And I have already seen it on previous H5 build. Gave up and used Ralink2800 as a hostapd device. But really appreciate if there will be a tip/solution since rtlXXXC devices support concurrent mode - I can use one adapter for both AP and client.

This is not related to OPi PC2 and H5 in any way. And I wold try to get working a combination the existing in-kernel driver and non-Realkek hostapd first.

Stretch is possible, but kernel for this board is not quite ready. We are working round the clock to finish this in planned due in 1-2 months.
 
Current status: 
HDMI DRM driver, CEC, HDMI audio, I2S (requires overlays)
Missing features: DVFS, THS U-boot is most likely broken

If you ran the latest beta: armbian-config -> software -> install headers
https://github.com/armbian/documentation/blob/master/docs/images/armbian-config-6.png

When doing your own build, the build process will generate something like output/debs/linux-headers-next-sunxi64_5.33_arm64.deb.
Copy that file on the target board and install it using "dpkg -i output/debs/linux-headers-next-sunxi64_5.33_arm64.deb".
 

You mean it failed after update or it never worked on this board?
 

Not possible.