Hi developers, I have an issue with my old version SkyStar2 not locking on any transponder. The sat line got checked out fine using an external receiver box. So I enabled debugging of the b2c2_flexcop modules (using a recent hg checkout) and got the following messages: Aug 8 13:40:34 localhost kernel: i2c success Aug 8 13:40:34 localhost kernel: mt312: R(126): 01 Aug 8 13:40:34 localhost kernel: b2c2-flexcop: found the vp310 (aka mt312) at i2c address: 0x0e Aug 8 13:40:34 localhost kernel: DVB: registering frontend 0 (Zarlink VP310 DVB-S)... Aug 8 13:40:34 localhost kernel: b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S (old version)' at the 'PCI' bus controlled by a 'FlexCopII' complete So apprently everything is fine till now, right?! But next I get the follwing messages repeating over and over again: Aug 8 13:40:34 localhost kernel: Contunuity error flag is set Aug 8 13:40:34 localhost kernel: 0 valid irq took place so far Aug 8 13:40:34 localhost kernel: isr for flexcop called, apparently without reason (00000100) This looks wrong, right?? Using the scan utility from the dvb-apps I don't get any successful lock on any transponder I tried on Astra 19.2E. The SkyStar2 card is sharing an IRQ with the eth0 device in my system. Might this be an issue? Unfortunatelly I can not switch PCI slots since only 2 slots are available and the other one is already occupied by a FF-DVB card which only fits into this slot. What's wrong? Anything else I could try? TIA & regards, Thomas _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
