Er zijn 52 reacties in dit onderwerp

[mikel]

Hallo,

 

bei meiner Zgemma H7S funktioniert unter Image 7.2 kein Modus 12 mehr.

Log anbei.

 

Gruß mikel

Bijgevoegde Bestanden

•  enigma2_crash_1580720130.log   18,74K   12 Aantal bijlagen

Veranderd door mikel, 3 februari 2020 - 10:10

[mikel]

Kann hier vom Team niemand etwas zu sagen?

 

Bei Auswahl Modus 12 stürzt die Box ab und startet wieder im Modus 1, siehe Log in #1.

[rantanplan]

IOError: [Errno 2] No such file or directory: '/tmp/startupmount/STARTUP_14'

Ich vermute mal das dort falsche Einstellungen gespeichert wurden und der Versuch der Wiederherstellung dann damit fehl schlägt.

Veranderd door rantanplan, 6 februari 2020 - 17:18

[littlesat]

Indeed where does STARTUP_14 come from...?

Usually when the slot becomes above 12 is should make slot 2 from it....?

Looks like canMode12 does not work somehow here.... Maybe something does currupt some STARTUP files... did you install a recovery image on the H7?

Veranderd door littlesat, 7 februari 2020 - 14:45

[mikel]

Ich habe jetzt mal ein neues Image 7.2 geflasht, mit und ohne Übernahme von Einstellungen, kein Modus 12 möglich.

Dann habe ich ein Image 6.2 geflasht, Modus 12 möglich, damit habe ich dann mein aktuelles Backupimage 7.2 geflasht und nun kann ich wieder den Modus 12 auch mit meinem aktuellen 7.2 nutzen.

 

Ist schon komisch was das 7.2 alles so bereit hält, auch die Einstellungen konnte ich von 7.1 nicht übernehmen und musste diese händisch neu machen.

 

 

I have now flashed a new image 7.2, with and without applying settings, no mode 12 possible.

Then I flashed an image 6.2, mode 12 possible, so I flashed my current backup image 7.2 and now I can use mode 12 again with my current 7.2.

It's funny what the 7.2 has so ready, I couldn't take the settings from 7.1 and had to do it manually.

[mrvica]

the same here, tried Multiboot.py from develop. still the same, I have OpenPLi 7.2 on my second partition, here what sys says

root@h7:/var/volatile/tmp# cat /sys/firmware/devicetree/base/chosen/bootargs
root=/dev/mmcblk0p8 rootsubdir=linuxrootfs2 kernel=/dev/mmcblk0p4 rw rootwait h7_4.boxmode=1root@h7:/var/volatile/tmp#

I have OpenATV in first partition, in mode 1 I have

root@zgemmah7:/tmp# cat /sys/firmware/devicetree/base/chosen/bootargs
brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait h7_4.boxmode=1root@zgemmah7:/tmp#

in mode 12 I have

root@zgemmah7:/tmp# cat /sys/firmware/devicetree/base/chosen/bootargs
brcm_cma=520M@248M brcm_cma=200M@768M root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait h7_4.boxmode=12root@zgemmah7:/tmp#

[littlesat]

In develop the slots do now depend on content of the STARUP.. files.... did you install the latest recovery image on that box?

[littlesat]

Mmm the box does not have a recovery image... does de STARTUP partition has the STARTUP_..._MODE_... files with all the poiblitities.... with the latest develop image they are currently mandatory. Might be we need a change in the bsp.
For standard 7.2 release this should be no issue

Veranderd door littlesat, 7 februari 2020 - 18:12

[mikel]

Nach Neustart meiner Zgemma H7S wieder gleiches Problem, Modus 12 startet nicht, siehe Log #1.

Was kann ich tun? Oder könnt ihr etwas ändern?

 

After restarting my Zgemma H7S the same problem again, mode 12 does not start, see log # 1.

What can I do? Or can you change something?

Veranderd door mikel, 9 februari 2020 - 12:46

[littlesat]

First answer my question please.... when the box misses the Startup_.... files it is explained.... but when you use pure 7.2 you should not get any issue.

[mikel]

Flashed a current one in Part 2 over the old 7.2 and took no settings.
Mode 12 is not possible. See current log.

 

Bijgevoegde Bestanden

•  enigma2_crash_1581252356.log   19,01K   0 Aantal bijlagen

[mikel]

My images on the box

 

Startup1 is HDF
Startup2 is PLI
Startup3 is ATV
Startup4 is HDF

 

Mode 12 works for all other images.

 

I have almost only PLI in operation.

 

Can I exchange any startup files there?

Veranderd door mikel, 9 februari 2020 - 13:59

[mrvica]

he said already that he tried with 7.2 USB image

https://forums.openp...dpost&p=1162099

where we have to look for the STARTUP files?, in OpenATV I have







root@zgemmah7:/tmp# dir /boot/
drwxr-xr-x    2 root     root         16384 Jan  1  1970 .
drwxr-xr-x   16 root     root          4096 Feb  1 18:03 ..
-rwxr-xr-x    1 root     root           161 Feb  9 13:39 STARTUP
-rwxr-xr-x    1 root     root           161 Jan 28 22:45 STARTUP_1
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_2
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_3
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_4
root@zgemmah7:/tmp#

root@zgemmah7:/tmp# dir /dev/block/by-name/boot
lrwxrwxrwx    1 root     root            14 Feb  7 18:58 /dev/block/by-name/boot -> /dev/mmcblk0p1
root@zgemmah7:/tmp#

in OpenPLi

oot@h7:/var/volatile/tmp# dir /boot/
drwxr-xr-x    2 root     root          4096 Jan 31 18:18 .
drwxr-xr-x   15 root     root          4096 Jan 30 18:57 ..
lrwxrwxrwx    1 root     root            18 Jan 27 01:31 backdrop.mvi -> /boot/bootlogo.mvi
lrwxrwxrwx    1 root     root            23 Jan 27 01:31 bootlogo.mvi -> /usr/share/bootlogo.mvi
lrwxrwxrwx    1 root     root            18 Jan 27 01:31 bootlogo_wait.mvi -> /boot/bootlogo.mvi
lrwxrwxrwx    1 root     root            20 Jan 27 01:31 radio.mvi -> /usr/share/radio.mvi
root@h7:/var/volatile/tmp#

root@h7:/var/volatile/tmp# dir /dev/block/by-name/boot
lrwxrwxrwx    1 root     root            14 Jan  1  1970 /dev/block/by-name/boot -> /dev/mmcblk0p1
root@h7:/var/volatile/tmp#

root@h7:/var/volatile/tmp# mkdir boot

root@h7:/var/volatile/tmp# mount /dev/block/by-name/boot /tmp/boot

root@h7:/var/volatile/tmp# cd boot/

root@h7:/var/volatile/tmp/boot# dir
drwxr-xr-x    2 root     root         16384 Jan  1  1970 .
drwxrwxrwt    4 root     root           160 Feb  9 13:58 ..
-rwxr-xr-x    1 root     root           124 Feb  9 13:57 STARTUP
-rwxr-xr-x    1 root     root           161 Jan 28 22:45 STARTUP_1
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_2
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_3
-rwxr-xr-x    1 root     root           162 Jan 28 22:45 STARTUP_4
root@h7:/var/volatile/tmp/boot#

[mikel]

I didn't flash with USB, just online flash.

[mikel]

Habe nochmals das aktuelle PLI_6.2 online in Startup 2 geflasht und hier geht Modus 12 ohne Probleme.

 

Flashed again the current PLI_6.2 online in Startup 2 and here Mode 12 goes without problems.

[littlesat]

There exist no startup_... file for mode 12.... these are missing and need to be added....
So we miss STARTUP_x_MODE_1 and STARTUP_x_MODE_12 field on your box.... you only have straight STARTUP_X files which is not compatible any more and is only doing mode 1...

Veranderd door littlesat, 9 februari 2020 - 15:09

[mikel]

How do I do that?

 

Is that only possible via USB Neuflash?

 

Flashed again the current PLI_6.2 online in Startup 2 and here Mode 12 goes without problems.

Veranderd door mikel, 9 februari 2020 - 15:12

[littlesat]

I’m not sure if our latest images do install it when flashing from usb and clearing all slots.... or someone needs to adapt the bps.

Veranderd door littlesat, 9 februari 2020 - 15:11

[mikel]

Does that come with an update?

[littlesat]

Actually for now no idea...
I try for tomorrow to create the eight required files....
Likely zgemma need to change bsp layer and/or the first image you did installed does something differently...

Veranderd door littlesat, 9 februari 2020 - 16:56