We have a history of previous LE11 (nightly test ) builds here:
https://test.libreelec.tv/11.0/RPi/RPi2/
You could check through them, finding out with which build the issue started might give some clues.
so long,
Hias
We have a history of previous LE11 (nightly test ) builds here:
https://test.libreelec.tv/11.0/RPi/RPi2/
You could check through them, finding out with which build the issue started might give some clues.
so long,
Hias
frakkin64 no, we don't publish stats, they are rather boring anyways as they didn't change too much over the years (total RPi userbase always was in the 70-80% ballpark, only a few shifts between RPi1, 2/3, 4 over time).
And, yes, forum posts are only about issues, the users without problems are mainly silent - except for some rare "thank you"s here and there.
OFC there's still a significant amount of RPi2/3 users on LE9 (because of HEVC) and the absolute number of RPi2/3 installations is still very large.
And we also see still lots of other devices on older LE versions, most likely because they still "work just fine" - so no need to upgrade.
Chip crisis prevented lots of users from upgrading to RPi4, this might change in the next half year when RPi4 production (hopefully) ramps up and shops can stock them again. So I expect to see RPi2 (which is already down to about 5%) and RPi3 installations to decline in numbers and RPi4 to increase.
so long,
Hias
I don't know what the installs look like with LE11, but the impression from the release notes is that most RPi3 users may not be upgrading due to the loss of HEVC accelerated decoding.
The number of RPi2/3 users on LE10 and LE11 is actually quite high, during the last year the overall userbase distribution has been quite stable at roughly 40% RPi4, 30% RPi2/3, 20% Generic/x86, 10% everything else.
LE11 is quite new which means we have roughly 5 times as many LE10 users as LE11 users, but still this means quite a lot of LE11 RPi2/3 installations.
I'd also recommend testing with RPiOS and current "rpi-update" kernel, this will be the same as current LE11 nightly build and if there's an actual issue with the mmc driver (which is not caused by wearing out SD card, overclock, undervoltage etc) then RPi engineers would be the ones who could analyze and fix the issue - so posting on RPi forums would be best.
Personally I've never had such an issue on RPi2/3 (mainly using Sandisk Extreme and Extreme Pro 32GB SD cards here).
so long,
Hias
Please test with the latest LE11 nightly build (20230312) from here:
https://test.libreelec.tv/11.0/
They include a kodi update to 20.1-Nexus with several HD audio fixes.
Beware though that wifi may be broken, that's a known issue that will be fixed in future nighlies - and the upcoming LE 11.0.1 release.
so long,
Hias
Enable debug logging and use "pastekodi" to provide logs - the stuff you uploaded to google is inaccessible.
so long,
Hias
Thanks a lot for reporting back and glad it's working now!
You can simply use the image for now until we release LE 11.0.1. Of course we'll include the fix in future versions and I also created a pull request on the RPi linux kernel as it's affecting RPiOS as well
so long,
Hias
Can you please test with a clean install of this build:
and add "ssh video=HDMI-A-1:1280x1024D drm.debug=0x04" to cmdline.txt
I noticed a bug in the RPi video driver which prevented working around EDID issues (like you have) with video=... which I've fixed in the above image.
If it works please report back (and then you can drop the drm.debug=0x04 option in cmdline.txt), if it does not please run "pastekodi" and post the URL.
so long,
Hias
Re-encode the files on your PC and apply HDR_>SDR tonemapping. There's no other way if you are playing the videos on RPi4.
so long,
Hias
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 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