Ev0

It's a question of how to deal with problems that users pass on.


@OpenBH
If feedback is immediately nipped in the bud because you reply that there can't be a problem, then you won't get any more feedback.
You shouldn't make it that easy for yourself.

The 'blue screen' is there and comes from the kexec and as Fremske writes, it's not a problem if it only flashes briefly.

twol read it here as in the ATV and PikeBishop is no beginner!

https://www.opena.tv...html#post536012

If the box stalls with this 'BlueScreen' then it's coming from the Kexec and then there's a problem!

It is clear to this user that you should definitely keep a minimal image for Slot0 or r or whatever.
But even if it is not clear to him, it shows that you need a little more explanation when using it.

The image or better the entire boot can no longer be continued and ends with the blue screen.
All multiboot images can then no longer be saved.
A new flash is required.

I can only appeal to take this seriously.

A log is not possible from the area, as I see it.

If by @OpenBH you are replying to me, then @Ev0 would be better in future

I have already posted, that I have found a way to see the blue screen myself, I have to turn off my tv and then turn it on at the right time to see it, otherwise my tv simply does not display it.

As for my other point, you have now linked to another thread and looking at the information posted there, he is using 2x usb 3.0 hubs on both rear usb 3.0 ports, so yes it is very possible that the hubs are the reason for his issue.

Usb 3.0 is slower to init than usb 2.0 ports on vu+ boxes and as kexec checks for usb 3.0 it halts the process for a short time (to check for images on usb sticks), so it is possible that with his additional active hubs, this extra wait time is the reason for his box freezing at this point (perhaps his hubs don't react fast enough, once kexec continues), I don't know it's only a guess but nobody else seems to have this issue.

@neo
The content is already clear.

On the one hand, the working boot version is always my top priority.
The users didn't miss it in this forum and liked their VU+ just the way it is.

So now they're being forced to change their ways, even though it's not coming from VU+.

On the other hand, the acceptance of commits that not only make it necessary to check the construction, and also the flash image, is not so easy.

@
littlesat's statement

I cannot simply forward this PR because I cannot control it.
This should really only be done by people who have tested it on their own VU+ box.

Something is being changed on the boot here.
This is something different than any other .bb
 

Nobody is forced to change anything.

You (the end user) has the option to enable it or not.

If you do not enable, then the image is the same as it always was, except it will show 1 new option (to enable multiboot), if you don't select that new option then nothing has changed.

What I do wonder (based on this topic), if there is no recovery menu, how do you select a different slot to boot from in case the current/active slot is bricked and doesn't boot? If that doesn't exist, the solution is of limited use.

You have 3 ways to get to the base (recovery) image in that eventuality.

1) if you are in a multiboot image, you can select Recovery Mode.
2) if you have an image that is in a crash loop for example, you can put a blank file called STARTUP_RECOVERY onto the usb stick or hdd installed in the box, then power off and on the box (or press and hold the power button on the remote for 12 seconds to force a reboot).
3) If you are stuck at bootloader splash screen for any reason, you can put that same blank STARTUP_RECOVERY file onto a fat32 formatted usb stick, insert in the front, remove any usb from the rear, power off and on again and it will boot the recovery iamge.

 

In last version image BH

Crrosepg was update

Updated for what?

 

Where is the commit?

 

https://github.com/E...02345d29f50ee9c

@dany

If you use the rename option in OpenMultiboot, you can give each image (except flash) it's own name.

Then the bootmenu will name the images correctly for you.