Posts by chewitt

Quote from QBJack

Hmm, is there maybe a typo in the wiki as I only see two "move-after" and not one "move-before" commands in the example from the above mentioned wiki page:

Stop blindly copying things from the wiki. It shows general hints not verbatim instructions. Your existing service file results in a connection. You can add move-after or move-before commands to adjust the routing config. You can also run the move-after/before commands from the SSH console to experiment in-situ and see the impact on the routes on your box. Go experiment, figure out what combination you need, then add the same sequence to the file. If you don't need static routes, don't add static routes.

The error message is quite clear, no?

It should be under /storage/.kodi/addons/service.tvheadend43/dvb-scan

ConnMan adds a route to the WireGuard server so you do not need to. All you need is the move-after/move-before connmanctl comands to adjust the interface/service order so WireGuard is not the default route that everything is tunnelled down (and the interface you want to be default, is the default. Run the commands manually to experiment and get things working, then set the same sequence in the .service file.

NB: I also add some static routes in my .service file to e.g. a Tvheadend server that I want to access from the local network and not via the WireGuard tunnel, as WireGuard would add 2,000km to an already 4,500km distant Tvheadend instance.

Quote from handy7000

Is there any way I can add a kernel module or something similar to a newer version of Libreelec that will help me get back VC1 decoding? If not is there anything else I can do beyond re-encoding my VC1 titles or buying a newer device? Neither of these options are too appealing to me?

The upstream Linux kernel used in LE10+ images does not support VC1, the driver has simply never been written. It does exist in the older vendor kernel used in LE 9.2 and older images, but as you found, these days these have issues with TLS certificates (can be solved with a custom image) and general add-on compatibility. There's about 0.01% code in-common between the upstream and vendor kernels and Kodi removed support for amcodec (and all the other proprietary codec methods) a long time ago now so the options are rather limited. AMLGX is self-admittedly a bit of a compromise and not as feature complete as older images. There has not been much development on the codecs for a few years and they are what they are. I would recommend re-encoding to H264 as the decoder for this is in quite good shape and more family-friendly. You can also re-encode to HEVC, but this driver was never fully completed and it has glitches, e.g. seeking is not brilliant. Anything more needs new hardware.

I merged the PR to master. It will hopefully end up in LE 12.0.2 as well.

See https://github.com/LibreELEC/LibreELEC.tv/pull/9587

You can replicate this locally by creating /storage/.config/udev.rules.d/98-eventlircd.rules with the same content as the PR.

I'm interested in testing/feedback a) to get this merged for LE13, b) potentially to backport for LE12.2.

The patch was merged in Kodi master branch (Piers) but hasn't been backported, so it won't be in the Kodi 21.2 release which I'm expecting to be tagged tonight with an LE 12.2 release to follow-on sometime in the next week.

LE13 nightlies are here: https://test.libreelec.tv/13.0/ (scroll down for latest files). I won't ever promise a nightly is stable, but at this point it's an accurate term. I've personally been running them for a long time.

Quote from QBJack

Could you please help here with specific commands?

https://wiki.libreelec.tv/configuration/wireguard#known-issues

Pirates aren't welcome in this forum.

It's a long-running issue that impacts a small number of users. It is not RPi hardware specific. Things that may help:

• Disabling fast-transition (FT) in access-point radio properties
• Not using WPA3
• Moving the device closer to the access-point to improve signal strength

It is probably an issue with iwd (as reverting to wpa_supplicant works around it) but it remains unresolved largely because nobody who can replicate the issue has code-level fault finding skills, and nobody among project staff or regular technical contributors with such skills can replicate the problem.

rtl8723bs: Invalid-key while connecting to wifi on LE12 · Issue #8731 · LibreELEC/LibreELEC.tv

This is a continuation of issue #7166 but for LE12. When running LibreELEC-H6.aarch64-12.0-nightly-20240312-d108ae1-pine-h64-model-b.img: I get invalid-key…

github.com

This is resolved now.

Quote from drjackel

will there be a Kodi 21.2 built with the newer kernels and a Inter ARC bug fixes ?

No, LE12 uses Liinux 6.6 for most hardware. There are LE13 nightlies with newer kernels and newer Kodi too; and while I won't ever promise a pre-release version to ne 'stable' it's an accurate description right now.

In the "PC" world vendors expect users to use a monitor and control the screen with a mouse/keyboard, so nobody adds the CEC chip as it's extra cost. In the "ARM" (SoC) world everyone expects the box/board to be connected to a TV so 95% of devices include CEC functionality. In short ..

Quote from RenEH

Any chance we can get this feature implemented/merged?

If it gets merged into upstream Kodi we will have the feature. That won't happen though, because it's a hack, albeit a clever one.

Yup, so take the 4-8GB backup tar file, clean install the new device, restore the 4-8GB backup from the tar file. You'll be done 12-18 hours faster than block cloning a 128GB SD card. Users constantly obsess about cloning, but you don't need an identical card, you only need one with the same data on it, and that's the easiest/fastest route to that objective.

NB: As you discovered, most cards do not have exactly 100% the same 'disk' geometry which complicates block cloning.

Use connmanctl to review and perhaps change the interface sequence order to modify routing.

While 98% of the boxes out there have the same Broadcom RTL8211F chip inside, there are occasionally other chips used, and they can be using a different bus slot which requires a different device-tree and/or maybe an additional driver in the image. As a start, share the system log (assuming you can access SSH over WiFi).