robbieb43

An interesting issue I have found (recognizing this is the pli board) relates to openvix and openatv latest builds (6.6 005 and 7.5 14/8/24).

I have been trying the latest builds as they appear from these two teams as they appear on the feed, to see if they too will support "off the shelf operation" with this troublesome CAM. The answer up until now has been no. However these latest two releases now will clear the Kabelio channels from install. However, once you reboot the CAM fails to initialize and no GUI restarting or inits or resets help. The only way to make it reinitialize is to pull the CAM out and reinsert it with the box booted.  Clearly something I do not want to do very often.

Given that it works OK from the flash and that openpli 9.0 works OK, it seems unfair to blame the drivers on this occasion.

dmesg gives:

[  119.564824] [AUD]: AUDIO_CONTINUE 0 0 aph=0x0
[  119.569200] [AUD]: AUDIO_CONTINUE aph=0 0 0
[  127.888262] 0: cannot recognize pc card
[  131.082648] [VID]: VIDEO_SET_STREAMTYPE 0 
[  131.086779] [VID]: VIDEO_SELECT_SOURCE 1  0

Clearly these images have made improvements but these is some that this CAM does that differs from those used to test the software.

Just a footnote to this.

My newly arrived VU Duo 4k SE, loaded with pli 9 from a very recent overnight build, worked fine without any special configuration with the Kabelio CAM (in other words using the same SW as the Zgemma H7S).  My conclusion would be that if you intend to use Kabelio I would not buy a Zgemma H7S.

Many thanks in particular to Bloke76 for the very useful input and of course to the other contributors.

Hello everyone,

 

since I have started this topic and was not able to get the kabelio cam working with a running oscam I have tried openatv image 7.3.
I have to say it all works smoothly, not even a single issue that stops the CI when both Oscam and Kabelio is in use. CI+ helper is not needed if you dont want the RTL Group channels.

With openpli it was either using CI Module OR Oscam. I've tried to edit the config with Ignore commands, never was able to get it work.

So there must be something in the drivers or image of openpli that is totally different to openatv.

One take away from this is that it seemed to work on openATV and not pli, and it was better with oscam than without on that. I should perhaps give this a go before throwing my box out of the window, given the apparent difference in approaches in pli and oe for CI+ (talked about in the general CI+ thread).

Tried this (actually with ATV7.4) and no luck.

I also note that the zgemma site has its own version of the helper so I tried that and the results were unchanged.

Your problem seems to be that set of descrambling key failed (according to your log). Thats why it says you have no access....
That is generaly issue with the drivers...
If you use a zgemma specific CIPlusHelper plugin how it behave?

I agree. I clearly have had a couple of other quirks along the way that perhaps are issues relating to me setup but with these recent tests, done in a clean environment and newly scanned channels, the error is that the CAM cannot descramble the channel.  Assignment is working as it would not get this far if it was not.

I have tested it with the each of the three helper options and this is what I get:

1. /etc/ciplus: Communications OK

2. Default helper (option /etc/ciplus not installed): Communications OK

3. Zgemma Helper (option /etc/ciplus not installed): Communications Error

I have also now tried OpenATV and OpenVIX with the appropriate helpers and get a similar result: cannot descramble the channel. I even had a try with minisatip on openATV with enigma halted and the /etc/ciplus certs from the helper and it seemed to be doing the same result.

I am reluctantly coming to the conclusion that drivers seems the most likely cause. I wonder whether something in the Kabelio software update (1.0120) that I received when I first activated it has caused an incompatibility?  Look out for a box flying past your window any day soon.

Drivers are the same for all images, they are supplied by the vendor as binary files.

I think this supports the conclusions I am drawing. I note also your earlier comments on drivers and restarts on VU+ boxes: I think you are right and it suggests that things are not working right when you need repeated reboots to get things to initialize etc.

Hello everyone,

 

since I have started this topic and was not able to get the kabelio cam working with a running oscam I have tried openatv image 7.3.
I have to say it all works smoothly, not even a single issue that stops the CI when both Oscam and Kabelio is in use. CI+ helper is not needed if you dont want the RTL Group channels.

With openpli it was either using CI Module OR Oscam. I've tried to edit the config with Ignore commands, never was able to get it work.

So there must be something in the drivers or image of openpli that is totally different to openatv.

One take away from this is that it seemed to work on openATV and not pli, and it was better with oscam than without on that. I should perhaps give this a go before throwing my box out of the window, given the apparent difference in approaches in pli and oe for CI+ (talked about in the general CI+ thread).

Rob, have you read the whole thread?

did you clear file " ci0.xml " before trying again with initializing and adding the channels one by one?

Yes I had and actually did not read it like that, however since I do not know what is happening in the software as you add channels I thought this is worth a try as a long shot (as above, assignment is clearly working but I suppose its possible that certain information is created elsewhere as you add the channel). I started with an empty ci0.xml and added one by one, but sadly to no avail.

I think I have just about exhausted my options - I have used a clean usb flash with no other multiboot images loaded, nothing restored and all but a single tuner enabled. I manually scanned the single transponder with the Kabelio channels. I did this as I felt there were some odd things happening in my previous logs with namespace errors etc.

I used the overnight pli dev build from 22/5/24 and installed the enigma2-plugin-extensions-ci_plus_helper-openpli8.x_4_all plugin. It seems to be best to disable it from running and use the install /etc/ciplus option, however I tried the vanilla helper, and the Zgemma specific helper and  rebooted each time.  No other plugins or softcams were installed.  On some occasions the CI initialises itself after an enigma restart and sometimes it needs to be initialised with a reset. I did not restart again after the manual CAM reset.

The results seem to be the same. This is the abridged log with /etc/ciplus installed and the others disabled, which appears to show everything working except it says I do now have access to this channel. As noted previously, it works in the Technomate.

[CI] Slot 0 plugged
[CI] '1:0:19:E1:2DB4:13E:820000:0:0:0:' is in service list of slot 0... so use it
[CI] (1)Slot 0, usecount now 1
[CI] eDVBCIInterfaces setInputSource(1, CI0)
[CI0] setSource: B
[eDVBCIInterfaces] gotPMT
[CI0] setCaParameter
[CI0] CA demux_id = 0
[CI0] tunernum = 1
[CI0 SESS] slot: 0x35b350



[eMMI_UI] mmiScreenAddText(CI Plus authentication completed successfully)
[eMMI_UI] addText CI Plus authentication completed successfully with id 3
[eMMI_UI] CI Plus authentication completed successfully
[eMMI_UI] mmiScreenFinish
[CI0 SESS] slot: 0x35b350
[CI0 RCC] set_descrambler_key
[CI0 descrambler] using ca device /dev/dvb/adapter0/ca0
[CI0 RCC] setting key: new ca device: 0, new key: 1
[CI0 descrambler] set key failed
[CI0 SESS] slot: 0x35b350
[CI0 SESS] slot: 0x35b350
[eMMI_UI] Tmenu_last
[eMMI_UI] mmiScreenBegin
[eMMI_UI] 2 texts
[eMMI_UI] text tag: 9f 88 03
[eMMI_UI] 15 bytes text
[eMMI_UI] mmiScreenAddText(CI+ KABELIO CAM)
[eMMI_UI] addText CI+ KABELIO CAM with id 0
[eMMI_UI] CI+ KABELIO CAM
[eMMI_UI] text tag: 9f 88 03
[eMMI_UI] 30 bytes text
[eMMI_UI] mmiScreenAddText(Smart card number XXXXXXXXXX-0)
[eMMI_UI] addText Smart card number XXXXXXXXXX-0 with id 1
[eMMI_UI] Smart card number XXXXXXXXXX-0
[eMMI_UI] text tag: 9f 88 03
[eMMI_UI] 20 bytes text
[eMMI_UI] mmiScreenAddText(Press OK to continue)
[eMMI_UI] addText Press OK to continue with id 2
[eMMI_UI] Press OK to continue
[eMMI_UI] text tag: 9f 88 03
[eMMI_UI] 26 bytes text
[eMMI_UI] mmiScreenAddText(No Access for this Service)
[eMMI_UI] addText No Access for this Service with id 3
[eMMI_UI] No Access for this Service
[eMMI_UI] mmiScreenFinish
[CI0 SESS] slot: 0x35b350
[CI0 SESS] recvCloseSessionRequest

I am not even sure I know a sensible next step though one question I do have is: is it possible for the CAM to appear as though it has authenticated but due say to an incorrect certificate, not be communicating correctly?