52 replies to this topic

[bloke76]

yeah, it seems to be an driver issue.

as wanwizard says, only a gui restart, or disable/able cam gets it back working.

 

such a shame, as it is so inconvenient. sigh

 

I also experience that openpli gets very slow and it takes a while until I am able to exit the ci cam options, it looks like the box is very busy and hanging. Sometimes the ci module doesnt get recognized, a gui restart helps.

Edited by bloke76, 6 February 2024 - 08:55.

[littlesat]

The communication to the ci ‘menu’ can indeed be slow… nothing to do about this as the ci is the thing that respond slow. CI is actually kind of sj… e.g. also handling ci+ takes multiple even more or up to 10 seconds…. Causing races and dead locks especially when drivers do not take this into account. Maybe that is also why ‘slowzap’ plugin might add value…

Edited by littlesat, 6 February 2024 - 09:02.

[John 74]

Hello, which would be the best buy for a brand new receiver that would work together with Kabelio (CI+) and OpenPli 9? Maybe two recommendations?

Thanks and greetings!

[Dimitrij]

Pulse4K(mini) /Zgemma(twin/combo)/GB UE 4K

Edited by Dimitrij, 11 April 2024 - 07:53.

[littlesat]

Maybe also consider trying Develop? As far I know there are changes made to the CI handling here.

[Dimitrij]

The VU+ receiver is the worst option for using CI+, at least on openPLi.

[DimitarCC]

The VU+ receiver is the worst option for using CI+, at least on openPLi.

 

I dont agree since most of CI+ modules work fine with Vu+ boxes with OpenPLi develop without any additional plugins...

I dont see any issues with zapping and oscam in parallel if the settings are correct.

In fact Pulse4K working worst than Vu+ (at least with my CI+ module...dont know about Kebelio) and have to be installed a plugin so to work ok and still even with the plugin sometimes i get a black screen on zap. I dont have that issues with Vu+Duo4KSE without any plugins.

That with OpenPLi develop...

Edited by DimitarCC, 11 April 2024 - 10:16.

[Pr2]

You need a plugin to have CI+ on OpenPLi whatever the STB brand. On VU+ you need the CI+ certificate file while on some other brand you need a small application running.

You probably think that you don't need a plugin because autorestore does the job for you and restore the certificate.

 

Pulse4K is also working fine with the CI+ but having CI+ working is a savant combination of timing, different plugin: slowzap for CI and CI assignement, and sometimes some specific setup in oscam dvbapi file.

You can have different issue with different brand and a setup working fine with brand A will not work as-is out-of-the-box on brand B, every settings needs to be tuned.

You can compare CI+ setup with HDMI-CEC setup.

 

My father is TV addict and he is using both the CI+ and OScam on a Pulse 4K and trust me at the very first problem he had he called me. So if CI+ had problems with the Pulse4K I would be aware. 

But of course it is based on my own experience with the CI+ CAM that I can test on my setup.

 

For you black screen problem install slow zap for CI and enable the Restart service after play (find the ones that needs it) and your black screen problem will be solved.

[DimitarCC]

I think we have to differentiate things....

One is certificates another is external plugin (binary) to be needed for CI+.

Here we talking in particular for Vu+... I have 4 models (4K) that have CI slots and none of them have problems with CI+.

SlowZap is not needed for Vu since as i said there are no issues with CI+ decoding and handling. Oscam works fine too in parallel with CI+ module if you assign correctly the services and blacklist the sids.

Dont misunderstand me i like Pulse4K too but the requirement to use a plugin (binary) that fixes CI+ handling make it to be worse than Vu+ which requires certificates only.

Thats why i dont agree Vu is worst choice for CI+ when it actually works better.

Edited by DimitarCC, 11 April 2024 - 13:11.

[littlesat]

You need a plugin to have CI+ on OpenPLi whatever the STB brand. 

->

Not true... for a lot of boxes you only need to put licenses/certificates on the correct location and format.

 

At this moment it is sometimes needed to disable and re-enable the CI+ module to get it correctly (re)initialized... so we need a kind off OFF/ON method after a restart or reboot etc....... but most times it simply works

 

With the newer code there exists a mechanism that checks if a CI module does indeed encrypt a service. It can be considered to add a kind of work-a-round that does disable and re-enable a CI when you zap to a service and after a specific timeout it is not decoded... or something like that.... just to keep the CI awake.... not optimal, but it might be considered... 

Edited by littlesat, 11 April 2024 - 14:11.

[DimitarCC]

 

Not true... for a lot of boxes you only need to put licenses/certificates on the correct location and format.

 

 

Yes that's the case with Vu+....So far i didnt have issues with module freeze. So i didn't had need to restart it...Ofcource that on Vu+Duo4KSE and with my CI+ module. Behavior varies between modules and boxes.

But definitely Vu+ is not the worst choice now

[WanWizard]

Agree, and

 

SlowZap is not needed for Vu since as i said there are no issues with CI+ decoding and handling. Oscam works fine too in parallel with CI+ module if you assign correctly the services and blacklist the sids.

 

this is very important.

 

I have found that if I don't use a combination of CI assigment and Oscam blacklist, to make sure any particular SID is only handled by either the CI or Oscam, it is not stable on VU+.

 

Since I've properly configured it, I never have a CI failure in my Solo 4K anymore.

 

The only issue that remains is that when I am testing and restarting Enigma a lot, the communication with the CI is sometimes lost, probably due to the fact it isn't initialized correctly when Enigma starts again, so I need to disable/enable to get it to work again.

[littlesat]

As far I know indeed slowzap does not really help here and the only thing you indeed need to do is do the OFFON method in case you restart enigma2 and sometimes the box... I still hope we can find a way to improve that part.

[DimitarCC]

 

The only issue that remains is that when I am testing and restarting Enigma a lot, the communication with the CI is sometimes lost, probably due to the fact it isn't initialized correctly when Enigma starts again, so I need to disable/enable to get it to work again.

 

What is lost? What module says when you go in CI menu? Is it gives error?

I mean what is the output from internal module menu?

[WanWizard]

The driver writes timeout errors to the log.

 

Normally when the module is in use, you see stuff like

[76710.411046] >>cid=1, sid=0 r=2 s=0
[76711.911807] >>cid=1, sid=0 r=2 s=0

in the log.

 

If the issue appears, it says something like

[76710.411046] >>cid=1, timeout

In the menu, the module is still visable, but when you select it (OK on the name to enter the module menu), it does not respond.

 

Doing an "init" or a "reset" in the CI menu also does nothing, only disable/enable reactives it.
 

 

[DimitarCC]

Ok... I have never seen that on Duo4kse... Maybe because drivers are different or have something to do with the different kernel...

[WanWizard]

I've had it on the Duo 4K (not SE) and have it on the Solo 4K.

 

But as said, only occasionally, so it's probably a race in the drivers. But I can reproduce it easily by disabling the CI assignment plugin and removing the Oscam blacklists, and then zap a bit to channels which can be decrypted by both the CI and Oscam.

 

For example NPO1 / 2 / 3 on 23.5, which use simulcrypt, for which I have a Viaccess CI (caid 0500) and two smartcards (Nagra caid 1817 and caid 1818, different providers, same channel).

 

So it might be related to Enigma receiving CW's from different sources for different CAID's simultanously?

Edited by WanWizard, 11 April 2024 - 17:18.

[littlesat]

I know we hate work-a-rounds... but is this something we can detect in enigma2 when it happens?

 

 

The driver writes timeout errors to the log.

 

Normally when the module is in use, you see stuff like

[76710.411046] >>cid=1, sid=0 r=2 s=0
[76711.911807] >>cid=1, sid=0 r=2 s=0

in the log.

 

If the issue appears, it says something like

[76710.411046] >>cid=1, timeout

In the menu, the module is still visable, but when you select it (OK on the name to enter the module menu), it does not respond.

 

Doing an "init" or a "reset" in the CI menu also does nothing, only disable/enable reactives it.

Edited by littlesat, 11 April 2024 - 17:34.

[WanWizard]

First step is to find the problem. Which until now nobody has been able to do.

 

And I doubt it can be solved. The warm boot issue could be worked around by having Enigma disable / enable all CI modules when it starts, but that doesn't fix the other (and more relevant issue) which causes decoding to stop.

 

This is obviously caused by the whole system not being designed to deal with CW's from multiple sources simultanously. So really fixing would most likely require a complete rewrite on the entire CW handling code.

[littlesat]

For common interface the box streams the stuff through the ci then there is no cw involved here….. so far I see it this is a driver issue and at this phase of live it can only be work-a-round

Edited by littlesat, 11 April 2024 - 18:19.