474 replies to this topic

[Ev0]

OpenBlackHole 0.1 is working in Multiboot for me.

 

I just installed the image whilst in the flash image, and renamed it, so that it did not match the name of the image in flash.

 

So for me, it is called OBH 0.1

 

 grab.jpg   60.86KB   12 downloads

[bacicciosat]

Solo2 or duo2 ?

 

in duo2 i have a loop

 

open-multiboot - error: cannot open framebuffer device
open-multiboot - debug: remount /media into /omb/open-multiboot/OpenBlackHole-0.1-vuduo2_usb/media
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
open-multiboot - debug: mount /proc
open-multiboot - debug: mount /sys
open-multiboot - debug: mount /media
open-multiboot - debug: run volatile media
open-multiboot - debug: run mdev
open-multiboot - debug: check device /dev/sdb1
open-multiboot - debug: found data on device /dev/sdb1
open-multiboot - debug: discover images
open-multiboot - debug: load modules
/dev/dvb/adapter0/video0: No such file or directory
open-multiboot - debug: backup kernel for image 'OpenBlackHole-0.1-vuduo2_usb'
/dev/mtd2: No such device or address
open-multiboot - error: cannot open framebuffer device
open-multiboot - debug: remount /media into /omb/open-multiboot/OpenBlackHole-0.1-vuduo2_usb/media
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
open-multiboot - debug: mount /proc
open-multiboot - debug: mount /sys
open-multiboot - debug: mount /media
open-multiboot - debug: run volatile media
open-multiboot - debug: run mdev
open-multiboot - debug: check device /dev/sdb1
open-multiboot - debug: found data on device /dev/sdb1
open-multiboot - debug: discover images
open-multiboot - debug: load modules
/dev/dvb/adapter0/video0: No such file or directory
open-multiboot - debug: backup kernel for image 'OpenBlackHole-0.1-vuduo2_usb'
/dev/mtd2: No such device or address
open-multiboot - error: cannot open framebuffer device

[Ev0]

Solo2 or duo2 ?

 

in duo2 i have a loop

 

open-multiboot - error: cannot open framebuffer device
open-multiboot - debug: remount /media into /omb/open-multiboot/OpenBlackHole-0.1-vuduo2_usb/media
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
open-multiboot - debug: mount /proc
open-multiboot - debug: mount /sys
open-multiboot - debug: mount /media
open-multiboot - debug: run volatile media
open-multiboot - debug: run mdev
open-multiboot - debug: check device /dev/sdb1
open-multiboot - debug: found data on device /dev/sdb1
open-multiboot - debug: discover images
open-multiboot - debug: load modules
/dev/dvb/adapter0/video0: No such file or directory
open-multiboot - debug: backup kernel for image 'OpenBlackHole-0.1-vuduo2_usb'
/dev/mtd2: No such device or address
open-multiboot - error: cannot open framebuffer device
open-multiboot - debug: remount /media into /omb/open-multiboot/OpenBlackHole-0.1-vuduo2_usb/media
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
open-multiboot - debug: mount /proc
open-multiboot - debug: mount /sys
open-multiboot - debug: mount /media
open-multiboot - debug: run volatile media
open-multiboot - debug: run mdev
open-multiboot - debug: check device /dev/sdb1
open-multiboot - debug: found data on device /dev/sdb1
open-multiboot - debug: discover images
open-multiboot - debug: load modules
/dev/dvb/adapter0/video0: No such file or directory
open-multiboot - debug: backup kernel for image 'OpenBlackHole-0.1-vuduo2_usb'
/dev/mtd2: No such device or address
open-multiboot - error: cannot open framebuffer device

 

Working on Duo2 for me

I think it is important to install OBH into multiboot from flash, and also to rename it before you try to boot it so that the multiboot name does not match the name in flash.

[dany]

OpenBlackHole 0.1 is working in Multiboot for me.

 

I just installed the image whilst in the flash image, and renamed it, so that it did not match the name of the image in flash.

 

So for me, it is called OBH 0.1

 

grab.jpg

-all multiboot images have the right name into openmultiboot  plugin

- which image are u using in flash - obh or bh ?

i will test it now again because obh doesnot boot here- using vuduo2

-

Edited by dany, 8 June 2015 - 22:55.

[Ev0]

 

OpenBlackHole 0.1 is working in Multiboot for me.

 

I just installed the image whilst in the flash image, and renamed it, so that it did not match the name of the image in flash.

 

So for me, it is called OBH 0.1

 

grab.jpg

-all multiboot images have the right name into openmultiboot  plugin

- which image are u using in flash - obh or bh ?

i will test it now again because obh doesnot boot here- using vuduo2

-

 

 

Obh 0.1 in flash and using Duo2

 

I have used both fixes that bacciosat has posted.

 

The files posted on post #58 and also the file posted on post #68

 

I was in the flash image, when I installed OBH into multiboot too (I did try to do it first of all from inside OpenPli but it failed to boot then).

Edited by Ev0, 8 June 2015 - 22:59.

[dany]

it doesnot work here , it hangs on bootlogo

i used both fixes open_multiboot and OMBManagerInstall and renamed the image from OpenBlackHole 0.1 to OpenBlackHole-image

should i instal kernel-module-nandsim_3.13.5-r1_vuduo2 for obh too?

[bacicciosat]

Not working here too

Ev0 did you disabled animations or installed something in your obh in multiboot ?

[Ev0]

Not working here too

Ev0 did you disabled animations or installed something in your obh in multiboot ?

It is not working for me now either, since I booted to another image, it won't let me back in again.

So maybe I managed to glitch the matrix somehow when it worked before

But when it did work, both animations and xbmc worked.

Edited by Ev0, 8 June 2015 - 23:29.

[bacicciosat]

In the meanwhile i have patched the bootmenu.

 

Instructions are the same on the post n. #68 of this thred

Now all the names in bootmenu should be right and you should no need to rename images

 

 

Attached Files

•  open_multiboot.zip   63.86KB   87 downloads

[dany]

bacicciosat ,,, and you tell me that Ev0 is a great beta tester

 

i should be in his place

 

gentlemen really you are doing a great job .. lets continue testing   

i am always ready to share you

[Ev0]

bacicciosat ,,, and you tell me that Ev0 is a great beta tester

 

i should be in his place

 

gentlemen really you are doing a great job .. lets continue testing 

i am always ready to share you

lol

 

There is a way to get it working, if you see my screenshot there is 6gb flash.

 

It just seems it's not a consistent way to do it

[bacicciosat]

It seems to be in a paradox

Now OpenBlackHole seems to be able to boot every image from multiboot except OpenBlackHole.

 

Edited by bacicciosat, 8 June 2015 - 23:44.

[dany]

looooooooooooooooooool , really thank you all , I forgot my illness through my talk with you

 

there is some thing strange here

obh based on pli , and could today fix the pli issue .. now pli works very well , so whats the matter with obh

 

continue testing ....

Edited by dany, 8 June 2015 - 23:53.

[dany]

bacicciosat ... last fix ( open-mutiboot) works very well

it gives the correct name - even bootmenu works now if you boot from pli

really i wish if all images could show bootmenu , not only pli image

[bacicciosat]

dany not perfect.

It is added the number version at the end.

I will fix this too

[bacicciosat]

time to sleep.

I was thinking to remove the check about nandsim module so pli users will no need to install it to use the plugin

The kernel module nandsim is used to install new images but new images cannot be installed from Pli because branding module is not present.

So the plugin should work for standard operations without the need of nandsim.

[dany]

i just replaced the new fix - restart enigma2

when i boot from pli it showed me the correct name without numbers  for all images which were already installed in multiboot

before using last fix it was shwoing me wrong names forexample  instadeof pli it shows obh and even instadeof vti was showing obh

but maybe if i instal new image in multiboot it will added the number version at the end

[Ev0]

i just replaced the new fix - restart enigma2

when i boot from pli it showed me the correct name without numbers  for all images which were already installed in multiboot

before using last fix it was shwoing me wrong names forexample  instadeof pli it shows obh and even instadeof vti was showing obh

but maybe if i instal new image in multiboot it will added the number version at the end

You need to delete the images already installed in multiboot (you need to delete the multiboot folder and multiboot-upload folder from your usb or hdd). and reinstall multiboot to your usb or hdd, and then install the images again.

This is the only way to test this correctly.

[dany]

 

i just replaced the new fix - restart enigma2

when i boot from pli it showed me the correct name without numbers  for all images which were already installed in multiboot

before using last fix it was shwoing me wrong names forexample  instadeof pli it shows obh and even instadeof vti was showing obh

but maybe if i instal new image in multiboot it will added the number version at the end

You need to delete the images already installed in multiboot (you need to delete the multiboot folder and multiboot-upload folder from your usb or hdd). and reinstall multiboot to your usb or hdd, and then install the images again.

This is the only way to test this correctly.

 

i know that and you are right

but i am always doing the simple -fast ways to test -check any thing , sometimes succeeds very well and sometimes not

if not , then i start from 0 , by this way i could learn more

but if i

[bacicciosat]

Ok these are the latest fixes.

 

- bootmenu: remove version from image names

- no more needed kernel-module nandsim in Openpli images installed in multiboot

 

Instructions:

 

unzip files

- upload open_multiboot in the folder /sbin overwriting the original  (chmod 0755)

- upload OMBManagerInstall.py in the folder /usr/lib/enigma2/python/Plugins/Extensions/OpenMultiboot

 

Warning the changes will have effect only on the new installed images. So please delete previous image installations.