[linux-dvb] Troubles with DVB-C

["Philippe" <gaultier.philippe@free.fr>]

Hi,

I'm using vdr for 2 years.
Everything was fine until I moved to a new flat (800m from my old apartment)
I plugged my vdr-box and I could get all feeds from all the transponders
except for 3 transponders.

By the way, here is my configuration :
 - my official decoder works fine with no glitches and let me view all
channels.

 - DVB-C Full featured (ves1820)
 - CPU via c3@1GHz
 - 256Mo RAM

dmesg
----8<----
Linux video capture interface: v1.00
saa7146: register extension 'dvb'.
saa7146_core: found saa7146 @ mem d091d000 (revision 1, irq 10)
(0x13c2,0x0002).
DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1).
DVB: VES1820(0): setup for tuner sp5659c
DVB: VES1820(0): pwm=0x40
DVB: registering frontend 0:0 (VES1820 based DVB-C frontend)...
Technotrend/Hauppauge PCI rev2.1 adapter 0 has MAC addr = 00:d0:5c:20:6d:95
gpioirq unknown type=0 len=0
DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261c
DVB: AV7111(0) - firmware supports CI link layer interface
av7110(0): Crystal audio DAC detected
saa7146_fops: saa7146 (0): registered device video0 [v4l2]
av7110: found av7110-0.
----8<----

 - vdr 1.3.14
 - kernel 2.4.26
 - debian sarge
 - dvb-driver cvs 03112004


I checked with dvb-drivers :
 - dvb-kernel 1.1.1
 - dvb-kernel cvs

The driver wasn't able to lock on the three transponders.

123.125 OK
131.125 cannot lock (needs tune delay 2500)
139.125 OK
147.125 OK
155.125 cannot lock (needs tune delay 800)
163.125 OK
195.125 OK
211.125 cannot lock (needs tune delay 500)
219.125 OK
227.125 OK
235.125 OK
243.125 OK
251.125 OK
259.125 OK
267.125 OK
275.125 OK
283.125 OK
291.125 OK
714.375 OK
754.375 OK
842.375 OK

So I used 
 dvb-core dvb_override_tune_delay=500
I get one of the tree missing transponders (211.125MHz)
dvb-core dvb_override_tune_delay=800
I get two of the tree missing transponders (211.125MHz + 155.125MHz)
dvb-core dvb_override_tune_delay=2500
I get three of the tree missing transponders (211.125MHz + 155.125MHz +
131.125MHz)

Since I changed the tune_delay to 2500, I can lock on every channel but I
have some UNCorrectable errors on those channels.
I do not understand why my official decoder is OK (no glitches, .)

If someone has an idea and could help me correct these troubles, I would be
grateful.

Cheers
Philippe


Here some femon logs for :

127.125MHz (No glitche)
status 1f | signal ffff | snr f0f0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f0f0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f1f1 | ber 00000014 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f0f0 | ber 00000014 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f1f1 | ber 00000046 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr efef | ber 00000046 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f0f0 | ber 00000046 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f1f1 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr f0f0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK

131.125MHz (Lot of glitches)
status 1f | signal ffff | snr dada | ber 000a0046 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dcdc | ber 000a0046 | unc 00000001 |
FE_HAS_LOCK
status 1f | signal ffff | snr d9d9 | ber 000a0046 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 000d9e54 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dada | ber 000d9e54 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 000a131a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 000a131a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 000a2184 | unc 00000006 |
FE_HAS_LOCK
status 1f | signal ffff | snr dada | ber 000a2184 | unc 00000000 |
FE_HAS_LOCK

155.125MHz (Some glitches)
status 1f | signal ffff | snr dede | ber 00051b94 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dddd | ber 000516e4 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dfdf | ber 000516e4 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 00054790 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dcdc | ber 00054790 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 00054790 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dcdc | ber 00055e1a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dada | ber 00055e1a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dcdc | ber 000569dc | unc 00000000 |
FE_HAS_LOCK

211.125MHz (Lot of glitches)
status 1f | signal ffff | snr d8d8 | ber 00138d1e | unc 00000001 |
FE_HAS_LOCK
status 1f | signal ffff | snr d9d9 | ber 00138d1e | unc 00000002 |
FE_HAS_LOCK
status 1f | signal ffff | snr d9d9 | ber 00137f36 | unc 00000002 |
FE_HAS_LOCK
status 1f | signal ffff | snr d8d8 | ber 00137f36 | unc 00000001 |
FE_HAS_LOCK
status 1f | signal ffff | snr d9d9 | ber 00135f60 | unc 00000001 |
FE_HAS_LOCK
status 1f | signal ffff | snr d7d7 | ber 00135f60 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr d7d7 | ber 00139692 | unc 00000003 |
FE_HAS_LOCK
status 1f | signal ffff | snr d6d6 | ber 00139692 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr dbdb | ber 00139692 | unc 00000000 |
FE_HAS_LOCK

714.375MHz (No glitche)
status 1f | signal ffff | snr eaea | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ebeb | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ebeb | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ebeb | ber 0000000a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ebeb | ber 0000000a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 0000000a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ebeb | ber 0000000a | unc 00000000 |
FE_HAS_LOCK