Posts by vpeter

There is nothing to fix - it is working on openelec.
For libreelec I should only rebuild it (some RPi users already use it!). But now we are way to offtopic

Quote from IceQB

Also dont see it in unofficial OE Repository

It was newer there - it is unofficial unofficial semi supported.

Quote from IceQB

I came across your add-on on OE but seemed like its developement was dead or not working anymore

I updated it not so long back. And it was working including owncloud.

But probably better to wait for a docker.

In my LAMP addon I have mysql server also. But addoin was not build for LE yet. If there is interest I can do.

Check also folder /lib for them.

Quote from danielk

Is he reading our suggestions in this forum?

Yes, he is reading and aware of the issue. When he cooked something we will know.
Because this issue doesn't happen with my tv I can't help much.

I point logs to mk01. And when he cook something then we can move forward.
Until then it is the situation as is.

Quote from lrusak

New version should be 2.1.7

Then addons.xml was not updated.

Quote from CvH

The addon was reuploaded and is fixed - BUT - due the Kodi caching you need to remove /storage/.kodi/addons/packages/pvr-dvblink... and reinstall

pvr.dvblink-2.1.4.zip
date inside: 2016-04-11 20:03 <<<< seems old file?

Try this one.

LibreELEC-imx6.arm-7.0.0-no.signal.test.img.gz
view?usp=sharing

Please send both logs with this image and mk01 will look them.
Image has kodi running in debug mode, ssh is also enabled by default.
It has some extra Kodi and Linux patches.

Note to myself: pass_events == 0, videoscreen.updateresolutions == true.

To run different things on reboot and shutdown this few lines can help:

if /usr/bin/systemctl list-jobs | /bin/egrep -q 'reboot.target.*start' > /dev/null; then
  # reboot
else
  # shutdown
fi

I see new one.

Quote from lrusak

Problem with orange pi is the sunxi company who makes it and their GPL compliance issues.

I'm sure this is written wrong: sunxi community is great. But Allwinner who makes the SoC is bad

Quote from Alternativende

Is this permanent then? If so a hint in the Wiki would be nice, that if someone is running in the same direction and needs network from within the shutdown.sh is not getting into the same trouble as i did, don´t you think?

Now that you are the first user let's test this and report if works as it should in a few days. Then we will see how to proceed.

Like I wrote I didn't used existed kodi reboot service just to sure that something doesn't interfere with new service.

That's why I used NEW service shutdown_with_net.service and NEW script shutdown_with_net.sh. This script is executed on reboot and shutdown and doesn't support arguments.

Also I think your current shutdown. sh script has errors.

To resolve issue with no signal some logs are required from ssh console

dmesg | pastebinit
pastebinit /storage/.kodi/temp/kodi.log

If ssh not enabled yet it must be enabled with uEnv.txt file on first partition.
It is visible on Windows or mounted on Linux.
Current line

mmcargs=setenv bootargs 'boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0'

add ssh to it

mmcargs=setenv bootargs 'ssh boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0'

After reboot ssh should work.

To resolve issue with no signal some logs are required from ssh console

dmesg | pastebinit
pastebinit /storage/.kodi/temp/kodi.log

If ssh not enabled yet it must be enabled with uEnv.txt file on first partition.
It is visible on Windows or mounted on Linux.
Current line

mmcargs=setenv bootargs 'boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0'

add ssh to it

mmcargs=setenv bootargs 'ssh boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0'

After reboot ssh should work.