Posts by chewitt

The "direct update from LE9 is not supported" line is all about dissuading average users with low(er) skill levels because when add-ons go crashy and prevent the GUI from coming up those average users with zero CLI skills panic and generate a large amount of forum traffic. However if you understand your way around Kodi and the LE filesystem it's a fairly trivial update. The core OS updates from LE9 to anything newer with no issues since everything is packaged into KERNEL/SYSTEM. Add-ons are where all the problems occur; due to the Python2 > Python3 change that took place between LE9 and LE10 and then the multi-year version jump. However, after downloading the update .tar to /storage/.update all you need to do is stop Kodi and "rm -rf /storage/.kodi/addons/*" to ensure nothing to do with old add-ons remains except for settings in /storage/.kodi/userdata/addon_data, then let the update run, and reinstall add-ons from the respective repos once on LE12. Total time elapsed should be 5-10 mins at most.

I wouldn't expect any issues with a mix of RPi4/5 boards.

I've put the file on the sources.libreelec.tv server .. try again and it should be found now

I'm not 100% sure whether the newer display hardware in RPi4 boards supports 3D either. I do know 100% that the original (dated) RPi4 boot firmware in the LE 9.2.8 image will not boot newer iterations of RPi4 hardware, although that's fixable if you manually update the firmware files in the root folder of the SD card to current ones.

NB: I have no interest in the Amlogic 4.9 kernel and have no patches of any kind for it, so you're on your own with that quest. I'll give you the heads up that once you start changing Amlogic BSP kernel versions you will need to re-hack Kodi and pile of other dependencies to align with the new kernel. In short, any assumptions you are making on interchangability are most defiinitely wrong, and a world of version and dependency pain awaits you. Good luck, and please don't post here looking for guidance on that direction.

RPi3B+ on LE9.2.8 is the best (and final) RPi to support 3D things. RPi switched to the GBM display pipeline from LE10 onwards and the RPi4/5 have never supported 3D matters. It remains something that could technically be added and it's the RPi devs long list of rainy-day tasks, but I have low expectations it'll ever show. NB: I believe OSMC still support it with their devices, so that could be an option too. Best to check first by asking in their forum though.

I'm fine without a pile of stats being posted. Everyone has slightly different use-cases and test results are thus not universal truths to be followed. And in forums such discussions always end up with someone trying to prove something is/isn't better/worse/faster/slower than something else. I choose ignorance and less forum drama. If people want to run an RPi5 on an NVME drive .. go nuts. If people are happy running on an SD card .. go nuts. Go forth and watch movies.

Feel free to send a tested pull request to bump the versions. I place strong emphasis on the word 'tested' ..

LibreELEC (chewitt): 12.80.0 (RPi5.aarch64)
RPi5:~ # ls -l /
total 17
lrwxrwxrwx    1 root     root             8 May  9 07:40 bin -> /usr/bin
drwxr-xr-x   17 root     root          4240 May 16 15:26 dev
drwxrwxr-x   22 root     root          1004 May  9 07:40 etc
drwxr-xr-x    5 root     root         16384 Jan  1  1970 flash
lrwxrwxrwx    1 root     root             8 May  9 07:40 lib -> /usr/lib
lrwxrwxrwx    1 root     root            10 May  9 07:40 media -> /var/media
dr-xr-xr-x  218 root     root             0 May 15 21:58 proc
drwxr-xr-x   21 root     root           600 May 15 21:58 run
lrwxrwxrwx    1 root     root             9 May  9 07:40 sbin -> /usr/sbin
drwxr-xr-x   21 root     root          1024 May  6 21:24 storage
dr-xr-xr-x   12 root     root             0 May 15 21:58 sys
drwxrwxrwt    9 root     root           180 May 15 21:59 tmp
drwxrwxr-x   10 root     root           153 May  6 07:15 usr
drwxr-xr-x    9 root     root           220 May 15 21:58 var

The error is self-explanatory ^ the /opt directory does not exist in LibreELEC and you cannot add it, so you need to modify the script to use some location on the persistent /storage area.

RPi5:~ # cat /etc/resolv.conf 
# Generated by Connection Manager
nameserver 172.16.20.1
nameserver 8.8.8.8
nameserver 1.1.1.1

resolv.conf not resolve.conf ^

mount -o remount,rw /flash
nano /flash/config.txt

I have no issues with 1080p H264 and sync on an RPi5 (self-built nightlies) so I would make a random guess that you aren't using adjust-refresh and no mode whitelist is defined.

If there is no uEnv.ini file in the root of the SD card you are not using the AMLGX "box" image.

WireGuard.DNS = 10.2.0.1, 192.168.1.100

He configured the first as 10.2.0.1 and the second as a local PiHole device in the local network

Cron does not execute things in the default environment so you need to use the full path, e.g. /bin/bash /storage/.path/to/script.sh

Not possible. LE 9.2.8 uses the Amlogic 3.14 kernel (S905/S905X era) and this does not support S922X hardware.

The VPN provider probably does DNS round-robbin to distribute load. I wouldn't worry about trying to script/handle different IPs unless things stop working; then re-resolve the host, update the conf, then restart the WireGuard systemd service.

[provider_wireguard]
Type = WireGuard
Name = AirVPN
Host = 213.152.162.12
WireGuard.Address = 10.173.72.95/32
WireGuard.ListenPort = 1637
WireGuard.PrivateKey = REDACTED
WireGuard.PublicKey = REDACTED
WireGuard.PresharedKey = REDACTED
WireGuard.DNS = 10.128.0.1
WireGuard.AllowedIPs = 0.0.0.0/0
WireGuard.EndpointPort = 1637
WireGuard.PersistentKeepalive = 15

See if this ^ works. Host is the WireGuard server that you connect to, so you need to resolve nl3.vpn.airdns.org to an IP (not possible to use an FQDN with ConnMan) and WireGuard.Address is the IP allocated to you, and since you are not connecting to access an internal subnet I'm making an educated guess that this should be /32 not /24.

Quote from Free Man

Because, of course, if a tornado hits my house, the most important thing is to get Kodi back up and running ASAP!

Damn right