Posts by chewitt

Yup, as already stated in post #2 you cannot do this without building a custom version of Kodi with forced rotation baked in. Kodi needs to be able to read DRM properties to understand that rotation is required, and then needs to render the UI rotated to match the prescribed orientation. Kodi does not do that currently, so the patch is required to force change.

I've not seen reports of "Invalid Password" from other users except when wifi the passphrase is either wrong or contains illegal characters. There are also long-running reports of an "Invalid Key" error which is influenced by a large number of things; but the main one appears to be wireless signal strength, and RPi boards often suffer from poor signal due to the less than brilliant onboard antenna. RPi4 and RPi5 have different wifi chips and antenna layouts so can behave differently from the same location.

I've no idea what the "no route to host" issue is caused by. Please put Kodi in debug mode, reboot and then replicate the issue, then SSH in and run "pastekodi" and share the URL so we can see Kodi and system logs.

The OpenVPN config PIA distributes implements a Certificate Revocation List (CRL) check for security reasons, but the CRL data they embed in the config contains invalid dates and this causes connection failures with OpenSSL 3.3.0 or newer. Our master branch (LE13) bumped to 3.3.0 in April 2024 and is currently on 3.5.0, while the LE12 branch is currently on 3.2.4 - so I would assume you have moved from LE12 to LE13 and this introduced the issue.

See https://github.com/openssl/openssl/discussions/24301 - according to posts/reddit threads linked from that discussion thread the workaround is removing the <crl-verify> section from the PIA config.

Attempting to support a range of nVidia card generations is a complete clusterfcuk due to different drivers and their wildly different and incompatible dependencies. The latest generations over cards are starting to converge on the open-source standards used with Intel/AMD; and that's likely to force a decision to support only those cards. I've been experimenting with nouveau, but I keep finding issues which appear to be long-running and unresolved so I'm not seeing that as a good and reliable solution.

The /storage/logfiles directory is not a persistent log storage location. It maps to the \\LIBREELEC\Logfiles Samba share and a zip archive of logs will be auto-generated when the Samba share is accessed over the network. If you have not accessed the Samba share from the network there will (correctly) be no files in the directory.

Run "journalctl | paste" and share the URL generated so we can see the system log (Kodi debug logs are unlikely to be useful).

Quote from sufr3ak

I don't think it's Kodi, but possibly hardware related

You're not sharing a Kodi crash log so I have to assume Kodi didn't crash; and the debug log shared doesn't contain anything that stands out. However if as you suggest Kodi is not to blame and it's something lower level causing the issue, that won't ever show in the Kodi log anyway. For that reason you need to share the system log.

It will probably work and be reasonably fast. However your blind guess is as informed as our blind guess, so

Subtitles are broken on Amlogic devices that use a Mali Utgard GPU (all GXBB, GXL and GXM boards) due to changes in OpenGLES shaders that Kodi uses. The developer who made the breaking shader changes (Sarbes) is aware of the issue caused, but he doesn't appear to be doing anything about un-breaking things either.

I assume Allwinner/Rockchip devices are also impacted as some of them also use Utgard GPUs, although I've not seen user reports.

Go back to the oldest LE13 image in the nightly archive and check there. If it does not work, that's good, and you can start to 'bisect' the nightlies (Google what bisecting is if you're not familiar with the concept) to pinpoint the first-good image. We can then look at the changes made on/around that image date to see what might be required for LE12.

If the oldest LE13 image works, the changeset between LE12 and LE13 is too large to guess what the fix was so the solution will be to use the working LE13 image and you need to nag add-on developers to port their add-ons to K22.

You've posted an incomplete Kodi debug log (that doesn't show anything) and no system log. In short; nothing to comment on.

In short, no, because it should be implemented in Kodi and not handled locally for LE. It's been half-investigated by Kwiboo in the past, see https://github.com/xbmc/xbmc/pull/14358, but that PR includes a pile of other things that were a little ahead of the kernel DRM framework maturing and it was closed.

If you want to make a feature request, it should be done in the Kodi forum as this would be a Kodi feature.

video=HDMI-A-1:1920x1080@60D,rotate=90

Kodi does not currently support Linux DRM rotatation so you can configure things like this ^ in kernel boot params (syslinux.cfg) but this is interpreted by Kodi as a resolution change from 16:9 to 9:16 not a rotation. If you also patch Kodi sources like this: https://github.com/xbmc/xbmc/issu…ment-1694808244 it's possible to force a permanent rotation in Kodi too, but that requires you to build a custom LE image (not that hard, but not something everyone can tackle).

Copying xrandr from another image won't achieve anything because the 'x' in xrandr is for X11 and the Generic no longer uses X11 Windowing. The Generic-Legacy image still does, so you can cross-grade to that. The legacy image will still exist for LE13 but I won't guarantee it exists for LE14 .. the demise of X11 is long overdue.

You can also see if an LE12 nightly solves the problem?

Take a backup (in case you want to restore) then update to the current LE13 nightly and test again. Still an issue?

Run "pastecrash" from the SSH console and share the URL

If you grab the relevant Linux, Kodi, and FFmpeg patches (which are probably in jernej GitHub repo; he's one of the Allwinner kernel developers) you should be able to (re)compile things for another distro. There's no HOWTO guide for that kind of thing though, so it'll be down to your tinkering skills.

You need to paste the crash log that demonstrates the play + ffwd/rew + segfault event, not the clean post-crash log that doesn't contain anything useful.

If ffmpeg fails to decode the stream the issue is most likely with ffmpeg support for VAAPI or the Intel GPU driver which provides VAAPI (or an edge case with mesa) so I would start by reproducing the issue on a general purpose distro (in part to prove it's not LE specific) and then report the problem to ffmpeg developers via their 'trac' reporting tool.