Nightly builds (24th and 25th) directly gave issues; reverted back to your build and no issues for now.
I'm not proficient in retrieving log files.
If you could point me to a guide I can share them and provide feedback on the nightly builds.
What kind of issues did you have?
Info on how to get log files is in our wiki: https://wiki.libreelec.tv/support/log-files
so long,
Hias
I would like too but am using both HDMI Ports, so until that is fixed in the nightlies it‘s a no-no for me
Fair enough. We also hope that's fixed in the RPi kernel soon.
so long,
Hias
So, with the next RC the mentioned OOM fixes will be included?
Yes. We wouldn't mind though getting some feedback with current nightly testing 
so long,
Hias
Is this change also included in the RC1?
No, it will be in the next release. Please test with nightlies for now.
so long,
Hias
OOM killer issue should be fixed in latest nightly builds - please read the additional info here RE: Cant play 4K MKV files without crashing and test with the nightly.
so long,
Hias
We've switched the kernel to 64bit, the latest nightly build (currently 20210724) from Index of / already includes this change.
Please test with the official nightly builds instead of my older testbuild.
Note: there's a known bug in the kernel ATM, RPi4 won't boot if both HDMI ports are connected (eg if you use an AVR on the second HDMI port) - this should hopefully be fixed soon.
Also the latest builds enable 4kp60 output by default - if your TV supports 4kp60 but your cable isn't up to spec you may get no signal on TV. In that case add hdmi_enable_4kp60=0 to the end of config.txt to disable 4kp60 support
so long,
Hias
Just record the stream and see if you can reproduce the crash with the recorded file, then try to narrow it down to a short (30 seconds or so) snippet and upload that somewhere. This will also remove the PVR addon out of the equation.
Lots of us devs don't use or even have access to a PVR setup at all and we really need a short sample to look into such issues.
so long,
Hias
ghtester that crash log looks like it's something else, never seen that though.
If possible try to reproduce it with a small, local file and then upload that somewhere so we can try to reproduce and analyse the issue as well - PVR addons, corrupted streams etc add lot of points where things go wrong, that's not something we can easily look into.
In general always use the log upload function in LE settings or the "pastekodi" / "pastecrash" scripts as they also include the journal, config.txt and other settings that are important to us, in addition to just the kodi (crash) log. More often than not the kodi (crash) log alone is not enough to kmow what went wrong.
so long,
Hias
ghtester please always post "pastekodi" and/or kodi crash logs if you run into issues - as mentioned in the sticky in this forum - otherwise we have no idea what's going on.
RPi4 has a known issue of the OOM killer kicking in which will be resolved by switching to a 64bit kernel - see here RPi4: switch to 64bit kernel by HiassofT · Pull Request #5507 · LibreELEC/LibreELEC.tv · GitHub - if you had provided a "pastekodi" log I would know if it's the same issue or a different one.
so long,
Hias
With the milhouse build the firmware couldn't read the edid either but it seems it fell back to a safe 640x480 mode and also provided a 1920x1080 mode.
Please test the latest nightly with a known good HDMI cable (eg the one you used with the monitor) and your projector.
If that still doesn't work you can add the following parameters to cmdline.txt as a workaround, that should give you 1920x1080p60 output:
drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:Dso long,
Hias
MikeKL thanks!
I could reproduce the issue, the new kernel hangs during boot if two HDMI devices are connected (checked that here with two monitors).
It's a bug in the kernel, the same thing happens on RPi OS with the latest rpi-update kernel. I've opened a github issue here RPi4/kms: boot hangs if two monitors are connected · Issue #4465 · raspberrypi/linux · GitHub
Until that's resolved stick to the previous nightly build or leave the second HDMI unconnected.
so long,
Hias
samba working but ssh not is odd, nothing changed in that area. Are you sure it's enabled and worked with the previous build?
I'd recommend rolling back to the previous build, connect both the TV and the AVR and then grab the edid of both devices, then I'll see if I can reproduce the issue here.
run
cat /sys/class/drm/card0-HDMI-A-1/edid > edid-tv.bin
cat /sys/class/drm/card0-HDMI-A-2/edid > edid-avr.binand then upload the edid-tv.bin and edid-avr.bin files (put them into a zip so the forum software allows attaching it).
EDIT: ah, and please post pastekodi and modetest from the previous build, too.
so long,
Hias
Looks like someone already started working on a DRM grabber Raspberry Pi 4 with Libreelec v19 / Kodi Matrix, no grabber is working · Issue #983 · hyperion-project/hyperion.ng · GitHub - progress seems to have stalled a bit though
so long,
Hias
The latest nightly enables 4kp60 by default in distroconfig.txt. Please try with the stock distroconfig, wait a few minutes after powerup, then you should be able to ssh in.
Then run "pastekodi" and "modetest | pastebinit" and post the URLs, this should help us find out what went wrong.
Testing with 4kp60 here was fine but if something went wrong in the video driver it can hang for a while so bootup can take a bit.
Instead of changing distroconfig.txt you can also just add "hdmi_enable_4kp60=0" to the end of config.txt - this will survive further updates.
so long,
Hias
Hopefully the next couple of days.
It's already in internal testing, RPi4 worked fine (I tested it a couple of days ago) and IIRC the other platforms were fine, too.
so long,
Hias
You have to replace start.elf and fixup.dat on the FAT partition - see here RE: LibreELEC (Leia) 9.2.5
Note: last time I tested that was more than half a year ago and you might have to use an older firmware version (from 6-9 months ago) as it's not guaranteed that newer firmwares work with older kernels (or vice versa).
so long,
Hias
LE 9.2 doesn't support the RPi 400 as it's firmware is too old. You probably manually replaced the firmware files on 9.2.6 and those got changed back to the stock (i.e. too old) LE ones when updating to 9.2.7/8.
You have to replace firmware files again, or switch to LE 10 (which is the better solution as that will also give you working bluetooth and wifi).
so long,
Hias
4kp60 isn't available in 9.95.5, it will be available in the next release though.
so long,
Hias