Posts by HiassofT

    As you swapped the firmware for a much newer version my bet would be this is causing the issue - LE 9.2.8 is using an ancient 4.19 kernel and should be running the firmware that came with it.

    Just install official 10.0.4 or LE11 nightly versions.

    so long,

    Hias

    yullaw and all others who need the hdmi_mode/hdmi_group or input-switching workarounds to get a picture after boot, can you please test with this build:

    https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20230116232923-b261017.img.gz

    Write it to a spare SD card, don't make any other changes, and boot it - if the changes from popcornmix work as planned you should get a picture without needing any workarounds.

    so long,

    Hias

    If you are having issues please post full debug logs - otherwise we devs are unable to know the exact circumstances and background and won't be able to resolve potential issues.

    Enable debug logging in kodi, reboot, reproduce the issue then ssh in and run "pastekodi" (or use the log upload function in libreelec settings).

    The reason for not enabling 30/29.97/25Hz and instead allowing kodi to use double rates is that otherwise you'll run into issues with interlaced videos - they report as eg 25 Hz frame rate while they contain 50 fields and kodi will output that as 50 deinterlaced frames - and you'll get hefty issues trying to play 50 frames if kodi chose to setup display with 25 frames per second.

    so long,

    Hias

    Never ever hard power-off your system.

    There is no NTFS fsck for linux, the fsck.ntfs from ntfs3g only sets the "needs to be ckecked bit" - and you have to connect the drive to a windows PC and perform the filesystem repair there.

    It's best to format the drive as ext4 if you want to use it on linux.

    so long,

    Hias

    The log shows a read error from your NAS:

    Code
    2023-01-07 16:57:40.694 T:1048    ERROR <general>: Read - Error( -1, 110, Connection timed out )
    2023-01-07 16:57:40.694 T:1048    ERROR <general>: Process - <smb://192.168.1.3/Media/News/_move/Le.Pacte.Des.Loups.2001.DC.1080p.BluRay.DDP7.1.x264-W4NK3R.mkv> source read failed with -1!

    Network on the RPi4 side looks fine (nothing suspicious in logs) so it might be worth to check your network/switch/NAS and make sure you don't have any network/cabling issues and your NAS didn't go to sleep or something like that.

    so long,

    Hias

    Elysium sample is playing fine here as well.

    Might be worth testing with a different, 18Gbps certified HDMI cable, and without the JoyIT case (which seems to have a HDMI adapter board which could be problematic).

    BTW: RPi4 doesn't support 4k H264 playback, stick to H265 material.

    so long,

    Hias

    If you are having issues with EDID test without the case, and also a known good (or new) 18Gbps certified, fully wired HDMI cable - those two things solve about 95% of "display not working correctly" issues.

    Don't touch config.txt, gpu_mem=1024 can never work and even if it would it would only reduce usable memory without any benefit. 96 instead of 76 may help in very odd corner cases when dealing with out-of-spec H264 files but that's it.

    So in short: best use stock HW and SW setup - only adjust Kodi settings as outlined eg here https://wiki.libreelec.tv/configuration/4k-hdr

    Concerning hyperion: don't hold your breath for a solution soon, better thing about alternatives (external HDMI grabber or TV with ambilight built in).

    so long,

    Hias

    You can use the internal script "dump-active-edids" (it's used by "getedid" on RPi) to write the edids of all connected displays to /storage/.config/firmware/edid

    It'll tell you which HDMI/DisplayPort/... connections it detected, for each one it created a edid-<NAME_OF_CONNECTOR>.bin file - which you can then simply decode with edid-decode.

    eg here on RPi4 with one display connected to the first HDMI port (edid-decode cut down for brevity):

    You could also check through all the connectors in /sys/class/drm/, verify if the status reports "connected" and then use the edid file from there (eg /sys/class/drm/card0-HDMI-A-1/edid) - this is basically what that script does - but as card, and connector names may change it's probably easier to let the script deal with that :)

    BTW: so far we only tested the script on RPi, it should work on all other devices though, so if you have issue or notice something odd please tell us about it so we can fix/improve it.

    so long,

    Hias

    so long,

    Hias

    Thanks, this is interesting and useful information - this thread has become a bit convoluted, but most issues seemed to affect older (Samsung) models.

    Could you please test with the latest LE11 nightly build from here https://test.libreelec.tv/11.0/RPi/RPi4/…/11.0/RPi/RPi4/ ´(currently 20221215, scroll down to the end of the page) and if doesn't work test if the workaround of setting a different mode in config.txt works?

    Add the following to the end of config.txt

    Code
    hdmi_group=1
    hdmi_mode=20

    Also test (without those config.txt changes) if unplugging and replugging the HDMI cable gives you working video output, if yes set the display resolution in kodi to something different than standard (eg 1920x1080 at 50 Hz instead of 1920x1080 at 60 Hz) and report back if that works, too.

    Anyways, we'd need logs (with debugging enabled in kodi) of all working and non-working cases.

    so long,

    Hias