592 replies to this topic

[dpeddi]

This is exactly how it should not be done as it is an exception and the boot partitions locations are hardcoded as exception for vu+ in enigma2.

It seems you didn't fully understood the PR.
I suggest you to boot openpli from a openbh or openvix and troubleshoot enigma2 crash

[littlesat]

But it is still kind of hacky…. Stuff needs to be moved to the correct location and not that it just works… I was already afraid that stuff was inside that is hacky and at a level it works so no need for finetuning. To do this really good we also need a kind of recovery image.

And I really understand the patch…: but I also understands it needs some improvement.

Adding hardcoded stuff at that location in e2 should be avoided and also if x is seen the do y….. and that is what the code currently does. Box depended stuff we prefer to have in SystemInfo.py and this is doable also for the vu+ multiboot. You will see once you do it the code also most likely becomes more readable.

Edited by littlesat, 25 March 2023 - 17:37.

[twol]

But it is still kind of hacky…. Stuff needs to be moved to the correct location and not that it just works… I was already afraid that stuff was inside that is hacky and at a level it works so no need for finetuning. To do this really good we also need a kind of recovery image.

And I really understand the patch…: but I also understands it needs some improvement.

Adding hardcoded stuff at that location in e2 should be avoided and also if x is seen the do y….. and that is what the code currently does. Box depended stuff we prefer to have in SystemInfo.py and this is doable also for the vu+ multiboot. You will see once you do it the code also most likely becomes more readable.

@Littlesat - the Vu+ Multiboot implementation is simplicity itself.

Stupidly, I tried to make it easy for OpenPli by specifying the location of the STARTUP files, saving the troll through the normal boot devices (which works transparently  for all but the Zero4k, Duo4k).
Obviously in the OE-A with boxbranding, you just specify the specific root partition for Vu+ Multiboot, but as you don‘t support that, the possible partitions were  hardcoded for Openpli……just as  you do for the boot partitions in Multiboot.py .
Again stupidly,  for the benefit of OpenPli users, I added the UUID routine so they could also use a usb device to extend their capabilty to handle images.

Apart from the multiboot.py code,  the rest of the code sits in SystemInfo and a simple python routine to initiate multiboot  if thats what the user wants.
All in, we are talking about around 100 lines of code.
 

Compared to the hassles  with the sf8008, it really is simple.

Edited by twol, 25 March 2023 - 19:47.

[neo]

I can personally live with different partition names, there are enough differences between hardware. That is why there is an abstraction layer. Indeed, like OE-A's boxbranding.

 

If correctly implemented I don't see any issue with supporting it.

 

What we do miss is the update to the BSP, so two images are created: one to flash the box and create the partitions, and one that can be flashed into a partition with ofgwrite.

 

Without that the E2 changes are useless, it is rediculous to have to say to users that they should flash another image if that want this multiboot solution.

[Huevos]

I can personally live with different partition names, there are enough differences between hardware. That is why there is an abstraction layer. Indeed, like OE-A's boxbranding.

 

If correctly implemented I don't see any issue with supporting it.

 

What we do miss is the update to the BSP, so two images are created: one to flash the box and create the partitions, and one that can be flashed into a partition with ofgwrite.

 

Without that the E2 changes are useless, it is rediculous to have to say to users that they should flash another image if that want this multiboot solution.

So, you don't get it. The image you flash the box with is not a recovery image, it is a complete image. Then you flash other images into the created slots. There are not 2 images (one to flash the box and create the partitions, and one that can be flashed into a partition with ofgwrite). So once you load the complete image you can use ofgwrite to load the exact same image into a slot. And the second thing you don't seem to understand is the flash is not partitioned.

Edited by Huevos, 25 March 2023 - 23:06.

[Ev0]

There are NO partitions created at all.

If you were to put an image in slot 1 and filled it with plugins and used up all 3GB+ of free space, then you couldn't add another image into slots 2 or 3 on flash, you would need to edit the STARTUP_2 and STARTUP_3 files and point them to the usb stick instead (or just delete the STARTUP_2 and STARTUP_3 files manually and create new usb slots).

Edited by Ev0, 25 March 2023 - 23:07.

[neo]

So, you don't get it. The image you flash the box with is not a recovery image, it is a complete image. Then you flash other images into the created slots. There are not 2 images (one to flash the box and create the partitions, and one that can be flashed into a partition with ofgwrite). So once you load the complete image you can use ofgwrite to load the exact same image into a slot. And the second thing you don't seem to understand is the flash is not partitioned.

 

Did I use the word "Recovery image"?

 

I said the BSP needs adapting so an USB image is created that creates the flash partitions (or the partition that contains the slot directories), as the current image doesn't do that. And we need a udev change to make sure that partition isn't mounted.

 

If you can have one image file both both USB and multiboot flashing, that is only a plus.
 

Edited by neo, 25 March 2023 - 23:32.

[Huevos]

 

So, you don't get it. The image you flash the box with is not a recovery image, it is a complete image. Then you flash other images into the created slots. There are not 2 images (one to flash the box and create the partitions, and one that can be flashed into a partition with ofgwrite). So once you load the complete image you can use ofgwrite to load the exact same image into a slot. And the second thing you don't seem to understand is the flash is not partitioned.

 

Did I use the word "Recovery image"?

 

I said the BSP needs adapting so an USB image is created that creates the flash partitions (or the partition that contains the slot directories), as the current image doesn't do that. And we need a udev change to make sure that partition isn't mounted.

 

If you can have one image file both both USB and multiboot flashing, that is only a plus.
 

 

Nothing "creates the flash partitions" as explained several times above.

 

Commits for core are here: https://github.com/o...nds/meta-vuplus
 

Edited by Huevos, 26 March 2023 - 01:31.

[Abu Baniaz]

It is highly recommended to install OpenBh 5.2 onto your Vu+ 4K box, and just setup the basic features (image resolution, network connection and set a password in telnet etc, you do not need to setup tuners as they will not be used) but not to install ANYTHING else into the image as it is best to keep the installation as small as possible.

This image will be the "base" aka Recovery image for your box.

It should NOT be used for daily use or viewing tv as it is purely for setting up the Vu+ Multiboot environment, and the only other time you should need to use the Recovery image, is if you manage to mess something up and your box will no longer boot.

 

 

Noted the above comment. What is the official name of the above image which we are not meant to fully configure/use?  base, recovery or is there anything else

 

If no partitions/slots are created, where are the other images stored please?

Edited by Abu Baniaz, 26 March 2023 - 02:03.

[Ev0]

 

Noted the above comment. What is the official name of the above image which we are not meant to fully configure/use?  base, recovery or is there anything else

 

If no partitions/slots are created, where are the other images stored please?

 

You can call it Nigel if you want, it really doesn't matter, I just referred to it as Recovery image for simplicity.
 

The images are stored within the free space in the flash, or usb (depending on where you have chosen to create the slot for it).

Edited by Ev0, 26 March 2023 - 02:09.

[neo]

If I understand the E2 PR correctly, the images are stored in directories of that "base" image, in the only partition the VU+ emmc has, together with STARTUP information in the root of that partition.

 

Because it is a full image, it makes all that visible and accessable for end-users, which is imho a massive downside of this solution. An "it should not be used" warning doesn't stop any end user.

 

Ideally, we should make a minimal bootable image (as a sort-of recovery image), which only gives the option to either boot a slot, or flash a slot), and install that as the base image.

[neo]

The images are stored within the free space in the flash, or usb (depending on where you have chosen to create the slot for it).

 

How and where do you "choose" where to make those slots? If I ask about the fact such a the mechanism must exist, I get responses like I'm mad...

 

Not a big fan of allowing installation on removable media. Nice for testing for the people here, dangerous and undersired for end-users.

Edited by neo, 26 March 2023 - 02:13.

[Ev0]

Ideally, we should make a minimal bootable image (as a sort-of recovery image), which only gives the option to either boot a slot, or flash a slot), and install that as the base image.

Agreed, that would be the perfect solution, who is going to do it though ?

[Ev0]

 

The images are stored within the free space in the flash, or usb (depending on where you have chosen to create the slot for it).

 

How and where do you "choose" where to make those slots? If I ask about the fact such a the mechanism must exist, I get responses like I'm mad...

 

When you enable the Vu+ Multiboot, it will create 3 STARTUP_x files, which are pointing to the flash (eMMC), then you have the option to add extra slots to USB (if you have a usb stick mounted).

I have previously managed to fit 4 images into the eMMC, however this then means there isn't that much free space to play with, because the more you install in 1 of the images, the less space is free in the others (flash is around 3.5GB total, so with several images, it's easy to fill the flash), hence it was decided to limit it to 3 slots, as this would give "most" users enough free space to fully setup 3 images how they wish too.

The 3 auto generated STARTUP_x files can be edited (manually) to use the USB stick instead though (I only have STARTUP_1 using eMMC) and then STARTUP_2 and 3 are using USB on my boxes (and on the ultimo4k I have another 26 iirc USB STARTUP_x files) giving me a total of 28 images installed on the USB stick.

 

This means, with the "base / recovery" image installed and 1 image in Slot 1, with all my plugins/cams/settings etc etc I have around 2GB free space in flash still, I could install another image here, but as I have a 64GB USB stick connected, I don't see the point in filling up the flash when I don't need too.

[Abu Baniaz]

Apart from the Nigel image, how many slots are you allowed on the internal flash memory? Are you able to specify the sizes of these slots.

[neo]

Agreed, that would be the perfect solution, who is going to do it though ?

 

I'll have to think about it.
 
Making a minimal image in itself isn't a problem, I already have one like that which only contains oscam,. which I run on an old box as cardserver.
 
The challenge is to make a fail-safe minimal GUI like the recovery screens for the other brands, without having to pull half of Enigma in...

Edited by neo, 26 March 2023 - 02:21.

[neo]

When you enable the Vu+ Multiboot, it will create 3 STARTUP_x files

Where is this "enable" switch?

 

So, I have a USB stick, I download and unpack an image zip on it, plug the stick in, boot the box and press the button to start flashing. And then, where do these multiboot options magically appear?

Edited by neo, 26 March 2023 - 02:23.

[Ev0]

 

When you enable the Vu+ Multiboot, it will create 3 STARTUP_x files

Where is this "enable" switch?

 

Shutdown menu, where you would normally find the Multiboot Selector, once enabled the option vanishes and is replaced with the Multiboot Selector.

[Ev0]

Apart from the Nigel image, how many slots are you allowed on the internal flash memory? Are you able to specify the sizes of these slots.

See post above

[Abu Baniaz]

 

Apart from the Nigel image, how many slots are you allowed on the internal flash memory? Are you able to specify the sizes of these slots.

See post above

 

Sorry, still not clear on sizes of slots. Is it Nigel + 3 dynamic sizes, or total of 3 dynamic sizes? And are all those on the one partition of the internal flash memory? And if so, how are the areas that the different images occupy segregated?

Edited by Abu Baniaz, 26 March 2023 - 02:38.