Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Problems with SS2 and VDR (video data stream broken)



Hi,

 

first of all: Sorry, I am new to this list, and I hope that my issue still has not been discussed within the last weeks.

 

The problem: I am not able to get my SS2 working stable with VDR (as posted e.g. at http://www.vdrportal.de/board/thread.php?threadid=8401&sid=c2c3fb611956955700755ef15a50c8e1&hilight=skystar2&hilightuser=0). I already got some working recordings, but after having the PC run for several days (heat problem?), I get the message “video data stream broken” when I try to record from the SS2. Then, VDR is being restarted and the driver is being reloaded, but this does not help: VDR tries to continue the recording, but the driver still fails.

As there have been patches against some SS2 problems recently, I downloaded the CVS drivers from 06.12.2003 but they did not solve my problems (I previously had the drivers from beginning of november). Hasnīt the mentioned patch from 28.11.2003 by Wolfgang Thiel not been applied to the CVS (havenīt tried this one yet as I read about it first some minutes ago)? Is this patch mentioned worth trying?

 

Here is what I get when the driver is being loaded:

Dec  7 18:32:34 linux kernel: Technisat SkyStar2 driver loading Dec  7 18:32:34 linux kernel: skystar2.c: FlexCopII(rev.130) chip found Dec  7 18:32:34 linux kernel: skystar2.c: MAC address = 00:d0:d7:04:4d:c6:00:00 Dec  7 18:32:34 linux kernel: skystar2.c: key = Dec  7 18:32:34 linux kernel:  b2 00 00 00 Dec  7 18:32:34 linux kernel:  00 00 00 00 Dec  7 18:32:34 linux last message repeated 2 times Dec  7 18:32:34 linux kernel: DVB: registering new adapter (PCI device 13d0:2103 (Techsan Electronics Co Ltd)).

Dec  7 18:32:34 linux kernel: mt312.c: setup for VP310 Dec  7 18:32:34 linux kernel: DVB: registering frontend 1:0 (Zarlink MT312)...

 

This is what I see after I upgraded from drivers from November to the "Nikolausi" drivers :-):

Dec  7 18:55:24 linux vdr[5493]: ERROR: frontend 1: Invalid argument Dec  7 18:55:47 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_13, 0 Dec  7 18:55:47 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_OFF, 1 Dec  7 18:55:47 linux vdr[5493]: ERROR: frontend 1: Invalid argument Dec  7 18:56:10 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_13, 0 Dec  7 18:56:10 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_ON, 0 Dec  7 18:56:33 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_13, 0 Dec  7 18:56:33 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_ON, 0 Dec  7 18:56:56 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_18, 1 Dec  7 18:56:56 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_ON, 0 Dec  7 18:56:56 linux vdr[5493]: ERROR: frontend 1: Invalid argument Dec  7 18:57:19 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_13, 0 Dec  7 18:57:19 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_ON, 0 Dec  7 18:57:42 linux kernel: flexcop_diseqc_ioctl: SEC_VOLTAGE_13, 0 Dec  7 18:57:42 linux kernel: flexcop_diseqc_ioctl: SEC_TONE_OFF, 1 Dec  7 18:57:42 linux vdr[5493]: ERROR: frontend 1: Invalid argument ...

 

And this is what I get when the recording fails:

Dec  7 18:32:21 linux vdr[4827]: ERROR: video data stream broken Dec  7 18:32:21 linux vdr[4827]: initiating emergency exit Dec  7 18:32:21 linux vdr[4060]: emergency exit requested - shutting down Dec  7 18:32:22 linux vdr[4060]: emergency exit!

 

My configuration: VDR 1.2.6pre4, Nexus Rev 2.1, SS2 (rev 1.3?), SuSE 8.2 with SuSE kernel, Elitegroup K7S5A mainboard.

 

If this isnīt a know bug in the drivers please tell me which log I can send you to debug the drivers (I am not a programmer :-( )

 

 

With kind regards - and thanks in advance for any help

 

Jörg Knitter

 

 


Home | Main Index | Thread Index