Posts by HiassofT

Please use the crash upload function in LE settings (or pastecrash via ssh) to provide logs.

Most likely you are running out of (CMA) memory - the necessary info about that is not in kodi logs, but in pastecrash logs.

so long,

Hias

I could reproduce the issue and identified the Y2038 PR https://github.com/LibreELEC/LibreELEC.tv/pull/6727 as the culprit.

I've opened an internal discussion about that but IMO we should just revert that change as it's not fixing any real problems, just causing new ones.

so long,

Hias

It might be the cable (or the connections between cable and IDC connector) is faulty, such things happen.

so long,

Hias

As a temporary workaround add the hdmi_group/mode settings to /flash/config.txt, that will survive updates.

They set a different video mode than the usual default (which will later be used during LE startup) which seems to be enough to make the TV happy and show a picture.

so long,

Hias

See here RE: LibreELEC (Matrix) 10.0.3

so long,

Hias

RPi2-4 can only provide a max of 1.2A to USB - note that this is for all ports combined.

Raspberry Pi Documentation - Raspberry Pi hardware

The official documentation for Raspberry Pi computers and microcontrollers

www.raspberrypi.com

so long,

Hias

The two most common issues with USB drives are power consumption and dodgy USB controllers/bridges in the USB drive.

First make sure the drive is powered properly (RPi can only supply a very limited amount of power). If you are using a drive with it's own power supply then you should be fine. If you are using a bus-powered drive and connect it to a powered USB hub.

If your drive has some dodgy USB controller then first try with the current LE11 nightly build. It comes with a lot newer linux kernel and might already have workarounds for the dodgy controller in place.

If this doesn't help and/or you want to run LE10 then first try booting from a SD card (or your USB key), plug in the drive and post a full log (run "pastekodi" via ssh or use the log upload function) - this will give us some information about your drive.

You can also check dmesg/journal or lsusb output yourself.

The info you/we need are the manufacturer and model of the drive and the USB vendor and product id.

Searching for that eg on the RPi forum https://forums.raspberrypi.com/ might already give you the info you need - usually some usb quirks that you need to add to cmdline.txt.

The most common issue is broken UAS support in the drive, in that case you need to add something like usb_storage.quirks=1234:5678:u to /flash/cmdline.txt (where 1234:5678 need to be changed to the USB vendor/product ID of your drive).

so long,

Hias

You could try installing permanent EDIDs with "getedid create" (run that when the AVR showed up in audio settings) and/or add "vc4.force_hotplug=3" to /flash/cmdline.txt

Depending on the actual issue one of those options might be sufficient or you might even need both.

BTW: To remove the permanent EDID run "getedid delete" and reboot - you also need to do that if you want "getedid create" to read new EDIDs from TV/AVR (eg when switching TV/AVR or HDMI ports).

so long,

Hias

I'd really stay away from 1GB.

Kodi has rather long standing and yet unresolved issues with image handling (eg with pictures but also movie etc artwork) and is consuming too much (graphics) memory - which often leads to out-of-memory crashes.

We regularly see these issues on RPi2/3, which have 1GB.

so long,

Hias

It depends.

I usually whitelist 720p, too, so my TV (LG 55C8) does the upscaling.

But whitelisting SD has several drawbacks:

First of all GUI overlays, subtitles etc will then be rendered at a low resolution and look very ugly.

For SD material there's also the anamorphic problem, where pixels aren't square and kodi doesn't handle that too well and kodi doesn't signal 4:3/anamorphic 16:9 to the TV.

Lastly my TV has the annoying behavior of always cutting off overscan in SD resolution so parts of the GUI are missing.

If you can live with the limitations you are free to enable SD output but it's a lot more hassle free to just let kodi upscale SD to HD.

so long,

Hias

Stay away from the 1GB model, that's not enough for LE/kodi and IMO 8GB is overkill for LE.

So that leaves the 2 and 4GB models.

I usually chose the 4GB models (but that was before the chip and availability crisis and price difference between 2 and 4GB was small) but LE will run just fine with 2GB so pick whatever you can get.

so long,

Hias

uncomment means you have to remove the "#" at the beginning of the following two lines. That part of config.txt should then look like this:

# uncomment to enable analog audio output
dtparam=audio=on
audio_pwm_mode=1

so long,

Hias

Quote from PiMONSTER

Just updated by selecting 10.0.3 under channel. Seems OK.

BUT ...... the firmware update refuses to update.

selected and rebooted twice to no avail.

Still offers update from the installed January edition.

On reboot a screen does indicate update available and then rapidly disappears.

Remind me what are the commands to update via the terminal ?

Display More

I assume you are using an RPi4 and try to update bootloader firmware (which doesn't work with USB boot yet). In this case run

rpi-eeprom-update -a

and then reboot.

so long,

Hias

The kernel update https://github.com/LibreELEC/LibreELEC.tv/pull/7087 has been merged, the next nightly build should contain the fix.

so long,

Hias

Please run the following command while connected to your Grundig TV and post the URL you got:

modetest | pastebinit

so long,

Hias

Deri could you please test with this build:

https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20221102193102-92f9d97.tar

It includes the latest 6.0.6 kernel with the fix from 6.1

so long,

Hias

Ah, and our config.txt might also play an important role. The LE specific settings are in distroconfig.txt (which is included in config.txt)

LibreELEC.tv/distroconfig.txt at libreelec-10.0 · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

Most important bit for RPi4 is using 512MB of CMA memory - otherwise several 4k HDR files lead to a crash (the default of 256MB CMA is not enough).

so long,

Hias

We are using pretty stock RPi kernels, from https://github.com/raspberrypi/linux (rpi-5.10.y branch for LE10, currently rpi-6.0.y for LE11, we'll switch to the LTS kernel, probably 6.1, when it's out as RPi folks use LTS kernels as a base, too).

We only apply a few patches on top, you can find them in the packages/linux/patches/raspberrypi directory, eg here for LE10:

LibreELEC.tv/packages/linux/patches/raspberrypi at libreelec-10.0 · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

The only somewhat important patch is

linux-020-eld-constraints-for-compressed-formats.patch - it's a bit hacky but helps getting TrueHD/DTS HD passthrough with some TVs/AVRs (most TVs/AVRs are fine without it).

so long,

Hias