busfahrer303 are you running the latest firmware on your Onkyo AVR? Looks like latest one is from January this year
Might also be worth checking the various settings of the AVR and/or searching the net for similar problems - issues with buggy AVR firmwares are not too uncommon...
so long,
Hias
busfahrer303 please provide some more infos about your setup:
Are you connecting the RPi directly to a TV or via an AVR?
Which TV and/or AVR models are you using?
If you have an AVR in the chain, does it work if you connect the RPi directly to the TV?
It sounds like scrambling re-negotiation, which is needed for 4kp50/60, isn't quite working but I haven't spotted any obvious errors in the logs yet.
so long,
Hias
FYI the patch in the testbuild 3 posts above is also included in LE10.0.2 https://github.com/LibreELEC/Libr…nvalidate.patch
But there's really not much more we can do if no one bothers to test the testbuilds we provide and post some feedback...
so long,
Hias
You'll need it for HEVC. RPi4 has enough CPU power to decode H264 files in software, but not so much for full HD or 4k HEVC ones.
so long,
Hias
The reserved space is so that on normal linux installations, where the harddrive is used as a system disk, there's always some space purely reserved for system usage (logs, temporary files, other stuff the system needs to operate).
On non-system partitions/drives it's generally fine to set that to zero.
And on LE it's even more of a cosmetic issue as (almost) everything runs as root (with system privileges) anyways.
so long,
Hias
Cabling issues are actually quite common 
Nice to hear it's working now.
Skins are all there, you probably just need to refresh repos - push left to open the side pane and choose check for updates.
so long,
Hias
GORBULAN your log indeed shows the TV is constantly connecting and disconnecting. I'd recommend checking your cabling, a bad cable or connection (it could also be one of the HDMI connectors) can cause such issues.
You could try to work around it by installing a permanent EDID and video setting (in this case the TV's hotplug signal will be ignored) by running "getedid create" - but that'll be a bit tricky as you'd need to catch the right moment when the TV signals connected so it will probably take a few tries until that script completes successfully without errors.
so long,
Hias
hpmueller1971 I haven't seen this on LE 10.0.2.
Please test with LE10.0.2 and after the issue occurred ssh in and check if the RPi had throttled - insufficient power supply could cause such issues.
Run "vcgencmd get_throttled", it should show 0x0.
If it's 0x0 you could try applying a small over voltage, add over_voltage=2 to config.txt and see if that helps.
so long,
Hias
You've added drm.debug as a separate line in cmdline.txt - that doesn't work, eveything has to be in a single line. Please fix that and post a new log.
so long,
Hias
busfahrer303 first add "drm.debug=0x04" to the end of /flash/cmdline.txt (after "quiet", all on the same line) to get some more debug info, then reboot and reproduce the issue.
After that ssh in, run "pastekodi" and post the URL you got.
so long,
Hias
GORBULAN I'd recommend you add "drm.debug=0x04" to the end of /flash/cmdline.txt (after "quiet", all on the same line) first, this will provide some more debug info about video stuff.
Then reboot, ssh in and run "pastekodi" - and post the URL you got.
so long,
Hias
Taking a screenshot of the video plane isn't implemented in kodi yet - see https://github.com/xbmc/xbmc/pull/18741
I recommend leaving the render method set to "direct to plane", it has higher performance and on RPi4 it's needed for HEVC (and 10bit) videos.
so long,
Hias
Thanks for the report and the sample, I could reproduce the issue and have pinged RPi devs.
It seems to be an issue with HW video decoding, when disabling that (in settings->player) the sample plays fine - you could use that as a temporary workaround.
so long,
Hias
On the RPi 400 you have to use the HDMI connector next to the SD card slot.
so long,
Hias
Be very, very careful if you are not familiar with it - if you do something wrong you could easily format the wrong drive, wiping all the data. So make sure you only connect this one drive and not others.
First run "mount" to find the device node - it'll typically be /dev/sda1 or /dev/sdb1.
Then unmount the partition with "umount /dev/sda1" - use the device node you found out above in this and the following commands.
To make sure this worked, run "mount" again, the partition should no longer be listed.
If the partition was already formatted as ext4 you can simply run tune2fs to change the reserved block count - eg "tune2fs -m 0 /dev/sda1".
If you want to format it as ext4 run "mkfs.ext4 -m 0 -L MyVolumeLabel /dev/sda1" - Change MyVolumeLabel to the label you'd like to give the partition, it'll then show up with this name in the partition list in kodi.
Now reboot LE and the freshly formatted drive should show up in kodi.
BTW: if you run tune2fs with the "-l" (lower case "L") option it'll show details, including the label and reserved block count of the given partition. eg "tune2fs -l /dev/sda1". This won't alter the partition and it's safe to run it even if the partition is mounted.
so long,
Hias
mkfs.ext4 is present in LE.
You can use tune2fs (also present in LE) with the "-m 0" option to change the root reserved space to 0% - make sure you unmount the drive before doing that.
so long,
Hias
I have this hat
https://www.msldigital.com/collections/al…=30268836610182
which is a power switch for the raspberry pi.
Ah, this is important information. I highly suspect your poweroff/reboot issues are related to that hat - haven't seen anything similar on plain RPi4 installations (reboot, poweroff and then powercycling and gpio-shutdown overlay with a button all work fine).
so long,
Hias
Something went wrong, you should not have HDMI-A-2 in cmdline.txt unless you actually plugged something into the second HDMI port.
Remove all hdmi entries in config.txt (also the pixel encoding, it doesn't have any effect), ssh in and run "getedid delete", then reboot.
After that run "getedid create" again, it should report successful install of HDMI-A-1 edid and cmdline.txt should have drm.edid_firmware and video settings for HDMI-A-1 (but not HDMI-A-2):
LibreELEC:~ # getedid create
successfully installed edid override for HDMI-A-1
LibreELEC:~ # cat /flash/cmdline.txt
boot=UUID=2907-5719 disk=UUID=cf0bbd10-802c-41cf-bb8b-3bbe78425239 console=serial0,115200 earlycon=pl011,mmio32,0xfe201000 systemd.debug_shell drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:DIf LE doesn't come up after reboot or power off that's most likely a different issue, not related to video. You should at least have network (ping / ssh).
The logfile shows you installed an autostart.sh, what are you running from there? Might be worth removing that for testing - trying with a clean LE10.0.2 install on a separate SD card might also be worth a try.
so long,
Hias