How did you create crontab file? With crontab command?
Posts by vpeter
-
-
Works for me. Created shell file, make it executable, add cron entry with crontab -e and it was fired at a time I requested.
Didn't enabled anything - it just works.update.sh is very much relevant. But seems you know what you are doing...
-
Post the content of /storage/update.sh.
-
is there a kodi 16.1 with this kernel?LibreELEC-imx6.arm-7.0.2-sr-3.14.img.gz in Index of /imx6-solidrun-kernel-3.14/
-
I tested again without a second screen...now the size on a 4k is ok. So you need to test with a 4k main monitor and a second non-4k.
Good. To whom I need to send request for a two new monitors?Update: And I forgot - need also one computer to hook them up.
-
Next update should have this fixed. Confirmed on Windows but I hope it will also work for Linux.
Sadly mcfrojd newer post any feedback.
-
Not sure why i thought it was different now but you're right. When selecting x86_64 it generates a install disc and not a complete install.Not sure if current image supports new run mode - can be selected from bootloader menu (install, live, run). In run mode there is no need to make actual installation from one usb stick to another or hdd. If image is put directly to hdd it can be boot and used there.
-
Yesterday I was trying to use win32diskimager and I didn't succeed until I restarted windows. Same error as above. So something was definitely keeping device locked.
-
Isn't there a easy way to get LE on a SSD/HDD?/EDIT:
Okay found a way to get it done.
Create a Linux VM and mounted my SSD to it, using the Linux USB creation tool i managed to get LE installed on it.What is your idea how this could be done?
[hr]Doesn't win32diskimager already do that?
Backup function is on todo list. And yes win32diskimager can do that.
-
jako, thank you very much for this tests. Yes, writing speed was the reason for this test - previously I have something disabled and to be 100% sure to still working I ask you again.
Next version will be published in next few days and will include also this fixes for macOS Sierra.
Thanks again.
-
jako, can I ask you for one more test: LibreELEC.USB-SD.Creator.macOS-Sierra3.dmg
Just need confirmation if still works.
-
Good, now it is clear where the problem is.
Can you please try LibreELEC.USB-SD.Creator.macOS-Sierra2.dmg
-
jako, can you make me screenshot of Creator app when you have USB reader inserted and selected card? I would like to see the text.
-
I tried to create a µSD card for RPI3 under W7 and i got the following message from the USB-SD creator:
{Une erreur est survenue lors du vérouillage du volume.Erreur 5: 捁敲畦മ↡ⅺք谀ā"}
message from SD creator: erreur: couldn't open k:\The only possibility is to kill the application.
k:\ is obviously the drive number associated to the µSD card reader slot
When you got this message? When application starts or when writing to sd card?And I think this problem happen because some other application is using sd card at the same time and can't be exclusively locked by Creator. Check that.
-
jako, could you test this version?
LibreELEC.USB-SD.Creator.macOS-Sierra.dmg
I was told that in virtual machine Creator works. But maybe on real system it is something different.
-
Great! Will be included in next official build.
-
Can you try this version please and report back?
-
Let me explain how Creator app actually works. It must be started with sudo to get raw access to a device. But when app is started root privileges are dropped back to a user. Only when writing actually starts privileges are raised again. This works on Linux and on old macOS. But on Sierra something is different. Because I don't have access to any sch system it is just a little hard to fix the issue