Desperate! Firedtv DVBT/CI, encrypted channels

malte · **Joined:** 02 Feb 2009, 16:08 **Posts:** 13

mythtv, DVB-T, Boxer (teracom) sweden
Fedora 12, kernel

When i first got the firedtv i had an older patched kernel, this worked on all my encrypted channels, but then after a few months i could not decrypt 1 channel (TV3), Then after a while next one went down (kanal 5), and finaly all the channels on that mux.

I decided to upgrade, i started with fedora 11, kernel 2.6.30 (or 29, cant remember), but it got worse, now i could only decrypt 2 channels out of about 20, and it kept craching, so another upgrade! Fedora 12 (11.91), downgraded the kernel at first (problems with video-driver and kernel), now it got stable, but no encrypted channels at all? Upgraded to the latest kernel: 2.6.31-23, no luck.
It just tells me:

Code:

2009-09-24 16:29:02.247 DVB#0 CA: CiHandler needs CA_PMT
2009-09-24 16:29:02.247 DVB#0 CA: Creating CA_PMT, ServiceID = 840
2009-09-24 16:29:02.247 Adding elementary stream: video-mpeg2, pid(0x351)
2009-09-24 16:29:02.247 Adding elementary stream: audio-mp1-layer[1,2,3], pid(0x350)
2009-09-24 16:29:02.247 Adding elementary stream: private-data, pid(0x34e)
2009-09-24 16:29:02.247 DVB#0 CA: Sending CA_PMT with CPLM_ONLY to CI slot #0
Setting CA PMT.
Sending message=[9f 80 32 ]
2009-09-24 16:29:02.775 DTVSM(0) Error: Wrong PMT; pmt->pn(4780) desired(840)
2009-09-24 16:29:02.775 DTVSM(0) Error: Wrong PMT; pmt->pn(4770) desired(840)
2009-09-24 16:29:04.072 AFD: Opened codec 0xa0178e0, id(MPEG2VIDEO) type(Video)
2009-09-24 16:29:04.073 AFD: codec MP3 has 2 channels
2009-09-24 16:29:04.073 AFD: Opened codec 0xa017dd0, id(MP3) type(Audio)
2009-09-24 16:29:04.073 AFD: codec AC3 has 2 channels
2009-09-24 16:29:04.075 AFD: Opened codec 0xa0183c0, id(AC3) type(Audio)
2009-09-24 16:29:04.241 Preview: Grabbed preview '/var/mythtv/1002_20090924162841.mpg' 720x576@64s
[b]2009-09-24 16:29:06.504 PID 0x350 status: Encrypted[/b]
[b]2009-09-24 16:29:10.413 PID 0x351 status: Encrypted[/b]

I have checked and rechecked every setting, scanned and other testing with:

dvbt-scanaid
w_scan
scandvb
tzap (says has lock)
mplayer
cat (dvr0)

They all find it, but no go.

I decided that it was the CA module, so i went back to the store, they tested it, it was working.. Then i took the firedtv to a place they use windows (i don't), tested it, well it worked perfekt.. Updated the firmware when i had the chance.
I have perfekt signal, free view to the transmitter.

So, please, if anyone has an idea, or anything, please tell me.

If you need certain logs, tell me and i fix it!

Actually don't know if anyone here

.

Regards
Malte

JS36 · **Joined:** 06 Aug 2009, 10:55 **Posts:** 5

Think im having the same problem, many people have gotten problem with the encrypted channels lately in linux. Mine worked perfect before some upgrades in the package tree but im not sure what upgrades i did...

malte · **Joined:** 02 Feb 2009, 16:08 **Posts:** 13

JS36 wrote:

Think im having the same problem, many people have gotten problem with the encrypted channels lately in linux. Mine worked perfect before some upgrades in the package tree but im not sure what upgrades i did...

It looks that way yes.

The thing is that it finds the video/audio stream, and then complains about the encrypt on them.

Im going to try the latest fedora kernel now: 2.6.31-40, if that don't work i don't really know how to proceed, downgrade the system to a maybe working, but unstable, or keep the new with only fta channels...

Code:

2009-09-24 16:29:02.247 DVB#0 CA: Sending CA_PMT with CPLM_ONLY to CI 
...
2009-09-24 16:29:04.072 AFD: Opened codec 0xa0178e0, id(MPEG2VIDEO) type(Video)
2009-09-24 16:29:04.073 AFD: codec MP3 has 2 channels
2009-09-24 16:29:04.073 AFD: Opened codec 0xa017dd0, id(MP3) type(Audio)
2009-09-24 16:29:04.073 AFD: codec AC3 has 2 channels
2009-09-24 16:29:04.075 AFD: Opened codec 0xa0183c0, id(AC3) type(Audio)
2009-09-24 16:29:04.241 Preview: Grabbed preview '/var/mythtv/1002_20090924162841.mpg' 720x576@64s
2009-09-24 16:29:06.504 PID 0x350 status: Encrypted
2009-09-24 16:29:10.413 PID 0x351 status: Encrypted
...

JS36 · **Joined:** 06 Aug 2009, 10:55 **Posts:** 5

I'm using Ubuntu Jaunty and my problem is pretty similar but i have a few more errors, but still the only problem is that i can't watch encrypted channels...
mythtv, DVB-T, Boxer (teracom) sweden too

Code:

2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(900) desired(1050)
2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(760) desired(1050)
2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(910) desired(1050)
2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(970) desired(1050)
2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(1110) desired(1050)
2009-09-04 07:13:16.131 DTVSM(0) Error: Wrong PMT; pmt->pn(1090) desired(1050)
2009-09-04 07:13:16.132 DTVSM(0) Error: Wrong PMT; pmt->pn(65534) desired(1050)
2009-09-04 07:13:16.132 DTVSM(0) Error: Wrong PMT; pmt->pn(4510) desired(1050)
2009-09-04 07:13:16.132 DTVSM(0) Error: Wrong PMT; pmt->pn(4540) desired(1050)
2009-09-04 07:13:16.132 DTVSM(0) Error: Wrong PMT; pmt->pn(4660) desired(1050)
2009-09-04 07:13:16.138 DVB#0 CA: CiHandler needs CA_PMT
2009-09-04 07:13:16.138 DVB#0 CA: Creating CA_PMT, ServiceID = 1050
2009-09-04 07:13:16.138 Adding elementary stream: video-mpeg2, pid(0x423)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x35)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x61)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x80)
2009-09-04 07:13:16.138 Adding elementary stream: audio-mp1-layer[1,2,3], pid(0x422)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x35)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x61)
2009-09-04 07:13:16.138 Adding CA descriptor: CASID(0x500), ECM PID(0x80)
2009-09-04 07:13:16.138 Adding elementary stream: private-data, pid(0x420)
2009-09-04 07:13:16.138 DVB#0 CA: Sending CA_PMT with CPLM_ONLY to CI slot #0
Setting CA PMT.
Sending message=[9f 80 32 ]
2009-09-04 07:13:16.191 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x422
2009-09-04 07:13:16.471 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x10
2009-09-04 07:13:16.471 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x423
2009-09-04 07:13:16.591 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x0
2009-09-04 07:13:16.711 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x10
2009-09-04 07:13:16.711 DTVSM(0) Error: Wrong PMT; pmt->pn(5330) desired(1050)
2009-09-04 07:13:16.711 DTVSM(0) Error: Wrong PMT; pmt->pn(4760) desired(1050)
2009-09-04 07:13:17.716 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x10
2009-09-04 07:13:18.992 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x2f8
2009-09-04 07:13:20.119 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x384
2009-09-04 07:13:20.263 PID 0x422 status: Encrypted
2009-09-04 07:13:21.241 PIDInfo(0): Failed to open demux device /dev/dvb/adapter0/demux0 for filter on pid 0x10

malte · **Joined:** 02 Feb 2009, 16:08 **Posts:** 13

I get about the same on that channel to (kanal 5?)

But the main thing is, it don't matter if the "boxer" card are in the CAM or not.

I have tried 2 other kernels now, 2.6.29-6 and 2.6.31-40, same thing on both.

I wonder about: Sending message=[9f 80 32 ] thou? Its the same on both non fta and fta channels?

I read something about setting firedtv (cam?) to only fta, maybe something the driver sends get it in that state?

I have a new CAM now: Dilog 990525 boxer approved, it works perfekt i windows.

dvbsnoop confirms the settings:

Code:

DVB-DescriptorTag: 90 (0x5a)  [= terrestrial_delivery_system_descriptor]
            descriptor_length: 11 (0x0b)
            Center frequency: 0x03c76840 (= 634000.000 kHz)
            Bandwidth: 0 (0x00)  [= 8 MHz]
            priority: 1 (0x01)  [= HP (high priority) or Non-hierarch.]
            Time_Slicing_indicator: 1 (0x01)  [= Time Slicing is not used.)]
            MPE-FEC_indicator: 1 (0x01)  [= MPE-FEC is not used.)]
            reserved_1: 3 (0x03)
            Constellation: 2 (0x02)  [= 64-QAM]
            Hierarchy information: 0 (0x00)  [= non-hierarchical (native interleaver)]
            Code_rate_HP_stream: 2 (0x02)  [= 3/4]
            Code_rate_LP_stream: 0 (0x00)  [= 1/2]
            Guard_interval: 3 (0x03)  [= 1/4]
            Transmission_mode: 1 (0x01)  [= 8k mode]
            Other_frequency_flag: 1 (0x01)
            reserved_2: 4294967295 (0xffffffff)

The thing is, Henrik Kurelid also has boxer (i believe?), but he hasn't been here in a while, im going to try to reach him.

JS36 · **Joined:** 06 Aug 2009, 10:55 **Posts:** 5

I have found this one http://mythtv-fr.tuxfamily.org/forums/v ... ?pid=11278
my school-french isn't the best one so i tried using google-translate and this is what i got out of it:

Quote:

I think you've already read the info FireDTV on linux and linux driver availability.

It is clearly mentioned that the driver does not work with MythTV, it must be remembered that these drivers are quite recent and it uses the new interface S2API as MythTV developers have not yet integrated or validated elsewhere.

We must also remember that the developers have decided that MythTV interface s2api (which is the support of HDTV for DVB) will never be supported by version 0.21, but built only in version 0.22 (available only in version " Development "by compilation to date). I watch this integration (5882 on the ticket svn) which seems stalled for some time and patches available, no longer work with the latest versions of 0.22.

So to summarize, the drivers of the DVB-S2 cards are now integrated into the 2.6.29 kernel, they are mostly functional with Kaffeine, but not with MythTV. The release date of version 0.22 of MythTV is not advertised (and I do not think it is for tomorrow). So unfortunately, no solution in sight. (It is very early in the development process)

I also remember that the drivers of the DVB-S2 cards introduce new concepts that are not included in any version of MythTV. IT is impossible to receive the DVB standard part by using a DVB-S2 (everything works or nothing works, unfortunately).

So this means that it's mythtv 0.22 we need to get it working, have you tried the latest SVN? I'm going to test the patches and the latest SVN as soon as possible.

malte · **Joined:** 02 Feb 2009, 16:08 **Posts:** 13

That text was about dvb-S2 not terrestial, and the problem is outside mythtv, ive tried 0.22 (from fedora rawhide).

Or your work in mplayer, kaffein etc? Mine don't.

rmst · **Posted:** 30 Sep 2009, 20:25

Hi,

As I have mentioned earlier I too use DVB-T in Sweden and until now I had not noticed that something strange had started to happen lately. However, I too am having trouble with e.g. TV3 and Kanal5 on my FireDTV. I have used the same kernel since before I know that it was working fine. However I have updated MythTV to a newer 0.21-fixes release.

When looking through the logs after an "incident" when trying to watch TV3 i noticed that the Ca2Host message containing the PMT looked suspiciously large. From a first glance it looks like the length is more than 127, which means that the length field should be coded in an Length-Value notation instead of normal Value notation. Currently the driver sends a message to the card where it tells the card that the length of the message is in the area of 10^15 bytes. Quite big in other words...

The reason might be either that the CA descriptors of the channels might have changed or my latest MythTV upgrade does the CA descriptor parsing somewhat different than earlier versions (which I doubt).

I will look into this during the week and keep you posted.

Getmarken · **Joined:** 25 Apr 2009, 21:45 **Posts:** 1

Today I use Ubuntu Koala 9.10, I changed because the kernel have Firedtv as originally. When i used 9.4 with kernel 2.30 a few of my paychannels in the "boxer pakage" where funktioning but not all. Today no paychaller works! I use either Me-TV or kaffeine. Now I wonder if someone can tell me how to test what information the "CI0" have?? In XP on the same computer all my paychannels works. /Lasse

malte · **Joined:** 02 Feb 2009, 16:08 **Posts:** 13

Definitely a problem caused by boxer, found this(swedish):

http://www.minhembio.com/forum/index.ph ... pic=241363

Desperate! Firedtv DVBT/CI, encrypted channels

Who is online