Posts by perpis
-
-
Hello again,
I tried with a different video (lower quality) and it keeps showing the loading icon in loop. I have seen this error in the log:
CDVDVideoCodecDRMPRIME::Open - using decoder V4L2 mem2mem MPEG4 decoder wrapper
CDVDVideoCodecDRMPRIME::AddData - send packet failed: Invalid argument (-22)Maybe some ffmpeg config was off when compiling?
-
Hello, sorry for the late answer, I couldn't test it before. I just installed it and the first test looks fine, the same video file is not jumping for now. I will test it more, but I think that the problem is solved. Thank you very much to both!!
-
-
I was using libreelec 8 and I was able to play videos smoothly. I have changed to a nightly 13 and some videos are playing with jumps and even showing the buffering circle. Everything is the same (same hardware (cubox), same connection, same videos), the only difference is the change in libreelec version.
One of the videos failing has this info: mkv H264 1920x1080 3278447 bps
I have hardware acceleration on, but it shows SW when playing the video.
Does anyone have any idea why this is happening?
Thank you!
-
You are totally right. I thought this nightly was the last one working for cubox but it's not the case. I just updated libreelec and the repo works now and the GUI works smoother!
Thank you!
-
Yes, sorry, it is 13.0 (Linux 6.15.1). Kodi 22.0-ALPHA1 (21.90.700).
My PC is too old and it would be a real pain trying to compile on my own. I understand that both options you propose imply compilation, am I right?
For some add-ons I am able to download and install from zip, but for others, it is really hard to find the proper compatible version (e.g. retro arch, vfs). Is there any mirror in which I could find compatible add-ons?
Thank you
-
I have installed in my cubox a nightly version (nightly 20250610 a34f2d0) and trying to open libbreelec add-ons repository I get this error: could not connect to repository
Does someone know how I could fix it?
Thank you in advance!
-
I'm not very familiar with the docker service on libreelec, but I just realized you're still on LE8. Why not upgrade to 9?
Just because I can't. I have an i.MX6 uC and there is no available image for LE9 (hoping that it will be available one day here). And if I try to upgrade from LE itself, nothing happens.
-
Sorry to write again, does the log in the previous message give any hint to anyone?
Any help would be appreciated.
Thank you!
-
systemctl status docker.service
I get this:
Code
Display Moreservice.system.docker.service - Docker Application Container Engine Loaded: loaded (/storage/.kodi/addons/service.system.docker/system.d/service.system.docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-12-31 20:08:57 CET; 22h ago Docs: https://docs.docker.com Process: 472 ExecStart=/storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd --log-driver=journald --group=root● service.system.docker.service - Docker Application Container Engine Loaded: loaded (/storage/.kodi/addons/service.system.docker/system.d/service.system.docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-12-31 20:08:57 CET; 22h ago Docs: https://docs.docker.com Process: 472 ExecStart=/storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd --log-driver=journald --group=root $DOCKER_DAEMON_OPTS $DOCKER_STORAGE_OPTS (code=exited, status=1/FAILURE) Process: 437 ExecStartPre=/storage/.kodi/addons/service.system.docker/bin/docker-config (code=exited, status=0/SUCCESS) Main PID: 472 (code=exited, status=1/FAILURE) Dec 31 20:08:54 LibreELEC systemd[1]: Starting Docker Application Container Engine... Dec 31 20:08:56 LibreELEC dockerd[472]: time="2019-12-31T20:08:56.343281901+01:00" level=info msg="libcontainerd: new containerd process, pid: 710" Dec 31 20:08:57 LibreELEC dockerd[472]: time="2019-12-31T20:08:57.514205339+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded." Dec 31 20:08:57 LibreELEC dockerd[472]: Error starting daemon: error initializing graphdriver: driver not supported Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Main process exited, code=exited, status=1/FAILURE Dec 31 20:08:57 LibreELEC systemd[1]: Failed to start Docker Application Container Engine. Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Unit entered failed state. Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Failed with result 'exit-code'. standard inputservice.system.docker.service - Docker Application Container Engine Loaded: loaded (/storage/.kodi/addons/service.system.docker/system.d/service.system.docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-12-31 20:08:57 CET; 22h ago Docs: https://docs.docker.com Process: 472 ExecStart=/storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd --log-driver=journald --group=root● service.system.docker.service - Docker Application Container Engine Loaded: loaded (/storage/.kodi/addons/service.system.docker/system.d/service.system.docker.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-12-31 20:08:57 CET; 22h ago Docs: https://docs.docker.com Process: 472 ExecStart=/storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd --log-driver=journald --group=root $DOCKER_DAEMON_OPTS $DOCKER_STORAGE_OPTS (code=exited, status=1/FAILURE) Process: 437 ExecStartPre=/storage/.kodi/addons/service.system.docker/bin/docker-config (code=exited, status=0/SUCCESS) Main PID: 472 (code=exited, status=1/FAILURE) Dec 31 20:08:54 LibreELEC systemd[1]: Starting Docker Application Container Engine... Dec 31 20:08:56 LibreELEC dockerd[472]: time="2019-12-31T20:08:56.343281901+01:00" level=info msg="libcontainerd: new containerd process, pid: 710" Dec 31 20:08:57 LibreELEC dockerd[472]: time="2019-12-31T20:08:57.514205339+01:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded." Dec 31 20:08:57 LibreELEC dockerd[472]: Error starting daemon: error initializing graphdriver: driver not supported Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Main process exited, code=exited, status=1/FAILURE Dec 31 20:08:57 LibreELEC systemd[1]: Failed to start Docker Application Container Engine. Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Unit entered failed state. Dec 31 20:08:57 LibreELEC systemd[1]: service.system.docker.service: Failed with result 'exit-code'. standard input -
Don't try to manually start dockerd service. Reboot your device and do "docker ps -a". Post the result here.
Thank you for your reply. Yes, sorry, I first tried that command and the output was this:
CodeLibreELEC:~ # docker ps -a Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?That's why I tried further commands.
-
By ssh'ing in. If you're on Windows, I recommend putty. Ssh settings are in the libreelec settings
I did not realised I could SSH. I have tried and it seems it does not even load the docker:
Code
Display MoreLibreELEC:~ # dockerd INFO[0000] libcontainerd: new containerd process, pid: 14539 WARN[0000] containerd: low RLIMIT_NOFILE changing to max current=1024 max=4096 ERRO[0001] Failed to built-in GetDriver graph aufs /storage/.kodi/userdata/addon _data/service.system.docker/docker ERRO[0001] Failed to built-in GetDriver graph btrfs /storage/.kodi/userdata/addo n_data/service.system.docker/docker ERRO[0001] 'overlay' not found as a supported filesystem on this host. Please en sure kernel is new enough and has overlay support loaded. ERRO[0001] 'overlay' not found as a supported filesystem on this host. Please en sure kernel is new enough and has overlay support loaded. ERRO[0001] Failed to built-in GetDriver graph devicemapper /storage/.kodi/userda ta/addon_data/service.system.docker/docker INFO[0001] Graph migration to content-addressability took 0.00 seconds WARN[0001] Your kernel does not support cgroup memory limit WARN[0001] Unable to find cpu cgroup in mounts WARN[0001] Unable to find blkio cgroup in mounts WARN[0001] Unable to find cpuset cgroup in mounts WARN[0001] mountpoint for pids not found Error starting daemon: Devices cgroup isn't mountedAny further hint would be appreciated. Thank you!
PS: Kernel version is 3.14.79 if this helps.
-
Thank you, but where am I supposed to type in commands on Kodi? Is there any command line add-on for this?
-
See here for troubleshooting steps: LinuxServer.io docker addons and general docker info
Thank you for your reply. Yes, I read that page yesterday before asking here, but unfortunately I did not get any hint to solve my problem. It is not clear to me whether the docker image is running (from that link it seems it is just running while it is enabled). And if it is like that, then I still don't know how to access to the GUI with the browser.
-
If it's armv7, then the linuxserver one should work. But keep in mind that it first needs to install the docker service addon, which may take a little while.
Thank you for your reply. After some tries it did install with linuxserver. However, I am not able to reach the GUI interface, I get the following error:
ERR_CONNECTION_REFUSED
I do not even know whether it is properly running or not. How could I check it out make it work? Any hint?
Thank you again!
-
Hello,
I am a little confused with the loads of info in this thread. I am not sure whether it is possible to install the Plex media server on my setup:
Cuboxtv (iMX6)
LibreELEC 8.0.2
Kodi 17.3
The links from hugepants from the first post are broken links, the repo from tnds82 throws an error when trying to install it ("the dependency on ... could not be satisfied") and the LinuxServer.io repo shows 0% all the time when trying to install it. I do not know which path I can follow to get the PMS working.
Any help would be appreciated, thank you!
-
Thank you for the feedback. I hope the progress continues and finally a new release is out!