MythTV gets no signal when CI is attached to DVB-S card

[cg@…]

I'm using recent (15290) trunk with a DVB-S card (Satelco EasyWatch? DVB-S PCI) that supports an optional CI/CAM solution. The card works normally when no CI is attached in MythTV: I can use DiseqC, scan for channels etc.

As soon as I attach the CI (doesn't matter if the CAM/Smartcard is inserted or not) the card no longer gets a signal, _but_ only in MythTV. Scanning and szap'ing & dvbstream'ing on the console works as expected and the encrypted streams get decoded by the CAM.

I've tested this with two cards of the same type with the results being the same. I'm available for testing, you can also contact me on IRC in #mythtv on Freenode (anykey_).

[danielk]

We're going to need a "mythbackend -v record,channel,siparser" log both with and without the CI attached to the card.

Also does DVR work? If not, this is probably a driver issue for the DVB folks to look at.

[cg@…]

I can get you the log in a few days (probably an Friday). What do you mean with 'DVR'? The device in /dev/dvb/adapter0/dvr0? Together with cat?

[Janne Grunau]

Please make sure that the device works. Either with tuning the device and cat /dev/dvb/adapterX/dvr/0 or with another application with dvb support (VDR, kaffeine, ...)

[cg@…]

The device works with the following combination of commands:

szap -a0 -p -r -c channels_srg.conf "SF zwei"
cat /dev/dvb/adapter0/dvr0 > /TV/test.ts

Attached is a log from the backend, record,channel,siparser: log_record_scrambled.log is a log while recording an encrypted channel that should be decrypted by the CAM (works with the above commands) log_record_fta.log is a log while recording a free-to-air channel that should work without a CAM

In both cases, neither a file of the recording is created nor video is displayed on the frontend. This is a pretty blocker here

[cg@…]

Record log of a FTA channel

[cg@…]

Record log of a scrambled channel

[cg@…]

As requested by Janne in IRC, a log without the CI/CAM attached

[nick@…]

All, I can confirm this bug as its present in my system, using the same card/ci.

[robertm]

Original poster no longer able to reproduce this problem. Closing for now, but someone can open a new ticket with fresh verbose logs if they still see something like this.