Jump to content


twol

Member Since 10 Apr 2012
Offline Last Active 19 Dec 2023 18:56
-----

Posts I've Made

In Topic: Enigma2 and BBC/ITV at 27.5W Intelsat - a big challenge

31 October 2023 - 10:02

never had a problem editing the lamedb in previous openpli images, something not happening with openpli 9

well it depends on which Editor you are using ... need something like Notepad. Also make sure you copy back as is...
 


In Topic: Wrong screen size after reboot

17 August 2023 - 22:09

I have a Sonos soundbar and LG Oled ... Sonos goes into hdmi Arc and Vu+ into hdmi1  ... no issue. Are you able to do that with your LG TV?


In Topic: Vu+ 4K Multiboot

16 June 2023 - 10:42

When OpenViX/Openbh introduced multiboot for the Vu+4k boxes in February, we worked as a team (of 4 people) both in developing the code and suggesting changes...... which I think was the key element in this implementation.

So the initial implementation has evolved - not through fixing bugs but through a desire to make the solution as user practical as possible.
We responded also to suggestions/comments from outside the team (even Rantanplan), so that after USB flashing (or flashing Recovery) most initialisation is done in the Wizard setup, where a user can choose to keep the Vu+ standard image (note Rantanplan !) or choose the multiboot solution.

If multiboot is chosen and there is no slot 1 image, then that is created, images in slots 1 -> 3 (eMMC slots) are restored (if users have chosen the backup option before flashing) and the wizard reboots to slot 1.
Before exiting the wizard the Recovery image is stripped (reduced in size and functionality) and setup so that on re entry to the Recovery image an Image manager screen is shown so users can delete, download and flash images just like you would for example on the Zgemma Recovery image.

Rantanplan points out that there have issues
- well the OpenViX/Openbh main code has been stable since March, with the subsequent code move to the Wizard in the last few weeks(hence the noted changes).
- OpenATV have different requirements (use of BoxInfo and flashImage) so implementation of the multiboot code has taken longer, but they only started  implementation in mid April on ATV Captains return. 


In Topic: Vu+ 4K Multiboot

12 June 2023 - 10:42

 

I didn't say that was the sole reason. We inspected the PLi image and know where the size differences are.

 

 

Excuse me?
Yes, that's exactly what you said and it's wrong.

Besides that, you can't compare a pli image to the OE Alliance, there are a few other things that are built differently here.

However, when I look at the OE-Alliance images, they got bigger in between and seem to have gotten a little smaller again with the last update of python and the environment.

So please again, your statement that an image will be 30mb larger because of a python update to 3.11 is not correct.
 

 

I spent a lot of time last week, comparing the size of the .pyc files on a Vu+ Uno4k SE with the installed OpenPli (python 3.9) and OpenViX/OpenATV (python 3.11) images.
Apart from really small python modules, typically the OE-A .pyc modules were 1.7 ---> 2.0 times the size of comparative OpenPli modules.

Obviously both the python developers and myself could be wrong, so I would ask that you post your comparative results from a Vu+ 4K receiver so they can be sent to the python developers for clarification.  


In Topic: Vu+ 4K Multiboot

29 May 2023 - 15:40

So just for my personal understanding of the VU+ Multiboot process, can someone explain where are the slot stored and what the dependencies are between slots?

 

I was thinking that it will be possible to create the slot on the HDD (I have SSD in my boxes) but it seems by reading your comment that the slots are created in the flash itself, but the flash is not partitioned like a true multiboot STB is.

So slot 0 contains it all and slot 1,2,3 are "fake" slot created into slot 0.

 

Is it correct?

 

Would it be possible to create the slot on the internal HDD?

On Vu4k when  you normally flash you have a kernel and root partition. In Vu+  kexec multiboot the  root partition still contains the original root - modified (Recovery/slot0 ) and also as you flash slots 1,2 & 3, directories linuxrootfs1, 2 & 3 are added which contain the slot root & kernel).

In OpenViX/Openbh a decision was made to add further slots on a removeable usb device as apart from anything else, it saves complications with it being used as a system device(it holds the image partitions) and a work(hdd). So using an internal/external device (even ssd) for both images and work (hdd) can lead to complications.