Posts by chewitt

Yes, the #1 use of entware on *ELEC distros is installing piracy tools. We work closely with Team Kodi and take a similarly firm stance on that kind of thing. It's our distro and our choice. If you disagree .. feel free to fork our codebase and run a distro. CE isn't the first fork of our codebase and won't be the last. Forks are an essential part of our ecosystem. We like forks

If you want entware on LE you need to self-build an image with /opt added. Have a look at packages/sysutils/systemd/tmpfiles.d/z_01_openelec.conf for some prior art on adding directories.

Build instructions https://wiki.libreelec.tv/development/build-basics

Quote from ww75

As Wireguard seems to be the way to go in the future, it would be very nice to see it implemented directly into LibreElec

You mean like this? (4.5 years ago) https://github.com/LibreELEC/LibreELEC.tv/pull/4139

Read: https://wiki.libreelec.tv/configuration/wireguard

If you run "reboot" via SSH (at OS level) the system will be forcibly restarted if needed. If you send a reboot command via Kodi, it must be handled and passed to the OS. If Kod is in some kind of hung state that probably doesn't happen.

Honestly, nobody can remember that far back. Plan B is creating local .nfo files so you don't need to query data from the internet.

ARMv8 Amlogic chips support hardware deinterlacing - as long as the OS implements support for the hardware. In your case the tablet device is running Android so you're in the wrong forum - we support our own OS, not Android.

Log-in to the device over SSH.

No plans to revert official images to wpa_supplicant and the overall number of issues and impacted users is low. LE13 should be out sooner than later, and RPi devices should be using Linux 6.12 which we expect to be the next LTS release and thus the next base for RPi kernels too. It's not hard to self-build something that still uses wpa though; we intentionally left the package in the buildsystem so it was possible.

I have a hunch that Confluence gets updated from the Kodi repo, but the version that's updated-to is no longer compatible with the Kodi version you are using. That's probably a mistake/oversight on the Kodi side (the incompatible add-on shouldn't be added to that Kodi version's repo) but developers are rarely testing old versions so things can happen.

I would update to LE 9.2.6 - if things like optimised software decode are important, or newer. The position in the menu will change, but better to have a less buggy and working Kodi than no Kodi. You can probably hack the skin to change the position if it's a really big deal, although then you need to redo the change with each Confluence bump. These days there probably aren't many.

The NTFS-3G add-on should be in the LE repo (at least the LE13 repo, it might not be merged for LE12 yet) under Services. There's also an NTFS-PROGS add-on in the Tools section which has some of the utility binaries.

Drives that disconnect and reconnect on their own normally trace back to bad power supplies and/or bad USB cables.

IWD is currently missing CMD_EXTERNAL_AUTH support.

RFC patches were posted a few months ago: https://lore.kernel.org/iwd/2024082317…[email protected]/ but looks like some additional joining of dots is needed to get things working on RPi boards.

popcornmix what's the latest on that front? - I can see pelwell and @6by9 commenting so it's presumably on their radar.

LE automounts local devices via udev and remote devices through systemd .mount units: /etc/fstab is nothing more than a stub file to stop some binaries complaining that it doesn't exist. It is not writeable since it's inside the read-only squashfs SYSTEM file.

If you haven't unmounted the NTFS filesystem cleanly from the current device it will probably be in a "dirty" state and that needs to be cleared on Windows using chkdsk.exe before you can attempting mounting under Linux again.

Have a look at the NTFS-3G add-on in the "Services" section of the LE repo. This (added in the last week) add-on overrides the in-kernel driver and uses the older NTFS-3G userspace driver approach used in older LE releases.

echo "echo 1 > /sys/power/pm_async" > /storage/.config/autostart.sh

Run that command ^ and reboot and it should be applied to the OS on each boot. There's probably a modprobe method which will be lessy hacky, but if it works..

Quote from CurtyPi

With RealDebrid Premium.

And at that point we lost all interest in your problem. Pirates aren't welcome in this forum.

Are there any firmware updates pending? .. Check in the settings add-on.

Da Flex please explain how our wiki article on adding content via the local LE samba server going to help diagnose an issue with the Kodi SMB client?

The upstream (Kodi) change that caused the tearing was reverted on all LE images some time ago; leading to an eventual reverting upstream too.

If there's an issue it seems to be localised to your environment. I'm running a (self-built) nightly image on an RPi5 without any network issues and lots of other people run nightlies too; enough to flag-up any general networking issues. NB: The kernel changes in question will be irrelevant unless your home network is IPv6 based?

I'd start with a clean LE13 nightly image on a spare SD card. Any different?

hdmi_enable_4kp60=1

I'd start by removing that ^ from config.txt as the AVR only supports 1080p and that's forcing 4K modes. Any difference?