Posts by chewitt

Quote from Garzie

Can anyone point me to a how-to for installing the LibrEelec builds on these boxes - my box appears to be an old Edal T95Z plus (2g RAM 16g ROM) and runs ok with the "gxm_q200_2g" device tree file

Get the AMLGX "box" image from https://test.libreelec.tv/ .. write to SD card and then edit uEnv.ini to set the dtb name (do not rename the dtb to dtb.img). Insert the SD card and trigger recovery boot again so the LE bootscripts are loaded (else you have CE scripts which look for different files). If all is well it will boot. The "meson-gxm-q200.dtb" device-tree exists and should support most hardware.

This is probably best reported via the Kodi forus. It's not an LE specific issue.

FQDNs are not supported, you MUST use an IP address.

See https://forum.kodi.tv/showthread.php…5119#pid3085119 .. perhaps scroll back a little in the thread.

You will need to reflash the module from a Windows PC connected via USB cable (and some drivers, which need to be insalled). There are instructions for flashing core modules on the Raspberry Pi Foundation website (old links on the FiveNinjas GitHub site are dead now). The website instructions will not mention Slice, but they apply to any CM/CM3 device.

Add "textmode" to kernel boot params in cmdline.txt and attach a USB keyboard. LE will boot to a console instead of Kodi so you can see the output on-screen and save logs to a USB drive or experiment with connmanctl to connect to networks. Use 'iw' to change regulatory domain if that's important. Once you've either got it working or obtained logs so we can investigate what the issue is .. share info.

Jocke.Sve LE has never used wpa_supplicant.conf files and there are no plans to add support (we plan to drop wpa_supplicant and switch to IWD at some point in the near or mid-term future).

Quote from Garzie

Can we run Kodi 19 on the amlogic S912 boxes with any of the LE nightly build

Nightly images use Kodi Nexus (20) not Matrix (19). The images are not perfect but quite usable on S912 hardware as long as your media needs are not too exotic.

Quote from vhgroup

(whether they are pirated or not, who cares)

You might not care, but pirates are generally not welcome in this forum.

Connect an Ethernet cable for setup/investigation. NB: LE does not support/use wpa_supplicant.conf files.

Go look at the systemd .mount file samples in /storage/.config/system.d .. these are sequenced correctly during startup to mount things after the network comes up and before Kodi (and TVH add-ons) are started.

All I can say is .. it's not a software problem. It's about cables and physical connectivity.

If the box is running Kodi Helix (15.2) I suspect you have a Slice (CM1) device not Slice (CM3) as the CM3 board was launched some time after we forked LE from OE (the original SliceOS was based on OpenELEC) and it's around the time 5Ninjas ceased trading. The simple way to check is the RAM size. If it's 512MB it's CM1, and 1GB it's CM3.

Either way, the original SliceOS was installed via NOOBS, and if you have a working install you should be able to cross-grade from SliceOS to LE after placing the .tar file in /storage/.update, but I would stop Kodi first (systemctl stop kodi) and rename /storage/.kodi to /storage/.kodi-old to move existing data out of the way as it's a large version jump and it's worth spring cleaning at the same time.

See post #4

The concept of "pass-through" doesn't exist for video.

All the kernel + ffmpeg + kodi patches LE is using are either in the LE repo or the sources URL is clearly listed in package.mk files. In theory there is nothing to stop you replicating the LE experience elsewhere; although note that most Desktop distros are running Kodi via Xorg or Wayland which will create some limiations.

I'm not aware of any "download all the LE stuff for <distro>" tools, but our sources are all in our repo so feel free to write one

Quote from libreAU

Is there something I need to do to enable your build(s) to play dolby vision files ? Is there any support ?

You can write code for the Linux media framework and FFMpeg to support Dolby Vision!

In other words, right now there is no support.

it works here

[provider_wireguard]

Type = WireGuard

Name = WireGuard VPN Tunnel <= make this OpenWRT (or WireGuard or anything one-word)

Host = <OpenWRT ddns ip>

WireGuard.Address = <my Client internal IP>/32 <= make this /24

WireGuard.PrivateKey = <client generated Private KEY> <= use the client private key generated by OpenWRT

WireGuard.PublicKey = <OpenWRT Server Public KEY>

WireGuard.DNS = 8.8.8.8, 1.1.1.1

WireGuard.AllowedIPs = 0.0.0.0/0

WireGuard.EndpointPort = WG Server Listening port

WireGuard.PersistentKeepalive = 25

^ OpenWRT prob. generated a set of keys to use on the client end, as that's what's imported when you scan the QR code on a mobile device to import keys and config. So use those instead of generating your own.