Also responded on github. That container is for x86 and thus won't run on arm. I think I have somewhere created a test/dev version that could be converted to an arm version relatively easily. I'll look into it and will let you know.
For reference, linuxserver.io group (which I am a member of) release separate containers for x86_64, arm and aarch64
Here is the new install guide thread: showthread.php?tid=5556
I had a similar issue where the script wasn't finding the edid in the logs.
I ended up following the manual steps from the wiki and rebooted after turning logging on and finally the edid was included in the log (I tried a bunch of things but I believe the restart was what made it work)
You can install portainer from the linuxserver repo under libreelec repo. With portainer, you can start a docker container. There are a few options out there for handbrake including this one with a full gui: handbrake
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
Not that I'm aware of. I believe those things are pretty locked down. You can install kodi for Android though (sideload)
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 
Likely your docker addons. You must have those folders set in their settings (some are by default)
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:
CodeFeb 14 23:45:26 Nexbox kernel: kodi.bin[28872]: unhandled level 1 translation fault (11) at 0x66343765, esr 0x92000005 Feb 14 23:45:26 Nexbox kernel: pgd = ffffffc04ca66000 Feb 14 23:45:26 Nexbox kernel: [66343765] *pgd=0000000000000000 Feb 14 23:45:26 Nexbox kernel: Feb 14 23:45:26 Nexbox kernel: CPU: 3 PID: 28872 Comm: kodi.bin Tainted: G O 3.14.29 #1 Feb 14 23:45:26 Nexbox kernel: task: ffffffc05207c000 ti: ffffffc064abc000 task.ti: ffffffc064abc000 Feb 14 23:45:26 Nexbox kernel: PC is at 0x3dabd4 Feb 14 23:45:26 Nexbox kernel: LR is at 0x3b2219 Feb 14 23:45:26 Nexbox kernel: pc : [<00000000003dabd4>] lr : [<00000000003b2219>] pstate: 28000030 Feb 14 23:45:26 Nexbox kernel: sp : 00000000e2c00c28 Feb 14 23:45:26 Nexbox kernel: x12: 00000000000070c8 Feb 14 23:45:26 Nexbox kernel: x11: 00000000e2c00edc x10: 0000000000001000 Feb 14 23:45:26 Nexbox kernel: x9 : 0000000000000000 x8 : 0000000000000001 Feb 14 23:45:26 Nexbox kernel: x7 : 0000000066343765 x6 : 0000000066343764 Feb 14 23:45:26 Nexbox kernel: x5 : 00000000ee802a48 x4 : 00000000f437eee0 Feb 14 23:45:26 Nexbox kernel: x3 : 00000000011b2d68 x2 : 0000000000000000 Feb 14 23:45:26 Nexbox kernel: x1 : 0000000066343765 x0 : 0000000000000063 Feb 14 23:45:26 Nexbox kernel: Feb 14 23:45:35 Nexbox kodi.sh[28830]: Segmentation fault (core dumped) Feb 14 23:45:38 Nexbox kodi.sh[28830]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20170214234535.log
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:
Feb 14 23:45:26 Nexbox kernel: kodi.bin[28872]: unhandled level 1 translation fault (11) at 0x66343765, esr 0x92000005
Feb 14 23:45:26 Nexbox kernel: pgd = ffffffc04ca66000
Feb 14 23:45:26 Nexbox kernel: [66343765] *pgd=0000000000000000
Feb 14 23:45:26 Nexbox kernel:
Feb 14 23:45:26 Nexbox kernel: CPU: 3 PID: 28872 Comm: kodi.bin Tainted: G O 3.14.29 #1
Feb 14 23:45:26 Nexbox kernel: task: ffffffc05207c000 ti: ffffffc064abc000 task.ti: ffffffc064abc000
Feb 14 23:45:26 Nexbox kernel: PC is at 0x3dabd4
Feb 14 23:45:26 Nexbox kernel: LR is at 0x3b2219
Feb 14 23:45:26 Nexbox kernel: pc : [<00000000003dabd4>] lr : [<00000000003b2219>] pstate: 28000030
Feb 14 23:45:26 Nexbox kernel: sp : 00000000e2c00c28
Feb 14 23:45:26 Nexbox kernel: x12: 00000000000070c8
Feb 14 23:45:26 Nexbox kernel: x11: 00000000e2c00edc x10: 0000000000001000
Feb 14 23:45:26 Nexbox kernel: x9 : 0000000000000000 x8 : 0000000000000001
Feb 14 23:45:26 Nexbox kernel: x7 : 0000000066343765 x6 : 0000000066343764
Feb 14 23:45:26 Nexbox kernel: x5 : 00000000ee802a48 x4 : 00000000f437eee0
Feb 14 23:45:26 Nexbox kernel: x3 : 00000000011b2d68 x2 : 0000000000000000
Feb 14 23:45:26 Nexbox kernel: x1 : 0000000066343765 x0 : 0000000000000063
Feb 14 23:45:26 Nexbox kernel:
Feb 14 23:45:35 Nexbox kodi.sh[28830]: Segmentation fault (core dumped)
Feb 14 23:45:38 Nexbox kodi.sh[28830]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20170214234535.logYou can give the oscam docker addon a try. It's in the linuxserver repo under repositories in the libreelec repo
Docker works fine on my amlogic S905 box and intel mini pc. Thanks for wonderful works.I'm using mainly as Plex server.
But when I tried using PlexKodiConnect with amlogic S905 box, which also serve as Plex media server too, it can load all videos from Plex but just can't play. I don't know if this is a bug using both client and docker server on the same machine, or maybe just my error configuration. But I can play PlexKodiConnect on other Kodi box with no issue.
Anyway, not really a big deal for me. Because I'm not using that docker server box to play video much.
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
Hi there!
I’d like to buy a NUC7i7BNH and run ESXi with a couple VMs on it. One of the VMs should be an libreELEC.
I’ve read this threats
thread-4236.html
thread-2432.html
but I’m still confused:
I’d like to use the benefit of the NUC 7 with his GPU/h.265 capabilities while libreELEC is running in a VM. As mentioned by lrusak, I have to use the generic built.
What’s a/the generic built?
Where can I get the generic built?
Will my setup work? (NUC7, ESXi, …)
Thanks!
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
When is 9 coming?
Not for a while, it's just bleeding edge nightlies for now I believe. Stable 9 won't be released until after kodi "leia" stable is released.
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 laptopMy 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
