Posts by vpeter

Try

robocopy "D:\Media\Fotoramen" "Z:\Fotoramen" /MIR /COPY:DT /DCOPY:T

Compare the content of both archives to see what is the difference

I updated build Milhouse #0528and removed kodi profile folder. After new start I could install whatever addon version was in the repository.

Are you sure you look enough?

Quote from chelobaka

No. Intel is still working on kernel HDR support ....

Intel is also working on S9xxx SoC?

Quote from soyxan

Do you have any explanation for that?

No actually. I just look around how other docker services are started and saw this small change. Maybe

--attach , -a Attach STDOUT/STDERR and forward signals
-t, --time int Seconds to wait for stop before killing it (default 10)

Try with this Start and Stop:

ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start -a domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop -t 2 domoticz

Then I can't help you anymore. I only create container and for me it runs fine after reboot too.

After you create domoticz container do you run it from console to initialize it? Because I can run it just fine.

docker start domoticz

# look if completely started with
docker logs domoticz

When creating docker try without --restart unless-stopped.

You need to set variables STRIP and PKG_MAKE_OPTS_TARGET in function pre_configure_target() to evaluate them correctly because you are using environment variables STRIP and CC which are known little later. Correct reason can tell someone else

pre_configure_target() {
  STRIP="--strip --strip-program=$STRIP"
  PKG_MAKE_OPTS_TARGET="SYSCONFDIR=/storage/.config CC=$CC CWFLAGS="
  PKG_MAKEINSTALL_OPTS_TARGET="SYSTEMD_DIR=/usr/lib/systemd/system BINDIR=/usr/sbin install-systemd"
}

Also your build was compiled with ggdb

It starts for me fine. What was the command to create domoticz container?

Running this should work (from autostart.sh or systemd service)?

ntpd -p your_time_server:port

Seems correct place to me.

Quote from Shoog

heatsink/fan which you will have to bodge together yourself (at least initially)

They have both for other model and maybe it can fit on this model too.

Well, chewitt could ask RPi guys one more time about this issue. Seems there are only few people affected. You could also write on github issue on a link where this workaround is posted.

Here it is: libreelec-rpi2.arm-9.0-devel-20190514181900-3017890-bcdc-zero.img.gz

I forgot to change version. Let me know if you need "nicer" build which would actually show 9.0.2 version

I have no idea. Depends if Linux has required bits included. Which I doubt.