32 replies to this topic

[mcelliot_g]

I installed 7.3 RC multiboot on my HD51 today. Unfortunately the multiboot selector does not recognize any other images on the flash not even itself. I have a no images found message on the selector screen. Even FlashImage is not working well. All slots are flagged as empty, even if you flash another image on another slot you still get the no images found message.
What could have happened?

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk

[littlesat]

Might be related to a new multiboot system so likely you need to reflash completely.!

Edited by littlesat, 21 June 2020 - 14:56.

[WTE]

Maybe partition layout is damaged or a bug in new 7.3?

 

You can see if the images are still available on the partition

By putty/telnet

 

mkdir /tmp/userdata

mount /dev/block/by-name/userdata /tmp/userdata

cd /tmp/userdata

ls

 

Do you see linuxrootfs with a number behind then it all should been fine and it's probably a bug in openpli.

Edited by WTE, 21 June 2020 - 15:15.

[MCelliotG]

Here's what I got from WTE's commands (OpenPLI 7.3 is installed on slot 2).

openpli 7.3-rc hd51

hd51 login: root
root@hd51:~# mkdir /tmp/userdata
root@hd51:~# mount /dev/block/by-name/userdata /tmp/userdata
root@hd51:~# cd /tmp/userdata
root@hd51:/var/volatile/tmp/userdata# ls
linuxrootfs2  linuxrootfs3  linuxrootfs4  lost+found
root@hd51:/var/volatile/tmp/userdata#

So what is going on?

Bear in mind that in slot1 I have the latest OpenATV which has the new multiboot layout as well. So it should be compatible to OpenPLI.

However I have to note that SatDreamGR8 which moved to Zeus earlier, has the exact same issue with multiboot. Is it maybe a Zeus issue?

Edited by MCelliotG, 21 June 2020 - 18:14.

[littlesat]

7.3 rc != Zeus as it is still pyro..
I have it tested here on 3 boxes without issues.....
I would like to see the content of your startup directory...

Edited by littlesat, 21 June 2020 - 18:19.

[MCelliotG]

where do I locate it?

[mrvica]

mkdir /tmp/boot
mount /dev/mmcblk0p1 /tmp/boot
cd /tmp/boot
ls

 

I´m afraid you´ll have to flash USB image, all partitions will be gone and you need to set up new multiboot images all over

Edited by mrvica, 21 June 2020 - 18:53.

[MCelliotG]

root@hd51:/var/volatile/tmp/userdata# mount /dev/mmcblk0p1 /tmp/boot
root@hd51:/var/volatile/tmp/userdata# cd /tmp/boot
root@hd51:/var/volatile/tmp/boot# ls
STARTUP    STARTUP_1  STARTUP_2  STARTUP_3  STARTUP_4
root@hd51:/var/volatile/tmp/boot#

Luckily I did not install OpenPLI 7.3 on the first partition so I can hard-boot to OpenATV on Partition1. From there I can flash another image on partition 2 and get multiboot back.

The thing is I'm afraid if I flash OpenPLI 7.3 on the first partition I will either

a) not be able to use multiboot

use multiboot only with Zeus images.
 

 

[mrvica]

I think there must be 8 STARTUP_X´s, not just 4, OpenATV boot is still not compatible to OpenPLi, you have to flash the USB image and try to install other images in 2,3,4 partitions

[MCelliotG]

Not working if I bear in mind that I had already done that with SDG8 which has the very same problem.

OpenATV has 8 STARTUPs because it supports Mode 12 as well, it's not really an incompatibility.

[littlesat]

There must be nine startup files....one without extra’s that is the one that is actually boot. 4 fout mode 1 and four for mode 12. the old you need to arrange to have the good startup files first. 7.3 does parse these startup files to see what slots and modes are possible instead of hardcoded code. So when these files are wrong multiboot cannot work indeed. when was the last team you really flashed your hd51? We also support mode 12 so but files should be there....

Edited by littlesat, 21 June 2020 - 21:11.

[MCelliotG]

In all honesty even with OpenPLI 7.2 I never saw 8 startup files.

The last time I flashed my HD51 was when the new multiboot system was introduced. I had initially flashed SDG8 on slot 1 and had to flash OpenATV after I saw that multiboot was not working.

Tomorrow I will backup my images and try flashing OpenPLI 7.3 on slot 1 to see if anything is fixed.

[MCelliotG]

Small quick test.

1. Flashed openatv 6.4 (emmc recovery) image 1st partition

 Flashed openpli 7.3 slot 4

same behaviour. OpenPLI 7.3 is flashed successfully but gives again no images found.

 

2. Trying to flash OpenPLI 7.3 multiboot on slot 1

- Gives no partition (unable to flash). If I flash the non-multiboot, I think I'll have no multiboot!

 

So, what can I do?

Edited by MCelliotG, 22 June 2020 - 00:06.

[twol]

This has nothing to do with STARTUP files. OE-A uses 4 for the HD51 and uses code to handle the 2 bootmodes. OpenPli uses 8 to handle bootmode 1 and 12.

 - but the multiboot code should be the same across all the images 

[MCelliotG]

If nothing has changed in the multiboot code between the latest OpenPLI 7.2 and 7.3 RC, then it should be safe to assume that something in Zeus makes multiboot handling problematic! Flashing 7.2 works in any partition, plus if I flash the non multiboot image via USB I will lose any multiboot capabilities!

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk

[littlesat]

The very first hd51 multiboot images had incorrect startup examples.... that’s your issue while we now parsing these files. So you need to switch to a more recent stuff. Maybe this time openatv still has the old stuff. We get the new stuff from the bsp. Also (older) openatv does this hardcoded and ignores these startup files conpletely (which Openpli also did) So usb flash Openpli (or a later openatv?) and you’re done... and maybe also copy and paste the startup files to that folder might work....

Edited by littlesat, 22 June 2020 - 06:55.

[MCelliotG]

The question is if I flash the non multiboot 7.3 image via USB, will I lose any multiboot capabilities?
The multiboot images are impossible to flash this way.
I always flash the latest images. OpenPLI 7.2 has no issues with multiboot in whichever slot is flashed. The issue is with Zeus images.
What is your proposal since flashing any 7.3 image results in non images found?

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk

[WanWizard]

There aren't any zeus based images yet. 7.3-release is still based on Pyro.

[ims]

Image 6.x and 7.x should not work on same box, imho. PLi 7.x using initramfs and 6.x does not. If you will flash 7.x, then 6.x will not be found more, imho.

 

But it can also be true that everything I said is not true or did not happen

[MCelliotG]

OK, guys, PROBLEM SOLVED!!!

What I had to do is flash the 7.3 usb image via USB, fearing I would lose multiboot capabilities. Luckily I did not.

 

What seems to happen is this:

It looks like flashing the usb image and deleting the current partition table the latest OpenATV 6.4 creates if flashed via USB, fixes the multiboot with non OE-A images.

The good thing is that flashing an OE-A image after that in any slot, will retain the table, and compatibility. The only issue is that you cannot boot Mode12 from within OpenATV due to the differences already explained, but in all images the image list is now visible, so no problem for me.

Now, even SDG8 (Zeus) is working properly.

So, long story short, the distribution has nothing to do with the incompatibility, but OpenATV's workarounds do!

Nice things to know, I learned a lot today!

 

Thank you to everyone for your patience and suggestions!