The same problem occurs with LibreELEC-Generic.x86_64-9.0.1.ova.
I can can make it work by adding a second network adapter but for some weird reason the first adapter is not detected by LibreELEC.
Running VMware® Workstation 15 Pro 15.0.2 build-10952284, no problems with other Windows and Linux vm's.
I try to run libreelec-generic.x86_64-9.1-nightly-x.ova on VMware workstation 15.0.2.
Default I can't get any connection, there's one bridged lan adapter installed.
When I add an second lan adapter in nat mode, this one works, when making an ssh to the nat ip, I see only 1 networkadapter. I checked both adapaters are connected in the VMware GUI.
I can remove the first bridged adapter, the second NAT nic keeps working. I can also change it to bridged.
For some reason only Network adapter 2 works for Libreelec ?
Anyone already tried to build a custom dtb ?
I did some attempts but no luck so far, I am pretty sure the dvb frontend is cxd28xx.
I mixed the original dtb with some parts of p231_2g.dts found in the topic start post.
No need open the box. I have installed Terminal emulator app put the microsd with libreelec into the box and from terminal emulator app start with command reboot update.
And your terminal is connected to a virtual usb com port ?
[edit]
Oh wait, I understand, you installed an terminal app on the GTC 
How do I boot my GTMedia GTC from sdcard ?
I see 4 solder pads in a square on the bottom of the pcb. It looks like a switch can be mounted there. It's labeled 6SW1.
Is this the switch which resides behind the jack plug on a lot of 905 boxes ?
I soldered a little microswitch on the back of the pcb on the place labeled 6SW1. It works, I can boot from SD now !
The Zeepin A95X S905X 1GB/8GB works fine. It looks very similar to the Nexbox A95X. I bought it for 21 euro's on AliExpress, they are now slightly more expensive.
I use the gxl_p212_1g.dtb device tree. It needs a custom remote.conf
I don't use Samba shares myself, but I'm pretty sure I have read here (numerous times) that the newer builds require a Samba password.
If you are not using Samba passwords then the obvious fix would seem to be to start doing so (or use a different method of file access by your media box)
Ok, but as you can see mounts can be made to a windows10 machine without the need of a password. As I interpret this, it's a limitation in Kodi, the way it does the mounting stuff. It has nothing to do with samba versions, because the mounts do work if you make them at Linux level.
It's also strange smb browsing doesn't work at all in the 8.2 LE. In the older version, I could simply browse my network and every samba share (both windows and unix like) would pop up, and I could add them to my list like that.
I can make mounts to my Linux server and Dreamboxes without any problem. Only Windows 10 does not work.
I also played with the maximum smb version setting, it doesn't make any difference.
ps. an account with password also fixes the problem, but I still can't browse for smb shares.
I use advanced sharing in Windows 10, I just added an account called kodi with password with read only access to my share permissions.
Since 8.2 smb mounts to my windows10 machine won't work anymore.
I also can't browse smb, it only gives ..
With the 8.0 version I didn't have any problems.
Funny part is, doing manual mounts, all works fine (password less account) .
As workarround I created a /storage/.config/autostart.sh file
