592 replies to this topic

[dpeddi]

Actually, I made one bb recipe for all models.
And he asked if everything is ok, does it suit everyone?

Remember that the kexec kernel is different for each box.
The initrd image instead can be used on all boxes.

For more details here is the GitHub for the project.
https://github.com/B.../main/README.md

 

If the STARTUP_RECOVERY isn't enough to recover your slot0, you can flash a kernel aligned to your slot0 sing an usb stick usb (vuplus/boxname/kernel_auto.bin)..if you don't put the rootfs it just flash the kernel.

Edited by dpeddi, 30 March 2023 - 20:22.

[Dimitrij]

dpeddi

Thank you for your work and additional information..

[littlesat]

Can someone point me to the code where the file in the USB stick is checked so maybe I could find for an alternative. Maybe with adding content to it we can arrange something that when the box is rebooted a second time when enigma2 2 is not started the box automatically can go to recovery.

[dpeddi]

Can someone point me to the code where the file in the USB stick is checked so maybe I could find for an alternative. Maybe with adding content to it we can arrange something that when the box is rebooted a second time when enigma2 2 is not started the box automatically can go to recovery.

Here:

https://github.com/B...it-kexec.sh#L79

[dpeddi]

About the counter... Nice idea, but complicate things a lot... Then is difficult to identify a non working image... Usually you could get a working box with enigma2 bootloop.. 

 

A smart guy like you would connect to ssh ant check why enigma would bootloop... And probably wouldn't be nice to go back to recovery without any alert.

 

I thought at startup_recovery on usb as an easy way to go back into recovery without flashing a new kernel or connecting a serial cable or messing with ssh. It's use is to let you choose a new image if you entered into blackhole or vti that doesn't support multiboot at all.

 

 

 

... And sometimes I get crazy because I forget the stick with such file connected and it take me unexpectedly to recovery while choosing a different image

[neo]

The use case here is "not so smart guy who installed a downloaded skin which crashes Enigma". i.e. a typical end-user.

 

I can't immediately come up with a better solution, taking into account the lack of bootloader support for a recovery image.

 

Would it be possible to check for a keypress during bootup, for example "if a poweron keypress is detected during boot, start the recovery image"?

 

evtest can do that, so it should be possible to make something small that returns 1 if pressed, 0 if not?

Edited by neo, 31 March 2023 - 14:36.

[dpeddi]

Would it be possible to check for a keypress during bootup, for example "if a poweron keypress is detected during boot, start the recovery image"?

 

evtest can do that, so it should be possible to make something small that returns 1 if pressed, 0 if not?

 

Drivers aren't available at that kexec-multiboot first stage so neither frontpanel or remote are available.If you want something better (with remote and graphic output), try asking to vuplus...

 

If you want to spend some time you can give a try to kexec boot:

https://github.com/d...local-kexecboot

https://github.com/dpeddi/kexecboot

 

It have a gui, i wrote some patch to make it work on vuplus, but isn't compatible with STARTUP_xx of most implementation of multiboot implemented in enigma2... since it needs the vuplus driver is diffucult to make it to fit the kernel partition.

[neo]

Ok, clear. I doubt vuplus is willing to cooperate, if they're still alive...

[Guest-*0823016*]

They haven't been alive for a long time...see BH!

krime mobile

[WanWizard]

Not very intrested in what others think or say, we've been in contact with them only of 6 weeks ago...

[Guest-*0823016*]

They haven't been alive for a long time...see BH!

krime mobile

But at this point I'm wondering, why did BH abandon them or / was abandoned

krime mobile

[neo]

Only BH can answer that...

[Huevos]

Please be realistic about Vu+. Are they even contributing financially anymore? When was the last production run? Do you really think they are going to keep a team of developers active for years when they are not even producing the hardware? The current kernels are antique and there hasn't been a driver update for any of their hardware in more than 4 years. Maybe they do respond to email but that doesn't mean they are actively working on Vu+ hardware.

Edited by Huevos, 2 April 2023 - 09:40.

[Dimitrij]

dpeddi

What do you need for full support Multiboot?

Multiboot - allow OpenPli images to participate in a Vu+ Multiboot en

Vu Multiboot - init

 

and?

[littlesat]

The enigma2 part is already merged and improved.

[Huevos]

dpeddi

What do you need for full support Multiboot?

Multiboot - allow OpenPli images to participate in a Vu+ Multiboot en

Vu Multiboot - init

 

and?

 

 

You need VuplusKexec.py or similar for OpenPLi.

 

https://github.com/O...a/menu.xml#L243

https://github.com/O.../VuplusKexec.py

 

Once initialised this disappears from the menu.

Edited by Huevos, 2 April 2023 - 10:44.

[littlesat]

Brrrrr so you still need a special code…. do you really really need that? I thought that what was merged they it was all that is needed…. Sounds like we get a lot of false information here?

Edited by littlesat, 2 April 2023 - 11:18.

[Huevos]

No false information. The other commit was for compatibility. At that time PLi did not have the BSP change.

Edited by Huevos, 2 April 2023 - 11:47.

[Dimitrij]

 

dpeddi

What do you need for full support Multiboot?

Multiboot - allow OpenPli images to participate in a Vu+ Multiboot en

Vu Multiboot - init

 

and?

 

 

You need VuplusKexec.py or similar for OpenPLi.

 

https://github.com/O...a/menu.xml#L243

https://github.com/O.../VuplusKexec.py

 

Once initialised this disappears from the menu.

 

thanks

[littlesat]

Just my to cents to this extra code. The name from the file is somehow wrong as it indicates if vu then so it is something special for VU only which is from my point wrong… So I think it is much better to rename it to something what it does by or where it is needed for e.f. KexecMultibootInitScreen.py or so. Maybe for other boxes that do not support the ‘legacy’ multiboot it could also helpfull for…
I hope you understand what I mean.
I understood for now this is needed to setup the structure for it on the box as we do not have Amtrak recovery image .

Edited by littlesat, 2 April 2023 - 19:09.