LibreELEC 11 has aarch64 kernel but arm (32bit) userspace so you can't use aarch64 docker containers, you need to use arm (32bit) containers.
LibreELEC 12 (development just started this week) switched RPi4 to aarch64 - but it will take a while until it's out and as it's bleeding new edge right now I wouldn't recommend switching to it unless you are prepared for a bumpy ride, constant breakage and lots of bugs.
so long,
Hias
Well, it went quicker as expected, LE12 addons, including aarch64 are now available from the repo (just do a manual update).
Note that a few retroplayer addons are currently missing for aarch64 (I'll look into that the next days) and inputstream.adaptive is currently missing the aarch64 widevine update - that will follow the next days.
Also note that inputstream helper currently does not support installing widevine libs for aarch64, you have to do it manually for now - eg using the instructions from here:
https://github.com/emilsvennesson…ment-1423115046
so long,
Hias
aarch64 addon build seems to have finished fine, but they still need to be pushed to the server.
Fingers crossed that works fine and will be happening soon.
I won't promise an ETA for that though, we had to deal with a couple of issues setting up CI builds for the new LE11nightlies, adding aarch64 addons and switching RPi4 (and some Allwinner devices) to aarch64 the past few days.
so long,
Hias
It will take a few days until the updated inputstream.adaptive addon has been built and uploaded to our servers, but - yes - we've switched RPi4 to 64bit in our LE12 / master branch and it's working fine.
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 deviceso 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
