This issue has now been fixed, can you please give the latest nightly (currently 20210730) from here Index of / a try and report back if it works`?
so long,
Hias
Posts by HiassofT
-
-
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
FYI: This issue has now been fixed, please give the latest nightly (20210730 ATM) a try.
so long,
Hias
-
I've opened a github issue, the same happens in RPiOS KMS: blank screen after TV is brought out of standby on modes that need scrambling · Issue #4486 · raspberrypi/linux · GitHub
The strange thing is I already ran into that issue some time ago, reported it, then it was fixed (and working here with my LG C8) but now it no longer works here either...
so long,
Hias
-
Makes sense, however, how come I don't experience these issues on your build posted in this thread?
We recently enabled 4kp60 by default in nightlies, which needs higher clocks and is probably more sensitive to thermal throttling and FW reducing clock speed to prevent overheating.
You could try changing the display resolution to 1920x1080p60 in settings (in general that's the recommended setting as kodi GUI is 1080 anyways), that uses lower clock speeds and should be affected less.
so long,
Hias
-
Display More
Nightly build of 28-07.
After starting downloads (transmission in docker), video output stops. Samsung tv indicates that resolution is not supported.
Libreelec and docker still seems up & running.
Setup:
RPi4, original power supply, wired internet, external ssd (Samsung SSD T5 500GB), single HDMI cable connected, boot via external USB thumb drive.
Logs:
This is most likely caused by this issue: HDMI screen turns off when sustained high CPU usage on all cores · Issue #1598 · raspberrypi/firmware · GitHub - video output stops working when RPi4 overheats.
Make sure your RPi4 is properly cooled (eg heatsink or fan, if you use a case try without it) and/or avoid high workloads until that's fixed.
so long,
Hias
-
Thanks for testing! I could reproduce that here and have informed the RPi devs.
so long,
Hias
-
Thanks a lot for the logs, I could reproduce the issue now on my Pi 400 and it seems to be a RPi firmware issue.
Can you try updating the firmware files on the FAT partition of the SD card?
Download start4x.elf and fixup4x.dat from here GitHub - Hexxeh/rpi-firmware: Firmware files for the Raspberry Pi , rename them to start.elf and fixup.dat, respectively, copy them over the files on the SD card.
This fixed the issues on my Pi 400, no errors in the log and the (USB) keyboard worked, too.
so long,
Hias
-
Can you please post logs, both from 9.95.5 and 9.97.1?
ssh in and run "pastekodi" or use the log upload function in LE settings, then post the URLs.
https://wiki.libreelec.tv/support/log-files
so long,
Hias
-
Sorry, but this is not going to happen.
Not only would it be a lot of work (we had to rework kernel/initramfs build process in LE10 for kernel 5.4/5.10 which would all need to be backported) but it would also put us in the same boat as RPiOS with kodi 18 - broken HEVC playback.
See these unresolved issues:
Kernel 5.10 - Kodi does not play HEVC videos anymore · Issue #4380 · raspberrypi/linux · GitHub
We released LE10 RC1 last weekend and the final release is around the corner so just use that - like many other RPi4 users already do.
so long,
Hias
-
Can you test with the latest nightly from here Index of / ?
If it doesn't work, reproduce the issue, then ssh in, run "pastekodi" and post the URL. Also please post which TV you are using, and if it's connected directly or via an AVR.
so long,
Hias
-
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
