Posts by aptalca


    There's something weird going on with my A95X box with this latest update!
    It goes to sleep even though the power saving is turned off, then when you switch it back on, the blue LED comes on but the unit is 'dead', no response to ping or any HDMI output. I need to pull the power and plug it back in!?
    Also does anyone use 'docker'? Not working....
    Thanks!


    Docker works here fine. I even have the plex media server running as a container

    Yeah I have two first gen fire sticks and they are pretty laggy with kodi. I use them mainly for Netflix and Amazon video with occasional plex.


    I also have a second gen fire tv and that one works great with kodi even with a demanding skin


    Hi all!


    I got myself an android 6 box, nexbox a95x 8gb storage and 2g ram. I tried using the tutorial and downloaded the correct image and used rufus to get it onto a USB drive. I couldn't get it to the libreelec start screen. Any easy way to boot it up with this particular box? I don't have a button to toothpick either, right?


    Help would be appreciated. Thanks in advance


    I have the same box (but with 16GB rom)


    I used the libreelec usb creator tool.


    The toothpick button is inside the av port, at the base of it ;)


    Nevermind this report. Just realized 3 LE boxes all had a segfault at the same time. Only one is amlogic. I'm investigating it.

    Hi kszaq,


    Thanks for these builds. They work great on my Nexbox A95x S905x box. Although, I did just notice an issue.


    I leave my box on 24/7. Yesterday, I noticed that kodi service (just the service not the box) has been restarting itself every once in a while (while idle, with the screen off). Yesterday, it happened at 5:41pm and again at 11:45pm. Memory usage is very low at around 28% (2GB version).


    Here's the crashlog: GBZW
    I do have a couple of docker containers running in the background (they have been uninterrupted through these kodi restarts). Not many other addons otherwise and the box is mostly a fresh build (got it a few days ago). Is there anything in the crashlog that suggests an issue?


    In the meantime, I'll keep monitoring and will provide a debug log later.


    Thanks


    EDIT: Journaltcl gave me this for the time of the last crash:


    Just set up my s905x box and installed the plex docker addon. I am able to play videos from plex on the same machine using the official plex addon for kodi.

    Is your Box is a Nexbox A95x S905 ??
    If it is , That is Normal Behaviour using LE and you have to live with it.


    I'm confused, I have the Nexbox A95x, which is S905X. Is there a different S905 version?


    Mine turns on and off with the remote and I didn't put in a custom remote.conf, just the default.


    For the dtb, there are only two files for S905X, one for 1GB and another for 2GB


    When you go to the libreelec website, under the download section, select the one named generic.


    Make sure your nuc has vt-d as it is required for gpu passthrough.


    I've been running LE in a VM with an nvidia gpu passed through in kvm/qemu (vmware should also work). I believe there is a way to passthrough the on-board intel gpu to a VM (there is in qemu, not sure about vmware), which means the host OS and other VMs would have to run headless (since you can't put in discrete gpus in a nuc?!?)


    I would really recommend that you build a custom pc where you can add additional gpus and put in a cheap nvidia like the GT710 for host and LE can use the onboard intel gpu since that one supports 10bit h265 via hardware in linux. The nuc is not really meant to be a server

    Duly noted, thanks.


    One last thing. When the docker starts, if I go to my System Info window, the IP address of the LE box shows as 172.17.0.1


    If I issue docker stop and stop all containers, the IP address is restored to the correct one. And upon restart of docker reverts back to 172.17.0.1. Any way to fix this? When I was manually running docker I think I was able to solve this by appending "--net=host" to the docker start command.


    It's just a visual bug. Kodi retrieves all network interfaces from os and displays the first ip from that list in the gui. When docker is running, there are multiple network interfaces and the first ip happens to be the one for docker's internal virtual interface ip.


    Don't worry, it doesn't actually change kodi's ip address.


    In fact, I have a fire tv running kodi and it shows a weird ip that is not even in my lan ip range, within kodi. But I can connect to it through the fire tv's ip. The one shown in kodi must be some internal virtual lan used by the fire tv.


    These are the display settings of my laptop


    My goal is to record a tutorial of LibreElec. An other solution is to buy a hdmi cloner box or something. But i would realy like it to run in virtualbox. Can I use TeamViewer? Or other remote software?


    Wait, are you still trying it in VirtualBox? Please read through the thread. It's been stated multiple times that it doesn't work in VirtualBox. You need to use vmware


    Thank you for your awesome help!


    Some guidance with portainer please! So I installed it, enter the web UI from my windows PC, create a password, log in. After that in the connection page I have to enter remote connection, right? But here if I enter the IP address of my machine running LE/ portainer docker what happens if the IP address changes after reboots? And after connecting it took me to a dashboard where my running plex container was not listed. Everything was 0. Anything needed to be configured under networks etc? If there is some guide, please do point to it.


    No, you have to select the local option. Even though you are connecting remotely, portainer is running on the same machine docker service is running on, so it needs to connect to the local service.


    Once you do that, all containers and images should show up.


    Just a word of caution, don't use portainer to manage linuxserver addon installed containers, because the addons have their built in start, stop mechanisms through systemd and stopping and starting them through portainer will cause issues.


    You should use portainer to only manage containers you create through portainer itself.


    Glad to hear it worked. Unfortunately Linuxserver does not have a docker image for lms, so no addon for it.


    But I believe there are some images on docker hub made by others. You can install them through portainer


    When you reboot, it tries to update the docker image first. If there is no update, it starts right away. But if there's an update, it will download and extract it first, and then start the container.


    Plex docker image is fairly large and on wifi download may take longer, and with low powered devices the extraction may add more time.


    Portainer does the same thing too, but its image is tiny so the delay is not noticeable.