Posts by chewitt

It's hard to guess without seeing what the error is. Plan B .. clean install the second machine and get it on the network, enable ssh on both, and then use scp to recursively copy content between the boxes.

echo "options cfg80211 ieee80211_regdom=DE” > /storage/.config/modprobe.d/cfg80211.conf

^ swap "DE" for UK, FR, RU, etc. as required, and see if that makes a difference.

LE does not use nouveau. If you can boot a normal Linux distro and find the pci bus device IDs we can cross-check against nvidia drivers.

If you share the logs we asked for and we can see what's going on. If you don't share the logs and all we can do is guess.

I can see two issues:

a) The repository.unofficial.addon.pro reference is old cruft from an OpenELEC installation. The domain expired or is no longer available; and the add-ons there wouldn't be compatible with LE releases anyway (maybe v7.0 but not v9.2). This can/should be uninstalled.

b) The version of LE appears to be v9.1.x (pre-release) not v9.2 (release). I'd be inclined to start over with a new install (update to v9.2 and then rename /storage/.kodi to /storage/.kodi-old and reboot) and then only copy back things from the older install which are really essential. As a minimum you need to update and then the correct add-ons should be used.

There is no package manager in LE and we refuse to add more garbage realtek vendor binary drivers to the core distro as they break with every kernel bump and require onerous maintenance. There are several examples of people sumbitting (and us refusing) realtek drivers in our github repo - have a look at closed pull requests. Similar packages with sources obtained from somewhere might work. Or might not .. that's the problem with out-of-tree drivers. If you abandon the idea .. have a look for devices with a railink chip as these a generally supported in-kernel. Or get a wireless bridge that connects via Ethernet. They're often cheaper and give better range/reception than most USB cards.

I forget whether TVH supports TLS by default, but if not you can probably reverse proxy the connection from nginx which easly supports letsencyrpt and then all client/server comms runs through a encrypted tunnel.

Port knocking sounds wonderful until you try and find client apps that support it .. be prepared for a long wait.

Best place to ask will be the Plex forums, as Plex maintains the add-on in the Kodi repo.

Kodi uses Samba smbclient to mount SMB shares and this will not follow Windows aliases and maybe NTFS junction things (never heard of them). The only other thing you can try is mounting shares via systemd (see /storage/.config/system.d/) and then having Kodi access the now-local drive. I have no idea if the kernel SMB capabilities support following junction links or not .. you have to experiment.

LE packages Kodi to use ffmpeg libraries so there is no ffmpeg binary in the default OS image. We also package a normal binary version of ffmpeg in the ffmpeg-tools add-on. This is compiled with more options enabled to make it more suitable for use with other apps.

Use a decent router with a proper firewall (maybe even threat protection built-in) to protect the TVH server behind it, and port-map from non-standard ports on the router WAN IP (obscurity not security, but avoids some probing) to the standard ports on the TVH server. I wouldn't bother with VPN as TVH provides access to public broadcast video streams not personal data.

KVIM is a legacy image for VIM1 only. The add-on errors are likely caused by the Python2 to Python3 change in Kodi v19 - you'll probably need to remove all add-ons and reinstall them with K19 compatible versions. Once an add-on is reinstalled you can probably copy the config back to preserve settings. The fun thing is .. not all add-ons will be available in Python3 versions yet.

Initial WireGuard support has been merged but I regard it as an experimental feature. It's merged to LE master branch, also to LE 9.2 branch as more people are likely to use it there and thus more issues will be discovered. I will need to bump connman and the wireguard module/tools packages before we release LE 9.2.1 (no schedule).

There is no wg-quick or wg0.conf due to the embedded packaging of LE - read Creating WireGuard Keys [LibreELEC.wiki] to understand how it's implemented.

Most nVidia GPUs suffer from under-development on closed-source VDPAU so even if the card is vastly superior in mathematical compute capabilities it may not necessarily be any better than the Intel GPU which is still capable of hardware accelerating the same range of media. Kodi is not a complex OpenGL app, so it doesn't really need or benefit from high-end GPUs.

macOS stuff is the main hold-up as I understand it ..

Three suggestions that might work:

a) Enable "legacy boot" in BIOS settings which should disable EFI boot.

b) Boot from any other Linux distro USB and run "dd if=/path/to/LibreELEC-Generic.x86_64-9.0.2.img of=/dev/sda bs=1M" (checking the disk you want to write to is /dev/sda .. and noting the image is uncompressed to .img not .img.gz). This writes the USB image to the HDD, and in theory this should boot, time out the same way, but this time it self-installs to the HDD not the USB so you end up with a working install.

c) Remove the HDD and put it in a USB caddy to write the image to the HDD .. different way to the same result as B.

A is easier than B which is marginally more complex but requires no extra hardware like C

RPi4 haardware is capable of HDR but LE (and all other RPi distros) have no "software" support for HDR at the current time. It's still being worked on and might part of the future LE10 (Kodi v19) release if things keep going at the current rate of progress. No promises though.

It's sounds like the device is EFI booting and ends up following the "run" configuration (not sure how or why.. that's the only explanation). I've observed that EFI support tends to get worse the older machines are .. maybe that's the reason.

Anyway .. what happens when you type "installer" instead of leaving it alone?