Posts by chewitt

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.

The best thing to do is plug the device in and then have a look at "dmesg" output. If the kernel has the driver and it's detected you should see the driver probe and load firmware. If it does we have Tvheadend 4.3 and VDR as back-end server apps that can be installed from the LE add-on repo. There aren't any specific guides on setting them up in our wiki, but both apps have their own project websites with their own documentation and a Google search will find up a ton of HOWTO articles.

Have a read here: https://wiki.libreelec.tv/hardware/amlogic

Read: https://wiki.libreelec.tv/configuration/ir-remotes - If there's an existing keymap to reuse you can set it using the 'basic' config steps. If not you need to create your own via 'advanced' config steps (not complicated).

RPi4 has zero support for PCIe devices so why is it "embarrasing" for LE to omit support for PCIe SATA things in our RPi4 image?

Feel free to send a pull-request to GitHub enabling the kernel config that's needed.

2023-12-17 14:52:49.657 T:991      info <general>: [display-info] make: 'LG Electronics' model: 'LG TV'
2023-12-17 14:52:49.657 T:991      info <general>: [display-info] supported colorimetry:
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   xvycc_601:   false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   xvycc_709:   false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   sycc_601:    false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   opycc_601:   false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   oprgb:       false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   bt2020_cycc: false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   bt2020_ycc:  false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   bt2020_rgb:  false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   st2113_rgb:  false
2023-12-17 14:52:49.657 T:991      info <general>: [display-info]   ictcp:       false

^ No bt2020 colorimetry support being advertised via EDID = No HDR.

Most ARM SoC devices check for bootable code in SPI > eMMC > SD > USB, so most of the time u-boot is found on eMMC and then if u-boot has a bootscript search sequence for finding a kernel, it often starts searching SD > USB > eMMC so that some level of "boot from SD card" is supported. The fact that "boot from SD card" is technically "boot from eMMC" is often lost when people assume that booting ARM boards works the same as booting a PC with a conventional BIOS boot process.

The first move is to update to a current LE12 nightly and retest to see if your problem is resolved among the newer 'everything' in the master codebase. The releases are stable for use for a while, we're only waiting on Kodi to call RC1 before shipping a formal LE12 beta release.

I'm not seeing any issues with audio file playback using normal Kodi so it's probably best to report this to Jellfin add-on devs via the Kodi forum (as likely something specific to that add-on).

Some "git grep" in the buildsystem doesn't show anything dependent upon the mpv-drmprime package so it's probably an orphan that should be deleted. I'll ask in team chat.