Posts by chewitt

The "lima" driver is responsible for 2D graphics (the Kodi GUI) rendering. Do you have a visualiser running while music is playing?

If yes, disable it or change it and see if that makes any difference?

You can also update to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar which has newer kernel (so newer lima driver) + newer mesa + newer Kodi .. will be LE12 once Kodi moves to RC and we can release a formal beta. Newer is not always better, but newer is different, so we can see if it influences the outcome.

NB: I also have no idea how to debug this

LE 11.0.4 will be published shortly, but we will not enable auto-update until after Christmas at least, as we don't want to generate extra support traffic over the holiday period. You will be able to manually update once it's on the servers.

Is "wait for network" set in the LE settings add-on? .. what happens if you manually refresh the repo a minute after boot?

I rather doubt that I'll figure this out without access to hardware for local testing and tinkering. If you spot a hifi-shield card or even a complete C2 with one included for sale somewhere let me know.

Some morning brain farts:

It would be simple to do a custom LE image aimed at e.g. Tvheadend with more built-in/pre-configured. However the main challenge with DVB is that half the cards users show up with require a non-standard kernel hacked to run with a not-upstream driver so the more appliance-like you make a DVB image, the more limited the audience of users it might work-for becomes. The secondary issue is the inherent diversity of a global audience. LE active-install stats show we have more German (#1), Czech (#3), Spanish (#4) and French (#5) installs than English-speaking US/UK/CA/AU countries combined (#2/#6/#8/#9) so one design danger is assuming the audience and config requirements we see from (English-speaking) forums looks like the one we're most familiar with.

The add-on from edit4ever might be a good base to work from: https://github.com/edit4ever/script.module.tvh2kodi - the last update was a couple of years ago and Jason hasn't been active around here for a while so it probably needs some work. With my LE hat on: It would be great to have it combined with a setup wizard in our repo to make it more accessible. With my Tvheadend hat on: I don't believe the add-on depends on LE so updating and publishing to the Kodi add-on repo or perhaps to an independent repo that Tvheadend manages would increase the potential audience; albeit at the expense of integration with the LE settings add-on. NB: Tight integration creates the best user experience but typically increases maintenance and if you sense any hesitancy among project maintainers towards integrations; it's because we have an underlying desire to keep things as simple and low-maintenance and sustainable as possible. With that in mind, I suspect a series of good HOWTO guides for the main PVR back-ends in the LE wiki would be a good start for our users.

The RTL8189ES driver only exists in my private image (which is why you are stuck with them) so nightly changelogs are irrelevant. I checked the upstream repo that I get the driver from an I'm using the latest versions. Ping CGarces for input ^

2023-02-16 18:11:13.602 T:888     error <general>: ## LibreELEC Addon ## oe::load_url(http://releases.libreelec.tv/releases.json) ## ERROR: (URLError(gaierror(-3, 'Temporary failure in name resolution')))

^ The error is misleading: dateTime is before the start validity of the TLS certificate and thus the connection fails. If you move time forwards or fix NTP then connections should succeed. I have no issues accessing the repo here on an RPi5. Also note that the repo is intentionally not browseable from a browser so that's expected.

The Linux kernel doesn't support the dynamic formats like HDR10+ currently.

The kernel has bumped from Linux 6.6.x to Linux 6.7.x-rc so the shitty Realtek WiFi driver probably needs some fixing.

No PVR back-ends are preinstalled in the LE image, all must be installed from the LE add-on repo. It's also possible for users to install Docker and the linuxserver.io repo and run Tvheadend (and likely others) as a container. I would start by creating and proving the wizards to each PVR add-on, and once there's equivalent coverage, tackle hooking that into the first-run wizard.

Quote from genaker

I wasnt' able to get the logs, I checked the instructions but I couldn't do it...

It's a bit like going to a car mechanic (without the car) and asking why it doesn't work..

Have you removed the previously downloaded .zip from /storage/.kodi/addons/packages? .. because Kodi will reinstall using the already downloaded zip instead of redownloading if the file exists (deleting the add-on and settings via the GUI is not enough). The log snippet looks like it's trying to use something built for Xorg (needs OpenGL) wheras the GBM version would use GLES libs.

I put the wiki link in post #2

Quote from balanga

How do I get to see dmesg output?

Actually, I managed to login via ssh

And what happens if you type "dmesg" and hit enter?

It's not complicated and you can't break anything (worst case you delete a file and reboot to reverse changes). All it needs is some patience and initiative.

If you share logs we might be able to understand why it no longer works and take action (which is cheaper). You won't find many device recommendations because it's too much of a lottery.

LE12 nightlies are running Linux 6.6.x kernels (latest, and will be stable/LTS) and Linux 6.7 is still in the RC stages. Intel are very good at pushing support for new chips upstream. They are less good at fully testing all their media capabilities (their focus will be more on desktop distros) so there are occasional gaps in feature coverage and accidental driver breakage can happen. They do fix things that are reported to them, but few LE staff run x86_64 hardware these days so if there are issues the onus is on affected users to do the reporting. The general rule will always be that issues unreported upstream don't get fixed quickly.

Please describe the audio configuration (audio settings page/options) or take/share a photo.