LibreELEC-Generic.x86_64-11.0-nightly-20220618-b78941a.img.gz (sha256) worked straight away and is now sitting on an M.2 NVMe.
FYI: that's the oldest nightly we have - latest is down at the end (yeah, we know we should sort it newest->oldest, that's on our TODO list), better use that.
so long,
Hias
LibreELEC is using official Linux kernels and running a custom userland OS (so nothing like Debian, Arch, Fedora etc) and we don't use any window manager at all.
Kodi is in full charge over all graphics stuff and interfacing directly to the graphics drivers (that is, all the stuff your windowing system and window manager would normally do).
This has the benefit that kodi is in full control of everything graphics related and there are no additional layers in between that might decrease performance or hinder doing advanced stuff (like HDR output).
so long,
Hias
It seems ffmpeg is using software decoding which is too much for 4k - please verify if settings->player "Allow using DRM Decoder" and "Allow hardware acceleration with DRM PRIME" are both at the default (enabled) and "PRIME Render Method" is also at default (Direct To Plane)
so long,
Hias
See here https://wiki.libreelec.tv/support/update - simply copy the 10.0.3 to the update share and reboot.
As for the high CPU load - no idea, we need debug "pastekodi" log of 10.0.3, and you also could ssh in and check with "top" and "perf top" what's eating up the CPU resources.
so long,
Hias
I noticed a couple of things:
First of all you are running LE 10.0.2 - please test with the current 10.0.3 release
You seem to have connected the HDMI cable to the wrong HDMI port of the RPi - use HDM0 as HDMI1 has limited capabilities.
You seem to be playing through the emby addon - have you tested with SMB or the file copied to a USB pendrive / HDD?
You didn't enable debug logging and from the looks of it also not adjust refresh rate, together with whitelisting the important modes as described in the wiki. Please to the latter, permanently, and the first when you still have issues after the steps above.
Then upload the logfile either with the log upload function in LE settings or with "pastekodi" via ssh - the logfiles via the SMB share are unfortunately missing important info (guess we should fix that...)
so long,
Hias
Thanks for the log!
As expected RPi is running out of CMA (graphics) memory
Nov 24 23:49:06.029657 LibreELEC kernel: cma: cma_alloc: alloc failed, req-size: 720 pages, ret: -12
Nov 24 23:49:06.030344 LibreELEC kernel: bcm2835-codec bcm2835-codec: dma_alloc_coherent of size 2949120 failed
Nov 24 23:49:43.019743 LibreELEC kernel: [drm:vc4_bo_create] *ERROR* Failed to allocate from CMA:You could try with more memory, add eg dtoverlay=cma,cma-384 (or cma-512) to config.txt to increase it from 256 to 384/512 MB or use another less heavy skin.
There's also a long standing issue that kodi buffers way too many pictures than it actually should and thus is eating graphics memory for breakfast - until that's exhausted and it just crashes. Unfortunately there are no fixes for that yet 
so long,
Hias
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
RPi2-4 can only provide a max of 1.2A to USB - note that this is for all ports combined.
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
