474 replies to this topic

[dany]

i am using vuduo2

and i am ready to do any test .. donot worry

[dany]

Hallo bacicciosat

bad news .... even openblackhole doesnot work on openmultiboot
when restart the box ... it hangs on (blackhole splash screen) bootlogo
and i think this is normal because this image is based on pli .. so they have the same issue

i did other test ... when i tested before openatv on flash and used openmutiboot ,i installed these images vti , openatv , vix
i backed-up them all to my hdd ... i used telnet for backup
few minutes ago i reflashed the box with openblackhole .. format the usb stick
and i could restore all backed-up images to the usb .. and they all work very well
so ... is openblackhole and openatv have the same openmutiboot files ? i think so , and they have the same version too (1.0+git83)

thank you

[bacicciosat]

Sure dany, i builded a module to make OBH compatibile with OEA plugins (branding) so we can use in OBH the official version of OpenMultiboot like openatv.

I have only patched it to fix the issue of volatile-media for pli and obh.

I have checked now the installation on Duo2 and yes i confirm your issue. This is a bug affecting OpenMultiBoot official version that doesn't work with OpenPli in Vudo2.

 

Here is the serial log.

We have a nice KENEL PANIC

open-multiboot - debug: backup kernel for image 'OpenPLi-4.0-beta-vud+-----------------------------+
[VID]: VIDEO_SET_STREAMTYPE 0 
[VID]: VIDEO_SELECT_SOURCE 1  0
[VID]: VIDEO_PLAY 1  2 0
ECC failed: 0
ECC corrected: 0
Number of bad [VID]: VIDEO_CONTINUE 1  1 
blocks: 0
Numbe[VID]: VIDEO_CLEAR_BUFFER 1  1 0
r of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00700000...
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  0
open-multiboot - debug: the framebuffer device was opened successfully
open-multiboot - debug: current mode is 1920x1440, 32bpp, stride 7680
open-multiboot - debug: current mode is 1280x720, 32bpp, stride 7680
open-multiboot - debug: the framebuffer device was mapped to memory successfully
open-multiboot - debug: set color palette
open-multiboot - error: failed to set color palette
open-multiboot - debug: set manual blit
open-multiboot - debug: input device opened
open-multiboot - debug: current lcd is 140x32, 8bpp, stride 140
[VID]: VIDEO_SET_STREAMTYPE 0 
[VID]: VIDEO_SELECT_SOURCE 1  0
[VID]: VIDEO_PLAY 1  2 0
[VID]: VIDEO_CONTINUE 1  1 
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  0
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000a

Rebooting in 180 seconds..

[dany]

i think you have other solution , I do not know if you had read my comment in the Previous Page comment 56 and here is again :

when i tested your meoboot 1.0-r14 .. the pli image was worked very well  , but then i had problem with vti image ,, couldnot use dcc or putty -no cennection (disconnection)

and always when i click on meoboot plugin i got this error : sorry , meoboot can be installed or upgraded only when booted from flash

and i think you could fix the disconnection issue and build new version of meoboot to work with all images

Edited by dany, 7 June 2015 - 23:01.

[bacicciosat]

I think we have to go with openmultiboot that is better.

But don't worry i am in touch with the author and will sort the issue that affect duo2.

[Dimitrij]

Same problems for solo2.
Maybe they are related to the not native nandsim?

Edited by Dimitrij, 8 June 2015 - 15:47.

[bacicciosat]

no no solo2 here work fine.

[bacicciosat]

Hallo bacicciosat

bad news ....

 

Hi Dany, i have fixed (thx to skaman)

The fix will be included in the next image updates.

 

In the meanwhile here is a workaround solution.

 

Instructions:

1) Flash your duo2 with latest OBH

2) BE SURE TO DELETE ALL THE PREVIOUS OPENMULTIBOOT FOLDERS FROM YOUR HDD AND USB

3) before to start the plugin unzip this file and upload it in /sbin (you have to overwrite the original) and be sure it is executable (chmod 0755)

4) Run OpenMultiBoot plugin abd install from it Openpli image

 

You should have working all the images you will install.

 

Boot and reboot all the times you like

You will have also the bootmenu available when you will boot from Pli (not in boot from images with OpenGL libs).

 

If you want to run the plugin from openpli too remember to install in PLi the kernel module nandsim.

Attached Files

•  open_multiboot.zip   63.87KB   130 downloads

[bacicciosat]

@ dany, forgot...

don't install new images from multiboot, remember to install new images from flash.

 

@Dimitri.

The issue fixed is related only to duo2.

The duo2 with the original plugin can boot all the images except Pli because other images have OpenGl libs installed.

The images with Opengl lib installed cannot run the bootmenu so they boot succesfully.

Pli image run the bootmenu. But the bootmenu try to write to the lcd and it is not compatible with Duo2 double lcd (VFD + grahpics) so when OpenMultiBoot try to boot from Pli it crashes at bootmenu stage and cause a kernel panic.

This fix disable the lcd so OpenBootMenu can boot also from Pli without issues.

[dany]

Hi bacicciosat

- i just overwrite the attach file (ope-multiboot) - and restart the box

- install pli image

- install kernel module nandsim

- reboot the box many times ,, its ok now

 

note- i didnot reflashed my box or deleted the multiboot images in usb .. i leaved every thing as before . just overwrite the attach file and instal pli in usb

as i said pli image now works very well .. i tried to use the bootmenu to boot other image but the box hangs on bootlogo

i think i should do what you asked .. i must reflash my box - format usb - and donot use the multiboot images

[dany]

 Hi bacicciosat

i am doing just few tests

- i reflashed the box and overwrite the attached file

- still using the muttiboot images in usb ... they all work now very well

- i see the bootmenu just when i boot from pli

- if i use the bootmenu to boot other image .. the box reboot and hangs on bootlogo

my questions -- is that because i am still using the multiboot images , is it possible to use bootmenu

[bacicciosat]

Hi dany the boot menu is working here with the new images installed after the fix.

But maybe Ev0 can reply better than me about tests.

He is the better tester in the world i think

[dany]

really thats a great bacicciosat

but I am very sick today

maybe iam doing some thing wrong ..

i did what you asked - new reflash-format usb-overwrite the attached file-instal pli in usb -install kernel module nandsim- and instal openblackhole in usb

but i noticed you still have bugs in the fix file

- openblackhole still not work on openmutiboot in usb .. the box hangs on bootlogo

- i didnot see pli image on the bootmenu list , it was by this way ...openblackhole (flash) .. under it openblackhole-0.1 under it openblackhole 0.1

so he write openblackhole twice instadeof pli image

i saw the pli image on bootmenu list just after i reflased the box again - used the fix file - insert the usb reboot the box

 

i am very ill today - but i will try it again .. maybe i did something wrong

[bacicciosat]

No dany you are not doing something wrong.

There is an issue with the names in bootmenu because OpenMultiboot was wrote for OEA images and get image name and version from branding module.

But Pli has not the branding module so bootmenu don't know what is the name of the image and assign to it the name of the image in flash.

But if you select it also if the name is wrong it should work.

[bacicciosat]

Maybe i will patch the bootmenu too to try get the right names instead to use module.

But now i have to take a break.

 

I reflashed thousands of times, lose sleep hours and fired one nice usb tuner TURBO during one of the kernel panics.

[dany]

No dany you are not doing something wrong.

There is an issue with the names in bootmenu because OpenMultiboot was wrote for OEA images and get image name and version from branding module.

But Pli has not the branding module so bootmenu don't know what is the name of the image and assign to it the name of the image in flash.

But if you select it also if the name is wrong it should work.

Hi bacicciosat

Of course you have a long experience in this field

I'm going to do all over again - step by step to be sure

but iam sure that openblackhole doesnot work in usb  and i will check bootmenu

[bacicciosat]

Yes obh doesn't boot.

i have checked it now.

[dany]

Maybe i will patch the bootmenu too to try get the right names instead to use module.

But now i have to take a break.

 

I reflashed thousands of times, lose sleep hours and fired one nice usb tuner TURBO during one of the kernel panics.

really iam very sorry for that , i didnot saw this comment

but to see the right name ,.... first install all images in usb , remove usb from rear- reflah your box - put your usb in the rear of box 

[Ev0]

@dany

 

If you use the rename option in OpenMultiboot, you can give each image (except flash) it's own name.

 

Then the bootmenu will name the images correctly for you.

[dany]

Ev0 .. thank you , i know that , I just wanted to let you know the results