16 replies to this topic

[rhurbarb]

I have installed the latest Openpli image to a new Vu4kse and I was wondering if I need to install Blackhole first, or was that method used if you corrupted an Openpli install?

Thanks

Edited by rhurbarb, 12 October 2024 - 19:04.

[WanWizard]

Huh?

[rhurbarb]

I recall screwing my openpli image on a Dreambox or Vu receiver and to make Openpli work I had to load Blackhole image in 1st followed by openpli. Did I dream it?

Edited by rhurbarb, 12 October 2024 - 22:42.

[Tech]

Are you talking about an installation from scratch or is it a multiboot?

[WanWizard]

I can only imagine it maybe being relevant when using OpenMultiboot, which shares kernels between images, but in all other cases?

[rhurbarb]

Not multiboot just normal, from scratch. Back in the day I had to load a Blackhole image in after an openpli image install . Something was corrupted and I was told to do this which worked for me. I have loaded the Openpli image in and it seems ok but I was wondering what the Blackhole image had which the Openpli did not. Cheers

Edited by rhurbarb, 13 October 2024 - 20:33.

[Dorfkind]

Can´t understand anything, sorry...
If you're not talking about multiboot, each single image has nothing to do with the others.

[gintarasarm]

Take and install the first image from this site after then from the OpenPli site whichever you want

http://code.vuplus.c...model=vuduo4kse

Edited by gintarasarm, 13 October 2024 - 21:31.

[gintarasarm]

When you download from this site what I gave the image for your receiver do not forget to make an update via telnet Internet and after that install OpenPli image what  do you want

[WanWizard]

Why would you want (or need) to? Don't tell me we have to start fighting this kind of fake news now?

 

All my VU+ boxes never had anything else flashed than OpenPLi.

[littlesat]

I still do not understand the issue you experience at all...

 

For VU+ you can initiate multiboot via the screen where you flash the images.... once and only when initiated you also have the multiboot option at boot select screen in the power management menu (menu last option). After installing it from the flashimage menu you can flash a different slot from that same screen...

 

Other images have always the multiboot option in the power management menu, even when multiboot is initiated/installed.... That was why I thought flash-image is a better and smarter place place to locate the multiboot initiated.

Maybe you just did not find the option in OpenPLi?

Edited by littlesat, 14 October 2024 - 14:10.

[gintarasarm]

@littlesat  I think his question was what factory image should be used to flash the Vu+ box before installing another image? That's why I gave him a link to the factory image for Vu+ since many forums said that you first need to flash the Vu+ with the factory image and only then install the image you want... but then @wanwizard explained that you don't need to flash any factory image, but just flash the image you want... I think that's exactly the question he had

[WanWizard]

The correct answer is "None". There is indeed no benefit in flashing A before flashing B, flashing from USB erases the full flash chip, and its partitioning. No matter what was there before, the bootloader will wipe it all.

 

( In PC terms, it is equivalent to wiping a complete disk device with dd, then create new partitions using fdisk, then using dd to write disk images into those partitions )

 

Having said that, it is possible to flash only specific partitions, like only the kernel, or only the root filesystem, by omitting files in the flash directory (created from the zip). In that case, the partioning is left in place, and must match the partioning expected.

If it doesn't, it might write over partition boundaries (the bootloader doesn't check size), resulting in a non-booting box because the rootfs is damaged.

 

This is only a problem if an image from an image builder is flashed that has altered the manufacturers partition scheme. This can be remedied by flashing a full image, from any image maker using the standard manufacturer partition (which OpenPLi does).

Edited by WanWizard, 14 October 2024 - 16:16.

[gintarasarm]

@WanWizard, 

Thank you very much for your detailed and clear answer!

Edited by gintarasarm, 14 October 2024 - 17:34.

[rhurbarb]

Maybe I did use multiiboot in the past. Was a long time ago. Thanks for explaining guys. Cheers

[WanWizard]

Te be clear, this is about solutions like OpenMultiboot or MeoBoot. Not about a multiboot using boot partition separation.

 

An image consists of two components: the linux kernel and the rootfs.

 

A true multiboot system use both for each boot environment, so that when you select an image to boot, the correct kernel is started, the one that belongs with that rootfs.

OpenMultiboot and other software solutions however use only one linux kernel, the one the box was flashed with, and uses software tricks to have multiple Enigma versions in a single filesystem.

 

Which means you can have a mismatch between kernel en libraries, and this is particularly a problem when you have an older kernel with newer libraries.

Hence the advice to flash something other than OpenPLi release, as our release images are stable and not bleeding edge, under the assumption that "newer" is backwards compatible with "older".

 

Which isn't always true, which in turn is why we don't support software multiboot solutions...

[rhurbarb]

Thank you for explaining that. Understood. Cheers.