Vu+ Real Multiboot Now Available

Ferbius said:
I would like to ask if it is possible to install the kexec multiboot without creating the slots in recovery?
Or is it possible to ensure that the slots created in 1.2.3 can be deleted from the multiboot screen and leave only those created on USB?!!


IT:
Vorrei chiedere se possibile installare il multiboot kexec senza creare gli slot in recovery?
Oppure se e possibile far si che gli slot creati 1.2.3 si possono eliminare dal schermata multiboot e lasciare solo quelle create su usb?!!
Click to expand...
The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.
- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need them)
 
Ev0 said:
Why do you want to do this ?

It can be done, but I don't understand your reason for wanting too.
Click to expand...
The reason is why I want all the space for recovery images that I normally use and use the images in the extra slots to play with them
You will say but pretend that the 3 slots aren't there... :)

IT:

Il motivo e perchè voglio tutto lo spazio per immagine di Ripristino che uso normalmente e usare le immagini nei slot extra per giocarci
Tu dirai ma fai finta che non ci siano le 3 slot ... :)
 
Liquid said:
The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.
Click to expand...

Liquid said:
- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need the
Click to expand...

Liquid said:
The procedure is complicated that's why has been created the utility to install it.

What you are asking is not supported but, but you can do that manally.
If you consider enough confident you can just install vuplus-multiboot as usual to convert the first image into a recovery image,
- then with sftp/ftp/ssh delete the STARTUP_x slot you don't want/need and rename the one you want to keep to the right sequence.
- you can edit subdir= entry inside each startup file and adjust it to stay aligned with the slot.
- take a backup of that STARTUP_x files (you might need them)
Click to expand...
ok thanks I'll do some tests but for me personally nothing more than to tinker around a bit.... I always back up the flash without multiboot ;)

IT:
ok grazie faccio delle prove ma per me personalmente niente di più che per smanettare un pò .... faccio sempre il backup della flash senza multiboot ;)
 
If I installed OpenMultiboot ( found in latest OpenBH 5.4.1.007 ) for old VU+ MIPSE 1.3 Ghz VU+ Duo2 - is it right or will have crashes?
 
The main fact about this new Multiboot (that is surely much better than the old OpenMultiboot) is that is not possible to choose an image at the startup. This is the only lack compared to OpenMultiboot.
 
Receiver VU DUO 4K SE. I flashed and selected multiboot, in the menu "menu - standby and reboot - multiboot" I see two options:
1. Recovery mode: boot to access recovery options
2. Slot 1 eMMC: OpenBH 5.4.1.008 (24-10-2024) (current).
Why did it install in slot 1, and not in slot 0? And how to transfer it
to slot 0?
 
garik1959 said:
Receiver VU DUO 4K SE. I flashed and selected multiboot, in the menu "menu - standby and reboot - multiboot" I see two options:
1. Recovery mode: boot to access recovery options
2. Slot 1 eMMC: OpenBH 5.4.1.008 (24-10-2024) (current).
Why did it install in slot 1, and not in slot 0? And how to transfer it
to slot 0?
Click to expand...
Slot0 in this multiboot solution is the recovery
 
garik1959 said:
But I pressed slot 0 and the receiver hung on Started Enigma, I had to reflash it. What should I have done?
Click to expand...
Paste the log from /home/enigma2/log so we could analyze..
Or you could have copied /STARTUP_N into /STARTUP to start the previous slot (using FTP or with telnet)
 
Hi
Since I have never set up multiboot and am a bit confused, I wanted to summarise.

1. I make an image backup of the current image.

2. I do a clean flash (from USB or via Image Manager?).

3. I only set up the network, password, resolution and nothing else.

4. After restarting, I go to Image Manager and from there I can flash the image I have selected.

Have I understood this correctly?

Additional question: can I restore the image backup made in point 1 via Image Manager?

And finally, if I make an image backup already having multiboot, how do I flash it using the traditional method via USB-disabled receiver, pressing standby, etc.? Will this erase the entire multiboot and everything will return to the standard settings as before multiboot?

Thanks for your answers, they may be obvious, but before I start playing around with this, I want to be at least somewhat sure that I understand it correctly.
 
OK,
I did something wrong.

I downloaded it in Image Manager and did a flash (fresh version).

After restarting and starting the flash, I was asked whether I wanted multiboot or normal, and I chose multiboot.

It said that it would take about 5 minutes for each slot, and then it would restart.

After restarting, everything froze on the start screen (immediately after booting), but I have access to telnet.

I wanted to do a clean flash from USB, but after turning off the receiver, it behaves as if it does not detect USB.

Can anyone help?
 
After several attempts and some Googling, I managed to get the system going again. But I can no longer use USB as a method for flashing.

According to Google, the reason is a corrupt kexec-multiboot

which takes control of how the system boots. Even changing the boot order in cmdline.txt does not help, because kexec-multiboot ignores it anyway.

Is there any way to return to the previous state, or is there any possibility of running recovery or something similar?

Code: 
root@vuduo4kse:~# cat /proc/cmdlinelibata.force=1:3.0G,2:3.0G,3:3.0G root=/dev/mmcblk0p9 rootfstype=ext4 rootflags=data=journal rootwait rw coherent_pool=2M vmalloc=622m bmem=630m@394m bmem=383m@1665m bmem=443m@2625m
root@vuduo4kse:~# cat /boot/cmdline.txtlibata.force=1:3.0G,2:3.0G,3:3.0G root=/dev/sdb1 rootfstype=vfat rootflags=data=journal rootwait rw coherent_pool=2M vmalloc=622m bmem=630m@394m bmem=383m@1665m bmem=443m@2625m
 
Kexec-multiboot doesn't alter the stb bootloader.

If the box refuses to flash from usb there could be multiple reasons:

- You put the zip on the root of the stick instead unzipping it by preserving the directory structure
- you put the usb stick into the wrong usb slot.. try using both front or back connector
- your stick have wrong partitioning or wrong filesystem. The filesystem needs to be FAT, the stick should be without partition.

Please double check
 
Liquid said:
Kexec-multiboot doesn't alter the stb bootloader.

If the box refuses to flash from usb there could be multiple reasons:

- You put the zip on the root of the stick instead unzipping it by preserving the directory structure
- you put the usb stick into the wrong usb slot.. try using both front or back connector
- your stick have wrong partitioning or wrong filesystem. The filesystem needs to be FAT, the stick should be without partition.

Please double check
Click to expand...
I will buy new USB stick, I check already 2.
I always place the unpacked image in the root directory. In this case, there is only one directory on the USB stick: “duo4kse” - that's my box.

I always format it to FAT32 using Windows File Explorer first.
And just one more: What is the EXACT correct force flash procedure for VU+ Duo 4K SE?
Thanks.
 
Liquid said:
Please double check
Click to expand...

You absolutely right!
Problem was USB stick (I got confused because I used 2, both faulty).
I get new USB stick, complete format Fat32 using Rufus and boom! Flash working from first try.

Thanks for clarifying that it's not Kexec-multiboot's fault.
That motivated me to get a new USB stick and continue working.
 
You must log in or register to reply here.
Back
Top