Posts by chewitt
-
-
The root of the SMB share is the /storage folder in the OS. So from there, visit to Configfiles > hosts.conf - but note that you must use a text editor that supports Unix line endings to edit the file, i.e. Notepad++ as most versions of the default Notepad.exe app don't and Windows line endings cause problems.
-
https://www.silicondust.com/product/hdhomerun-connect-duo/ and https://www.silicondust.com/product/hdhomerun-connect-quatro/ both support DVB-T/T2 ..the Hauppage tuners are generally well supported upstream though (they invested in upstreaming drivers).
-
Official:Forum rules/Banned add-ons - Official Kodi Wiki
You will receive no support for your install in this forum. Good luck.
-
Nothing LE related I think. Best to report via the Skin add-on support thread in the Kodi forums so the authors investigate.
-
How are you running moonlight? - we deprecated our add-on so presumably something in a Docker container?
-
One down, more to go. The main one is Kodi moving to RC releases. There are still some important changes pending upstream. In the past we'd be trying to release-match Kodi with beta's and such but these days (older, wiser, etc.) we're not in a rush.
-
I'm not aware of anything within the Kodi ecosystem; there is a very deliberate focus on playing media from YouTube, not downloading it.
-
The OS contains cron already so all you need to do is "crontab -e" to start editing in nano, then paste the cron content, and ctrl+o (save) and ctrl +x (exit) .. and all should be good. NB: In LE /profile doesn't exist so you need to be using somewhere on /storage
-
It's best to ask questions about specific add-ons in their support thread in the Kodi forums - it's unlikely to be an LE specific issue.
-
If you have one on LE11 and one on LE12 it will "work" but they're accessing different versions of the DB so you loose watched/unwatched status and you'll need to scrape new content into both DB's. The LE12 nightlies are stable to use. There will be a kernel bump to Linux 6.6 at some point soon; that's one of our critera before moving to LE12 beta > release.
-
Have a look at HDHomeRun boxes for a 'Network' tuner device. Then use something else as the client/player device. In the long term you can update the client as needed for latest features while the tuner remains the same. It avoids lots of kernel/driver matching complexity which is often a challenge due to the state of DVB drivers in the kernel.
-
Keep in mind that libreelec use U-Boot mainline (not the legacy one with proprietary blobs that maybe librecompurer folks suggests)
LibreComputer are upstream champions so I would expect their boards to work correctly. Their lead (Da Xue) is normally reachable in Slack in East Coast US hours to check things.
-
I'd guess they broke support for detecting LibreELEC as the add-on is trying to "apt-get" packages in the background, i.e. thinks it's running on a Debian based distro like Ubuntu, and that doesn't work on LE. You need to post the issue on their GitHub issue tracker.
-
Seems that it has ARM A53 CPU so I think it is a SOC S905 and that I could use the LibreELEC-AMLGX.arm-11.0.3-box image to root it.
If you scroll down the page far enough it shows "CPU: Hisilicon Quad-core" which means it's not Amlogic and we currently have zero support for any HiSilicon chips (all their chips require horrid vendor kernels, nothing upstream).
-
LE has no current support for 32-bit (ARMv7) boards of any kind, and that's unlikely to change.
-
New wiki article to cover this topic: https://wiki.libreelec.tv/configuration/ssl-tls-certificates
-
All you need to do is put your own certs in /storage/.config/cacert.pem and reboot. On restart ssl-config.service appends that content to the default cacert.pem file when creating /run/libreelec/cacert.pem which is the symlink target for /etc/ssl/cacert.pem.
