Posts by chewitt

[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.

LE 9.2.8 is the most recent image https://releases.libreelec.tv/LibreELEC-Slice3.arm-9.2.8.img.gz .. there are no LE10 images for RPi3 based hardware at the current time and there are no plans for further Slice images (not enough users to warrant the effort) but some work will be done to ensure the RPi2 image has the needed device-tree bits for it to be convertable for Slice3. NB: Slice3 has the same capablities as an RPi3 so there is no 4K support at all.

Just use a current LE11 nightly. The rate of change on Kodi is quite slow and the images are stable.

Go read post #2 again.

popcornmix .. something missing for RTC in the upstream kernel?

https://wiki.libreelec.tv/configuration/edid <= follow the "getedid" instructions; LE10 uses a completely diffferent graphics stack to LE9.2

Share the system log (dmesg or journal) after startup.

As the title of this thread clearly states your intention to download media using torrent suits, the thread is locked and will be deleted. Pirates are not welcome in this forum.

Quote from tomera69

is there a way for me to make it work on 9.2.6?

It can be done by backporting the newer kernel (with drivers that support the newer GPU) onto the 9.2 codebase. There are deliberately no guides and HOWTO instructions on that kind of thing. If nightlies work, you have a solution.

It's hard to describe my thoughts. The add-on name sounds like pirate shitware; but choosing dubious sounding names isn't against forum roles. Using a ton of code obfuscation isn't open-source minded, but again we don't have any explicit rules that say this is bad and against forum rules. The "I promise my code doesn't do bad stuff" is probably well intentioned but also seems to send the wrong vibe. TL/DR; it's all probably "legitimate" but my instincts are telling me this is shady and binning the thread will avoid drama.

If you poke around in Escalade's GitHub repo you'll find some prior art for adding an NFS server. It's not something we've ever felt the need for in core images as Samba works well enough and most folks will just get confused. FWIW, I've always used SMB and never had any issues (other than occasional self-inflicted mistakes). It might not be "fastest" but it's always been "fast enought" .. over Ethernet of course.

Random guess .. increase the settings level to advanced or expert, it might be hidden in basic.

No logs = No problem

I have no clue about remotes, sorry..

Quote from mgear

Are the Matrix's addons compatible with Nexus or addon writers will have to redo them yet again?

Matrix/Nexus are both Python3 so add-on differences are minor and unlikely to require much effort from authors.

https://wiki.libreelec.tv/support/log-files

Enable "Adjust refresh" and configure the whitelist for 1080@60/59.94/50/24/23.976 and 4K@60/59.94/50/30/29.97/25/24/23.976 and set the Kodi desktop to 1080p@60. Read https://wiki.libreelec.tv/configuration/4k-hdr

"Team Kodi" is more accurately described as "small group of developers doing their own thing with occasionally overlapping interests" and as is common with non-commercial FOSS projects there is not much product management and no schedule. One of the few things its developers have ever consistently agreed upon is the need to reduce the complexity and improve maintainability of the codebase. That's the prime driver and motivation for the V4L2 long-term technical direction. Linux is inherently a fragmented ecosystem so we need to follow standards and be an advocate and agent-of-change for the establishment of those standards.