[linux-dvb] KNC1 DVB-C Plus CI/CAM not working

Rutger ter Borg rutger at terborg.net
Fri Nov 9 09:01:04 CET 2007


> > The system keeps looping over inserted/ejected messages if the CAM is
> > inserted:
> >
> > Nov  3 16:06:04 fraggle kernel: ACPI: PCI interrupt for device
> > 0000:00:08.0 disabled
> > Nov  3 16:13:56 fraggle kernel: Linux video capture interface: v2.00
> > Nov  3 16:13:56 fraggle kernel: saa7146: register extension 'budget_av'.
> > Nov  3 16:13:56 fraggle kernel: ACPI: PCI Interrupt 0000:00:08.0[A] ->
> > GSI 19 (level, low) -> IRQ 19
> > Nov  3 16:13:56 fraggle kernel: saa7146: found saa7146 @ mem
> > ffffc200001fce00 (revision 1, irq 19) (0x1894,0x0023).
> > Nov  3 16:13:56 fraggle kernel: saa7146 (0): dma buffer size 192512
> > Nov  3 16:13:56 fraggle kernel: DVB: registering new adapter (KNC1 DVB-C
> > Plus MK3)
> > Nov  3 16:13:56 fraggle kernel: adapter failed MAC signature check
> > Nov  3 16:13:56 fraggle kernel: encoded MAC from EEPROM was
> > ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
> > Nov  3 16:13:56 fraggle kernel: saa7146_vv: saa7146 (0): registered
> > device video0 [v4l2]
> > Nov  3 16:13:56 fraggle kernel: KNC1-0: MAC addr = 00:09:d6:6d:88:7b
> > Nov  3 16:13:56 fraggle kernel: DVB: registering frontend 0 (Philips
> > TDA10023 DVB-C)...
> > Nov  3 16:13:56 fraggle kernel: budget-av: ci interface initialised.
> > Nov  3 16:13:56 fraggle kernel: budget-av: cam inserted A
> > Nov  3 16:13:56 fraggle kernel: budget-av: cam ejected 5
> > Nov  3 16:14:00 fraggle kernel: budget-av: cam inserted A
> > Nov  3 16:14:00 fraggle kernel: budget-av: cam ejected 5
> > ...
> > Nov  3 16:14:04 fraggle kernel: budget-av: cam inserted A
> > Nov  3 16:14:05 fraggle kernel: budget-av: cam ejected 5
> >
> > , and this inserted/ejected loop keeps repeating. The messages stop when
> > the CAM is removed from the CI module. The system runs in 64 bit mode on
> > an AMD64.
> >
> > Given this,
> > * Is it more likely to be a driver problem, or a hardware problem? If it
> > is a driver problem, in which source file should I start looking?
> > * What cross-checks could I do next to determine the exact problem?
> >
>
> I've seen that before. I can't garuantee my solution also works for you,
> but: check your CI cable (flatcable between your TV-station card and
> cineview).

Thanks for the reply. I have checked the cable, and to be sure the cable 
wasn't faulty, I contacted KNC1. They sent me a new cable for testing 
purposes that arrived within two days. Excellent service!

Unfortunately it didn't change the situation: the results are identical to 
what I reported earlier. 

So, zapping to channels works,

fraggle:~# czap 'Nederland 2'
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
123 Nederland 2:388000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64:181:182:8005
123 Nederland 2: f 388000000, s 6875000, i 2, fec 0, qam 3, v 0xb5, a 0xb6
status 00 | signal aeae | snr b6b6 | ber 000fffff | unc 00000047 |
status 1f | signal d2d2 | snr f3f3 | ber 00000798 | unc 00000004 | FE_HAS_LOCK
status 1f | signal d2d2 | snr f3f3 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal d2d2 | snr f3f3 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal d2d2 | snr f3f3 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

but recording / trying to get data from the device

fraggle:~# cat /dev/dvb/adapter0/dvr0 > test.mpeg

results in empty files, and the ejected/inserted loop keeps running as shown 
in my first message. I've managed to flash the Alphacrypt CAM in a PCMCIA 
slot on a laptop, so I guess this is not the showstopper. The program card 
works in an other device, so this isn't it as well. I rechecked that the 
TV-station card has its own IRQ, which is the case.

Could it be the CI module? What do you think?

Thanks,

Rutger




More information about the linux-dvb mailing list