Posts by HiassofT

Cris_ from your logs it looks like the RPi isn't detecting the AVR - HDMI shows up disconnected in modetest.

Can you try adding drm.debug=0x04 to the end of cmdline.txt?

pastekodi plus modetest outputs from a cold boot (RPi disconnected from power) would be great.

If you don't see the LE splash then ssh in and reboot. Do you see the LE splash now? If yes, please post pastekodi/modetest outputs of that, too.

Also try adding video=HDMI-A-1:1920x1080M@60D (note the "D" at the end) to cmdline.txt. Does this work? Again, pastekodi/modetest outputs would be great.

so long,

Hias

Please ssh in and post the output of "pastekodi" and "modetest | pastebinit" while running LE 10.0.1

so long,

Hias

Latest LE11 nightly RPi2 build from https://test.libreelec.tv/ should start fine on RPi zero 2 (LE10 would also work but we have no RPi2 builds yet).

Note though that 512MB RAM will be quite tight and you may run into out-of-memory issues.

so long,

Hias

Quote from nicoco

Could you please elaborate on both the tinkering process and the drawbacks?

Simulateneous output was great for me with previous version, I'd like to do it again! My pulseaudio skills are limited but I guess that is the way, right?

I've never tried it myself but IIRC there were forum posts from others who did that and reported that audio was significantly delayed. The search function should help you find the posts.

so long,

Hias

YCbCr output isn't implemented in the graphics driver yet, so output will always be RGB 4:4:4, 8bit ATM.

The hdmi settings in config.txt won't have any effect and tvservice is also obsolete - newer tvservice versions will now show a warning instead of printing confusing and wrong info like "TV is off"

LibreELEC:~ # tvservice -s
tvservice is not supported when using the vc4-kms-v3d driver.
Similar features are available with standard linux tools
such as modetest from libdrm-tests.

"modetest" is included in LibreELEC and will show you what modes are available, the EDID read from the TV/monitor, output properties etc.

so long,

Hias

The easiest workaround is to connect the RPi to a similar monitor with non-broken EDID and run "getedid create" via ssh. LE will then permanently use the EDID of that monitor (you can remove that with "getedid delete" later, if needed).

so long,

Hias

Please provide more info, at least we need a pastekodi debug log where you reproduced the issue.

Did you do anything special to trigger this, eg switching resolutions? Is the previous nightly (20211026) OK?

The only way I can trigger that is when switching to 720x480i or 720x576i and then back to eg 1920x1080, but this is a known issue for quite a while (and those modes should better be avoided as they are buggy and result in pixelated output).

so long,

Hias

This is a known issue which is even mentioned in the release notes https://libreelec.tv/2021/08/26/libreelec-matrix-10-0/

Quote

4K50/60 output is supported by the driver, but has some known issues (eg “no signal” when TV is put into standby and back on)

It'll be fixed in LE 10.0.1

so long,

Hias

See here: RE: Cannot Install/Update Addons

so long,

Hias

You seem to have replaced config.txt with the old version from LE 9.2 with a high gpu_mem setting - that won't work.

Do a fresh install and keep config.txt as is.

so long,

Hias

Use the forum search function and you'll find this thread RE: Playback issues with YouTube Addon

so long,

Hias

LE 9.0 (and before) use the old openssl 1.0.2 version which is tripping over the DST Root CA X3 expiration end of September - read more about it here: https://www.openssl.org/blog/blog/2021…RootCertExpire/

Fortunately applying the workaround 1 (removing the cert) is quite easy:

First create the directory /storage/.config/system.d/openssl-config.service.d:

mkdir -p /storage/.config/system.d/openssl-config.service.d

then create a file drop-dst-x3.conf in there (full path is /storage/.config/system.d/openssl-config.service.d/drop-dst-x3.conf) with the following content:

[Service]
ExecStartPost=sed -i '/^DST Root CA X3/,/END CERTIFICATE/ d' /run/libreelec/cacert.pem

Now reboot and kodi (and curl etc) should be happy again.

so long,

Hias

The fixes were just merged today and will be in the next nightly and in LE 10.0.1

so long,

Hias

ErikSwan the RPi4 HDMI driver exposes standard DRM connector properties to set HDR metadata and colorimetry (BT709/2020) info, like eg Intel and AMD drivers do it, too. This is included in current upstream kernels (since 5.14) and in the downstream 5.10 RPi kernel - I haven't checked with the upstream kernel though.

The driver also exposes a max_bpc connector property to switch from 8bit to 10 or 12bit output, but YCC output (4:4:4 or 4:2:2) selection isn't implemented yet - the driver always outputs in RGB 4:4:4 ATM.

There's a draft PR to allow RGB/YCC selection via another connector property https://github.com/raspberrypi/linux/pull/4201 but ATM it's a bit unclear if it will be implemented that way or if it should be handled internally in the video driver (eg 4kp60 can't output 12bit 4:4:4 due to bandwidth limitations, auto-switching to 4:2:2 may be desirable in that case).

so long,

Hias

Just copy the tar file to the Update SMB share (or to /storage/.update/ via ssh/scp) and reboot.

so long,

Hias

Are you using ASS subtitles? If yes, then look here: RE: LibreELEC RPi4 9.95.2 does not reproduce .ASS subtitles

so long,

Hias

kodi.bin consuming about 15-20% on idle is quite normal on a clean install. Keep in mind that this is the percentage of a single core, RPi4 has 4 cores so it can go up to 400%. If you look at the "%Cpu(s)" summary in top you'll see about 95% idle.

Also keep in mind that the CPU frequency will have scaled down to 700MHz (check with bcmstat.sh or "vcgencmd measure_clock arm") and the load values reported from top are relative to that. So in absolute terms (4 cores at 1.5GHz max) kodi comsumes about 2.5% of available CPU resources.

Of course addons etc running in the background will consume CPU resources, so 20-30% (of a single core, at 700MHz) still look rather plausible.

so long,

Hias

Ballistic did you actually reproduce the issue before creating the log? Log entries look like you grabbed the log immediately after startup.

Also the logs show you are connecting through a Denon AVR.

Does the issue also happen if you leave the AVR out of the chain and connect the TV directly to the RPi? If yes, please provide a debug pastekodi log where you reproduced the issue and state the exact model number of your TV.

so long,

Hias