474 replies to this topic

[Dimitrij]

i tested all last 3 uploaded files but the vuduo2 box didnot restart

so i rflashed the box again

Please install image openATV and use original OpenMultiBoot to feed.

It will be interesting to know the results of the test.

[dany]

yes . i did

openatv 5.0 on flash with original OpenMultiBoot

openatv5.0-openatv4.2-vti image 8.2.1 on usb .... perfect - every thing is ok with these images

but pli image and blackhole ... they donot work with OpenMultiBoot , the box hangs after installed these images

the other issue ... this plugin didnot show the bootmenu , to change image you have to go into openmultiboot plugin to select the image you want

 

iam ready to do any test you ask

 

thanks alot

Edited by dany, 1 June 2015 - 20:12.

[cobus]

If you have openatv in flash try this with pli than it works.

 

You need to apply a fix on OpenPLi images in order to boot (this patch is not accepted by OpenPLi yet)....

Go to the location where OpenPLi is store (lets assume /media/usb) and find the following file: /media/usb/open-multiboot/openpli/etc/init.d/volatile-media.sh

And change the following line:

From:

Code:

mount -t tmpfs -o size=64k tmpfs /media

To:

Code:

mountpoint -q "/media" || mount -t tmpfs -o size=64k tmpfs /media

Or simply copy the file from /etc/init.d/volatile-media.sh into /media/usb/open-multiboot/openpli/etc/init.d/volatile-media.sh

And try to boot OpenPLi.

[dany]

cobus .. thank you

 

it doesnot work here ,

ok for the first time when you instal openpli on usb multiboot and restart the box .. it works alwyas normal , but when you restart the box again it hangs on pli bootlogo

 

i donnot know but maybe something there is a difference between xtrend and vuduo2 drivers

[bacicciosat]

Ok until we will not have something goos working i will adapt a version of meoboot for OBH and pli

[rtzhjgg0]

[dany]

Ok until we will not have something goos working i will adapt a version of meoboot for OBH and pli

that will be perfect

but please  .. i wish if we could use difference kernels

i know that we can use telnet for backup-restore multiboot images but i hope if you could add backup-restore multiboot images option

[bacicciosat]

 

Ok until we will not have something goos working i will adapt a version of meoboot for OBH and pli

that will be perfect

but please  .. i wish if we could use difference kernels

i know that we can use telnet for backup-restore multiboot images but i hope if you could add backup-restore multiboot images option

 

 

Sorry you are asking too much to meoboot.

Meoboot always load kernel from flash.

Currently i have adapted it for OpenBlackHole and it seems to work with OpenBlackHole in flash and Pli and other derivates in multiboot.

But it seems not possible the contrary. If you install Meoboot on Pli in flash you cannot boot OBH and other images that have Opengles and Xbmc because of different drivers managment.

 

So it seems better that you go with OpenMultiBoot.

About it @Dimitrij:

Maybe your patch is not wrong. Have you added to your ipk the dependencies for mtd-utils mtd-utils-ubifs ?

[Dimitrij]

bacicciosat

No, depending not added.
But the problem seems to be in something else.

[Dimitrij]

I checked outputs boxbranding.so for Solo2.

They coincide with the data for solo2 from my patch plugin.

[bacicciosat]

Dimitrij.

I had the same problem in meoboot develop these days testing on Pli.

I had an empty file in image extraction.

I discovered that this is because Pli doesn't include in the image packages mtd-utils mtd-utils-ubifs

so the executable to extract the image are not available.

Someone have them only because have installed other ipk like backup-suite that have those dependencies and installed before but there are not in the standard image and if you don't include dependencies OpenMultiBoot cannot work i think.

[bacicciosat]

Ok the first alpha of meoboot for OpenBlackHole.

If someone want to try in the meanwhile you wait for a better solution for Pli....

 

It can boot in multiboot

1. OpenBlackHole
2. OpenPli
3. OpenAtv
4. Vix
5. Vti

...... other images not yet tested.

 

 

WARNING THIS IS AN ALPHA VERSION. USE AT YOUR RISK ONLY FOR PERSONAL TESTS WITH OpenBlackHole in flash.

 

Instructions:

upload the 2 ipk in /tmp
click on green -> yellow -> manual install ipk packages

Warning:
1) frist install meoboot
2) second install meoboot-init

 

P.s. Because of all these images have implemented vu+ proxy drivers and kernel support meoboot cannot work with Pli in flash to boot those images for Solo2, SoloSE, and duo2-

But it should work with images for the box that does'nt have gles support like solo duo uno, ultimo and zero.

So i suppose you can try this version of meoboot with Pli in flash but only for Solo, duo, uno, ultimo, zero.

Remeber only that if you install meoboot with Pli in flash you need to install first nandsim module.

 

 

 

Attached Files

•  meoboot-init_0.1-r33_mips32el.ipk   8.89KB   86 downloads
•  meoboot_0.1-r14_mips32el.ipk   109.23KB   109 downloads

[bacicciosat]

nandsim modules for zero and ultimo if you want to test with Pli in flash

You don't need nandsim modules to test with OpenBlackHole in flash.

 

That's all.

It is better to wait for a working version of OpenMultiboot that should be a better solution.

Attached Files

•  kernel-module-nandsim_3.9.6-r1_vuultimo.ipk   20.73KB   29 downloads
•  kernel-module-nandsim_3.13.5-r1_vuzero.ipk   20.54KB   42 downloads

[Dimitrij]

Dimitrij.

I had the same problem in meoboot develop these days testing on Pli.

I had an empty file in image extraction.

I discovered that this is because Pli doesn't include in the image packages mtd-utils mtd-utils-ubifs

so the executable to extract the image are not available.

Someone have them only because have installed other ipk like backup-suite that have those dependencies and installed before but there are not in the standard image and if you don't include dependencies OpenMultiBoot cannot work i think.

At my request, OMB checked for solo2.
Packages mtd-utils/mtd-utils-ubifs/solo2 nandsim module + solo2 boxbranding.so were installed.

The result is an empty folder...

[betacentauri]

The plugin executes several commands to extract the image. Look into the code and execute them manually. Then you can perhaps find the reason why it don't works.

[foxbob]

Solo2,Openblackhole 0.1.Meoboot install openatv 5.0 - OK,openpli 4.0 - OK,bh2.1.6 - not OK,do not start.

[bacicciosat]

Solo2,Openblackhole 0.1.Meoboot install openatv 5.0 - OK,openpli 4.0 - OK,bh2.1.6 - not OK,do not start.

 

Thank you for test.

[bacicciosat]

bacicciosat

No, depending not added.
But the problem seems to be in something else.

 

 

Yes you are right. I have logged and there is something wrong.

I hope to find time to take a glance to this but i'm very busy

Archive:  /media/hdd/open-multiboot-upload/OpenPLi-4.0-beta-vusolo2-20150531_usb.zip
  inflating: vuplus/solo2/initrd_cfe_auto.bin
  inflating: vuplus/solo2/kernel_cfe_auto.bin
  inflating: vuplus/solo2/reboot.update
  inflating: vuplus/solo2/root_cfe_auto.bin
<  2524.896388> [gRC] main thread is non-idle! display spinner!
[nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0
[nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0
[nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0
[nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0
NAND device: Manufacturer ID: 0x20, Chip ID: 0xac (ST Micro NAND 512MiB 1,8V 8-bit)
NAND device: 512MiB, SLC, page size: 2048, OOB size: 64
flash size: 512 MiB
page size: 2048 bytes
OOB area size: 64 bytes
sector size: 128 KiB
pages number: 262144
pages per sector: 64
bus width: 8
bits in sector size: 17
bits in page size: 11
bits in OOB size: 6
flash size with OOB: 540672 KiB
page address bytes: 5
sector address bytes: 3
options: 0x8
Scanning device for bad blocks
[nandsim] warning: write_byte: command (0x0) wasn't expected, expected state is STATE_READY, ignore previous states
Creating 1 MTD partitions on "NAND 512MiB 1,8V 8-bit":
0x000000000000-0x000020000000 : "NAND simulator partition 0"
dd: can't open '/media/hdd/open-multiboot-tmp/vusolo2/root_cfe_auto.bin': No such file or directory
UBI: attaching mtd5 to ubi1
UBI: scanning is finished
UBI: empty MTD device detected
UBI: attached mtd5 (name "NAND simulator partition 0", size 512 MiB) to ubi1
UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512
UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
UBI: good PEBs: 4096, bad PEBs: 0, corrupted PEBs: 0
UBI: user volume: 0, internal volumes: 1, max. volumes count: 128
UBI: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 4150666950
UBI: available PEBs: 4012, total reserved PEBs: 84, PEBs reserved for bad PEB handling: 80
UBI: background thread "ubi_bgt1d" started, PID 1862
UBI device number 1, total 4096 LEBs (520093696 bytes, 496.0 MiB), available 4012 LEBs (509427712 bytes, 485.8 MiB), LEB size 126976 bytes (124.0 KiB)
UBI error: ubi_open_volume: cannot open device 1, volume 0, error -19
UBIFS error (pid 1864): ubifs_mount: cannot open "ubi1_0", error -19
mount: mounting ubi1_0 on /media/hdd/open-multiboot-tmp/ubi failed: No such device
umount: can't umount /media/hdd/open-multiboot-tmp/ubi: Invalid argument
UBI: detaching mtd5 from ubi1
UBI: mtd5 is detached from ubi1

[bacicciosat]

OK i found a little time to look.

 

The first error in your patch that i found is that for vu+ boxes the BOX_NAME fails to match the condition values. So the wrong values are assigned.

 

This because of the routine you used to extract box name.

elif fileExists("/proc/stb/info/vumodel"):
	try:
		l = open("/proc/stb/info/vumodel")
		model = l.read()
		l.close()
		BOX_NAME = str(model.lower())
		l.close()
		BOX_MODEL = "vuplus"

A strip of tthe string is needed

elif fileExists("/proc/stb/info/vumodel"):
	try:
		l = open("/proc/stb/info/vumodel")
		model = l.read()
		l.close()
		BOX_NAME = str(model.lower().strip())
		l.close()
		BOX_MODEL = "vuplus"

With this fix the box name will match the correct values.

But there are oter issues in patch of the extract image.

[bacicciosat]

Ok i have found and fixed all.

 

The second issue was about image path.

The variable OMB_GETIMAGEFOLDER = str(box) in this value is not correct for vu+ boxes.

 

So you have to find line:

if BOX_MODEL == "vuplus":

and add after

OMB_GETIMAGEFOLDER = "vuplus/" + BOX_NAME

After this fix all will work. The images will be extracted and booted.

 

Thanks Dimitrij for the patched version, you made a great work !!