If you are using LE10 then don't worry about them. If you are on LE9.2 you shouldn't worry about them because you'll need to update to LE10 eventually
From what you said, it looks like it's been resolved in LE10?But When I updated RPI4 to LE10 (LibreELEC-RPi4.arm-9.95.1.img.gz),the same question comes up:
After learning about this thread, RPI4 on Libreelec 9.1.502 thumbnail/pictures problems
This raises the question of how to check if the values set for GPU_MEM and CMA are valid.
At present, different situations occur for different Docker images.
For Dreamacro/Clash, there is no system restart when “Docker Stop” is executed.
For OpenWrt only container, after execution, the LE system will be restarted; Oofnik/OpenWrt, for example, is a lean version of OpenWrt.
Doesn't seem to have much to do with GPU MEM?
Hi matthuo - search for “widevine 32” in the forum. But a good response from one of the posts is:
“arm" is 64-bit kernel and 32-bit userspace for compatibilty with add-ons that need software widevine (DRM) support, and aarch64 is 64-bit kernel and 64-bit userspace which means no widevine support (as only 32-bit libs are sourceable).
There are a number of community members / builds that build aarch64 user space. But not in the main, so as to support the widevine.
Got it.
For compilation, after selecting ARCH=arm, the kernel will be configured as ARM 32 bits, and then the generated firmware, After query, is running on armv7.
Is there a problem with my choice?
My purpose is to modify network related Settings through menuconfig, so as to make the application available.
After looking at the project files on GitHub and compiling the firmware, it turns out that for RPI4 systems that only support ARM 32-bit, when is the plan to support 64-bit?
Now adjust the solution by ditching the sulinggg/openwrt:rpi2 image in favor of a more lightweight container, Dreamacro/Clash,
After testing, it seems that all the videos are playing normally.
But here comes a new problem, when starting the container, we need to use DHCP to automatically obtain IP for the container. However, LE plug-in Docker does not have MacVLAN DHCP plug-in. How to install this?Or is there a Docker-like plug-in that works?
I had the impression the issue only reported foor recent kernels. But it exist in kernel 4.19 too and therefore in LE 9.2.6.
So I can only wait for the progress of that issue in the next step.
This is a RPI4 kernel issue: LE10 rpi4-4gb oom errors / USB3 disk writes trigger OOM reaper on Pi 4 · Issue #3210 · raspberrypi/linux · GitHub
Edit: My fault., the issue seems only be reported for recent kernels like in LE 9.95 - not in your 9.2.6
GPU_MEM needs to be adjusted through this issue?The current default value is 320, how much should it be adjusted to?512?I can adjust it and try again.
Besides, why did you say it was your fault?
In addition, I used another platform, X905D, with 2G memory. After running Docker in Coreelec, there was no problem
You give little information but I see that using docker with 2 GB of RAM is not the most appropriate, nor do you say the size of your storage that could also cause problems, and finally you do not say the name of the docker image that you are testing.
I can only say that docker works great, I have seven services running permanently and four other services that I start or stop when I need them. Updates to docker images are also done automatically without any problems.
OS: LE 9.2.6
Docker: 9.2.0.127
HW: x86_64 RAM: 8G
Docker image: sulinggg/openwrt:rpi2
There's only 2 gigabytes of memory, but when the container is running, including the Netflix plugin running and playing movies, there's still 1 gigabyte of memory left, and that's the same problem, right?
Description:
After you install the Docker service Add-ones from Libreelec's library and run an OpenWrt image, you get a container as normal.
Then, playing the Netflix plugin, the screen plays step by step, discontinuous, and looks like it's losing frames.
The container is then stopped, LE restarts, and the container cannot be stopped.
OS: LE 9.2.6
Docker: 9.2.0.127
HW: RPi4 RAM: 2G
If you don't start the container, it's fine, Is there something wrong with Docker?
By adjusting the memory size and following the steps of Le Wiki, the compilation passed smoothly. Thanks for your reply!
[BUG]Problems encountered during compilation · Issue #5285 · LibreELEC/LibreELEC.tv · GitHub
not sure that applies here but worth a test
you may need to clean the failing package before rerun
failing package？ Such as....?
[BUG]Problems encountered during compilation · Issue #5285 · LibreELEC/LibreELEC.tv · GitHub
The Clone 9.2.6 project was compiled locally from the Ubuntu 20.04 environment, and the result appears in the following image：
Steps to reproduce the behavior:
Not found log file. If you know which path, please let me know
No
