RPi0-3 don't have any flashable firmware (like RPi4 does for the bootloader) so there's nothing you can or need to update.
Firmware files on the boot partition are updated automatically with LE updates.
so long,
Hias
RPi0-3 don't have any flashable firmware (like RPi4 does for the bootloader) so there's nothing you can or need to update.
Firmware files on the boot partition are updated automatically with LE updates.
so long,
Hias
Keep gpu_mem as it is (76 MB), in addition to that you need to add dtoverlay=cma,cma-256 (or cma.-192) to get it booting.
Note though that, like on LE10, kodi will then often crash when quickly browsing through the library as it needs a lot of (CMA) memory for pictures.
so long,
Hias
Your NTFS drive / partition wasn't cleanly unmounted and/or as errors - you need to connect that drive to a windows PC and fix the errors as mentioned before
Mar 09 11:50:52.158299 LibreELEC kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
...
Mar 09 11:50:52.158967 LibreELEC udevil[1856]: mount: mounting /dev/sdb1 on /media/Slim failed: Invalid argument
Mar 09 11:50:52.160004 LibreELEC udevil[1852]: mount: mounting /dev/sdb1 on /media/Slim failed: No such device
so long,
Hias
The screenshot in your first post is showing that your PiHole received a DNS A (address) request for "synologynas" and responded with NXDOMAIN (no address) - so your PiHole doesn't know anything about a "synologynas" host in your LAN.
You may want to add your local domain name (eg ".lan") to the source hostname (eg "synologynas.lan") and make sure PiHole resolves the name to the IP correctly.
so long,
Hias
Just ssh in and run "getedid create" - everything you need for RPi is in the image.
so long,
Hias
FritzOS 7.50, which is currently being rolled out, adds support for wireguard
so long,
Hias
Is there a list of addons that require the Chrome browser to function somewhere?
None of the addons depend on Chrome.
so long,
Hias
Also drop the overclock settings you added to config.txt and check if your RPi works fine without them.
Overclocking abilities are very specific to each individual devices, some can't be overclocked at all while others will happily run at 2GHz - there's no guarantee for anything so take every guide that tells you that setting X and Y work fine with a huge grain of salt - at best take those guides as a rough starting point while for checking which settings work with your particular device.
If you overclocked your RPi and something doesn't work right the first thing to suspect is always that the overclocking parameters you used don't work for your device - so remove them before digging further.
so long,
Hias
A 100MB log file is definitely not normal (unless you enabled some component logging bits, which aren't needed here - normal debug logging will do fine).
I suggest you do a clean install of the latest nightly on a separate SD card or USB stick. Only setup display resolution and whitelist, and play the file with that. If it fails, post the log.
so long,
Hias
hdmi_force_hotplug (and most other hdmi_ settings in config.txt) ceased to have any effect since LE10 - vc4.force_hotplug in cmdline.txt is the replacement for it.
so long,
Hias
Use vc4.force_hotplug=1 - inval_delay and cec_debug were temporary test settings that have been removed and replaced with force_hotplug.
so long,
Hias
Installed last nightly build and same error happened
then please post a crashlog from it
so long,
Hias
See the info in our wiki:
https://wiki.libreelec.tv/support/log-files
https://wiki.libreelec.tv/support/update
if you run "pastecrash -c > my-log-file" you can save the crash log to a file, copy it over to your PC and simply attach it here to a post.
so long,
Hias
Maybe someone know what the burst of kodi.sh[864]: Failed to import fence to syncobj: -1 means.
That seems to come from mesa https://gitlab.freedesktop.org/mesa/mesa/-/bl…v3d_fence.c#L92 but I've never seen that issue here so no idea. Kodi crashlog might tell us more.
so long,
Hias
Just use the "upload crash log" option in LE settings, immediately after kodi crashed and restarted or ssh in, run "pastecrash" and post the URL you got from it.
BTW: please test with the latest LE11 nightly from here, it contains some additional video decoder fixes.
https://test.libreelec.tv/11.0/RPi/RPi4/
so long,
Hias
Good to hear LE11 is running fine on your setup, too!
Skipped frames with GUI overlays is a known kodi issue, unfortunately no solution for that yet.
The current LE11 nightlies should be very stable, I'm running them as a daily driver here. LE11 final should be out in the next couple of weeks and so far I'm not aware of any major issues on RPi.
So it should be safe to use it until LE11 final is released.
so long,
Hias
Thanks for the samples! Both of them play fine on LE11 and the scroller/ticker is smooth, too.
so long,
Hias
We can't tell more without a sample - I asked for it in post #2 - so you'll have to test yourself if it works with LE11 nightlies.
so long,
Hias