Search results

  1. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    So unzip & copy the attachment to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX and reboot, if you use Putty init 4 before copy and init 3 afterwards Post the debug, would like to see both returns in debug from ofgwrite ...... it should not crash as before.
  2. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    So does slot 5 show an image installed in MultiBootSelector (long press power)? and if so what happens if you try to boot it???
  3. T

    Vu+ Real Multiboot Now Available

    Post debug log. …I assume its ext4?
  4. T

    Vu+ Real Multiboot Now Available

    The code was written to use the existing eMMC and usb devices.
  5. T

    Vu+ Real Multiboot Now Available

    Because it was added to work with eMMC and usb devices….. using a device as hdd & system partition can cause issues. if you would prefer OMB feel free to use it.
  6. T

    Vu+ Real Multiboot Now Available

    If you are using the ssd already as an HDD, you will likely see some issues if the device is also used to contain images (it becomes a system device). If you are not concerned about this, then manually add a STARTUP ….. but don,t expect any support if you have issues.
  7. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Normally when you flash an image, it will reboot to that image slot(standard multiboot function), I think with OpenATV you can flash an image without rebooting.
  8. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Both openpli and openatv for duo4k require a multiboot.py update, which the BH team can supply if not already posted on the forum.
  9. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Why? Like any multiboot receiver, you only need flash one image, which you can then either software update or flash in place.
  10. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Put the file in the active image. /boot is the boot eMMC partition and you shouldn't be updating that. All the slot info (STARTUP_xxx) appears in /boot, which also hold the eMMC images, but not the usb images.
  11. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Every image is a discreet image….. and you can have eMMC images and images in an attached usb device. You will only see the eMMC images linuxrootfs1-> 3 in /boot So the easiest approach is to add to the active image in Root ( /) and ensure that when you add a file, you run a settings backup...
  12. T

    Vu+ Real Multiboot Now Available

    so the backup is not correct You could try unzipping your backup, adding the vuplus folder and re zipping
  13. T

    Vu+ Real Multiboot Now Available

    I want to know what files are in there after the unzip
  14. T

    Vu+ Real Multiboot Now Available

    So assuming you haven,t run it since whats in /media/hdd/imagebackups/imagerestore/vuplus/duo4k
  15. T

    Vu+ Real Multiboot Now Available

    The debug is required so that we can see what was sent to ofgwrite. The newroot exists message you can disregard as it doesn,t stop a successful flash. What is the HDD and is it internal or external. If external is it powered? Ofgwrite has an issue finding the files
  16. T

    HowTo Vu+ Multiboot in OpenBh 5.2

    Long press power, multibootselector screen, select image, delete
  17. T

    Vu+ Real Multiboot Now Available

    @darog69, you obviously have a huge ego to feed, in releasing a software change that is still in development(we were working still late last night) and also without reference to the guy(dpeddi) who developed the multiboot hosting facility for Vu systems over many years & integral to this...
  18. T

    Vu+ Real Multiboot Now Available

    Looks pretty good at the moment, lots of work, but I think we are just cleaning up a few loose ends.
  19. T

    IMDB makes image stuck because of a skin element missing?

    will be included in next Image build or copy unzipped plugin.py to /usr/lib/enigma2/python/Plugins/Extensions/IMDb
  20. T

    IMDB makes image stuck because of a skin element missing?

    Fix submitted to imdb plugin
Top