[Split] Immer auf der Suche nach Neutrinos...

[darog69]

Hello, how to correctly configure the heads in Vu Solo 4k?
My satellite installation:

Tuner A-Satellite Motor SG2100
Tuner B-Unicable

[BPanther]

Just have you listet. Try A = 1 as Diseqc Type, B = 2 (or 4) as Unicable.

[darog69]

In Openpli I have these settings:

config.Nims.0.diseqcMode=positioner
config.Nims.0.latitude=50.297
config.Nims.0.longitude=18.787
config.Nims.0.powerMeasurement=false
config.Nims.1.advanced.lnb.1.lof=unicable
config.Nims.1.advanced.lnb.1.scrList=1
config.Nims.1.advanced.lnb.1.unicableManufacturer=Inverto
config.Nims.1.advanced.lnb.1.unicableProduct=IDLB-QUDL-UNI2L-OPP
config.Nims.1.advanced.sat.130.lnb=1
config.Nims.1.advanced.sats=130
config.Nims.1.configMode=advanced
config.Nims.2.advanced.lnb.1.lof=unicable
config.Nims.2.advanced.lnb.1.scrList=1
config.Nims.2.advanced.lnb.1.unicableManufacturer=Inverto
config.Nims.2.advanced.lnb.1.unicableProduct=IDLB-QUDL-UNI2L-OPP
config.Nims.2.advanced.sat.130.lnb=1
config.Nims.2.advanced.sats=130
config.Nims.2.advanced.unicableconnected=true
config.Nims.2.advanced.unicableconnectedTo=1
config.Nims.2.configMode=advanced
config.Nims.3.advanced.lnb.1.lof=unicable
config.Nims.3.advanced.lnb.1.scrList=3
config.Nims.3.advanced.lnb.1.unicableManufacturer=Inverto
config.Nims.3.advanced.lnb.1.unicableProduct=IDLB-QUDL-UNI2L-OPP
config.Nims.3.advanced.sat.130.lnb=1
config.Nims.3.advanced.sats=130
config.Nims.3.advanced.unicableconnected=true
config.Nims.3.advanced.unicableconnectedTo=2
config.Nims.3.configMode=advanced
config.Nims.4.advanced.lnb.1.lof=unicable
config.Nims.4.advanced.lnb.1.scrList=4
config.Nims.4.advanced.lnb.1.unicableManufacturer=Inverto
config.Nims.4.advanced.lnb.1.unicableProduct=IDLB-QUDL-UNI2L-OPP
config.Nims.4.advanced.sat.130.lnb=1
config.Nims.4.advanced.sats=130
config.Nims.4.advanced.unicableconnected=true
config.Nims.4.advanced.unicableconnectedTo=3
config.Nims.4.configMode=advanced
config.Nims.8.multiType=1
config.Nims.8.terrestrial_5V=true

[BPanther]

Then you have all datas.

0 = A = 1 -> Diseqc
1= B = 2 -> Unicable CH1 - SCR 0 - FREQ see -> this or this
2= C = 3 -> Unicable CH2 - SCR 1 - FREQ see -> this or this
3= D = 4 -> Unicable CH3 - SCR 2 - FREQ see -> this or this
4= E = 5 -> Unicable CH4 - SCR 3 - FREQ see -> this or this

Links german, but search for your unicable switch and for the right frequency.

[darog69]

I give up, I haven't seen more confusing settings in any other image
Astra 19.2 was picked up, but nothing else or Unicable for which I set:

Tuner 2 (SCR0): 1210 MHz
 Tuner 3(SCR1): 1420 MHz
Tuner 4(SCR2): 1680 MHz
Tuner 5(SCR3): 2040 MHz

If you could this screen show only under Motor settings
Configuration is very easy on any other image

[BPanther]

Tuner 2, Master, Unicable, select your sat, change lnb config if needed, unicable scr 0, unicable frequ 1210, unicable pin if needed

If this not work, try tuner 5, because I think tuner 1-4 are one phys tuner and 5-8 the second tuner.

[darog69]

I still have a question about Multiboot -Solo4k STB-Startup, does this plug-in ENIGMA2-STB-STARTUP_1.00-20190517_ALL.IPK work only on Neutrino, because I installed it in Oenatv 6.3, but I have empty in the plugin window?
Does this plugin divide flash into new partitions or do it have to be done in a different way?
I have added the required entry in fstab:
/ dev / mmcblk0p1 / boot auto defaults 1 1

It looks like:
rootfs / auto defaults 1 1
proc / proc proc defaults 0 0
devpts / dev / pts devpts mode = 0620, gid = 5 0 0
usbdevfs / proc / bus / usb usbdevfs noauto 0 0
tmpfs / var / volatile tmpfs defaults 0 0
/ dev / mmcblk0p1 / boot auto defaults 1 1
UUID = 5c1e1d10-bace-461a-ab3c-c637a19acc30 / media / usb auto defaults 0 0
UUID = eeb7e2a7-110c-4a4c-b14b-1012a3985b5f / media / hdd auto defaults 0 0

root@vusolo4k:
d
[K



b
l
k
i
d


/dev/sda1: LABEL="hdd" UUID="eeb7e2a7-110c-4a4c-b14b-1012a3985b5f" TYPE="ext4" PARTUUID="612ebfc8-01"

/dev/mmcblk0p4: UUID="7bebba2f-671e-4bb0-96f7-d934ec93d663" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="b65bbc49-5567-48ee-9164-447dbe5c6b1c"
/dev/sdb1: LABEL="usb" UUID="5c1e1d10-bace-461a-ab3c-c637a19acc30" TYPE="ext3" PARTUUID="960286c4-01"
/dev/mmcblk0: PTUUID="51dc0b5e-d6e3-469d-9df3-cb4befb8b463" PTTYPE="gpt"
/dev/mmcblk0p1: PARTLABEL="kernel" PARTUUID="25a7af6c-6ac0-41f6-bb90-247a14054a5d"
/dev/mmcblk0p2: PARTLABEL="initrd" PARTUUID="d97255c4-d757-48bc-8e2d-5b3067950b9a"
/dev/mmcblk0p3: PARTLABEL="splash" PARTUUID="8a2626d0-8ace-49f7-8203-479726119c32"
root@vusolo4k:

[BPanther]

The plugin is ONLY for E2, testet with original, VTI and OATV. You forgot to add the line at /etc/fstab and reboot - see -> VUSOLO4K - MultiBoot <- again.

[darog69]

I think I'm fine

[BPanther]

Sorry my fault. I forgot in the guide that at the first switch to multiboot ALL partitions must be flashed. Added now for all VU. Just copy the rootfs1.* to 2,3 and 4 - same with the kernel1.
You can - if needed - make a full backup from your running e2 with the plugin imgbackup for later flash. Just copy this one file from the rootfs.tar.bz2 at /var/tuxbox/plugins to the hdd (right 755) and start this with ./imgbackup /hdd (or wherever you want).

[darog69]

I test it on Openatv 6.3 and there is no such path: / var / tuxbox / plugins

[BPanther]

You should use the rootfs1.tar.bz2 - the neutrino. Just unpack this or use midnight commander, 7zip or whatever you want for the archive.

Or use the E2 function for a settings backup, should also work. The imgbackup makes a full backup for the active partition, not only settings. Thats only the different.

[darog69]

I gave it like this:
Neutrino-rootfs1.tar.bz2
rootfs2.tar.bz2-Openatv.6.3
rootfs3.tar.bz2-Openpli7.1
rootfs4.tar.bz2-Hyperion
After uploading, Neutrino starts, but after choosing in Multiboot startup2 (Openatv6.3) it does not start, on LCD VuSolo4k
What am I doing wrong?

[BPanther]

ALL Kernels must be from Neutrino or the System does not starting. The Kernel has important changes for multiboot. I have written this at the multiboot guide.

- kernel1_auto.bin -> neues Kernel für MultiBoot
- kernel2_auto.bin -> wie 1 (auch für E2 das neue Kernel benutzen, nicht das von E2 mitgelieferte, sonst hängt der Bootvorgang!)
- kernel3_auto.bin -> wie 1 (auch für E2 das neue Kernel benutzen, nicht das von E2 mitgelieferte, sonst hängt der Bootvorgang!)
- kernel4_auto.bin -> wie 1 (auch für E2 das neue Kernel benutzen, nicht das von E2 mitgelieferte, sonst hängt der Bootvorgang!)

or translated with google:

- kernel1_auto.bin -> new kernel for MultiBoot
- kernel2_auto.bin -> like 1 (also for E2 use the new kernel, not that supplied by E2, otherwise the boot process hangs!)
- kernel3_auto.bin -> like 1 (also for E2 use the new kernel, not that supplied by E2, otherwise the boot process hangs!)
- kernel4_auto.bin -> like 1 (also for E2 use the new kernel, not that supplied by E2, otherwise the boot process hangs!)

[darog69]

Thank you very much for your patience and help, one more question, do I have to add an entry in fstab in every image from subsequent startups 2,3,4 ?
The image started after choosing startup2, but it's not Openatv but Openvision, I don't know why, and in the STB-Startup Plugin I have


root@vusolo4k:~# blkid
/dev/mmcblk0p11: UUID="8d71212b-589a-4737-95b6-bcb5b7c19c8c" TYPE="ext4"
/dev/mmcblk0p9: UUID="9737299b-f420-47ec-9ff6-446b309f268a" TYPE="ext4"
/dev/mmcblk0p7: UUID="5dd8769c-0277-4c0f-9c0c-d2990b28b723" TYPE="ext4"
/dev/mmcblk0p5: UUID="6b9b8057-b8fd-44be-afff-e1516054e567" TYPE="ext4"
/dev/mmcblk0p1: TYPE="vfat"
/dev/sda1: LABEL="hdd" UUID="eeb7e2a7-110c-4a4c-b14b-1012a3985b5f" TYPE="ext4"