Posts by ozolli

Quote from Teppopups

Upgrade or Clean install? Because LE 7.0.3 didn't have this issue. I suppose that all the settings preserved during the upgrade procedure. This can be verified by doing full config reset on LE 8.0.1.

Clean install on 7.90.x then upgrade since then.

Quote from vitorp07

@ozolli
I guess you are having more luck than we did, on what kind of hardware you have LibreELEC installed on?

Here is intel 4690s + Nvidia GTX 1070

Intel N3150.

It's already set to 1.000000 everywhere here...

Just saw the discussion here : Package updates by lrusak · Pull Request #1452 · LibreELEC/LibreELEC.tv · GitHub

When trying to start a container:

Phoenix:~/.kodi/addons # docker start lemp
Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"cgroup\\\" to rootfs \\\"/storage/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/52657e45c9f38c6d6ba9dd684723461fe5957053c3b6660a257b82e1eba946a1/merged\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""
Error: failed to start containers: lemp

Seems to be related to systemd upgraded to 233:
FS#53271 : [docker] systemd 233 breaks docker with cgroups v2

I tried to compile the docker addon with v17.03.1-ce as per the above link but it doesn't fix this issue.

The workaround in Can not run any docker container (fresh install after reboot) · Issue #28109 · moby/moby · GitHub , adding

-v /sys/fs/cgroup:/sys/fs/cgroup:ro

to the docker run/create command line did the trick.

Quote from aptalca

I hardcoded a 10 second pause between the container creation/start and kodi service coming up. In my case, it takes about 4 seconds for mysql to be up and running after container start.

I have done that a different way with my lemp container :

while [ ! $(docker exec lemp ls /run/mysqld/mysqld.sock 2>/dev/null) ]; do sleep 0.5; done

You may have to adapt it to the location of the socket in your container.

clarkss12 : Why do you mount your volume twice ?
The systemd unit should suffice.

Thank you chewitt for the 3.10 kernel explanation ; I was wondering why these 2 beasts were not compatible.

If you have a look at the Docker addon package.mk the WeTek Play is not compatible :

PKG_ADDON_PROJECTS="Generic RPi RPi2 imx6 WeTek_Hub WeTek_Play_2 Odroid_C2"

Quote from chewitt

Code for the update back end is not public and for several reasons there are no current plans to change that. If you'd like to explain your interest in more detail we may be able to answer questions.

Ok I get that.
I would like to know how the reply from this file is constructed so I can do my own implementation to auto-update a custom distribution.
I have already set up the releases server with the releases.json file.
I don't need the other code you may have for your internal needs

EDIT: Well, if I'm not mistaken the reply is something like:

{"data": {"folder": "releases", "update": "LibreELEC-Generic.x86_64-8.0.0.tar"}}

Hello devs,

I am looking for the source code of updates.php declared here :

service.libreelec.settings/defaults.py at master · LibreELEC/service.libreelec.settings · GitHub

Is it available somewhere please ?
Thanks !

Here the 7.95.3: LibreELEC-Generic.x86_64-8.0-304.134_9221cfc73.tar?dl=1

Quote from bam

ozolli No, it was upgrade to the next official new build. Did you compile your build yourself?

Yes. In fact it's a build with an old nvidia driver for some people needing it.

Did you compile this yourself ?

On my build it's ok :

olivier@backup:~/ozLE$ head build.LibreELEC-Generic.x86_64-7.95.2/image/system/usr/share/kodi/addons/skin.estuary/addon.xml
<?xml version="1.0" encoding="UTF-8"?>
<addon id="skin.estuary" version="1.9.10" name="Estuary" provider-name="phil65, Ichabod Fletchman">

New tarball with the mtrr patch. It's a 7.95.2 one.
Here : Dropbox - Link not found

Quote from elfurbe

Also my xrandr output shows an incorrect "Broadcast RGB" setting, it should be forced to "Full" by autostart.sh. This was a previous Kodi best-practice for proper black levels (TV set to limited, X output set to full, Kodi set to limited), but perhaps 17+newer GPU has created some synergy here that I'm unaware of and "Video 16:235 pass-through" is expected now.

Yes it is on Intel GPUs. It's basically a "Full" mode which also implements the Intel zero copy approach to directly render the decoded NV12 surface.

Ok I will try to apply a mtrr patch and come back with a new tarball.
Unfortunately I cannot test it myself so you will have to try it yourself.

Quote from milhouse

Alternatively, you might be able to find someone willing to build LibreELEC 8.0 with the 304.xx driver in place of 340.xx

I built one a few days ago with NVidia driver 304.134. It is between 7.95.1 and 7.95.2.
Here: Dropbox - Link not found