592 replies to this topic

[Guest-*0823016*]

Simply. What do you need the multibot for???

krime mobile

[Guest-*0823016*]

It's math... I have I have the others.

krime mobile

[Huevos]

Simply. What do you need the multibot for???

krime mobile

This thread is not about the usefulness of multiboot. That discussion was years ago and PLi decided to include it.

[neo]

If you don't need it, don't use it. It is that simple.

 

As a developer / tester, it is invaluable, it always gives you a working image to fall back to.

[40H3X]

So maybe only NB and and behind expert mode.

[littlesat]

That discussion was years ago and PLi decided to include it.

 

​Actually I implemented it originally for OpenPLi and it costs me a lot of discussion/streamlining to get something 'universal' over different brands. Also regarding the online flash which was also part of that project already years ago. I tried to do it in a most structural way as e.g. the OE-A images had it, but less structural. Therefore I'm also careful when making exceptions for manufacturers, but I slept on it and I think adding a kexec feature to it can be done... This is actually a standard by itself ...

 

I use the multiboot many times for development. So I can work in a development slot... and when I watch TV I can quickly go to a working slot .... when the user interface is somehow stuck in the experimental image most times I can quickly switch to the stable image via the Recovery screen.... Still an important feature what is missing here, as now the only method to go back to the working and stable image is hoping you still can access the box via putty/telnet and arrange that after a reset/reboot that stable image can still be selected without reflashing the complete stuff. So for me personally the feature is only really useful when a recovery method is included. 

Edited by littlesat, 29 March 2023 - 12:56.

[neo]

That was my reason for saying a recovery image of some sort is needed, because if the currently selected slot doesn't boot, you're stuffed as there is no way to select another image.

 

The "official" multiboot hardware has a physical switch or a remote button for that. As that is bootloader functionality, we can't implement something similar.

 

If it still boots we as experts might be able to do something with telnet or ssh, but you can't expect an end-user to have that expertise.

Edited by neo, 29 March 2023 - 13:37.

[Ev0]

That was my reason for saying a recovery image of some sort is needed, because if the currently selected slot doesn't boot, you're stuffed as there is no way to select another image.

 

The "official" multiboot hardware has a physical switch or a remote button for that. As that is bootloader functionality, we can't implement something similar.

 

If it still boots we as experts might be able to do something with telnet or ssh, but you can't expect an end-user to have that expertise.

You can put a blank file named STARTUP_RECOVERY onto a usb stick, put it in the box and reboot (power off, or press and hold power button on remote for 12 seconds) to force a reboot, it will then boot recovery.

[neo]

Ah, ok, so there is a work around. Good to know, thanks !

[Ev0]

Ah, ok, so there is a work around. Good to know, thanks !

You can do the same thing with hdd or mounted ext4 usb if you boot an image that doesn't have a multiboot selector, to get out of the image.

Once in the recovery image just remember to rename or remove the file, otherwise the box will always boot recovery image.

[neo]

Once implemented someone has to go through this topic and create a wiki page with all this information .

[Dimitrij]

Vu Multiboot - init

 

I must have made a mistake somewhere.

What's maybe wrong?

Or maybe someone else will make the correct patch.

[twol]

Vu Multiboot - init

 

I must have made a mistake somewhere.

What's maybe wrong?

Or maybe someone else will make the correct patch.

So what error do you get because this is a pretty straight forward implementation … the only issue is that the startup file is a  zip (gz) that I had to rename to stop the build unzipping it.

[twol]

 

That discussion was years ago and PLi decided to include it.

 

​Actually I implemented it originally for OpenPLi and it costs me a lot of discussion/streamlining to get something 'universal' over different brands. Also regarding the online flash which was also part of that project already years ago. I tried to do it in a most structural way as e.g. the OE-A images had it, but less structural. Therefore I'm also careful when making exceptions for manufacturers, but I slept on it and I think adding a kexec feature to it can be done... This is actually a standard by itself ...

 

I use the multiboot many times for development. So I can work in a development slot... and when I watch TV I can quickly go to a working slot .... when the user interface is somehow stuck in the experimental image most times I can quickly switch to the stable image via the Recovery screen.... Still an important feature what is missing here, as now the only method to go back to the working and stable image is hoping you still can access the box via putty/telnet and arrange that after a reset/reboot that stable image can still be selected without reflashing the complete stuff. So for me personally the feature is only really useful when a recovery method is included. 

 

@Littlesat - thinking you are missing the fact that there is a recovery image - the first one installed. 
Unfortunately, when I wrote the python code(constantly corrected by the  rest of the OpenViX/OpenBH team) , Recovery is  constantly treated as slot 0 (which once multiboot is initiated it occupies).
During ALL the testing, I have never not been able to get back to this Recovery image……either through choosing Recovery in MultiBootSelector(as you would for any multiboot receiver with a Recovery option), or bad image …..it boots recovery, or choose image on usb (and pulled) .. boots to Recovery. 
So its pretty resilient … and I hammer these multiboot boxes pretty hard during testing …..and as sometimes my code broke the multiboot, if anybody was going to have issues … its me.
Also the Recovery image is pretty well protected, if you override all the messages when flashing teh Recovery slot, before flashing you can backup all the eMMC image slots and restore them after flashing.
So its possible to update the Recovery image and not lose the existing images.

Edited by twol, 29 March 2023 - 21:05.

[twol]

Vu Multiboot - init

 

I must have made a mistake somewhere.

What's maybe wrong?

Or maybe someone else will make the correct patch.

Naive question, but I am assuming that you copied the files straight from the OE-A as they are receiver specific.

[Dimitrij]

 

Naive question, but I am assuming that you copied the files straight from the OE-A as they are receiver specific.

And what's naive about it if I can't check the changes?

Therefore, I ask other developers who understand this more, for advice.

[littlesat]

Unfortunately, when I wrote the python code(constantly corrected by the  rest of the OpenViX/OpenBH team) , Recovery is  constantly treated as slot 0 (which once multiboot is initiated it occupies).
During ALL the testing, I have never not been able to get back to this Recovery image……either through choosing Recovery in MultiBootSelector(as you would for any multiboot receiver with a Recovery option), or bad image …..it boots recovery, or choose image on usb (and pulled) .. boots to Recovery. 
So its pretty resilient … and I hammer these multiboot boxes pretty hard during testing …..and as sometimes my code broke the multiboot, if anybody was going to have issues … its me.
Also the Recovery image is pretty well protected, if you override all the messages when flashing teh Recovery slot, before flashing you can backup all the eMMC image slots and restore them after flashing.
So its possible to update the Recovery image and not lose the existing images

 

Fair response... but 'what-if' the slot 0 image fails... then there is no backup. And that is still the difference... Indeed you can try to recover via USB as this seems to be implemented.

And therefore it might be a good idea to have a slot with an extreme small image in 'slot recovery' that just have a small UI that arrange flashing of slots, selecting slots etc... Actually other brands are doing this .... and because VU+ does not offer it the community needs to do it somehow.

 

For now we need to wait for this feature, which has real added value, the BSP is changed.... unless this at least when another image is in slot 0, you can go to OpenPli and from openPLi back to another slot. And I also hope that I offered some small cosmetic to it.

 

What I still do not understand is the mechanism behind when slot 0 is forced being selected after a reboot?

->

Sorry I got it... "You can put a blank file named STARTUP_RECOVERY onto a usb stick, put it in the box and reboot (power off, or press and hold power button on remote for 12 seconds) to force a reboot, it will then boot recovery."

 

I understand making a real small recovery image is a lot of work... It is not a have-to or must-have. I'm aware all depends on volunteer work.

Edited by littlesat, 30 March 2023 - 08:23.

[twol]

 

 

Naive question, but I am assuming that you copied the files straight from the OE-A as they are receiver specific.

And what's naive about it if I can't check the changes?

Therefore, I ask other developers who understand this more, for advice.

 

I asked you what the issue was and tried to be helpful, as I added the changes to the OE-A……which work on the OE-A  so must know something!
… or are you just upset because I commented on you copying things?

[Dimitrij]

Actually, I made one bb recipe for all models.

And he asked if everything is ok, does it suit everyone?

[Dimitrij]

 

"You can put a blank file named STARTUP_RECOVERY onto a usb stick, put it in the box and reboot (power off, or press and hold power button on remote for 12 seconds) to force a reboot, it will then boot recovery."

This need add in Multiboot screen for info.

And add option auto create/remove STARTUP_RECOVERY onto a usb stick.

Edited by Dimitrij, 30 March 2023 - 09:12.