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
Try adding video=HDMI-A-1:1920x720M@60
so long,
Hias
The log shows that the video driver read an invalid edid from your projector and therefore refused to output via HDMI.
Did you have to use any hdmi_... config.txt settings with the older milhouse build?
Can you run "pastekodi" on the milhouse build as well and also run "tvservice -d edid.bin" on it and upload the resulting edid.bin file?
so long,
Hias
Can you please test with the latest LE10 beta version? LE 9.2 contains a rather old kernel and firmware.
so long,
Hias
Doesn't anyone have an idea, not even the developer?
Ah, this seems to be a quirk in the firmware handling/parsing of dt parameters - the dtoverlay scope of vc3-kms-v3d, which is loaded in distroconfig.txt on RPi2/3, seems to persist after the include in config.txt so the audio parameter applies to the overlay.
The solution is quite simple, clear the overlay scope with "dtoverlay=" or move the dtparam=audio=on statement up, before the include distroconfig.txt.
eg
dtoverlay=
dtparam=audio=on
audio_pwm_mode=1so long,
Hias
One thing I did notice is that during the boot the red LED on the Pi was coming on and off which I havent seen before. It normally stays on permantently after power on.
The red LED must be permanently on. If it's going off it means you have a power supply problem which you need to solve first - if the power isn't stable the RPi won't run stable and it could well be that the odd crashes you are seeing are caused by that.
Disconnect all USB peripherals and everything else you might have attached (fans, HATs etc) and make sure everything's working fine. I also strongly recommend using the official RPi power supply as that's known to work just fine.
so long,
Hias
Can you connect with ssh when connected to the projector? If yes run "pastekodi" and "modetest | pastebinit" and post the URLs.
There's currently a bug in the video driver, if the HDMI cable isn't plugged in or the driver doesn't detect a display then RPi2/3 lock up during boot - this can also be caused by a broken (or not fully wired) HDMI cable, so testing with a different HDMI cable would be worth a try, too.
so long,
Hias
