Posts by HiassofT

Kernel+firmware bump PR just got merged, the next nightly will include that.

LE uses the start_x variant of the firmware, http://start4x.elf/fixup4x.dat renamed to http://start.elf/fixup.dat, so it's best to test with "start_x=1" in config.txt on RPiOS to make sure the exactly same firmware is used.

Or you can download http://start4x.elf/fixup4x.dat from here https://github.com/raspberrypi/firmware , rename them to http://start.elf/fixup.dat and put them on the LE /flash partition.

so long,

Hias

Yes, video decoding is working at 10bits but display output only in 8. BTW: this is already fixed in development builds, next LE10 release will have it, too.

so long,

Hias

Not really sure. There's been a recent firmware change affecting clocks https://github.com/raspberrypi/fi…70f31a98167eef6 - I plan to update kernel+firmware in LE later this week, so might be worth giving it a try after that.

It could also be that the silicon in the RPi4 is marginal - a small overvoltage in config.txt might help.

Also please test with RPiOS and latest rpi-update kernel.

so long,

Hias

It looks like the firmware crashed. Can you try with a complete clean install on a separate sd card? Not sure if force_turbo and/or core_freq_min might play a role in that.

Edit: if this doesn't help please also test with latest RPiOS and see if you get the same "Firmware transaction timeout" splat.

so long,

Hias

Somehow you seem to be running an ancient firmware version (start.elf)

Jan 18 11:35:43.585387 LibreELEC kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2021-09-30T19:21:54, variant start_x

Try a fresh install, this should be 2022-01-06

so long,

Hias

Quote from powerarmour

I'm hopeful the DRM pull for 5.18 will help these sort of issues, I've always found hotplug detection to be pretty janky on RPi4's:

Code

Handover display from firmware to vc4 more gracefully, and support nomodeset.

These changes are already in the LE RPi kernel, they are just being added to upstream.

I'm not aware of any hotplug detect issues so far - if you experience any problems that are not related to broken hardware/adapter/cables please provide more info (logs with drm.debug=0x04, TV/monitor/AVR model etc).

so long,

Hias

Quote from Skripo

getedid create gives the following:

error: cannot detemine active connectors

This means hotplug detect isn't working. Try without your Argon One case, most likely this is the culprit, or add video=HDMI-A-1:D to /flash/cmdline.txt as a workaround.

so long,

Hias

Crashes with teletext are to be expected as this isn't fixed in kodi.

Frame drops / stuttering with overlays are also a known issue, the cause is not quite known yet though, probably some bud or oddity in kodi's render code.

As for RPi3: it seems to be running out of CMA memory. Can you try increasing it a bit, default on RPi3 is 256MB, testing with 320MB or 384MB would be interesting:

Add the following line at the end /flash/config.txt (use cma-384 for 384MB):

dtoverlay=cma,cma-320

so long,

Hias

lomion the teletext crash looks like an old kodi issue that still isn't fixed https://github.com/xbmc/xbmc/pull/17921

Can you give this build a try? https://www.horus.com/~hias/tmp/libr…358-de11582.tar

It contains a newer kodi Matrix version with several PVR fixes - could be that the PVR channel crash is fixed with it. If not please enable debug logging and post a new crash log.

so long,

Hias

Please post logs with the "upload crash log" option in LE settings.

so long,

Hias

The "flip done" / "blank display" issue unfortunately is rather intermittent - I haven't got it here yet but others (including RPi devs) run into it more frequently.

Just keep an eye on it (whether you use the freshly installed nightly or the other SD card) and if something odd happens just ssh in, run "pastekodi" and post the URL.

so long,

Hias

irisheyes47 thanks, but we need a pastekodi log - ssh in and run "pastekodi".

If it's the issue I'm speaking about dmesg/journal should contain "flip done timed out"

so long,

Hias

irisheyes47  camelreef can you please post a "pastekodi" log after you ran into the black screen / no picture issue?

There's a known bug in the current 5.15 kernels which causes that, would be good to know if it's the same issue or not.

so long,

Hias

imforumman can you please test if this build solves the issue?

https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-10.0-devel-20220124180358-de11582.tar

It contains a patch from popcornmix https://github.com/popcornmix/lin…3b576a466584234 that should help.

so long,

Hias

If you don't want to return the broken case you should be able to work around the issue by adding video=HDMI-A-1:D to cmdline.txt (after "quiet", on the same line) or runing getedid create with the TV connected directly to the RPi on HDMI0.

so long,

Hias

zehner the explanation is here - it caused issues with 4kp50/60 which need scrambling.

Quote

There was a bug in the kernel driver where we would read the edid without hotplug being asserted which is against spec (and caused issues with re-enabling scrambling after switching hdmi input).

Instead of writing long posts please just test without the case and it's HDMI adapter PCB (or whatever it's plugging into the RPi's HDMI ports inside).

The logs you posted indicate that hotplug works fine on the second HDMI port but not on the first one - which is very likely caused by the adapter inside the case (Argon one case had a myriad of these problems because of manufacturing defects and the like).

If this works just return the case and get a replacement.

so long,

Hias

Quote from zehner

How can the case be the problem, if the same case with the same cable on the same port renders the screen before 10.0.1 (everytime, not only sometimes) and only the update breaks the signal (everytime, not only sometimes).

...

Have a look at this thread or

https://github.com/raspberrypi/firmware/issues/1648

The answer to your question is in the issue report you linked, read this and the following comments: https://github.com/raspberrypi/fi…ment-1003779792

so long,

Hias

Use otg_mode=1 instead - see eg here https://github.com/LibreELEC/Libr…mment-739526268

so long,

Hias