[vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-22 Thread Pierre-Yves Paranthoen (PERSO)
hi Klaus,
 
Ok here are a few results :
 
1.4.7 :
Resetting slot 0...ok.
Resetting slot 1...ok.
Module ready in slot 1
Creating connection: slot 1, tcid 1
 9 -- 01 01 82 01 01
 9 -- 01 01 83 01 01 80 02 01 00
   .  .  .  .  .  .  .  .  .
 9 -- 01 01 A0 01 01
 9 -- 01 01 80 02 01 80
   .  .  .  .  .  .
 9 -- 01 01 81 01 01
 9 -- 01 01 A0 07 01 91 04 00 01 00 41 80 02 01 00
   .  . .  .  .  .  .  .  .  A  .  .  .  .
OpenSession 00010041
New Resource Manager (session id 1)
 9 -- 01 01 A0 0A 01 92 07 00 00 01 00 41 00 01
 9 -- 01 01 80 02 01 00
   .  .  .  .  .  .
1: == Profile Enq
 9 -- 01 01 A0 09 01 90 02 00 01 9F 80 10 00
 9 -- 01 01 80 02 01 00
   .  .  .  .  .  .
 9 -- 01 01 A0 01 01
 9 -- 01 01 80 02 01 80
   .  .  .  .  .  .
 9 -- 01 01 81 01 01
 9 -- 01 01 A0 09 01 90 02 00 01 9F 80 11 00 80 02 01 00
   .  . .  .  .  .  .  .  .  .  .  .  .  .  .  .
1: == Profile
1: == Profile Change
 9 -- 01 01 A0 09 01 90 02 00 01 9F 80 12 00
 9 -- 01 01 80 02 01 00
   .  .  .  .  .  .
 9 -- 01 01 A0 01 01
 9 -- 01 01 80 02 01 80
   .  .  .  .  .  .
 9 -- 01 01 81 01 01
 9 -- 01 01 A0 09 01 90 02 00 01 9F 80 10 00 80 02 01 00
   .  . .  .  .  .  .  .  .  .  .  .  .  .  .  .
1: == Profile Enquiry
1: == Profile
 9 -- 01 01 A0 1D 01 90 02 00 01 9F 80 11 14 00 01 00 41 00 02 00 41 00 03
00 41 00 24 00 41 00 40 00 41
 9 -- 01 01 80 02 01 00
   .  .  .  .  .  .
 9 -- 01 01 A0 01 01
 9 -- 01 01 80 02 01 80
   .  .  .  .  .  .
 9 -- 01 01 81 01 01
 9 -- 01 01 A0 07 01 91 04 00 02 00 41 80 02 01 00
   .  . .  .  .  .  .  .  .  A  .  .  .  .

 
1.7.0 ( i've swaped i few channels) :
 
Slot 1: reset...ok.
Slot 2: reset...ok.
Slot 1: no module present
Slot 2: module ready
Slot 2: creating connection 1/1
Slot 2: create connection 1/1
 2: -- 01 01 82 01 01
 2: -- 01 01 83 01 01 80 02 01 00
.  .  .  .  .  .  .  .  .
Slot 2: connection created 1/1
Slot 2: receive data 1/1
 2: -- 01 01 81 01 01
 2: -- 01 01 A0 07 01 91 04 00 01 00 41 80 02 01 00
.  . .  .  .  .  .  .  .  A  .  .  .  .
Slot 2: open session 00010041
Slot 2: new Resource Manager (session id 1)
 2: -- 01 01 A0 0A 01 92 07 00 00 01 00 41 00 01
Slot 2: == Profile Enq (1)
 2: -- 01 01 A0 09 01 90 02 00 01 9F 80 10 00
 
 
Pierre
 
 
 
 
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-22 Thread Klaus Schmidinger
On 04/22/08 18:58, Pierre-Yves Paranthoen (PERSO) wrote:
 hi Klaus,
  
 Ok here are a few results :
 ...

Please provide more data - everything until you switch to
an encrypted channel.

Klaus


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-20 Thread Pierre-Yves Paranthoen (PERSO)
Hi,

I've been using VDR for a while now uder an old 1.4.7 vdr version with a
DVB-S Nexus with CI  and my official subscription card.
I wanted to upgrade to the lastest version of VDR and compiled it all OK.
But, the problem is that the new version can't switch to encrypted channels.
Is there something particular to done to enable encrypted channels ?
Particular syntax for the channels.conf file ?

I could not find that in the docs.

Thanks for helping.

Regards

Pierre



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-20 Thread Klaus Schmidinger
On 04/20/08 08:55, Pierre-Yves Paranthoen (PERSO) wrote:
 Hi,
 
 I've been using VDR for a while now uder an old 1.4.7 vdr version with a
 DVB-S Nexus with CI  and my official subscription card.
 I wanted to upgrade to the lastest version of VDR and compiled it all OK.
 But, the problem is that the new version can't switch to encrypted channels.
 Is there something particular to done to enable encrypted channels ?
 Particular syntax for the channels.conf file ?

Please post the channels.conf entry of one of these channels.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-20 Thread Pierre-Yves Paranthoen (PERSO)
Hi Klaus and thanks for getting back to me.
 
I tried my orginal (ver 1.4.7) channels.conf under the new installation
using this syntax :
 
TF1;CSAT:11895:vC34:S19.2E:27500:171:124=fra,125=eng:53:500,100:8371:1:1074:
0
 
As it was not working i've generated a new channels.conf :
 
TF1;CSAT:11895:vO0S0:S19.2E:27500:171:124=fra,125=eng:53:0:8371:1:1074:0
 
I also tried to manually edit the channel info under the OSD and put the FTA
value as described in the changelog. Then change to another channel and came
back to the modified one.
 
No result at all. 
 
 
I'm still investigating and i've also remarked that VDR was randomly
accessing correclty to the CAM module :
 
first case :
 
Mar 31 07:49:04 localhost vdr: [18366] CAM 1: no module present
Mar 31 07:49:05 localhost vdr: [18366] CAM 2: module present
Mar 31 07:49:06 localhost vdr: [18366] CAM 2: module ready

Second case :
Mar 31 08:42:07 localhost vdr: [18366] CAM 1: no module present
Mar 31 08:42:10 localhost vdr: [18366] CAM 2: Aston Module 1.0300, 01, 0100,
0100
 
 
I came back once more under 1.4.7 and the second case always runs OK.
 
preety strange ...
 
Pierre
 
 
On 04/20/08 08:55, Pierre-Yves Paranthoen (PERSO) wrote:

 Hi,

 

 I've been using VDR for a while now uder an old 1.4.7 vdr version with a

 DVB-S Nexus with CI  and my official subscription card.

 I wanted to upgrade to the lastest version of VDR and compiled it all OK.

 But, the problem is that the new version can't switch to encrypted
channels.

 Is there something particular to done to enable encrypted channels ?

 Particular syntax for the channels.conf file ?



Please post the channels.conf entry of one of these channels.



Klaus


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-20 Thread Klaus Schmidinger
On 04/20/08 11:31, Pierre-Yves Paranthoen (PERSO) wrote:
 Hi Klaus and thanks for getting back to me.
  
 I tried my orginal (ver 1.4.7) channels.conf under the new installation 
 using this syntax :
  
 TF1;CSAT:11895:vC34:S19.2E:27500:171:124=fra,125=eng:53:500,100:8371:1:1074:0
  
 As it was not working i've generated a new channels.conf :
  
 TF1;CSAT:11895:vO0S0:S19.2E:27500:171:124=fra,125=eng:53:0:8371:1:1074:0

Looks good.

 I also tried to manually edit the channel info under the OSD and put the 
 FTA value as described in the changelog. Then change to another channel 
 and came back to the modified one.
  
 No result at all.
  
  
 I'm still investigating and i've also remarked that VDR was randomly 
 accessing correclty to the CAM module :
  
 first case :
  
 Mar 31 07:49:04 localhost vdr: [18366] CAM 1: no module present
 Mar 31 07:49:05 localhost vdr: [18366] CAM 2: module present
 Mar 31 07:49:06 localhost vdr: [18366] CAM 2: module ready
 Second case :
 Mar 31 08:42:07 localhost vdr: [18366] CAM 1: no module present
 Mar 31 08:42:10 localhost vdr: [18366] CAM 2: Aston Module 1.0300, 01, 
 0100, 0100
  
  
 I came back once more under 1.4.7 and the second case always runs OK.

I'm not quite sure what you mean with first and second case.
What's the difference between these two cases?

You could try changing

#define MODULE_CHECK_INTERVAL 500 // ms

to a higher value (like 1000 or so).

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Upgrading from 1.4.7 to 1.7.0 : info: Channel not available!

2008-04-20 Thread Klaus Schmidinger
On 04/20/08 12:23, Pierre-Yves Paranthoen (PERSO) wrote:
 Sorry for missexplaning.
  
 First case is CAM results detection in 1.7.0 only.
  
 Second case means the CAM is 100% correctly detected under 1.4.7 and 
 randomly and correctly detected under 1.7.0 (a correct detection maybe 
 each 15/20 times after a vdr-1.7.0 restart)
  
 I've made changes in ci.c (initial 500ms, second 1000 ms, third 2000 ms) 
 then restart after a make clean and recompilation. Here is a log extract 
 using the latest generated channels.conf :
  
 (channels 26  36 are making part of my valid subscription)
  
 Apr 20 12:13:17 localhost vdr: [27875] CAM 1: no module present
 Apr 20 12:13:17 localhost vdr: [27875] CAM 2: module ready

Since there is no more CAM 2:... message after this, it looks like
your CAM did not respond.

Please activate the DumpTPDUDataTransfer and DebugProtocol switches
in ci.c and send me the resulting output from both version 1.4.7 and
1.7.0.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr