twol

Excuse my usual intrusion, but multiboot is of little use to the normal user because actually switching from one image to another for the simple sake of doing it is absolutely ridiculous!
What is it for the normal user?
It is only useful for those who are curious about the "profession".
I understand that it is a "challenge" but only for......

krime mobile.

For the normal user ( whoever that may be) there are some basic uses of multiboot….
1) upgrade to a new version without replacing the working image, means that the user minimises any issues with the new release.
2) some users still want python2 plugins that haven,t or cannot be converted to python3, so running both a python 2 and python3 image is possible with multiboot.

3) some normal users even have  sufficient interest to try other images, whilst keeping their existing image.
 

Of  course  some users will just accept what they are given.

@rantanplan
@littlesat

 

Obviously neither of you have tried it.
There are no changes to the current OE-A builds for the Vu+ 4K boxes, other than a couple of additions. So No changes to Vu+ bootloader, no changes to flash or partition layout
..... and as it just builds off the current multiboot implementations in most images, can host images in a multiboot environment without changes where eMMC slots are being utilised.

.. and if someone wants to revert to the standard one image Vu+ partition,  that can be done quite simply by a straight forward image flash.

 

 
 

@Marchella, hdmicec - have you tried changing the wakeup call (imageView on or Textview on)?
Its not a hisilicon issue - it maybe an issue getting the 2 devices to talk correctly.
I have Zgemma H9 Combo (non se) and H9S se (same chipset as H10) and handle hdmicec perfectly normally in both my setups (one of which is direct to LG Oled55c9). Debug logs show quite normal hdmicec interchange.

I am not using OpenPli on H9S se but hdmicec code is so similar across images I wouldn‘t expect this to be an issue.

What are the urls we can add… and please note the boxnames could be different… deviate from manufacturer’s bsp.

Maybe this will help…..
config.imagemanager.imagefeed_ViX = ConfigText(default="https://www.openvix.co.uk/json", fixed_size=False)

config.imagemanager.imagefeed_ATV = ConfigText(default="http://images.mynonp...m/openatv/json", fixed_size=False)

 

some box names are different between OE-A images and OpenPli

Just to show how unbiased we are on OpenViX!!

Try switching tuners around (physically) so dvb-s2 card is in position A - so sat then are in tuners A -> H numerous issues reported with tuner cards in „wrong“ slots

you should new flash & reset up or nim settings likely to be messed up

if I upgrade I want it all to work

need to have 2 x sat

whats the best Zero4K ?

 

I always used vu+ boxes

 

are there these days any better alternatives?

There are many alternatives all offering better price/performance - depends exactly on your requrements. Out of the boxes I have (see signature) I would choose the AX HD61, alternatively  I guess Octagon sf8008. If you prefer a FBC tuner receiver then its Gigablue or Vu+.

@Dimmie

"bachupsuite" is obviously a typo. I had typed backupsuite correctly in two other places in the same post.

 

@twol

I installed openvix and the backup appeared to be progressing successfully with three temporary folders fully created under /media/hdd/imagebackups.

 

However, that too failed with

 

"Image manager

Error: Timeout elapsed, sorry"

 

The temporary folders remain. Unfortunately the "release" folder is not populated.

Any ideas?

 

OpenVIX full backup appears to backing up all four images on the box.

 

under "root" there is

linuxrootfs1

linuxrootfs2

linuxrootfs3

linuxrootfs4

 

and each of these folders appears to contain the full file structure of the four images I have installed.

 

Is this why it is taking so long and "times out"?

 

Only the image selected is backed up

What device are you backing up to? ... if its slow it might need an extended timer.

The backup does take a long time for some of these HisIlicon receivers.

Suggest rather than waste time here on OpenPli forum, you post on the ViX forum and we can sort it there

It would be worth selectively editing this post and using it as a HDD selection sticky - with my background I thought I knew most things about disks - but shows how quickly you can miss something and be out of date.
Really useful information that makes you think hard.

Both OpenATV and OpenViX can build a USB flashable zip containing the active image - not aware of any OpenPli facility to do this ... but obviously if you backup all your settings/plugins (to a device that can be accessed later) you can use the OpenPli qick restore mechanism at boot time..

Both OpenATV and OpenViX can build a USB flashable zip containing the active image - not aware of any OpenPli facility to do this ... but obviously if you backup all your settings/plugins (to a device that can be accessed later) you can use the OpenPli qick restore mechanism at boot time..

If you use the USB flashable zip, then the active image is in slot 1

 

You can install OpenATV from openpli by putting the image in the root of the USB as ZIP file as you download it from their website... so not unpacked..

 

I understand these will be OK?

http://images.mynonp...p?open=mutant51

The OpenATV ZIP contains hd51 folder which contains disk.img, imageversion, kernel.bin and rootfs.tar.bz2 files.

 

All OE-A image zips for the HD51 contain a disk image, kernel and root files, so you can USB & Online flash.  OpenPli provides a usb image flash zip (disk.img) and a multiboot image zip (kernel plus root)

You have to remember that OpenATV (and the OpenATV image clones) use code that was written well over 2 years ago when the 1st multiboot receiver HD51 was released - zgemma just copied the same approach.

Both OpenPli (with FlashImage) and OpenViX (ImageManager) tell you which slots are empty and if occupied which Image is installed (OpenViX will also give you the Image version/date/Dev build, depending on the Image installed) - so you use a similar procedure to get the image onto the receiver and then choose the appropiate slot to flash - no need to remember what is installed in STARTUP_x

2 options:-
USB flash using the OpenPli usb version with the disk.img.
Or.... if you have OpenATV installed, copy the OpenPli multiboot version to a directory and use the OpenATV Imageflash (use the „local“ button to find the directory containing the OpenPli zip file) and then flash it to slot 1.

the usb version only needs the disk.img which contains the kernel & root already inside the image.

 

Did you use a loop through cable from output tuner A to input Tuner B? The tuners don´t have an internal connection

 

Tuner B is also configured for unicable with a different SCR?

The Tuner B is configured equal to tuner A,

the antenna cable is connected to a switch with 4 outputs but i only have a connected cable that comes down to the decoder.,

I tried to change the scr 1/2/3/4 but it does not resolve, I also tried to connect the antenna cable to the tuner B of the decoder but the problem remains

 

You need tuner A & B with different scr's

And that's probably the reason ATV created one HbbTV plugin that runs on all boxes?

It would be nice if they open sourced/shared it then, so everybody can use it (just like OpenPLi shares everything with everybody)..

True, and I think that's the case as ATV is Open Source (but not sure); worth a good look.

You are wrong. Hbbtv from OpenATV is not open source (yet).

I find that strange as it is part of the OE-A, so any receiver that has support can install the qthbbtv plugin, in any of the OE-A images. Whilst OpenPli is not part of the OE-A surely it must be easy for Openpli to install??