474 replies to this topic

[bacicciosat]

Oppsss... forgot to post files

 

 

Attached Files

•  OMBManagerInstall.zip   4.64KB   121 downloads
•  open_multiboot.zip   63.83KB   120 downloads

[bacicciosat]

@Dimitrij: All the work made here is working in Open Black Hole

Now OpenMultiboot works fine and can boot more than 90% of known e2 images.

The bootmenu is fixed and report the right names

The issue with duo2 is fixed

 

The only known issue it that OBH cannot run another OBH in multiboot.

 

The sourced of this work are avilable in Open Black Hole git.

Are two patches the you can adapt to your version where needed.

You can find here:

http://git.vuplus-co...c7e7be6;hb=HEAD

 

best regards

meo

[Dimitrij]

@Dimitrij: All the work made here is working in Open Black Hole

Now OpenMultiboot works fine and can boot more than 90% of known e2 images.

The bootmenu is fixed and report the right names

The issue with duo2 is fixed

 

The only known issue it that OBH cannot run another OBH in multiboot.

 

The sourced of this work are avilable in Open Black Hole git.

Are two patches the you can adapt to your version where needed.

You can find here:

http://git.vuplus-co...c7e7be6;hb=HEAD

 

best regards

meo

Thank you very much for your help.

But what about this https://github.com/v...a-vuplus/pull/6, without nandsim new images do not unpack.

[bacicciosat]

 

@Dimitrij: All the work made here is working in Open Black Hole

Now OpenMultiboot works fine and can boot more than 90% of known e2 images.

The bootmenu is fixed and report the right names

The issue with duo2 is fixed

 

The only known issue it that OBH cannot run another OBH in multiboot.

 

The sourced of this work are avilable in Open Black Hole git.

Are two patches the you can adapt to your version where needed.

You can find here:

http://git.vuplus-co...c7e7be6;hb=HEAD

 

best regards

meo

Thank you very much for your help.

But what about this https://github.com/v...a-vuplus/pull/6, without nandsim new images do not unpack.

 

 

Where is the problem ?

You can provide with your plugin also the ipk of the kernel module.

Users will install first the module and then the plugin.

[Ev0]

I have installed:

 

OpenPLi 4.0

BH 2.1.6.1

OpenVix-Hades 011

OpenAtv 4.2

OpenAtv 5.0

VTi 8.2.2

 

All have installed fine and all names reported as I named the .zip files.

 

I did also install OBH 0.1 into Multiboot, and it boots just once for me again, but if I restart or try to boot OBH in multiboot again it fails.

[Dimitrij]

And where to get modules?

vu+ eight different models.

[bacicciosat]

Ok here are.

Attached Files

•  kernel-module-nandsim_3.9.6-r1_vuduo.ipk   20.72KB   23 downloads
•  kernel-module-nandsim_3.9.6-r1_vusolo.ipk   20.81KB   23 downloads
•  kernel-module-nandsim_3.9.6-r1_vuultimo.ipk   20.73KB   20 downloads
•  kernel-module-nandsim_3.9.6-r1_vuuno.ipk   20.72KB   30 downloads
•  kernel-module-nandsim_3.13.5-r1_vuduo2.ipk   20.57KB   30 downloads
•  kernel-module-nandsim_3.13.5-r1_vusolo2.ipk   20.58KB   63 downloads
•  kernel-module-nandsim_3.13.5-r1_vusolose.ipk   20.57KB   28 downloads
•  kernel-module-nandsim_3.13.5-r1_vuzero.ipk   20.54KB   12 downloads

[dany]

every thing is ok here .... without losing installed images in usb (mutiboot)

 

i will see if these fixes working with openatv openmultiboot

[dany]

yes .... it works very well here

openatv-5.0 in flash - openpli now works very well in multiboot after used the fixed files

[Ev0]

All images I posted above are booting, and online updating just fine (excluding BH 2.1.6.1 as there are no updates and OBH as it fails to boot more than once as you know already).

I can jump between them as much as I want.

[dany]

yes evo .. all those images are working here very well too

you are right obh fails to boot

really bootmenu is very useful .. but the only way to use it .. when you boot from pli image

[Ev0]

really bootmenu is very useful .. but the only way to use it .. when you boot from pli image

 

The bootmenu only works in OpenPLi as it does not have OpenGLes support (no animations or xbmc).

 

All other images have the later kernel that support the above.

If OpenPLi change kernels to support animations and xmbc, then the bootmenu will disappear completely.

[dany]

I understand that very well because meo has explain it before

but i mean maybe could meo fix this known issue later

[Ev0]

I am not sure it is possible (I think if it was meo would have done it, but he knows better than I do), however I personally prefer not to have the boot menu, as it means bootup is faster.

Edited by Ev0, 9 June 2015 - 21:59.

[dany]

faster (30 sec) ... thats all

 

meo .....   i donot know if we can use this plugin for pli in flash ,,, especially after fixed files ... maybe it will work

[bacicciosat]

 

really bootmenu is very useful .. but the only way to use it .. when you boot from pli image

 

The bootmenu only works in OpenPLi as it does not have OpenGLes support (no animations or xbmc).

 

All other images have the later kernel that support the above.

If OpenPLi change kernels to support animations and xmbc, then the bootmenu will disappear completely.

 

 

Ok a little explanation about OpenMultiBoot and the issue of bootmenu.

 

OpenMultiBoot is at the present in my opinion the best multiboot solution for enigma2 box.

This because the other multiboot systems like meoboot always load the drivers and the kernel from the flash and later perform a chroot into the target image.

This means that if you have blackhole in flash and openpli in multiboot you will have a mixed image Openpli with kernel and drivers of BlackHole with all the relative issues.

 

OpenMultiBoot do something different. It backups the kernel of each installed image and store it so when you select the image to boot it flashes the kernel of the image that have to be booted and then boot it with the coorect kernel and drivers.

The only issue of this system is that at every image change, the kernel is "flashed".

This should seems not nice for the flash of the box, but you have to consider that you will never change 10 images every day and that the kernel is really smaller than a full image.

 

So with OpenMultiBoot we have finally the compatibility with all images and each image will works fine like it was in flash and not in multiboot. For this reason you can have in multiboot images with OpenGl and images without it or with and without Xbmc

and all the images will work fine.

 

The only limit of OpenMultiBoot is at the present that the bootmenu is not working with the VU+ images that use OpenGL.

So if you boot from OpenPli you will have bootmenu, if you boot from another image you have to previously select the image to boot from the plugin.

 

The issue of BootMenu is simply to explain. It doesn't depend by OpenGL itself but by the way that VU+ have implemented the loading of the drivers.

 

In all the e2 images before this Vu+ implementation, the driver for the framebuffer can be loaded at the very beginning of the boot.

You can load only the driver needed to have the framebuffer available and later, when one image is selected you can start the ordinary init procedure.

This because to show something on the screen (bootmenu) you need the framebuffer.

So this procedure to run the framebuffer was image-indipendent.

With the OpenGl implementation Vu+ have moved the load of the drivers at the end of the rcS.d in the file vuplus-platform-util. This means that the framebuffer is available only after the init procedure of the image is already started and many things image-dependents are already running so you cannot change image at that stage or you will mix things and we will have again issues.

 

So What's happen in meoboot and OpenMultiBoot when they boot and OpenGl image ?

They try to load the driver for the framebuffer and they try to launch the bootmenu. But the video hardware is not inizialized and the bootmenu is not showed and the procedure continue.

 

At the present time i don't see a solution about this issue. The only solution i can figure is to try to modify the loading sequence of the Vu+ drivers. But i don't like to ply with these things.

Maybe Skaman that is the author of OpenMultiBoot and it knows it much better than me could find a solution.

But he is really busy now.

 

Sorry for my english, really bad. I know that my words are not so clear.

[dany]

a great explanation ... thank you meo so much

 

i know that you are doing your best

 

skaman .... openatv team ?

[bacicciosat]

At the present time i don't see a solution about this issue. The only solution i can figure is to try to modify the loading sequence of the Vu+ drivers. But i don't like to ply with these things.

Maybe Skaman that is the author of OpenMultiBoot and it knows it much better than me could find a solution.

But he is really busy now.

 

 

I have to correct myself.

It seems that i found the solution.

Now Bootmenu is available in all the images with OpenGL too.

I have fixed also the issue of OBH not booting when installed in mutiboot.

All is ok now. OpenMultiBoot seems perfect.

 

Thanks to all the testers.

[rtzhjgg0]

 

I have to correct myself.

It seems that i found the solution.

Now Bootmenu is available in all the images with OpenGL too.

I have fixed also the issue of OBH not booting when installed in mutiboot.

All is ok now. OpenMultiBoot seems perfect.

 

Thanks to all the testers.

 

Thanks for all you done to make OMB PLi-friendly

[greatred]

Very interesting development, I`m eager to test it with vuuno.

Please advise if I can leave OpenPLi in flash and test a OBH as a multiboot image ?