No impact, because either:
a) nVidia falls in-line behind mesa and Kodi GBM/V4L2 work transparently extends to cover their GPUs with little effort
b) nVidia continues to play games, and once we drop X11 support nVidia GPU support dies with it, requiring little effort
It's something we will track.
/storage/.config/asound.conf
The official line is we don't support virtual setups and the OVA exists to support ad-hoc functional testing and dev work in vmware only - any other use case and hypervisor is skiing off-piste and is done at your own peril. There's a large jump in kernel version between LE 9.2 (v5.1) and LE 10 (v5.10) so my gueess is there might be some kernel defconfig changes needed.
Can you repeat a clean restore on 9.95.1 then run "journalctl | paste" about 30 seconds after boot and share the URL generated. I'm wondering whether the box has an RTC chip or gets time from NTP? .. and whether time has been correctly set at the point the restore is performed.
echo "nvidia" > /storage/modprobe.d/blacklist.conf
cp /etc/X11/xorg-radeon.conf /storage/.config/xorg.conf
cp /usr/lib/udev/rules.d/97-xorg.rules /storage/.config/udev.rules.d/97-xorg.rules^ You can edit the 97-xorg.rules files so there is only a line for the "radeon" driver. I'm not sure this will achieve anything though as if I read the scripts correctly it''s simply not finding the radeon card hardware, which maybe points towards slow loading drivers and some kind of timing issue.
Have you reported the issue to the TVH developer(s)? .. they're going to be the people who fix it, not LE devs.
What happens if you boot LE from a USB stick instead of using it under a hypervisor?
Somebody know how fix bluetooth?
put the BT firmware file in the same folder..
mkdir -p /storage/.config/firmware/brcm^ create and download correctly named files in that folder and reboot - no need to hack the SYSTEM file
I'm running my own image with some minor tweaks, but only cosmetic things. Do you have any funny characters in passwords?
I'd guess the drives are EXT4 formatted? EXT2/3/4 reserve 5% space for root to ensure (when the disk is a system drive) that core processes have available space to operate. So the drives showing 0% available have < 5% free. You can use tune2fs to reduce the percentage that's reserved. This can have a negative impact on fragmentation, but with media drives that contain large (should be contiguous) files this is probably a lesser concern than for system drives. You can run e.g. "tune2fs -m 1 /dev/sde1" to set the percentage at 1%.
Your description implies that build completed but the devicee does not boot. It would be informative to know at what point in the boot sequence the device fails to boot, hence the request for UART output. However it looks like you're one of those users who is fixated on a specific thing and knows better than us how debug a boot problem. So 
and good luck. NB: LE 9.2 is a dead codebase so I would restart with LE10 anyway.
SMB configs are simple but there are many variables to guess from. So unless you describe what you're trying to connect to in detail, we can't help.
Note that RPi4 using LE 9.2.6 does not support 4K@50/60 modes (anything above 4K@30) without additional options set in config.txt, and there is currently no equivalent support in the LE10b1 release (4K60 is still being worked on).
<?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
<!-- enable debug logging -->
<loglevel hide="false">1</loglevel>
<videodatabase>
<type>mysql</type>
<host>192.168.1.100</host>
<port>3306</port>
<user>username</user>
<pass>password</pass>
</videodatabase>
<musicdatabase>
<type>mysql</type>
<host>192.168.1.100</host>
<port>3306</port>
<user>username</user>
<pass>password</pass>
</musicdatabase>
<videolibrary>
<importwatchedstate>true</importwatchedstate>
<importresumepoint>true</importresumepoint>
</videolibrary>
</advancedsettings>^ FYI, this is mine, with minor edits to change credentials
There is no issue with using the </advancedsettings> tag (works fine here with a range of devices I test with). I'd guess there is an XML formatting problem somewhere else in the file.
Yeah, but it's the same answer.
Very sad to hear.
The GBM/V4L2 pipeline has probably been actively used on about 10% of the overall range of x86_64 hardware that users probably have. Some of that percentage will be low-risk, but we're expecting a fair number of quirks to surface. So you might be in a rush to use an "official" image instead an otherwise working fine "community" image, but LE10 already impacts 85% of our userbase (RPi) so Generic is in the queue and will have its day (along with the likely end of nVidia support) but some more elapsed time is a good thing. We're not in a rush.
