Posts by benni0815
-
-
CvH: Sorry that it took so long but now I tried what you suggested.
In the mean time I was able to upgrade to Beta 1 and 2 (thanks to my post-flash.sh script).
I removed all files from /flash except for KERNEL and SYSTEM, copied LibreELEC-WeTek_Play.arm-8.95.001.tar into the Update Samba share and rebooted. The result was again: Missing (target) kernel.img or SYSTEM!.
-
-
Btw: This is how my /flash directory looks like after the update:
Code
Display MoreLibreELEC (official): 8.90.009 (WeTek_Play.arm) wetek:~ # l /flash/ total 131608 -rw-r--r-- 1 1000 1000 6530916 Dec 8 14:16 KERNEL -rw-r--r-- 1 1000 1000 6521044 Oct 10 22:38 KERNEL.bak -rw-r--r-- 1 1000 1000 121704448 Dec 8 14:16 SYSTEM -rw-r--r-- 1 root root 78 Dec 8 14:12 post-flash.sh wetek:~ # md5sum /flash/KERNEL 427c7d5a7695cca226627dd361f1142c /flash/KERNEL wetek:~ # md5sum /flash/SYSTEM 1b3ceaf805ef8f6ecf58dcf9f1391a16 /flash/SYSTEM
So the kernel was also updated correctly.
-
Yes this is an old install which initially shipped with some OpenELEC version which I updated from release to release.
I could remove KERNEL.bak but this should not change anything I guess? Removing the KERNEL file would result in an unbootable system, wouldn't it?
But I tried something else with the new alpha 009 (LibreELEC-WeTek_Play.arm-8.90.009.tar).
First I just copied it into /storage/.update without changing anything else. Which again brought the "Missing (target) kernel.img or SYSTEM!" error as before:
But I found out that after mounting the /flash partition the init script tries to execute /flash/post-flash.sh if it exists.
So I created a script with that name and the following content:
The next update attempt then worked!
So again my question: Do you accidentially set the wrong kernel file for Wetek Play 1 in projects/WeTek_Play/options?
Line 138 (as of 6db1ac5f83):
-
Code
Display MoreLibreELEC (official): 8.90.008 (WeTek_Play.arm) wetek:~ # df -h Filesystem Size Used Available Use% Mounted on devtmpfs 426.0M 0 426.0M 0% /dev /dev/ubi0_0 200.5M 123.2M 72.6M 63% /flash /dev/data 2.9G 760.1M 2.2G 25% /storage /dev/loop0 116.0M 116.0M 0 100% / tmpfs 428.0M 0 428.0M 0% /dev/shm tmpfs 428.0M 8.8M 419.1M 2% /run tmpfs 428.0M 0 428.0M 0% /sys/fs/cgroup tmpfs 428.0M 1.4M 426.6M 0% /var tmpfs 428.0M 4.0K 428.0M 0% /tmp wetek:~ # l /flash/ total 131204 -rw-r--r-- 1 1000 1000 6530884 Dec 1 17:53 KERNEL -rw-r--r-- 1 1000 1000 6521044 Oct 10 22:38 KERNEL.bak -rw-r--r-- 1 1000 1000 121294848 Dec 1 17:54 SYSTEM
KERNEL.bak is the renamed KERNEL file from Alpha 006 and KERNEL the renamed kernel.img from Alpha 008. (I renamed the KERNEL files.)
-
Hi,
some weeks ago I upgraded my Wetek Play 1 from LE 8 to v8.90.006 ALPHA. Due to some bugs I tried to switch back to LE 8 but this failed for some reason I did not see. (I am using the analogue output of the Wetek on an old CRT TV. During the update step the Wetek does not supply a proper signal on the analogue output. The TV just shows garbage.)
Two day ago I tried to upgrade to the latest alpha (8.90.008) and realized that this also did not work. I then connected a LCD and saw that the upgrade script (packages/sysutils/busybox/scripts/init I assume) failed with "Missing (target) kernel.img or SYSTEM!". That made sense, because there was no kernel.img in /flash. There was just a /flash/KERNEL (and as far as I can remember has always been). I then created an empty /flash/kernel.img file and the upgrade finally succeed (but the upgrader copied the new kernel into /flash/kernel.img).
I looked into projects/WeTek_Play/options and saw that KERNEL_NAME="kernel.img" is set there. Is this a mistake?