4kp60 output isn't supported in any of the current beta versions up to and including beta 5 - enabling 4kp60 in config.txt results in "no signal" issues so you shouldn't do that.
It took quite a while to get 4kp60 working properly (the kernel driver change was quite involved) so I deliberately waited after the beta 5 release before adding it - there are probably still issues we missed so this needs some time testing in nightly builds.
So consider this a bit experimental.
so long,
Hias
No changes regarding 10/12-bit output yet, but we just merged a huge set of kernel and ffmpeg changes. They improve H265 decoding performance, fix a couple of H264 decoding issues and add 4kp60 output.
so long,
Hias
Please give the latest nightly build (currently 20210630) from here Index of / a try.
We just merged a bunch of ffmpeg and kernel fixes and your sample played fine here with that.
so long,
Hias
Keep GPU, CMA and buffer settings as they are, changing those is quite dangerous, rarely helps and most often results in non-working or unstable systems.
If kodi crashed you should have a kodi_crash.log file in /storage/.kodi/temp/ - please upload that (or just use the crash log upload function in LE settings).
The "new" log doesn't show you playing a video file, the "old" one shows you played a file with TrueHD audio. There are a couple of known issues with TrueHD in kodi, so try selecting a different audio stream (eg the AC3 one) and see if this works.
so long,
Hias
Oh, you could have saved yourself and us a lot of time if you had mentioned that you used an Argon case before - these cases seem to cause a lot of trouble... See eg this recent post: RE: LibreElec 9.95.4 on Raspberry Pi 4 with Argon One V2 case - HDMI problems
so long,
Hias
CodeFeb 02 15:29:47 LibreELEC kernel: scsi host0: uasIs STICKY: If you have a Raspberry Pi 4 and are getting bad speeds transferring data to/from USB3.0 SSDs, read this - Raspberry Pi Forums still an issue on RPI4?
Yes, it is, but usually it manifests itself in tons of USB errors, disconnects/reconnects etc in dmesg - which does not seem to be the case here (journal was clean in that respect).
so long,
Hias
Thanks for the log! The only suspicious entries are these:
Feb 02 15:29:49 LibreELEC udevil[707]: The disk contains an unclean file system (0, 1).
Feb 02 15:29:49 LibreELEC udevil[707]: The file system wasn't safely closed on Windows. Fixing.Checking the filesystem of the NTFS drive on Windows might be worth a try - but the log doesn't contain any of the usual USB issues messages so not really sure what's happening there.
so long,
Hias
Before you go ahead and re-format the drive I'd recommend posting the journal after the issue occurred. If there are kernel or ntfs issues they should be logged there.
Run the following command and post the URL:
journalctl -a | pastebinitso long,
Hias
Both vcdbg logs show that the firmware can't read the EDID of the TV, which is quite odd.
Can you test with some other (computer) monitor or TV and check if any of these work with stock RPiOS or LE (without config.txt changes)?
so long,
Hias
Performance problems with 1080p50/60 H264 decoding on LE10 on RPis (2-4) are a known issue. It's being worked on, some improvements are in the queue and should appear in nightlies soon, but it's still not perfect yet.
so long,
Hias
You have configured the display to 4096x2160 - change that to 3840x2160 (UHD mode) then the black bars will disappear.
so long,
Hias
What do you men test with KMS not FKMS.
distroconfig.txt contains
dtoverlay=vc4-kms-v3d,cma-512 but you replaced it with
dtoverlay=vc4-fkms-v3d,cma-512 in config.txt - that's the legacy video driver
so long,
Hias
Something doesn't quite add up - the EDID in the modetest output you posted reports it's a Samsung Syncmaster, running at 1920x1080p60.
So which TV/monitor did you use in that test?
Please also test with KMS, not FKMS, and post logs with stock http://config.txt/distroconfig.txt and the cmdline.txt changes from post #6
so long,
Hias
Can you please run the commands in post #6 RE: Cannot get LE to run on Raspberry PI 4 4GB of RAM on your working and (if possible) on your non-working setups? It would be really interesting to see the logs, they might provide some more insight.
In addition to that also run the following command and post it's output, too.
vcdbg log msg 2>&1 | pastebinitConcerning power supply: note that LE10 won't show the lightning bolt, undervoltage messages will be in dmesg / kernel log though
so long,
Hias
Have you tried a different HDMI cable?
Needing hdmi_force_hotplug indicates the RPi can't detect the presence of the TV - which is often caused by a bad (or not fully wired) cable. RPi firmware will then fall back to 1024x768 video mode.
You need to resolve this issue first, the new driver heavily relies on getting correct info from the TV - the EDID contains info about supported video and audio modes, which is crucial for correct operation.
BTW: if you add "ssh" to the end of cmdline.txt ssh will be activated (it's deactivated by default) then you should be able to connect with putty if it's up.
so long,
Hias
Would these steps also help troubleshoot 9.2 on RPi 4?
No, video configuration completely changed in LE10, using the standard linux methods instead of the legacy RPi specific config.txt method.
This bugreport read as it might be a video driver/mode issue while the issue you linked seems to be something completely different (also you seem to get video output on screen).
so long,
Hias
Please try with a clean installation of the latest LE10 beta, leave config.txt and distroconfig.txt as they are and add the following options to the end of cmdline.txt:
video=HDMI-A-1:1280x720M@60D drm.debug=0x04This should give you working video output at 1280x720.
Then ssh in, run the following commands and post the URLs you got from them:
pastekodi
modetest | pastebinitIf video and audio are working fine you can then drop the drm.debug option and just keep the video option in cmdline.
so long,
Hias