[vdr] AW: Re: DVB-c channel tuning/locking does not work 100% since VDR 1.1.19

["just4all" <just4all@gmx.de>]

Klaus and Jaakko thank you for your replies,

First of all here are the specifications of my DVB-c. I bought it from
Hauppauge over 2 Years ago.

Text on component side:
CAB-DVB Rev.: 2.1 
TTC99.10

Stickers on component side:
C-rev.2.1 1800_000405_001404010087

Stickers on RF part: 
TDBE2-031A 
TDBE2-031A 
032113A

Text on solder side: 
BTI ML-1 
94V-0 
1600
   
Sticker on solder side: 
No SN Sticker

ic 
Philips 
SAA 7146A H 
CA7222.00 
ktD0006V3
ic 	
VLSI VISTA 
0005  N655701
VES1820- 
DVB-C Receiver
COMATLAS 27294°
ic 
Texas Instruments DSP 
TMX320AV7111GFN 
CD-0005-3 
9337246 
1
ic 
CY7C024V- 
25AC 0007 
E 04 702645
ic 
HYUNDAI KOREA 
HY57V161610D 
9921A TC-8
ic 
Siemens
HYB3118165BST-60 
France K E20040
9066
ic 
Texas Instruments 
O3A41XT
320AD80C

After I applied the patch my log says the following regarding the dvb
driver:

kernel: DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1
or 2.2).
kernel: PCI: Enabling device 00:0a.0 (0004 -> 0006)
kernel: PCI: Found IRQ 3 for device 00:0a.0
kernel: ves1820.c: setup for tuner sp5659c
kernel: VES1820: pwm=40
kernel: DVB: registering frontend 0:0 (VES1820 based DVB-C frontend)...
kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app
00012502
kernel: VES1820: init chip
kernel: VES1820: init chip
kernel: 0:0: drift: +0.000000, bending: +0.000000
kernel: ves1820.c: tuning to 378.000000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover
kernel: 0:0: drift: +0.000000, bending: +0.000000
kernel: ves1820.c: tuning to 378.000000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover
kernel: 0:0: drift: +0.125000, bending: +0.000000
kernel: ves1820.c: tuning to 378.125000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover
kernel: 0:0: drift: -0.125000, bending: +0.000000
kernel: ves1820.c: tuning to 377.875000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover
kernel: 0:0: drift: +0.250000, bending: +0.000000
kernel: ves1820.c: tuning to 378.250000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover
kernel: 0:0: drift: -0.250000, bending: +0.000000
kernel: ves1820.c: tuning to 377.750000 MHz
kernel: 0:0: delay: 0.500000s
kernel: 0:0: call recover

Perhaps it possible to reinclude a retry if the channel is not locked
directly in vdr like it was in 1.1.18. In my opinion it shouldn't
decrease the zapping speed and it would solve my problem. If I am
totally wrong .. sorry but I am nor a coder neither a Linux crack.

Greets
David

-----Ursprüngliche Nachricht-----
Von: kls@cadsoft.de [mailto:kls@cadsoft.de] Im Auftrag von Klaus
Schmidinger
Gesendet: Sonntag, 29. Dezember 2002 10:46
An: vdr@linuxtv.org
Betreff: [vdr] Re: DVB-c channel tuning/locking does not work 100% since
VDR 1.1.19

just4all wrote:
> 
> Hi all,
> 
> as you all know since VDR 1.1.19 the Tuning is a single thread of
course
> the channel switching is a lot faster now ..but with my DVB-c is does
> not work right.
> Some channels stay dark mostly when the channel is on another
frequency.
> Then I have to wait for 5 min or longer until the tuning is done
> sometimes the tuning still did not work after an hour. When the TV
stays
> black in VDR 1.1.19 or 1.1.20 there appears no error message in log
> files. When I switch to a "problem channel" in VDR 1.1.18 or earlier
the
> following appears in the logs:            switching to channel 9
> 
> ERROR channel not locked on DVB Card ..retrying
> After the retry the picture appears. I heard that a driver change
around
> the 11-01-2002 caused that the channels are not locked right. I also
> found a diff file ( http://gyre.weather.fi/~jaakko/dvb/ ) for
> dvb_frontend.c and ves1820.c witch tunes +- 0.125mhz to lock the
channel
> right but it does not with my card. With this patch no channel tuning
> works anymore.
> Does anyone have the same Problem and found a workaround or something
> like that?
> Any hint is welcome!!!

There appears to be a problem with tuning on DVB-C cards. Please see the
other threads about this. I believe there is a patch for the driver that
cures this.

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr"
as subject.



--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.