HowTo Vu+ Multiboot in OpenBh 5.2

hello.
i am a little confused about multiboot.

ultimo4k, vti in flash.

i tried neoboot, but then booting stopps every times.


so my quedtion, is it posdible to keep vti in Flash,
and bh and pli in flash or on hdd with this multiboot?

vg.
No,. because VTi does not support multiboot.

You will have to reflash, then reinstall VTi afterwards into a multiboot slot.
 
Hello

I have a problem I tried to install the Open Black Hole 5.3 I wanted to put some image in Open Multiboot but I have to have done something wrong now the receiver remains with the frontal display off and appears on the TV the skin of Open Black Hole but does not start I have Try with USB Sticks formatted and copied the Startup_Recovery turn off Reciver and turn on receiver with Usb stick inserted but does not change always appears on the TV the open black hole skin with the writing in the lower Starting Enigma2 ...

how can I solve?

Thank in advance
 
Hello. Replacing the file from post 1 (Multiboot.py) to the OpenAtv 6.4 image causes the image not to boot. It stops at the OpenAtv 6.4 bootlogo. Some solution?
 
I've been using VU+multiboot for a long time.
I have OpenBH 5.4.1, OpenPLI 8.3 and PurE2 7.4 in flash, no USB slots at this time.
I finally updated OpenPLI v8.3 to v9.1 with backup (SSD is inside).
Now everything is black, startup_recovery blank file doesn't help, and I can't even flash any image from the front usb stick in the classic way.
The front power button is occasionally blinking but that's all.
No telnet access either.
What to do?
 
I've been using VU+multiboot for a long time.
I have OpenBH 5.4.1, OpenPLI 8.3 and PurE2 7.4 in flash, no USB slots at this time.
I finally updated OpenPLI v8.3 to v9.1 with backup (SSD is inside).
Now everything is black, startup_recovery blank file doesn't help, and I can't even flash any image from the front usb stick in the classic way.
The front power button is occasionally blinking but that's all.
No telnet access either.
What to do?

You have few choices...

You can connect a serial cable (you can assemble it with simple instruction) to understand what is happening

Or you can prepare a fat32 stick prepare it with openbh image and flash the kernel (remove root.tar.bz) from /vuplus/boxmodel/ directory.

The box shuold restart with the original image you have in flash. (if this don't happen probably the flash process for unknown reason messed up the recovery image)

After the box would restart you can download /kexec-multiboot.log, you can try to read it to understand what was happening with multiboot.

In /linuxrootfs1, /linuxrootfs2, /linuxrootfs3 you can restore some file from the image you have in multiboot


Good Luck
 
Still no luck so I'll play with serial cable next week.
It doesn't sound good.... but if it doesn't start for unknown reason, restoring the backup corrupted the image in flash...
Restoring with serial cable could be difficult... I don't remember if it give to you a prompt...
 
Back
Top