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.logIf 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.logIf 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.
I was using this: le shutdown with net - Pastebin.com
I created new service which runs script /storage/.config/shutdown_with_net.sh script on shutdown/reboot. Just to not interfere with existing services/scripts.
Was working 100%.
Yes, I can set this to false in guisettings.xml. Will make test image.
LibreELEC-imx6.arm-7.0.0-no.update.resolution.img.gz (untested)
update resolutions is set to false by default - of course this will work only on fresh install.
view?usp=sharing
everyone told me that update would be as easy as just drop the .tar on the update folder. LIARS!
You do know imx6 image is community build? Which means not everything will ever work for everybody.
Sometimes I'm just wondering why did I even touch imx6 project in le... Maybe would be better to just leave it die!
vpeter, is it possible to turn it off by default? i know it is kodi + kernel issue, and not LE issue.
many issues will be resolved by this step.
Yes, I can set this to false in guisettings.xml. Will make test image.
Why is it 4px more?
Sadly I don't know. I choosed this kernel as it is more modern. But support is limited. That's also the reason why this build is community based and not official. If it works for someone: great. If not: not sure if we can fix the issue.
Try fresh install on spare sd card.
I tried adapting my service and information from that link didn't help much. Back to drawing board...
One option would be to run perl with zap2xml in docker.
The closest thing to fix this issue was new service /storage/.config/system.d/kodi-reboot.service (shutdown.sh always gets reboot parameter):
[Unit]
Description=Kodi reboot script
After=network.target
[Service]
Type=oneshot
Environment=HOME=/storage
ExecStart=/bin/true
ExecStop=-/bin/sh -c ". /etc/profile; exec /bin/sh /storage/.config/shutdown.sh reboot"
RemainAfterExit=yes
[Install]
WantedBy=kodi.targetBut for some reason it didn't work 100% reliably.
When I was trying to get this kernel running with LVDS display with resolution 1366x768 it was no-go. After lot of time I got info that resolution must be set by module 8. And 1366 is not. When I changed to 1360 it works like a charm.
So I read the entire post and see that a txt file have to been manualy create and put in download folder.
Actually only downloader folder must be created manually. And then selection addon should create the file.
I have only CuBox-i i4Pro and this was used for development. I don't know what are the differences between this versions.
vpeter, does the beta in download page it's the same you uploaded few days ago for test?
You mean official beta? Then no. In my beta2 there is a different libcec used which solves some problems for some users.
From what I see the author distributes statically linked binary for Linux (x86). He would just need to compile same thing for RPi.