Posts by matthuo

  • About the error when generating the image for RPi4

    The image error is generated below, it is due to the lack of dtb file, is it because ARCH=arm64 is selected in the menuconfig configuration, which causes this error?



    Successful build, creating image...

    Parallel mksquashfs: Using 2 processors

    Creating 4.0 filesystem on /home/matt/LibreELEC.tv/target/LibreELEC-RPi4.arm-10.0-devel-20210413080833-c5d7822.system, block size 1048576.

    [==============================================================================================================================================================================================================/] 7327/7327 100%


    Exportable Squashfs 4.0 filesystem, zstd compressed, data block size 1048576

    compressed data, compressed metadata, compressed fragments,

    no xattrs, compressed ids

    duplicates are removed

    Filesystem size 111889.52 Kbytes (109.27 Mbytes)

    37.11% of uncompressed filesystem size (301542.07 Kbytes)

    Inode table size 78152 bytes (76.32 Kbytes)

    25.31% of uncompressed inode table size (308790 bytes)

    Directory table size 91863 bytes (89.71 Kbytes)

    41.49% of uncompressed directory table size (221406 bytes)

    Number of duplicate files found 172

    Number of inodes 9339

    Number of files 7231

    Number of fragments 194

    Number of symbolic links 721

    Number of device nodes 0

    Number of fifo nodes 0

    Number of socket nodes 0

    Number of directories 1387

    Number of ids (unique uids + gids) 2

    Number of uids 1

    root (0)

    Number of gids 2

    root (0)

    unknown (81)

    Running /home/matt/LibreELEC.tv/packages/tools/bcm2835-bootloader/release

    cp: cannot stat '/home/matt/LibreELEC.tv/build.LibreELEC-RPi4.arm-10.0-devel/image/system/usr/share/bootloader/*.dtb': No such file or directory

    *********** FAILED COMMAND ***********

    . ${FOUND_PATH}

    **************************************

    make: *** [Makefile:12：image] Error1

  • About GPU_MEM on RPi4

    Quote from HiassofT

    If you run LE 10 then leave gpu_mem at the default (76MB). It's only needed for H.264 hardware decoding. Setting it higher just wastes memory.


    so long,


    Hias

    Does LE10 dynamically adjust GPU_MEM?Not sure if the video plugin will be used on the GPU (according to the Netflix plugin, it probably won't), so I hope it can be adjusted dynamically.

    In addition, stopping a docker container will cause a LE10 restart. Does this have anything to do with the fact that the GPU_MEM setting is still high?For now, though, the default is still 76.

  • About GPU_MEM on RPi4

    Quote from lrusak

    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:

    Post
    RE: Exception after starting a container via Docker
    (Quote from matthuo)

    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.
    mglae

  • Exception after starting a container via Docker

    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?

  • About ARM64 On RPi4

    Quote from heitbaum

    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.

  • About ARM64 On RPi4

    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?

  • Exception after starting a container via Docker

    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?

  • Exception after starting a container via Docker

    Quote from mglae

    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?

  • Exception after starting a container via Docker

    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?