> > > [EMAIL PROTECTED] .tzap]# /usr/src/dvb-apps/util/szap/tzap "BBC ONE" > > > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > > > status 01 | signal 0029 | snr c000 | ber 00003fff | unc 00000100 | > > > status 1f | signal 002a | snr ff3a | ber 000000c5 | unc 00000024 | > > > FE_HAS_LOCK > > > status 1f | signal 002a | snr ffff | ber 00000000 | unc 000000c6 | > > > FE_HAS_LOCK > > > status 1f | signal 002a | snr ff91 | ber 0000006e | unc 000000c3 | > > > FE_HAS_LOCK > > > status 1f | signal 002a | snr ffff | ber 00000000 | unc 000000b3 | > > > FE_HAS_LOCK > > > status 1f | signal 002a | snr ffe2 | ber 0000001d | unc 000000a5 | > > > FE_HAS_LOCK > > > status 1f | signal 002a | snr ffff | ber 00000000 | unc 00000098 | > > > FE_HAS_LOCK > > > > Check the uncorrected errors. Whenever it is non-zero, you have > > corruption in your data stream. This can't be caused by the 0.17 > > upgrade. > > > > Strange that your BER is so low and yet uncorrected errors so high. What > > frontend is on your cards? mt352? > > > > Thanks Hamish for so many good new information about the DVB stuff ;) > Could you just explain more about it? Which values are important in > the output of (tsc)zap? I've been always looking at the FE_HAS_LOCK > string only. Then I've ctrl-C tzap if the first line didn't have a > lock but the following ones. Is this ok?
Here's my dmesg output related to dvb cx2388x dvb driver version 0.0.4 loaded cx2388x: snapshot date 2005-01-13 ACPI: PCI interrupt 0000:01:08.2[A] -> GSI 11 (level, low) -> IRQ 11 cx88[0]/2: found at 0000:01:08.2, rev: 5, irq: 11, latency: 64, mmio: 0xe1000000 cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (Hauppauge Nova-T DVB-T)... ACPI: PCI interrupt 0000:01:09.2[A] -> GSI 7 (level, low) -> IRQ 7 cx88[1]/2: found at 0000:01:09.2, rev: 5, irq: 7, latency: 64, mmio: 0xe4000000 cx88[1]/2: cx2388x based dvb card DVB: registering new adapter (cx88[1]). DVB: registering frontend 1 (Hauppauge Nova-T DVB-T)... Though I'm now about to give myself a good slap as the wife seems to have identified the problem that its one of the cards that might be playing up. I've deleted it from myth config and she's happily watching the soaps as we speak. Testing with xine identified it straight away. However, I'd be interested in anyone who's identied any potential problems with the chipsets involved.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
