Posts by chewitt

Start with a debug log that demonstrates the issue occuring. We will be interested to understand the system config and type of media being played, e.g. to see if it's 4K60 which requires more power (could be power issues) leading to undervolt warnings in the system log. It could also be the cables if not 'certified' ones. Regular causes of display problems also include micro-HDMI to HDMI adapters, Argon 40 cases, and a load more things. System temp is also something to be tracked.

In terms of releases/versions, I would update to an LE13 nightly image instead of downgrading to LE11. Nightlies cannot be tagged as stable due to Kodi not-yet-starting the Piers release cycle, but I've run them daily on an RPi5 for the last year and half .. they seem pretty stable to me

You can't download it, you need to build it:

https://wiki.libreelec.tv/development/build-basics

https://wiki.libreelec.tv/development/build-advanced#debug-images

Top won't be very enlightening as it shows no detail on what threads are active. For that you'll need other tools and a debug version of Kodi that includes symbols; we strip them from the binary after compile to save space.

Have a read, it's not entirely about 4K/HDR: https://wiki.libreelec.tv/configuration/4k-hdr

========== /flash/cmdline.txt ==========
boot=UUID=2001-4441 disk=UUID=30f5d869-400e-4a82-8b7b-a5173e9001ba quiet console=ttyAMA10,115200 console=tty0 drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin,HDMI-A-2:edid/edid-HDMI-A-2.bin video=HDMI-A-1:D video=HDMI-A-2:D

I'm wasting my time ^ .. Good luck.

video=HDMI-A-1:1024x600M@60

Remove everything from config.txt, and append that ^ to cmdline.txt

Better?

Quote from libreAU

But I can definitely tell the difference between 8 and 12 bit hdr.

Well, you think you can, but since your source media is either 8-bit or 10-bit, you can only tell the difference between 8-bit and 10-bit media; which is more than enough, hence broadcasters don't bother with 12-bit media.

Pastebin a Kodi log (SSH in, run "pastekodi") so that we can see what config is being used. I'll say again (third and final time) that forcing EDID is not the solution to your problem. Also use the HDMI port nearest the power connector.

Your setup is not receiving correct EDID and thus the picture is not being interpreted correctly. This is normally caused by bad cables or adapters and the correct solution is having EDID correctly exposed "normally" .. the get edid script should only be used for faking presence of the TV/AVR to workaround boot order problems.

The monitor that you captured EDID data from has no speakers, hence Kodi detects no audio capabiities. EDID capture is not the solution to your problem.

balbes150 10-bit HEVC issue is resolved with a workaround (the proper fix will be complicated) see: https://github.com/chewitt/linux/…376930a5fa28a4a

I started looking at RK3576, but looks to be 'early' for support still (another kernel and u-boot cycle needed). Then I look at RK356X, and then older 64-bit boards. I'm going to consolidate all the kernel defconfigs into one common one to make maintenance easier.

Append video=HDMI-A-1:1920x1080M@60 to boot params in cmdline.txt and see if that resolves things? If not, ensure you are using a 4K certified micro-HDMI to HDMI cable and not micro-HDMI to HDMI adapters (which often cause issues), or if using an Argon case; remove the board from the case and connect direct to the TV to prove that the adapters in the case are causing the issue.

If none of that works, power off, remove the SD card, power on to the firmware screen and check it reports 'EDID' on the active HDMI connection (use the port nearest the power connector). Report back.

Quote from eliaslear

i have at least 4x the amount of pirated movies on mine

Noted. Don't bother asking for support around here again.

Quote from PeteAklNZ

I'll just use my workaround until LE13 is available.

The only reason LE13 isn't released is nobody in Team Kodi volunteering for the task of release manager. LE13 nightlies are otherwise available and quite stable for use.

RK3588 current state using my working branch: H264 works well and older MPEG2/VC1 codecs are software decoded. HEVC 8-bit seems to work but 10-bit has some kind of wrong format/modifier problem. AV1 is missing due to no hwaccel in ffmpeg and older wip patches exist but don't work, and the effort needs reviving. VP9 is missing due to no kernel driver, and Collabora tell me this is not planned right now. I've flagged the HEVC 10-bit issue to Collabora devs working on HEVC support.

I didn't look at 4K support anywhere yet, but I believe there are still some things missing for that (both in DRM and in some of the drivers). NB: Only Direct to Plane should be used (EGL is for Intel/AMD/etc.) and unless you massively screwed up Kodi settings reinstalling won't achieve anything.

In config.txt:

* Remove initramfs edid.cpio

* #comment out hdmi_enable_4kp60=1 as this requires more power

If you are using any kind of micro-HDMI adapter, bin it and get a proper micro-HDMI to standard HDMI cable. Or if you are using an Argon case, remove the board from the case and connect it direct to the TV (it uses an adapter, and adapters cause problems). Also try other HDMI ports on the TV (not all are equal).

It's trying to run the GUI at 4K60 and perhaps the TV doesn't support 4:2:0 input or the cables don't support the bandwidth needed or something. Either way the GUI is best at 1080p, see: https://wiki.libreelec.tv/configuration/4k-hdr

Edit cmdline.txt to remove the unnecessary EDID stuff, then append video=HDMI-A-1:1920x1080M@60 to force the initial DRM output to 1080p@60Hz. Fixed?

The Kodi log isn't useful (not a debug log) and mostly informs that you are playing pirated media. The kernel section of the logs is more useful and suggests the drive you are storing your stolen media on is in the process of surrendering to the gods and will not be long on this earth:

Jul 16 22:33:06.550020 KODI kernel: ata2.00: exception Emask 0x10 SAct 0x40 SErr 0x90200 action 0xe frozen
Jul 16 22:33:06.550347 KODI kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed
Jul 16 22:33:06.550432 KODI kernel: ata2.00: failed command: unknown
Jul 16 22:33:06.550533 KODI kernel: ata2.00: cmd 60/00:30:30:c6:33/01:00:ac:02:00/40 tag 6 ncq dma 131072 in
                                             res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jul 16 22:33:06.550621 KODI kernel: ata2: hard resetting link
Jul 16 22:33:12.420089 KODI kernel: ata2: link is slow to respond, please be patient (ready=0)
Jul 16 22:33:16.556749 KODI kernel: ata2: found unknown device (class 0)
Jul 16 22:33:16.710088 KODI kernel: ata2: softreset failed (device not ready)
Jul 16 22:33:16.710275 KODI kernel: ata2: hard resetting link
Jul 16 22:33:20.416627 KODI kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jul 16 22:33:21.960017 KODI kernel: ata2.00: configured for UDMA/133
Jul 16 22:33:21.960211 KODI kernel: sd 1:0:0:0: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=15s
Jul 16 22:33:21.960834 KODI kernel: sd 1:0:0:0: [sdb] tag#6 Sense Key : 0x5 [current] 
Jul 16 22:33:21.961340 KODI kernel: sd 1:0:0:0: [sdb] tag#6 ASC=0x21 ASCQ=0x4 
Jul 16 22:33:21.961826 KODI kernel: sd 1:0:0:0: [sdb] tag#6 CDB: opcode=0x88 88 00 00 00 00 02 ac 33 c6 30 00 00 01 00 00 00
Jul 16 22:33:21.962302 KODI kernel: I/O error, dev sdb, sector 11479008816 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
Jul 16 22:33:21.962367 KODI kernel: ata2: EH complete

Karma