Jump to content


Photo

OSMIO4K Multiboot Crash (Pli 7.1)


  • Please log in to reply
57 replies to this topic

#1 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 16:35

There is a crash when current OpenPli image is first downloaded and the multiboot option is selected. The multiboot option works after the first crash for me, but slot #2 is missing. Installing a Multiboot.py file from a different image that works correctly solves the issue for me. Crash log attached.
Thanks. EB



Re: OSMIO4K Multiboot Crash (Pli 7.1) #2 ccs

  • Senior Member
  • 84 posts

+2
Neutral

Posted 21 September 2019 - 17:00

….. no crash log. :unsure: 



Re: OSMIO4K Multiboot Crash (Pli 7.1) #3 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 17:09

Well...
Let's try it again!
Thanks.
 

Attached Files



Re: OSMIO4K Multiboot Crash (Pli 7.1) #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,394 posts

+821
Excellent

Posted 21 September 2019 - 17:12

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/Console.py", line 37, in finishedCB
  File "/usr/lib/enigma2/python/Tools/Multiboot.py", line 57, in appClosed
OSError: [Errno 2] No such file or directory: '/tmp/testmount/usr/share/bootlogo.mvi'
[ePyObject] (CallObject(<bound method EnigmaLogFatal.write of <bound method ConsoleItem.dataAvailCB of <bound method EnigmaLogDebug.write of <bound method PollReactor._cancelCallLater of <bound method PollReactor._moveCallLaterSooner of <bound method PosixReactorBase.callLater of <bound method DelayedCall.__init__ of <bound method CList.__call__ of <bound method eLabel.eLabel_setText of <bound method CList.__call__ of <unbound method eLabel.eLabel_setText>>>>>>>>>>>,(0,)) failed)

Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: OSMIO4K Multiboot Crash (Pli 7.1) #5 littlesat

  • PLi® Core member
  • 49,179 posts

+527
Excellent

Posted 21 September 2019 - 17:25

We derive the date from the image from this bootlogo.mvi file... when one of the images do bot have this mvi it can wrong... with openatv and vix it should go fine. What further images do you have installed.
We could consider to add for the file exist and/or find another way to detect the date the image was last time upgraded.

Edited by littlesat, 21 September 2019 - 17:27.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OSMIO4K Multiboot Crash (Pli 7.1) #6 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 18:06

I have OpenPli, SatDreamGr, and OpenVix images in multiboot.
The image in slot #2 has a customized bootlogo, so maybe that is my problem?

The PLI image crashes when first installed, and that log has been attached.
The PLi image does not crash anymore after that, but the image slot #2 where the customized bootlogo is located is not displayed for a multiboot option. Boot to another image besides PLi, and slot #2 is seen as a multiboot option.



Re: OSMIO4K Multiboot Crash (Pli 7.1) #7 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,394 posts

+821
Excellent

Posted 21 September 2019 - 18:10

The problem I think is Littlesat is trying to be "too smart"... ;)

 

In the end it's a bootable partition (or not), and no clue what is actually on that partition. The fact that it is an Enigma image, and one with particular features, is ihmo far from a given....


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: OSMIO4K Multiboot Crash (Pli 7.1) #8 littlesat

  • PLi® Core member
  • 49,179 posts

+527
Excellent

Posted 21 September 2019 - 19:19

Sounds like custunized bootlogo is somehow ‘hacked’ into the image... to solve it we need to check if the file exist or pit a try/except around it... but doing this the ‘date’ cannot be determined (so what... I can put unknown instead)

Edited by littlesat, 21 September 2019 - 19:20.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OSMIO4K Multiboot Crash (Pli 7.1) #9 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 19:28

This is the difference I find in the Multiboot.py files.
 

PLi = (os.stat('/tmp/testmount/usr/share/bootlogo.mvi').st_mtime).strftime('%Y-%m-%d'))}

SDGr = (os.stat('/tmp/testmount/usr/bin/enigma2').st_mtime).strftime('%Y-%m-%d'))}



Re: OSMIO4K Multiboot Crash (Pli 7.1) #10 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,394 posts

+821
Excellent

Posted 21 September 2019 - 20:24

@Littlesat, ping Athoik, he should be able to tell you why it is different. 


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: OSMIO4K Multiboot Crash (Pli 7.1) #11 twol

  • Senior Member
  • 259 posts

+7
Neutral

Posted 21 September 2019 - 21:08

I have OpenPli, SatDreamGr, and OpenVix images in multiboot.
The image in slot #2 has a customized bootlogo, so maybe that is my problem?
The PLI image crashes when first installed, and that log has been attached.
The PLi image does not crash anymore after that, but the image slot #2 where the customized bootlogo is located is not displayed for a multiboot option. Boot to another image besides PLi, and slot #2 is seen as a multiboot option.

@bandido When in Vix image is SatdreamGR handled correctly? And gives the build date?
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
.........DVB-S2X into 90cm dish (27.5W)
Edision Osmio 4K using Legacy ports on multiswitches
Octagon SF8008 DVB-S2X tuner using Legacy ports on multiswitches
Zgemma H9 C/S into Giga4K
Zgemma H9Combo legacy ports on multiswitches
Zgemma H9twin using legacy ports
Multibox
Dinobot Mini 4K

Re: OSMIO4K Multiboot Crash (Pli 7.1) #12 littlesat

  • PLi® Core member
  • 49,179 posts

+527
Excellent

Posted 21 September 2019 - 21:27

When checking on enigma2 binary is not good as it only increases when the enigma2 binary is updated... on openpli the mvi is always updated and includes everything in the image regarding the latest upgrade.... so the other image Goes the wrong direction.
I’ll make Some solution.... at least avoid a crash when someone ‘plays’ with the bootlogo.mvi....

Edited by littlesat, 21 September 2019 - 21:30.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OSMIO4K Multiboot Crash (Pli 7.1) #13 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 21:39

VIX handles the multiboot images correctly, but I do not know what the displayed dates are supposed to be. I do not know if they are supposed to be dates the image was installed or the dates for image creation.

.



Re: OSMIO4K Multiboot Crash (Pli 7.1) #14 littlesat

  • PLi® Core member
  • 49,179 posts

+527
Excellent

Posted 21 September 2019 - 21:46

My intent was the last date of upgrade... as that indicates the real date of the image. The flash date is not the good indicator here.
When someone known a better check for the intent please let me know. (Even retreiving the flash date is sticky). Openpli updates every build the mvi... so I thought this is the best indicator.

Edited by littlesat, 21 September 2019 - 21:48.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OSMIO4K Multiboot Crash (Pli 7.1) #15 Abu Baniaz

  • PLi® Contributor
  • 1,079 posts

+25
Good

Posted 21 September 2019 - 21:54

Surely the date of Enigma2 will be the build date if no updates are done. If it is updated, the update date will be more reliable/accurate than the mvi date. not 100 accurate though.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

Re: OSMIO4K Multiboot Crash (Pli 7.1) #16 el bandido

  • Senior Member
  • 137 posts

+5
Neutral

Posted 21 September 2019 - 21:55

I went through the multiboot menu or multiboot list in each of the three image Types that I have installed. And I get 3 different sets of dates...



Re: OSMIO4K Multiboot Crash (Pli 7.1) #17 twol

  • Senior Member
  • 259 posts

+7
Neutral

Posted 21 September 2019 - 22:23

This is not a straight forward issue, as images use slightly diifferent formats to decide on the last date/time for an update.
In OpenVix its not an issue because you can pick up the Release or Dev build number both at 1st flash and after a software update - so the information is always accurate(not based on date stamping) - other images such as OpenPli/OpenATV use opkg update date stamping (differently) so it should be reasonably accurate, but ........
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
.........DVB-S2X into 90cm dish (27.5W)
Edision Osmio 4K using Legacy ports on multiswitches
Octagon SF8008 DVB-S2X tuner using Legacy ports on multiswitches
Zgemma H9 C/S into Giga4K
Zgemma H9Combo legacy ports on multiswitches
Zgemma H9twin using legacy ports
Multibox
Dinobot Mini 4K

Re: OSMIO4K Multiboot Crash (Pli 7.1) #18 Abu Baniaz

  • PLi® Contributor
  • 1,079 posts

+25
Good

Posted 21 September 2019 - 22:27

But what?



Re: OSMIO4K Multiboot Crash (Pli 7.1) #19 twol

  • Senior Member
  • 259 posts

+7
Neutral

Posted 22 September 2019 - 07:18

But what ? It would be nice if an image is going to identify by date/time stamping that it used a common method - there are only 3 „base“ images OpenPli (and their clones), OpenATV (and their clones) and OpenVix- (in my view!) of which the 1st two use date/time stampmg - so at least accommodate that in your image
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
.........DVB-S2X into 90cm dish (27.5W)
Edision Osmio 4K using Legacy ports on multiswitches
Octagon SF8008 DVB-S2X tuner using Legacy ports on multiswitches
Zgemma H9 C/S into Giga4K
Zgemma H9Combo legacy ports on multiswitches
Zgemma H9twin using legacy ports
Multibox
Dinobot Mini 4K

Re: OSMIO4K Multiboot Crash (Pli 7.1) #20 littlesat

  • PLi® Core member
  • 49,179 posts

+527
Excellent

Posted 22 September 2019 - 07:25

We do not use opkg update date as that je not accurate as you can also execute it without upgrade (eg by ui when you go to add/remove plug-ins).
Openvix has something that needs a commit on GitHub. When they don’t do it on a day it is also not accurate.
We do change the bootlogo.mvi each day. The bootlogo is created by the build server and therefor Unique for the build.
The gsod should be solved.
Making agreements between images is an utopy.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users