[VU+ Duo4K SE] ViX 6.3.003 bogs my box down

[Orlandox]

Can you guys check if you have the same problem on OpenBH 5.2 or Vu factory image?

Just save current image in multiboot.

I can check it with OpenBH 5.2.002 later at my Ultimo4K.
P.S. My coffee break is over, have to continue work.

 

[Micci]

Are the people with the problem using some kind of "helper" plugin?

If so you need to set up from scratch without the plugin.

If you are referring to some kind of ”ciplushelper”, then no, not to my knowledge. Tinkered with one ages ago on a different image, but never on ViX.
How to check and see if there is such a plugin? And is there really no other way to remove it but to start from scratch?

 

[tappari]

Can you guys check if you have the same problem on OpenBH 5.2 or Vu factory image?

Just save current image in multiboot.

OpenBH has same problem with Conax info

 

[Orlandox]

Yes, I can confirm that also.



P.S. OpenPLi shows 'initialize module', but no disturbancies or freezing on picture.

 

[tappari]

I made again clean flash without restoring setups and plugins with 003 to my Duo4K SE.
This is what happens when I insert CI+ adapter and card:

It does not go further from this.

 

[Huevos]

I made again clean flash without restoring setups and plugins with 003 to my Duo4K SE.
This is what happens when I insert CI+ adapter and card:
View attachment 64963
It does not go further from this.

Is this the same Finnish module the others are using?

 

[Micci]

Mine is a "LA Digital" (Smit) CI+ module. It shows up as "Conax CA" in the Common Interface menu.
I also have a "Finnsat CAMC-CIP" (Neotion) module that shows up as "Conax CSP CIPLUS CAM" in the Common Interface menu.

Both seem to be working in 6.3.002, although I had to reboot my box yesterday when the paychannels went black on the LA Digital (a very rare occurrence indeed).
Didn't try the Finnsat module in .003.

 

[tappari]

Mine is also Smit. This info is from 6.3 002 image:

 

[tappari]

I just wonder if CI+ authentication system is from ATV because all messages are in German language?

 

[Huevos]

I just wonder if CI+ authentication system is from ATV because all messages are in German language?

That German is not in our enigma so no idea where it is coming from.

 

[Micci]

Somezing german has slipped into the 6.3.003 package for the Duo 4K SE?
My box had some screens in german flicker by when I was restoring my backup at 1st boot. Never done that before.
And I believe german images don't work too well together with CI+ cards.

Herr Flick of ze Gestapo has gone undercover inside our boxes?

 

[Huevos]

The German is not in our enigma (based on a search of the enigma repo and its translations) so must be coming from some third party module.

 

[Orlandox]

From debug log:

< 225.4017> 16:15:13.3582 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 225.4027> 16:15:13.3591 [CI] Slot: 1 setSource: K
< 228.8615> 16:15:16.8179 eDVBCICAManagerSession::setCAIDs casCount = 0
< 232.0273> 16:15:19.9838 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 232.0281> 16:15:19.9845 [CI] Slot: 1 setSource: K
< 235.7083> 16:15:23.6647 eDVBCICAManagerSession::setCAIDs casCount = 0
< 238.8616> 16:15:26.8180 [CI] eDVBCIInterfaces setInputSource(10, CI1)
< 238.8624> 16:15:26.8188 [CI] Slot: 1 setSource: K

and that continues about 3 min and 13 sec after that no disturbancies and no picture freezing. But it still shows 'no module found' ...

 

[Micci]

Flashed to 6.3.003 again and am testing the Finnsat/Neotion CA module instead of the Smit module. Now everything seems to be working. But the CI info is all in german, just like Tappari said.

Will try to see if I can make a multiboot and have my .002 in the other boot slot, just in case.

 

[Micci]

Is there a fix coming for those who have a Smit CI+ module? Someone on the Finnish forum noticed there were some changes to the CI files between .002 and .003.
Everything was running like a dream until .003.
IF IT WORKS, DON’T FIX IT.

I also noticed a difference during 1st boot between .002 and .003. I used the exact same Settings Backup file and restored settings & plugins to both images using the file.

.002 restore went without a hitch and rebooted to a working setup. Both CI+ modules are working.

.003 showed a message in german about a CI error (”CI fehler”) during the restore, until it eventually finished and rebooted. The Smit CI+ module doesn’t work. The Neotion module works, but it’s a bit slow with channel changes.

 

[Huevos]

IF IT WORKS, DON’T FIX IT.

Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.

 

[tappari]

Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.

With which modules it didn`t work? And what are those lot more modules?
Please list them.

 

[Orlandox]

Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.

Is it possible to add a selectable parameter to 'CiSelection' menu, where you can select your module type ? Then both module types should work OK.

 

[Micci]

Yes, but it didn't work for most modules. Now it works on a lot more modules than before, although some are not compatible with the change.

You can't be serious that I'll have to throw away BOTH my modules. One of them is a very new one (supposed to be state-of-the-art) and it started working very sluggishly after the update (channel changes are much slower). Both were working just fine before.

Can you list the modules that DO work, so I don't waste any more money on the wrong one.

Why did you at first deny that there were any changes to the CI files, when there clearly are? And why don't these problems affect any other boxes, just the Duo 4K SE?

Again, if it works, don't fix it.

 

[tappari]

I have 4 modules and SmartWi 3 with 4 client cards. Ultimo4K, Duo4K SE, Uno4K SE and Sony tv are using those.
I`m not going to by 3 new adapters and pair them just because of 6.3 003 image failures.
I just use VU+ Multiboot and 002 image and watch if you and OpenBlackHole team can fix it.