592 replies to this topic

[dpeddi]

 

vuduo4k needs extra sleep

Thanks for the test.

I hope you fix this.

And I will update the necessary files on the git.

 

4 seconds sleep rear connector (usb3) FAILURE

4 seconds sleep front connector (usb2) OK

so i should put about 12-13 seconds sleep to get usb3 stick to work... i think is too much

[Dimitrij]

 

4 seconds sleep front connector (usb2) OK

Great.

This is enough.

[Abu Baniaz]

That means you will not be able to close the front flap. Can an option for longer delay be created for people wanting to use rear USB? people can then choose what to use.

[Dimitrij]

 

That means you will not be able to close the front flap.

This need only force load STARTUP_RECOVERY,on the contrary, it will be seen that the flash drive must be removed.

[Abu Baniaz]

Sorry, I didn't realise that you were referring to the recovery process. It is easier to use the front USB than the ones at the back for flashing/recovery. Please ignore my comment about extra delay for USB 3 socket at back.

[djuro1]

I installed in fles openpli Nightly builds, after installing the image I installed vuplus-kexec and in the Shutdown / Restart option I selected and disabled Vu+ Multiboot, but after the restart the receiver cannot start the image. The receiver is vu solo+ 4k. Have you tried it on solo+ 4k?

[Dimitrij]

dpeddi

works

thanks

KEXEC-1ST STAGE: STARTUP_RECOVERY not present in /dev/sda
KEXEC-1ST STAGE: STARTUP_RECOVERY found on /dev/sda1
KEXEC-1ST STAGE: copying STARTUP_RECOVERY into STARTUP
KEXEC-1ST STAGE: loading STARTUP from /dev/mmcblk0p9...

 

[Dimitrij]

[vuduo4k] vuplus-kexec -update kernel_auto.bin

[djuro1]

I installed in fles openpli Nightly builds, after installing the image I installed vuplus-kexec and in the Shutdown / Restart option I selected and disabled  Vu+ Multiboot, but after the restart the receiver cannot start the image. The receiver is vu solo+ 4k. Have you tried it on solo+ 4k?

I thought I would enable Vu+ Multiboot

Edited by djuro1, 13 April 2023 - 09:31.

[marto]

 

I installed in fles openpli Nightly builds, after installing the image I installed vuplus-kexec and in the Shutdown / Restart option I selected and disabled  Vu+ Multiboot, but after the restart the receiver cannot start the image. The receiver is vu solo+ 4k. Have you tried it on solo+ 4k?

I thought I would enable Vu+ Multiboot

 

As per discussion in OpenBH forum, there is a problem with Solo 4K. Looks like no fix yet. 

 

Hereby to confirm that the Multiboot is working fine on Ultimo 4K, just in Menu-Settings-Flash Image i see only the OpenPLi images. Those from other teams are not available, so i had to manually put them in media/hdd/downloaded_images, and then to install them from the menu in to desired slot.

[djuro1]

 

 

I installed in fles openpli Nightly builds, after installing the image I installed vuplus-kexec and in the Shutdown / Restart option I selected and disabled  Vu+ Multiboot, but after the restart the receiver cannot start the image. The receiver is vu solo+ 4k. Have you tried it on solo+ 4k?

I thought I would enable Vu+ Multiboot

 

As per discussion in OpenBH forum, there is a problem with Solo 4K. Looks like no fix yet. 

 

 

 

I started this topic on the obh forum, but I thought that if the openpli image was installed in slot 0, it would start the image. All other images can be installed and run on vu solo 4k in any slot except bh image, vix, openpli and all images that use openpli base. All images can be installed and run on duo 4k se

Edited by djuro1, 13 April 2023 - 14:18.

[Tech]

Hereby to confirm that the Multiboot is working fine on Ultimo 4K, just in Menu-Settings-Flash Image i see only the OpenPLi images. Those from other teams are not available, so i had to manually put them in media/hdd/downloaded_images, and then to install them from the menu in to desired slot.

Just change the "alternative url for images listed on Flashimage" (Menu - Setup - System - Customize) into 'all' and all images will be visable.

[marto]

 

Hereby to confirm that the Multiboot is working fine on Ultimo 4K, just in Menu-Settings-Flash Image i see only the OpenPLi images. Those from other teams are not available, so i had to manually put them in media/hdd/downloaded_images, and then to install them from the menu in to desired slot.

Just change the "alternative url for images listed on Flashimage" (Menu - Setup - System - Customize) into 'all' and all images will be visable.

 

I didn't notice that option before. Now i have them. Thanks! 

[cobus]

 

When will the first version be ready to try?

 

I will restart the develop build in a minute. So when that build is finished .
 

 

Where can i found this (multiboot) in the image ?

[neo]

You need to activate it in the shutdown/startby menu (unless it has already been moved to a more logical place, like the flash image screen.

 

If you don't see it, you might need to install the kexec package manually, there were some dependency issues in the BSP which were only fixed recently.

[Dimitrij]

Expert mode, new image develop.

[cobus]

I have the newest ?

 1_0_19_4C05_835_600_FFFF0000_0_0_0_20230414205112.jpg   124.69KB   4 downloads

[Dimitrij]

I have the newest ?

1_0_19_4C05_835_600_FFFF0000_0_0_0_20230414205112.jpg

 

 

If you don't see it, you might need to install the kexec package manually, there were some dependency issues in the BSP which were only fixed recently

[cobus]

Thanks 

 

PS: Where can i found the package for UNO SE 4K

[neo]

On the commandline,

opkg install vuplus-kexec

or install it via package management (in software management).