[linux-dvb] Long delays until i get a lock on Hauppauge's Card

Kenneth Aafløy kenneth at linuxtv.org
Fri Jul 22 23:35:12 CEST 2005


fredag 22. juli 2005, 23:27, skrev HGM.bg (GMX):
> Hi,
> 
> I'm using kernel 2.6.13-rc3 and cvs checkout from today. I have a Athlon
> 2200+ system with 512 MB RAM and i have 1 Hauppauge Nexus-s 2.1 and 2
> Hauppauge Nova-s. Before starting VDR i use szap to tune all cards to a
> certain channel to avoid data stream broken in VDR.

Uh, that's ugly!

> Here is a log:
> Inserting DVB modules into kernel
> 
> reading channels from file
> '/vdr/DVB/dvb-apps/util/szap/channels-conf/dvb-s/Astra-19.2E'
> reading channels from file
> '/vdr/DVB/dvb-apps/util/szap/channels-conf/dvb-s/Astra-19.2E'
> reading channels from file
> '/vdr/DVB/dvb-apps/util/szap/channels-conf/dvb-s/Astra-19.2E'
> zapping to 25 'SAT.1':
> sat 0, frequency = 12480 MHz V, symbolrate 27500000, vpid = 0x06ff, apid
> = 0x0700 sid = 0x002e
> using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
> zapping to 25 'SAT.1':
> sat 0, frequency = 12480 MHz V, symbolrate 27500000, vpid = 0x06ff, apid
> = 0x0700 sid = 0x002e
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> zapping to 25 'SAT.1':
> sat 0, frequency = 12480 MHz V, symbolrate 27500000, vpid = 0x06ff, apid
> = 0x0700 sid = 0x002e
> using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0'
> status 03 | signal 5895 | snr 701a | ber 00007600 | unc 00000000 |
> status 1f | signal b2c0 | snr e283 | ber 00000200 | unc 00000000 | FE_HAS_LOCK
> status 03 | signal 9101 | snr be1d | ber 0000ff30 | unc 00000000 |
> status 03 | signal 8c0a | snr ba4b | ber 0000fff0 | unc 00000000 |
> status 1f | signal b3fe | snr e27d | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 07 | signal 9239 | snr ba9f | ber 0000ff08 | unc 00000000 |
> status 03 | signal 8c1f | snr bb26 | ber 0000ff50 | unc 00000000 |
> status 1f | signal b2c0 | snr e27a | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 03 | signal 58d0 | snr 7f62 | ber 0000ff60 | unc 00000000 |
> status 01 | signal 5910 | snr 80eb | ber 0000ffe0 | unc 00000000 |
> status 1f | signal b402 | snr e286 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal a63e | snr e562 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> ./runvdr.now.new.drivers: line 87:  4792 Beendet
> $ZAPDIR/szap -c $ZAPDIR/channels-conf/dvb-s/Astra-19.2E -a 2 -n 25
> ./runvdr.now.new.drivers: line 87:  4793 Beendet
> $ZAPDIR/szap -c $ZAPDIR/channels-conf/dvb-s/Astra-19.2E -a 1 -n 25
> ./runvdr.now.new.drivers: line 87:  4794 Beendet
> $ZAPDIR/szap -c $ZAPDIR/channels-conf/dvb-s/Astra-19.2E -a 0 -n 25
> 
> As you see it takes really long to get a lock on all cards. Why ? Is
> there any way to improve this ?
> Thanks

I'm confused, on which card does it take long to get a lock?

Kenneth




More information about the linux-dvb mailing list