BPanther's Neutrino Forum

Sure, you must add the fstab line for each e2 image, because they are independed systems.

It is a pity that there is no preview of what image is under a given starup, but it's still a great job

Hmm, only max. 4 Images and you don't know which you booting?

But you can rename the 4 STARTUP_X files e.g. to STARTUP_OATV, STARTUP_PKT or whatever, but STARTUP_ must be in front, more you can name what you want.

Do you have found other working E2 Images? I think VTI should also work if I remember right.

That's great and that's enough, and VTI is just one of those images that I do not really like. I will test and write which I managed to run

ps.And in which file should I add OATV, PKT .... in plugin.py?
And in which file should I add OATV, PKT .... in plugin.py?
or rootfs_OATV, rootfs_PKT .....?

Edit:I think I found it in boot

Only rename the 4 STARTUP_X files at /boot, no other changes needed. Multiboot files for usb etc. are the same as before. So you must still know whitch image is in whitch partition installed.
I suggest for the names e.g. STARTUP_1_OATV, STARTUP_2_PKT and so on. So you know the partition and the image.

I did so, thanks again



Edit :But I have a problem with switching between startup_1, startup_2, startup_3, startup_4. Maybe I am uploading the image to individual starups incorrectly, because after choosing e.g. startup_3_OATVnic does not happen
These files give you a USB stick:

darog69 hat geschrieben: Mo 26. Aug 2019, 20:55 Edit :But I have a problem with switching between startup_1, startup_2, startup_3, startup_4. Maybe I am uploading the image to individual starups incorrectly, because after choosing e.g. startup_3_OATVnic does not happen
These files give you a USB stick:

You should have a look at your picture - where is the rootfsX file, in your case rootfs4.tar.bz2? mkpart.update is only for the first full reflash (single<->multi) of all partitions needed.

I was wrong in this photo, i.e. when uploading the image to startup_3 should I have these files?

Yes, this is OK. If you flash you must see then after a while "Update rootfs Part 3". Then all OK and partition 3 will be flashed. If this not working, try formatting or an other USB device.

Important: Use the front usb and have no other usb devices connectet.

Only that you don't upload, and you can upload from any startup?

You can flash with usb device or ofgwrite - BUT ofgwrite must be changed for multiboot how in Neutrino, so you can not flash from E2, because they have no multiboot ofgwrite included. If you want flash from Neutrino an other partition with ofgwrite, e.g.:

ofgwrite -m3 /dir_with_files (kernel3.bin and rootfs3.tar.bz2)

I use /tmp, because the files are removed after a reboot.

I was able to upload to startup_1-BP-Neutrino, startup_ also I have Neutrino, it was supposed to be OATV, in startup_3-Opendroid 6.8, startup_4-OpenVix. So I still have to get to startup_2-OATV

Edit:I don't know why from the level of the newly uploaded image from E2 I can't change the STB-Startup plugin to another image from other startups. I choose e.g. startup or startup_2,3,4 and nothing happens, you can't go back to startup or to startup_1.

Edit2:I returned, but after selecting the desired image in STB-Startup, I had to do reboot, and should probably work after confirming OK
I still have to upload OATV to startup_2, but some file is missing on the USB stick because the rootfs2.tar.bz2 installation does not start

Only for OATV or also for other images and neutrino at partition 2? Maybe the file is defect...

It was rootfs.tar.bz2 from my backup, maybe that's the problem. I'll try it soon with a clean image. I also tried, as you wrote from the telnet command: ofgwrite -m2 / dir_with_files
Putting Neutrino kernel2_auto.bin and rootfs2.tar.bz2 in tmp image, but I don't know if I understood it correctly, because that was my answer:

vusolo4k:~# ofgwrite -m2 /dir_with_files

ofgwrite Utility v3.9.8 NMP-Edition
Found vuplus stb: solo4k
Author: Betacentauri
Based upon: mtd-utils-native-1.5.1 and busybox 1.24.1
Use at your own risk! Make always a backup before use!
Don't use it if you use multiple ubi volumes in ubi layer!

Flashing multiboot partition 2
Searching image files: Error path couldn't be resolved
Usage: ofgwrite <parameter> <image_directory>
Options:
-k --kernel flash kernel with automatic device recognition(default
-kmtdx --kernel=mtdx use mtdx device for kernel flashing
-kmmcblkxpx --kernel=mmcblkxpx use mmcblkxpx device for kernel flashing
-r --rootfs flash rootfs with automatic device recognition(default
-rmtdy --rootfs=mtdy use mtdy device for rootfs flashing
-rmmcblkxpx --rootfs=mmcblkxpx use mmcblkxpx device for rootfs flashing
-mx --multi=x flash multiboot partition x (x= 1, 2, 3,...). Only sup
orted by some boxes.
-n --nowrite show only found image and mtd partitions (no write)
-q --quiet show less output
-h --help show help

Ähmm... Not really...

This was an example, so you must use the right path.
ofgwrite -m2 /dir_with_files

No wonder why this message given by ofg:
Searching image files: Error path couldn't be resolved

Use the right path where you have put the files and flashing will working.