Posts by chewitt

There is/was a Kodi Backup add-on in the Kodi repo. I've never used it, but it might be worth looking into. It probably backs-up only to a "local" filesystem path, so to save off-box you'll need to configure a persistent SMB mount (there are instructions in the wiki) so there's a local filesystem path under /var/media/ to the remote NAS share.

The backup function in the LE settings add-on also captures /storage/.kodi, /storage/.cache, /storage/.config to a tarball which is saved to /storage/backups. Unless you are locally storing media on the SD card which needs to be preserved those are probably the only folders which need to be backed-up. It doesn't handle movement of the file off-box though.

The BT device list shows device-type icons so game controllers normally stand out from the noise of phones/laptops/etc. and there's probably only a single game controller in the list.

It's arguably a workaround/hack for the underlying issue of most ARM SoC hardware lacking the capability to tonemap (or if the hardware can do it, the kernel drivers don't exist) .. but you can submit a feature request to Kodi devs via the forums (or find the thread that's probably already there). It's not something that LE can solve; the issue is upstream from us.

video=HDMI-A-1:1920x1080M@60

If the box is connected to the HDMI-A-1 connector append this ^ to boot params in syslinux.cfg and see if forcing the initial DRM output to 1080@60 helps. Adjust as needed for whichever connector is connected. You want to run the GUI at 1080p anyway (see: https://wiki.libreelec.tv/configuration/4k-hdr).

The moral of the story is: if you really need AV1 support, get something that really supports AV1.

Start with tracking down BIOS and LSPCON firmware updates for the board and installing them (most will require Windows to run them from). If that doesn't fix anything I'm out of ideas as modern consumer Intel hardware is a mystery to me. It might need some kernel driver quirk applying; there are many to choose from in kernel drivers but I have no clue how you divine things.

I've replied in your other thread. Don't cross post the same thing please.

LE is an "embedded" style distro so it's not possible to change the Kodi version in an image as kodi.bin lives inside the read-only SYSTEM file which is uncompressed into a virtual filesystem (in RAM) on boot. Even if you could replace it, the file you're looking to download and use is a) an old version of Kodi, b) compiled for Debian so almost certainly wouldn't run on LE anyway.

https://wiki.libreelec.tv/development/build-basics (and adjacent wiki pages) contains instructions on how to self-build your own LE image. Start with building a default image. Then add the diff patch with Kodi changes to packages/mediacentre/kodi/patches and then rebuild the image; it will detect the patch and rebuild only the Kodi package. You can also add udev rules files to packages/mediacentre/kodi/udev.d and they will be included in the SYSTEM file or you can add them manually to /storage/.config/udev.rules.d sometime later.

NB: The "how to build an LE image" instructions that leecher1337 provides in the last post to that thread are not correct in a couple of places. I'd guess written by ChatGPT and not from actual experience.

Quote from imhotep

The Nightly works perfectly!

I disagree with that

but at least the audio and BT bugs are resolved, and the enthusiasm is appreciated..

Done

Yup, ConnMan is lightweight and perfect for our 'embedded' distro needs. If you're building a minimalist distro you don't look to include all the full-fat binaries of a general purpose OS. As long as it works for 99.99999% of users (and it does) we're good. You're the only person I can recall ever reporting this issue; and that means it's probably something environmental, i.e. something specific to do with your network or equipment (the router).

NB: The DHCP lease time is defined by config/policy on the DHCP server (router) not the client device that makes DHCP requests. So even if we did have a full-fat DHCP client tool it will work the same way. ConnMan did allow you to change lifetime values; but this is a dynamic protocol so when you send a renewal request and the server responds with a valid lease value, the values are overwritten.

Quote from sittich

This could potentially mean an additional 300,000 users

Nah, we know our userbase. At least 99.9999% of it has no clue about custom TLS certs. In a good year we might get 30 more.

Quote from Donald

I'm running 12.0.2 on an RPI4B

Please install the latest LE13 nightly on a spare SD card and see if the same issue still exists there. If yes, I'd like to see a PCAP of the DHCP request.

Quote from taurus

How do I get webgrab++ for LibreELEC?

Install Docker. Install the LinuxServer Docker add-on repo. It should be in there. If not, you can just pull their container direct from Docker Hub: https://hub.docker.com/r/linuxserver/webgrabplus

In the past there was an dedicated add-on in the LE repo, but people come/go from the project over time and it went unmaintained, and was eventually marked broken and removed from our repo back in 2019.

RAM isn’t the issue. VC1 files will be software decided so it’s about CPU. Here the RPi5 wins, but I’m not sure what the limits or expectations are for RPi4 with that codec.

popcornmix any opinions?

Nah. If renaming a file to “cacert.pem” is too complicated for you, you shouldn’t be messing with certificates in the first place.

The “ip a” command won’t survive a reboot but it’s trivial to put into an autostart.sh script or systemd service that’s executed on each boot.

Have you tested whether it’s something simple like the router not matching the MAC due to uppercase or lowercase letters. Some routers are crap like that. What’s logged on the router?

Quote from Donald

Problem is,when DHCP is selected, it always defaults to 192.168.1.126

The output of ip a that you shared disagrees with that statement as it clearly shows eth0 is assigned 192.168.1.5/24 as configured in the router. What makes you think it has the address 192.168.1.126 ?

The lifetime values can be manually changed with:

ip a change <ip> dev eth0 valid_lft <value> preferred_lft <value>