Re: [vdr] vdr-1.6.0 channel not available TT-2300-C FF card only
> SetPlayMode: 0 > frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) > GetDevice 20 0 1 -1 > no device found works: UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 doesn't work: Sky Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 > The problem is following the TT-2300-C card, not the cam or smartcard. > And > it's fine on the TT-1500 Budget card. > The "NO SIGNAL" coincides with the "GetDevice" message. > Any ideas? Can anyone suggest what I can do here? To me this looks like a v4l-dvb driver problem ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
> On 05/08/08 12:12, Simon Baxter wrote: OK - I'm getting this: SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) GetDevice 20 0 1 -1 no device found any ideas? >>> If it makes any difference, I'm running vdr-1.6.0 with a budget >>> TT-1500-C >>> (with Alpha Multicrypt) and a FF TT-2300-C (also with Alpha Multicrypt). >>> The card failing on this channel is the FF one (other card is tied up >>> recording on another transponder) >>> >>> only seems to be failing with a single channel - other encrypted >>> channels >>> within the same boquet work fine >>> >>> works: >>> UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 >>> >>> doesn't work: >>> Sky >>> Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 >> >> Have tried the 1.6.0-1 patch, still get: >> SetPlayMode: 0 >> frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) >> GetDevice 20 0 1 -1 >> no device found >> >> with this channel > > Here what you could try: > > - swap the CAMs > - use only one CAM at a time > - try the CAMs with either of the DVB cards Hi again The problem is following the TT-2300-C card, not the cam or smartcard. And it's fine on the TT-1500 Budget card. It's really weird. It's only the Movies channel affected, and each time I tune to it get about 1 second of picture then "NO SIGNAL". The "NO SIGNAL" coincides with the "GetDevice" message. Any ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 05/08/08 12:12, Simon Baxter wrote: >>> OK - I'm getting this: >>> >>> SetPlayMode: 0 >>> frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) >>> GetDevice 20 0 1 -1 >>> no device found >>> >>> >>> any ideas? >> If it makes any difference, I'm running vdr-1.6.0 with a budget TT-1500-C >> (with Alpha Multicrypt) and a FF TT-2300-C (also with Alpha Multicrypt). >> The card failing on this channel is the FF one (other card is tied up >> recording on another transponder) >> >> only seems to be failing with a single channel - other encrypted channels >> within the same boquet work fine >> >> works: >> UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 >> >> doesn't work: >> Sky >> Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 > > Have tried the 1.6.0-1 patch, still get: > SetPlayMode: 0 > frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) > GetDevice 20 0 1 -1 > no device found > > with this channel Here what you could try: - swap the CAMs - use only one CAM at a time - try the CAMs with either of the DVB cards Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
>> OK - I'm getting this: >> >> SetPlayMode: 0 >> frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) >> GetDevice 20 0 1 -1 >> no device found >> >> >> any ideas? > > If it makes any difference, I'm running vdr-1.6.0 with a budget TT-1500-C > (with Alpha Multicrypt) and a FF TT-2300-C (also with Alpha Multicrypt). > The card failing on this channel is the FF one (other card is tied up > recording on another transponder) > > only seems to be failing with a single channel - other encrypted channels > within the same boquet work fine > > works: > UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 > > doesn't work: > Sky > Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 Have tried the 1.6.0-1 patch, still get: SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) GetDevice 20 0 1 -1 no device found with this channel ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
>>> When recording one channel and attempting to watch another in the same >>> transport stream, or trying to switch to another transport stream (and >>> hence card) I get "channel not available" messages. After switching >>> back and forth to other transport streams, usually I can overcome this >>> problem. But occasionally I it won't play any channels in one specific >>> transport stream or another. >> You could add some debug outputs to >> >> cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView) >> >> to find out why it thinks that channel 9 is not available. >> >> Klaus > > OK - I'm getting this: > > SetPlayMode: 0 > frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) > GetDevice 20 0 1 -1 > no device found > > > any ideas? If it makes any difference, I'm running vdr-1.6.0 with a budget TT-1500-C (with Alpha Multicrypt) and a FF TT-2300-C (also with Alpha Multicrypt). The card failing on this channel is the FF one (other card is tied up recording on another transponder) only seems to be failing with a single channel - other encrypted channels within the same boquet work fine works: UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 doesn't work: Sky Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
>> When recording one channel and attempting to watch another in the same >> transport stream, or trying to switch to another transport stream (and >> hence card) I get "channel not available" messages. After switching >> back and forth to other transport streams, usually I can overcome this >> problem. But occasionally I it won't play any channels in one specific >> transport stream or another. > You could add some debug outputs to > > cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView) > > to find out why it thinks that channel 9 is not available. > > Klaus OK - I'm getting this: SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) GetDevice 20 0 1 -1 no device found any ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
Klaus Schmidinger kirjoitti 3.5.2008 kello 19.06: > On 05/03/08 16:24, Tero Siironen wrote: >> Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: >> >>> On 04/27/08 12:49, Tero Siironen wrote: ... I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. >>> Your CAM seems to "come and go". >>> Please try the 1.6.0-1 maintenance patch from >>> >>> ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff >>> >>> which increases the time between the CAM status checks. >> >> Doesn't help, log is pretty similar still and picture shows now and >> then for couple of seconds > > Looks like there are no more unexpected CAM resets, so the reason > for the > "channel not available" must be something else. Maybe the CAM doesn't > decrypt? > > You could add some debug output to cDevice::Action() to see whether > the TS packets are getting descrambled. Maybe the > TS_SCRAMBLING_TIMEOUT > needs to be increased. I will try to debug it more. The same channel works with VDR 1.4.7 so the CAM works. Also with 1.6.0-1 all other encrypted channels that I've access works with that CAM, so there is something in that one channel which causes problems with 1.6.0-1. But I will report again when I get some more data. -- Tero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 05/03/08 16:24, Tero Siironen wrote: > Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: > >> On 04/27/08 12:49, Tero Siironen wrote: >>> ... >>> I don't know if this is same problem or not but I'm having similar >>> symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot >>> tune >>> to that channel, while 1.4.7 works. As can be seen from the log, the >>> receiving starts from couple of seconds but stops right after giving >>> this channel not available message. My system has DVB-C 2.1 FF card >>> and >>> Satelco Easywatch budget card. All the other encrypted channels works >>> ok, but this one channel has problems with VDR 1.6.0. >>> >> Your CAM seems to "come and go". >> Please try the 1.6.0-1 maintenance patch from >> >> ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff >> >> which increases the time between the CAM status checks. > > Doesn't help, log is pretty similar still and picture shows now and > then for couple of seconds Looks like there are no more unexpected CAM resets, so the reason for the "channel not available" must be something else. Maybe the CAM doesn't decrypt? You could add some debug output to cDevice::Action() to see whether the TS packets are getting descrambled. Maybe the TS_SCRAMBLING_TIMEOUT needs to be increased. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: > On 04/27/08 12:49, Tero Siironen wrote: >> >> ... >> I don't know if this is same problem or not but I'm having similar >> symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot >> tune >> to that channel, while 1.4.7 works. As can be seen from the log, the >> receiving starts from couple of seconds but stops right after giving >> this channel not available message. My system has DVB-C 2.1 FF card >> and >> Satelco Easywatch budget card. All the other encrypted channels works >> ok, but this one channel has problems with VDR 1.6.0. >> > > Your CAM seems to "come and go". > Please try the 1.6.0-1 maintenance patch from > > ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff > > which increases the time between the CAM status checks. Doesn't help, log is pretty similar still and picture shows now and then for couple of seconds May 2 23:03:36 localhost vdr: [4340] VDR version 1.6.0-1 started May 2 23:03:36 localhost vdr: [4340] codeset is 'ISO-8859-1' - known May 2 23:03:36 localhost vdr: [4340] found 23 locales in ./locale May 2 23:03:36 localhost vdr: [4340] loading /video/setup.conf May 2 23:03:36 localhost vdr: [4340] loading /video/sources.conf May 2 23:03:36 localhost vdr: [4340] loading /video/channels.conf May 2 23:03:36 localhost vdr: [4340] loading /video/timers.conf May 2 23:03:36 localhost vdr: [4340] loading /video/svdrphosts.conf May 2 23:03:36 localhost vdr: [4340] loading /video/remote.conf May 2 23:03:36 localhost vdr: [4340] loading /video/keymacros.conf May 2 23:03:36 localhost vdr: [4340] reading EPG data from /video/ epg.data May 2 23:03:37 localhost vdr: [4341] video directory scanner thread started (pid=4340, tid=4341) May 2 23:03:37 localhost vdr: [4342] video directory scanner thread started (pid=4340, tid=4342) May 2 23:03:37 localhost vdr: [4340] probing /dev/dvb/adapter0/ frontend0 May 2 23:03:37 localhost vdr: [4344] CI adapter on device 0 thread started (pid=4340, tid=4344) May 2 23:03:37 localhost vdr: [4340] probing /dev/dvb/adapter1/ frontend0 May 2 23:03:37 localhost vdr: [4342] video directory scanner thread ended (pid=4340, tid=4342) May 2 23:03:37 localhost vdr: [4345] tuner on device 1 thread started (pid=4340, tid=4345) May 2 23:03:37 localhost vdr: [4346] section handler thread started (pid=4340, tid=4346) May 2 23:03:37 localhost vdr: [4348] CI adapter on device 1 thread started (pid=4340, tid=4348) May 2 23:03:37 localhost vdr: [4340] found 2 video devices May 2 23:03:37 localhost vdr: [4340] setting primary device to 1 May 2 23:03:37 localhost vdr: [4349] tuner on device 2 thread started (pid=4340, tid=4349) May 2 23:03:37 localhost vdr: [4350] section handler thread started (pid=4340, tid=4350) May 2 23:03:37 localhost vdr: [4340] assuming manual start of VDR May 2 23:03:37 localhost vdr: [4340] SVDRP listening on port 2001 May 2 23:03:37 localhost vdr: [4340] loading /video/themes/classic- default.theme May 2 23:03:37 localhost vdr: [4340] remote control LIRC - keys known May 2 23:03:37 localhost vdr: [4351] LIRC remote control thread started (pid=4340, tid=4351) May 2 23:03:37 localhost vdr: [4344] CAM 1: module present May 2 23:03:38 localhost vdr: [4341] video directory scanner thread ended (pid=4340, tid=4341) May 2 23:03:39 localhost vdr: [4340] switching to channel 1 May 2 23:03:39 localhost vdr: [4348] CAM 3: no module present May 2 23:03:39 localhost vdr: [4344] CAM 2: no module present May 2 23:03:39 localhost vdr: [4346] channel 4 (Nelonen) event Pe 02.05.2008 22:55-23:05 'IS Urheilu-uutiset' status 4 May 2 23:03:39 localhost vdr: [4346] channel 2 (YLE TV2) event Pe 02.05.2008 22:25-00:50 'Jääkiekon MM 2008: Kanada - Slovenia' status 4 May 2 23:03:39 localhost vdr: [4346] channel 6 (Sub) event Pe 02.05.2008 22:10-23:05 'Bones' status 4 May 2 23:03:39 localhost vdr: [4346] channel 3 (MTV3) event Pe 02.05.2008 22:36-01:10 'Windtalkers' status 4 May 2 23:03:39 localhost vdr: [4346] changing pids of channel 1 from 512+512:650=deu:0:2321 to 512+512:650=deu:1027=fin:2321 May 2 23:03:39 localhost vdr: [4340] retuning due to modification of channel 1 May 2 23:03:39 localhost vdr: [4340] switching to channel 1 May 2 23:03:39 localhost vdr: [4352] live subtitle thread started (pid=4340, tid=4352) May 2 23:03:39 localhost vdr: [4353] receiver on device 1 thread started (pid=4340, tid=4353) May 2 23:03:39 localhost vdr: [4354] TS buffer on device 1 thread started (pid=4340, tid=4354) May 2 23:03:40 localhost vdr: [4346] changing pids of channel 2 from 513+513:660=fin,661=sve:0:2321 to 513+513:660=fin,661=sve:2027=fin:2321 May 2 23:03:40 localhost vdr: [4346] changing pids of channel 3 from 305+305:561=fin:0:817 to 305+305:561=fin:1073=fin:817 May 2 23:03:40 localhost vdr: [4346] changing pids of channel 5 from 514+514:670=esl:0:2321 to 514+514:670=esl:3028=sve,3027=fin:2321 May 2 23:03:41 lo
Re: [vdr] vdr-1.6.0 channel not available
On 05/02/08 19:26, Simon Baxter wrote:
You could add some debug outputs to
cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView)
to find out why it thinks that channel 9 is not available.
Can someone help me out here?How do I do this?
Try the attached patch.
Klaus
--- device.c 2008/04/12 14:12:14 2.2
+++ device.c 2008/05/03 10:49:26
@@ -372,6 +372,7 @@
cDevice *cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView)
{
+ printf("GetDevice %d %d %d %d\n", Channel->Number(), Priority, LiveView, avoidDevice ? avoidDevice->CardIndex() : -1);//XXX
cDevice *AvoidDevice = avoidDevice;
avoidDevice = NULL;
// Collect the current priorities of all CAM slots that can decrypt the channel:
@@ -391,7 +392,9 @@
}
}
if (!NumUsableSlots)
+{printf("no usable CAM slots!\n");//XXX
return NULL; // no CAM is able to decrypt this channel
+}//XXX
}
bool NeedsDetachReceivers = false;
@@ -432,6 +435,7 @@
imp <<= 1; imp |= NumUsableSlots ? 0 : device[i]->HasCi(); // avoid cards with Common Interface for FTA channels
imp <<= 1; imp |= device[i]->HasDecoder(); // avoid full featured cards
imp <<= 1; imp |= NumUsableSlots ? !ChannelCamRelations.CamDecrypt(Channel->GetChannelID(), j + 1) : 0; // prefer CAMs that are known to decrypt this channel
+ printf("j = %d, i = %d, imp = %08X, Impact = %08X\n", j, i, imp, Impact);//XXX
if (imp < Impact) {
// This device has less impact than any previous one, so we take it.
Impact = imp;
@@ -446,6 +450,7 @@
break; // no CAM necessary, so just one loop over the devices
}
if (d) {
+ printf("device %d\n", d->CardIndex());//XXX
if (NeedsDetachReceivers)
d->DetachAllReceivers();
if (s) {
@@ -460,6 +465,7 @@
else if (d->CamSlot() && !d->CamSlot()->IsDecrypting())
d->CamSlot()->Assign(NULL);
}
+ else printf("no device found\n");//XXX
return d;
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
> You could add some debug outputs to > > cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView) > > to find out why it thinks that channel 9 is not available. Can someone help me out here?How do I do this? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 04/24/08 09:08, Simon Baxter wrote: > Hello > > I have 2x DVB-C cards with Alphacrypt multi-cams. A TT-1500-C budget > card and a TT-2300-C FF card and run vdr-xine. > > When recording one channel and attempting to watch another in the same > transport stream, or trying to switch to another transport stream (and > hence card) I get "channel not available" messages. After switching > back and forth to other transport streams, usually I can overcome this > problem. But occasionally I it won't play any channels in one specific > transport stream or another. > > What's the best way to diagnose this? How do I enable debugging to see > more info than is displayed in messages: > > Apr 24 18:53:56 callin vdr: [7375] switching to channel 8 > Apr 24 18:53:56 callin vdr: [30940] transfer thread started (pid=7375, > tid=30940) > Apr 24 18:53:57 callin vdr: [30939] femon receiver thread ended > (pid=7375, tid=30939) > Apr 24 18:53:57 callin vdr: [30941] femon receiver thread started > (pid=7375, tid=30941) > Apr 24 18:53:58 callin vdr: [30940] setting audio track to 1 (0) > Apr 24 18:54:04 callin vdr: [7375] switching to channel 9 > Apr 24 18:54:04 callin vdr: [30940] transfer thread ended (pid=7375, > tid=30940) > Apr 24 18:54:04 callin vdr: [7375] buffer stats: 47564 (2%) used > Apr 24 18:54:04 callin vdr: [7375] info: Channel not available! > Apr 24 18:54:04 callin vdr: [7375] ERROR: attempt to open OSD while it > is already open - using dummy OSD! > Apr 24 18:54:22 callin vdr: [7375] switching to channel 1 > Apr 24 18:54:22 callin vdr: [30942] transfer thread started (pid=7375, > tid=30942) > Apr 24 18:54:22 callin vdr: [30936] TS buffer on device 2 thread ended > (pid=7375, tid=30936) > Apr 24 18:54:22 callin vdr: [30935] buffer stats: 84600 (4%) used > Apr 24 18:54:22 callin vdr: [30935] receiver on device 2 thread ended > (pid=7375, tid=30935) > Apr 24 18:54:22 callin vdr: [30943] receiver on device 2 thread started > (pid=7375, tid=30943) > Apr 24 18:54:22 callin vdr: [30944] TS buffer on device 2 thread started > (pid=7375, tid=30944) > Apr 24 18:54:23 callin vdr: [30945] femon receiver thread started > (pid=7375, tid=30945) > Apr 24 18:54:23 callin vdr: [30942] setting audio track to 1 (0) > Apr 24 18:54:26 callin vdr: [7375] switching to channel 9 > Apr 24 18:54:26 callin vdr: [30942] transfer thread ended (pid=7375, > tid=30942) > Apr 24 18:54:26 callin vdr: [7375] buffer stats: 194204 (9%) used > Apr 24 18:54:26 callin vdr: [7375] info: Channel not available! > Apr 24 18:54:26 callin vdr: [7375] ERROR: attempt to open OSD while it > is already open - using dummy OSD! > Apr 24 18:54:42 callin vdr: [7375] switching to channel 21 You could add some debug outputs to cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView) to find out why it thinks that channel 9 is not available. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 04/27/08 12:49, Tero Siironen wrote: > > ... > I don't know if this is same problem or not but I'm having similar > symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune > to that channel, while 1.4.7 works. As can be seen from the log, the > receiving starts from couple of seconds but stops right after giving > this channel not available message. My system has DVB-C 2.1 FF card and > Satelco Easywatch budget card. All the other encrypted channels works > ok, but this one channel has problems with VDR 1.6.0. > > Here's the channels.conf entry: > > EuroNews;GlobeCast:306000:C0M128:C:6875:2221:2232=eng,2233=deu,2231=fra,2234=ita,2235=esl,2236=por,2237=rus,2238:768:B00:214:0:10:0 > > > and here's the syslog: > > Apr 27 13:31:53 localhost vdr: [10238] cTimeMs: using monotonic clock > (resolution is 999848 ns) > Apr 27 13:31:53 localhost vdr: [10238] VDR version 1.6.0 started > ... > Apr 27 13:31:53 localhost vdr: [10251] CAM 1: module present > ... > Apr 27 13:31:55 localhost vdr: [10251] CAM 1: no module present > Apr 27 13:31:55 localhost vdr: [10251] CAM 1: module present > ... > Apr 27 13:31:57 localhost vdr: [10251] CAM 1: no module present > Apr 27 13:31:57 localhost vdr: [10251] CAM 1: module present > ... > Apr 27 13:31:59 localhost vdr: [10251] CAM 1: no module present > Apr 27 13:31:59 localhost vdr: [10251] CAM 1: module present > Apr 27 13:32:02 localhost vdr: [10251] CAM 1: module ready > Apr 27 13:32:05 localhost vdr: [10251] CAM 1: Conax 4.00e, 01, 0B00, 04B1 > Apr 27 13:32:09 localhost vdr: [10251] CAM 1: doesn't reply to QUERY - > only a single channel can be decrypted > ... > Apr 27 13:33:32 localhost vdr: [10251] CAM 1: module reset > Apr 27 13:33:32 localhost vdr: [10251] CAM 1: module present > Apr 27 13:33:32 localhost vdr: [10238] switching to channel 1 > Apr 27 13:33:32 localhost vdr: [10238] CAM 1: unassigned > ... > Apr 27 13:33:33 localhost vdr: [10251] CAM 1: module ready > Apr 27 13:33:36 localhost vdr: [10251] CAM 1: Conax 4.00e, 01, 0B00, 04B1 > Apr 27 13:33:41 localhost vdr: [10251] CAM 1: doesn't reply to QUERY - > only a single channel can be decrypted Your CAM seems to "come and go". Please try the 1.6.0-1 maintenance patch from ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff which increases the time between the CAM status checks. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
Simon Baxter kirjoitti 24.4.2008 kello 10.08: Hello I have 2x DVB-C cards with Alphacrypt multi-cams. A TT-1500-C budget card and a TT-2300-C FF card and run vdr-xine. When recording one channel and attempting to watch another in the same transport stream, or trying to switch to another transport stream (and hence card) I get "channel not available" messages. After switching back and forth to other transport streams, usually I can overcome this problem. But occasionally I it won't play any channels in one specific transport stream or another. What's the best way to diagnose this? How do I enable debugging to see more info than is displayed in messages: Apr 24 18:53:56 callin vdr: [7375] switching to channel 8 Apr 24 18:53:56 callin vdr: [30940] transfer thread started (pid=7375, tid=30940) Apr 24 18:53:57 callin vdr: [30939] femon receiver thread ended (pid=7375, tid=30939) Apr 24 18:53:57 callin vdr: [30941] femon receiver thread started (pid=7375, tid=30941) Apr 24 18:53:58 callin vdr: [30940] setting audio track to 1 (0) Apr 24 18:54:04 callin vdr: [7375] switching to channel 9 Apr 24 18:54:04 callin vdr: [30940] transfer thread ended (pid=7375, tid=30940) Apr 24 18:54:04 callin vdr: [7375] buffer stats: 47564 (2%) used Apr 24 18:54:04 callin vdr: [7375] info: Channel not available! Apr 24 18:54:04 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:22 callin vdr: [7375] switching to channel 1 Apr 24 18:54:22 callin vdr: [30942] transfer thread started (pid=7375, tid=30942) Apr 24 18:54:22 callin vdr: [30936] TS buffer on device 2 thread ended (pid=7375, tid=30936) Apr 24 18:54:22 callin vdr: [30935] buffer stats: 84600 (4%) used Apr 24 18:54:22 callin vdr: [30935] receiver on device 2 thread ended (pid=7375, tid=30935) Apr 24 18:54:22 callin vdr: [30943] receiver on device 2 thread started (pid=7375, tid=30943) Apr 24 18:54:22 callin vdr: [30944] TS buffer on device 2 thread started (pid=7375, tid=30944) Apr 24 18:54:23 callin vdr: [30945] femon receiver thread started (pid=7375, tid=30945) Apr 24 18:54:23 callin vdr: [30942] setting audio track to 1 (0) Apr 24 18:54:26 callin vdr: [7375] switching to channel 9 Apr 24 18:54:26 callin vdr: [30942] transfer thread ended (pid=7375, tid=30942) Apr 24 18:54:26 callin vdr: [7375] buffer stats: 194204 (9%) used Apr 24 18:54:26 callin vdr: [7375] info: Channel not available! Apr 24 18:54:26 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:42 callin vdr: [7375] switching to channel 21 Hi, I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. Here's the channels.conf entry: EuroNews;GlobeCast:306000:C0M128:C:6875:2221:2232=eng,2233=deu, 2231=fra,2234=ita,2235=esl,2236=por,2237=rus,2238:768:B00:214:0:10:0 and here's the syslog: Apr 27 13:31:53 localhost vdr: [10238] cTimeMs: using monotonic clock (resolution is 999848 ns) Apr 27 13:31:53 localhost vdr: [10238] VDR version 1.6.0 started Apr 27 13:31:53 localhost vdr: [10238] codeset is 'ISO-8859-1' - known Apr 27 13:31:53 localhost vdr: [10238] found 23 locales in ./locale Apr 27 13:31:53 localhost vdr: [10238] loading /video/setup.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/sources.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/channels.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/timers.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/svdrphosts.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/remote.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/keymacros.conf Apr 27 13:31:53 localhost vdr: [10238] reading EPG data from /video/ epg.data Apr 27 13:31:53 localhost vdr: [10248] video directory scanner thread started (pid=10238, tid=10248) Apr 27 13:31:53 localhost vdr: [10249] video directory scanner thread started (pid=10238, tid=10249) Apr 27 13:31:53 localhost vdr: [10249] video directory scanner thread ended (pid=10238, tid=10249) Apr 27 13:31:53 localhost vdr: [10248] video directory scanner thread ended (pid=10238, tid=10248) Apr 27 13:31:53 localhost vdr: [10238] probing /dev/dvb/adapter0/ frontend0 Apr 27 13:31:53 localhost vdr: [10251] CI adapter on device 0 thread started (pid=10238, tid=10251) Apr 27 13:31:53 localhost vdr: [10238] probing /dev/dvb/adapter1/ frontend0 Apr 27 13:31:53 localhost vdr: [10252] tuner on device 1 thread started (pid=10238, tid=10252) Apr 27 13:31:53 localhost vdr: [10253] section handler
[vdr] vdr-1.6.0 channel not available
Hello I have 2x DVB-C cards with Alphacrypt multi-cams. A TT-1500-C budget card and a TT-2300-C FF card and run vdr-xine. When recording one channel and attempting to watch another in the same transport stream, or trying to switch to another transport stream (and hence card) I get "channel not available" messages. After switching back and forth to other transport streams, usually I can overcome this problem. But occasionally I it won't play any channels in one specific transport stream or another. What's the best way to diagnose this? How do I enable debugging to see more info than is displayed in messages: Apr 24 18:53:56 callin vdr: [7375] switching to channel 8 Apr 24 18:53:56 callin vdr: [30940] transfer thread started (pid=7375, tid=30940) Apr 24 18:53:57 callin vdr: [30939] femon receiver thread ended (pid=7375, tid=30939) Apr 24 18:53:57 callin vdr: [30941] femon receiver thread started (pid=7375, tid=30941) Apr 24 18:53:58 callin vdr: [30940] setting audio track to 1 (0) Apr 24 18:54:04 callin vdr: [7375] switching to channel 9 Apr 24 18:54:04 callin vdr: [30940] transfer thread ended (pid=7375, tid=30940) Apr 24 18:54:04 callin vdr: [7375] buffer stats: 47564 (2%) used Apr 24 18:54:04 callin vdr: [7375] info: Channel not available! Apr 24 18:54:04 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:22 callin vdr: [7375] switching to channel 1 Apr 24 18:54:22 callin vdr: [30942] transfer thread started (pid=7375, tid=30942) Apr 24 18:54:22 callin vdr: [30936] TS buffer on device 2 thread ended (pid=7375, tid=30936) Apr 24 18:54:22 callin vdr: [30935] buffer stats: 84600 (4%) used Apr 24 18:54:22 callin vdr: [30935] receiver on device 2 thread ended (pid=7375, tid=30935) Apr 24 18:54:22 callin vdr: [30943] receiver on device 2 thread started (pid=7375, tid=30943) Apr 24 18:54:22 callin vdr: [30944] TS buffer on device 2 thread started (pid=7375, tid=30944) Apr 24 18:54:23 callin vdr: [30945] femon receiver thread started (pid=7375, tid=30945) Apr 24 18:54:23 callin vdr: [30942] setting audio track to 1 (0) Apr 24 18:54:26 callin vdr: [7375] switching to channel 9 Apr 24 18:54:26 callin vdr: [30942] transfer thread ended (pid=7375, tid=30942) Apr 24 18:54:26 callin vdr: [7375] buffer stats: 194204 (9%) used Apr 24 18:54:26 callin vdr: [7375] info: Channel not available! Apr 24 18:54:26 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:42 callin vdr: [7375] switching to channel 21 Thanks___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
