Posts by chewitt

Quote from Angrydad

Is there somebody who can help me?

LE 9.2.8 is old now so our first response is going to be "Please test a current release" to eliminate all the fixes and updates that were made since (there's been a few). I appreciate there are possible reasons for remaining on LE9.2 with an RPi3, but even if there's an issue and that can be pinpointed (sharing some debug logs would be a good first step) there's not going to be any fixes in that release, it's a long dead codebase.

NB: Tvheadend has evolved too. How old?

The "amlogic" branch has current changes. You don't need to report on updates if things work the same as before.

Quote from CoolPenguin42

Maybe I buy an adapter that is not jmicron

There's enough reports on that adapter for me to think it has firmware problems, so probably not a terrible idea.

ozarks Panfork was a fork of panfrost (hence the name) hacked/adapted for ARM Mali Valhal hardware while "panthor" was still in the earlier stages of development. As panthor is now developed and upstream it's been superseded. In theory Direct-to-Plane with DRMPRIME decoding should be the default used; although until I have some RK3588 hardware to test with (some is allegedly being sent to me) i'm unable to do anything beyond theorize what's missing or required.

balbes150 please push changes to your GitHub repo, thanks.

There's nothing on the LE side to prevent boot from USB, but I've sometimes found that Android boxes will only boot from a specific USB port, and some boxes refused to boot from one. Roll dice and see what happens

dominion The fix (merged several weeks ago) was for all hardware so whatever your issue is, it's something else.

LE13 dropped "wl" because it broke compat with the kernel and it's not been maintained (no new version) in years. We chose not to enable "b43" as an alternative because although it's technicaly "in-kernel" it's similarly abandoned and unmaintained and the likely audience of impacted users can probably be counted on one hand. As previously commented, if you have one of those cards intalled somewhere it's probably simple and cheap to swap it for something better.

LE13 nightlies are bumped to Linux 6.15.1 and images in my test share are bumped to Linux 6.16-rc1. No functional changes are expected .. the media drivers are still abandoned.

Quote from ozarks

I dare say that as Wayland development matures, solutions will be created.

The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.

Kodi has long supported building with espeak-ng and historically we included it, but the package was disabled in distro options in January 2022 due to some kind of compile issue. There has been no formal espeak-ng release since then, so although there are continuing contributions and commits to the upstream source, the tooling we use to detect updated packages and bump them has not triggered, and espeak-ng support has never been reinstated.

The upstream source switched from autotools to cmake so our package build recipe needs to be reworked, but the latest GitHash can be build with a little fiddling. The perenial challenge is that nobody on staff uses TTS so we can tweak the package to build the binaries but whether we build something usable is always an unknown question.

Run "journalctl | paste" and share the URL

Have you implemented the general ideas discussed in https://wiki.libreelec.tv/configuration/4k-hdr ?

If yes, and you're using refresh rate changing and whitelist entries correctly, you might need to experiment with the SMB chunk size in SMB client settings. I rather doubt it's network performance though, unless the switch is saturated with traffic or a bad cable/port is causing something to run at half-duplex (but unlikely, else you'd see more general issues).

balbes150 is building the image with the Wayland windowing environment, and this restricts you to a single refresh rate because Wayland does not support dynamic refresh rate changes. This is why LE does not use Wayland in official images (only GBM, and Xorg for nVidia). The LE build system supports Wayland because it's used with the Lakka retrogaming fork.

Two options for forcing an update to the install:

a) Adding "ssh" to kernel boot params in cmdline.txt wherever PINN stores/places this on the SD card. This will force the device to start the SSH daemon on boot and if you then find the IP address of the device (from the router, or an mDNS app) you can SSH in and wget the latest LE image to /storage/.update then reboot to update.

b) Copying the same update file to the //LIBREELEC/Update SMB share which is enabled by default and maps to /storage/.update and then reboot by cycling power to start the update (not as clean, but will work).

The RPi5 stepping/mesa issue was resolved ages ago so I'm not sure why PINN is offering an older image?

procount, how does PINN get our images?

The backup and restore functions in the LE settings add-on are intentionally simple and save/load only to/from a "local" filesystem path; the intention is to support users saving the backup to a USB drive. However Linux is Linux, so if you go and mount a remote filesystem to a local path then it becomes accessible.

"nothing to see here, move along please"

I've never used NOOBS or its successor PINN so have no idea what the manual install process is. I'd guess you untar our file and drop the files on the SD card somewhere

balbes150 почему wayland?

Quote from Rv88

Something have change in the kernel.

LE9 = downstream vendor kernel

LE12 = mainline linux kernel

There is zero kernel code in-common between LE9 images and LE12 images.