I'm not 100% sure, but ISTR there are two problems:
a) Kodi has dependencies on samba 3.x and they need to bump to 4.x before we can use it
b) Samba changed its compile process between 3.x and 4.x and it became a challenge to cross-compile
I believe someone gave up on B as there was no point until A happened, but that was some time ago. I'm not sure anything changed though.
You might be able to connect if you unhide the network temporarily, connect to create/cache the connman service file, then rehide the network?
connmanctl
agent on
scan wifi
services
connect <string for your wifi>
NB: The security benefits of hidden WiFi are zero because periodic re-authentications made by connected devices in normal use leak the SSID to anyone with a network sniffer/cracking app and WEP security will inconvenience the same cracking app for no more than 300 seconds. Hacking your network is kindergarten stuff for any security researcher or script kiddie with a copy of Kali Linux. WPA2 is considered secure; so use it.
LibreELEC.tv/options at master · chewitt/LibreELEC.tv · GitHub
It can be set there, but the level of additional CPU optimisation you get during cross-compilation will be minimal and you probably break binary compatibility with Kodi add-ons in our repo that have not been compiled with the same configuration.
Correct, "git checkout 7.90.008" sets the repo to that specific commit.
Theory: I think you disabled "parent folder items" in Kodi GUI navigation and somehow you're being dropped into the "Services" folder in our repo (which doesn't have the PVR stuff in it) when you need to go back up a level to the root of our repo and then and into the PVR clients folder where pvr.hts can be found.
The way our build system works it's quite trivial to change one tiny part of the OS, but you cannot apply an incremental patch to existing KERNEL or SYSTEM files so you must replace both.
Changes we made in 008 to update the samba (server) configuration have nothing to do with SMB (client) usage by Kodi. The "unix_err: 6" errors are seen on all variants of Linux running most versions of Kodi in recent years (Google and you'll find a ton of references in Kodi forums) so I honestly have no idea what the issue is but if I'm guessing; it's a combination of the getting-dated SMB implementation in Kodi and the utter protocol stupidity that is Windows networking. Turn everything off, turn things back on slowly starting with whatever box is trying to be the NAS.
echo "blacklist nvidia" > /storage/.config/modprobe.d/blacklist.conf do that and reboot, and it should stop the nvidia driver loading so Xorg only has to contend with one GPU.
and please use "cat /storage/.kodi/temp/kodi.log | pate" so we don't have to suffer reading logs copy/pasted into forum posts.
Please post the whole debug log from clean boot and including an attempt to install the add-on
LE is not really designed to work with multiple different GPU types active and Kodi is not brilliant with multiple monitors, so you probably need to disable the onboard nVidia VGA in the BIOS if you want the AMD HDMI output to work reliably.
Enable CEC and use the TV remote?
Have a play with current alpha builds, i've seen multiple comments about BT stability being better (although not in a pulse audio context).
20:19:51 T:140529803257984 NOTICE: ADDONS: Using repository 
20:19:51 T:140529803257984 NOTICE: ADDONS: Using repository
20:19:51 T:140529803257984 NOTICE: ADDONS: Using repository
20:19:51 T:140529803257984 NOTICE: ADDONS: Using repository
<addon id="service.multimedia.vdr-addon" name="VDR PVR Backend" version="7.0.102" provider-name="libreelec.tv"><requires><import addon="os.libreelec.tv" version="7.0"/><import addon="xbmc.python" version="2.1.0"/><import addon="pvr.vdr.vnsi" version="0.0.0"/><import addon="script.config.vdr" version="0.0.0"/></requires><extension point="xbmc.service" library="default.py"><provides/></extension><extension point="xbmc.addon.metadata"><summary>VDR: a TV streaming server for Linux</summary><description>VDR (2.2.0) is a TV streaming server for Linux supporting DVB-S/S2, DVB-C, DVB-T/T2, IPTV and SAT>IP</description><disclaimer></disclaimer><platform>all</platform></extension></addon>This is information from addons.xml on our webserver, showing service.multimedia.vdr-addon exists. Perhaps enable debug logging and see if there are errors being logged. Make sure you don't have old OE config causing problems.
Have u installed OpenVPN as well? try installing this zip for openvpn
Err.. you realise that OpenVPN is fully embedded in the OS don't you, so that's not required.
Maybe i can install libreelec windows version and test it with keyboard.
last time I looked (and i'm pretty confident on this) we don't run on Windows 
I don't have any 802.11ac capable kit so it's not a requirement for me.