View Full Version : [VU+ Zero4K] Vu+ Multiboot Switching Images
I’ve enabled Vu+ Multiboot and now have Vix in slot 1 and OpenATV 7.2 in slot 2. Once switched to OpenATV, how to I switch back to Vix again, as there’s no Multiboot selector in OpenATV that I can see? Thanks
I’ve enabled Vu+ Multiboot and now have Vix in slot 1 and OpenATV 7.2 in slot 2. Once switched to OpenATV, how to I switch back to Vix again, as there’s no Multiboot selector in OpenATV that I can see? Thanks
Long press power button on remote should bring up menu with multibootselector(manager in atv) sel3xt and then select image slot.
Long press power button on remote should bring up menu with multibootselector(manager in atv) sel3xt and then select image slot.
Unfortunately it doesn’t. It brings up the reboot/restart GUI standard menu, and if I keep pressing power button then goes on to reboot the box back to OpenATV again.
Unfortunately it doesn’t. It brings up the reboot/restart GUI standard menu, and if I keep pressing power button then goes on to reboot the box back to OpenATV again.
So just to clarify atv power menu doesn,t show (this is on my uno4k)
Deep standby, multiboot manager, standby, sleep timer, reboot, restart gui
So just to clarify atv power menu doesn,t show (this is on my uno4k)
Deep standby, multiboot manager, standby, sleep timer, reboot, restart gui
Nope. It has everything but the Multiboot Manager
So just to clarify atv power menu doesn,t show (this is on my uno4k)
Deep standby, multiboot manager, standby, sleep timer, reboot, restart gui
Can you turn on debug logs…menu/system/logs settings… change log location to hdd, enable debug log and multiboot data….save and reboot(if it doesn,t do it for you)
… then post debug log here …..I just need debug upto when it shows a picture on the tv
Can you turn on debug logs…menu/system/logs settings… change log location to hdd, enable debug log and multiboot data….save and reboot(if it doesn,t do it for you)
… then post debug log here …..I just need debug upto when it shows a picture on the tv
Debug log attached
Sorry but a few basic questions!
do you have debug logs from before this????? e.g when you flashed ATV
So how did you flash OpenATV with ImageManager or ????
The OpenATV image is not seeing any multiboot files so something has gone wrong
......
Can you use filezilla? If so in / (root) you should see the STARTUP_n files at the bottom, I am assuming they are not there ?
SO can you do this:
stop the image (in putty type init 4 (space between)
with filezilla copy attachment to /usr/lib/enigma2/python/Tools
in putty init 6 (space between)
after reboot, post debug!
Sorry but a few basic questions!
do you have debug logs from before this????? e.g when you flashed ATV
So how did you flash OpenATV with ImageManager or ????
The OpenATV image is not seeing any multiboot files so something has gone wrong
......
Can you use filezilla? If so in / (root) you should see the STARTUP_n files at the bottom, I am assuming they are not there ?
I don’t have any logs straight after flashing ATV. I flashed by using image manager when in Vix. Downloading last nights ATV image and selecting slot 2 to install to. It wouldn’t be because I don’t use a hdd for these slots? I’ve only got the normal flash. There is no STARTUP_n files in root, just a Z image file.
Ok so after replaced file, debug logs attached. Multiboot menu is now there and showing my 2 slots used with Vix and ATV!
So copy that file multiboot.py
think you will fins files STARTUP.. IN /boot
Thanks twol. As per post 11, that file has fixed the issue. Does that mean the latest ATV doesn’t have that latest file in the image I downloaded?
Thanks twol. As per post 11, that file has fixed the issue. Does that mean the latest ATV doesn’t have that latest file in the image I downloaded?
It means that it doesn,t pick up the boot volume(which contains the STARTUP files)…….most of the Vu+ 4k boxes have the boot volume in the default list, but obviously the zero4k doesn,t.
The multiboot.py attachment has a code change that instantly finds the boot volume, plus a change for users that use a usb stick to hold images.
It means that it doesn,t pick up the boot volume(which contains the STARTUP files)…….most of the Vu+ 4k boxes have the boot volume in the default list, but obviously the zero4k doesn,t.
The multiboot.py attachment has a code change that instantly finds the boot volume, plus a change for users that use a usb stick to hold images.
It also probably means that if you flash openpli, you will need a file from me.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.