[linux-dvb] KNC1 DVB-C cam module not working on driver load
Hello, I have a small problem with the cam feature of the KNC1 DVB-C card. When I have the cam module inserted and then load the budget-av module (for example during system boot). The cam module doesn't initialize correctly. This is what my dmesg shows when I do "modprobe budget-av" saa7146: register extension 'budget_av'. ACPI: PCI Interrupt :04:07.0[A] -> Link [LNKB] -> GSI 17 (level, low) -> IRQ 90 saa7146: found saa7146 @ mem c219ec00 (revision 1, irq 90) (0x1894,0x0020). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (KNC1 DVB-C). adapter failed MAC signature check 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 KNC1-0: MAC addr = 00:09:d6:6d:5a:f0 DVB: registering frontend 0 (Philips TDA10021 DVB-C)... budget-av: ci interface initialised. budget-av: cam inserted A and after some time: dvb_ca adaptor 0: PC card did not respond :( If I then manually remove the alphacrypt cam from the CI interface and reinsert I get the following messages in my dmesg log: budget-av: cam ejected 5 budget-av: cam inserted B dvb_ca adapter 0: DVB CAM detected and initialised successfully After which I can succesfully use the card and watch encrypted channels. What can I do to make sure this will also work immedialy when the system boots? - Jeroen smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C cam module not working on driver load
Hi, Is it OK to re-post the question/problem below? As google doesn't really help me. Op 8-jan-2007, om 20:46 heeft Jeroen Asselman het volgende geschreven: Hello, I have a small problem with the cam feature of the KNC1 DVB-C card. When I have the cam module inserted and then load the budget-av module (for example during system boot). The cam module doesn't initialize correctly. This is what my dmesg shows when I do "modprobe budget-av" saa7146: register extension 'budget_av'. ACPI: PCI Interrupt :04:07.0[A] -> Link [LNKB] -> GSI 17 (level, low) -> IRQ 90 saa7146: found saa7146 @ mem c219ec00 (revision 1, irq 90) (0x1894,0x0020). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (KNC1 DVB-C). adapter failed MAC signature check 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 KNC1-0: MAC addr = 00:09:d6:6d:5a:f0 DVB: registering frontend 0 (Philips TDA10021 DVB-C)... budget-av: ci interface initialised. budget-av: cam inserted A and after some time: dvb_ca adaptor 0: PC card did not respond :( If I then manually remove the alphacrypt cam from the CI interface and reinsert I get the following messages in my dmesg log: budget-av: cam ejected 5 budget-av: cam inserted B dvb_ca adapter 0: DVB CAM detected and initialised successfully After which I can succesfully use the card and watch encrypted channels. What can I do to make sure this will also work immedialy when the system boots? - Jeroen smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C cam module not working on driver load
Op zaterdag 03-02-2007 om 16:31 uur [tijdzone +0100], schreef [EMAIL PROTECTED]: > Same problem here with different board (Nova-S CI) and different CAM module. > Is it a kernel bug? I don't know, perhaps an extra initialization is needed when a CAM module is allready present? However, I have seen once that the card did actually report a succesfull init when the driver loaded without removing the CAM module, I am unable to reproduce that behaviour though. - Jeroen ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] How do you know CAM is recognized ?
Op zondag 11-02-2007 om 10:14 uur [tijdzone +0100], schreef Kristof
Pelckmans:
> Yesterday I went to a shop and was able to see that my Alphacrypt is
> working well. I think my Technotrend card is not seeing the CAM. Do I
> have to add extra load parameters to the module or load extra modules ?
>
> ---
> lsmod
> Module Size Used by
> af_packet 13064 2
> snd_pcm_oss36640 0
> snd_mixer_oss 14464 1 snd_pcm_oss
> rtc10548 0
> parport_pc 23588 1
> lp 9604 0
> parport33736 2 parport_pc,lp
> stv0297 6784 1
> ide_cd 34720 0
> cdrom 34720 1 ide_cd
> tuner 60200 0
> snd_hda_intel 15896 5
> snd_hda_codec 158720 1 snd_hda_intel
> dvb_ttpci 96868 16
> snd_pcm61700 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec
> saa7134 114528 0
> snd_timer 18692 2 snd_pcm
> snd43748 14
> snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
> compat_ioctl32 1280 1 saa7134
> soundcore 6624 1 snd
> dvb_core 70568 1 dvb_ttpci
> ir_kbd_i2c 6928 1 saa7134
> i2c_viapro 7956 0
> saa7146_vv 44288 1 dvb_ttpci
> snd_page_alloc 7944 2 snd_hda_intel,snd_pcm
> video_buf 20228 2 saa7134,saa7146_vv
> saa714615112 2 dvb_ttpci,saa7146_vv
> ttpci_eeprom2304 1 dvb_ttpci
> ir_common 29828 2 saa7134,ir_kbd_i2c
> via_agp 8320 1
> videodev 26112 2 saa7134,saa7146_vv
> v4l2_common22144 4 tuner,saa7134,saa7146_vv,videodev
> i2c_core 17792 7
> stv0297,tuner,dvb_ttpci,saa7134,ir_kbd_i2c,i2c_viapro,ttpci_eeprom
> agpgart26444 1 via_agp
> v4l1_compat14724 3 saa7134,saa7146_vv,videodev
> evdev 8320 1
>
> 00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
> Subsystem: Technotrend Systemtechnik GmbH Octal/Technotrend
> DVB-C for iTV
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> SERR- Latency: 32 (3750ns min, 9500ns max)
> Interrupt: pin A routed to IRQ 22
> Region 0: Memory at febff400 (32-bit, non-prefetchable) [size=512]
>
> VDR does not mention my CAM :
I don't see a module budget-av loaded?
If you do a modprobe budget-av and check your "dmesg" log and perhaps
you see a:
"dvb_ca adaptor 0: PC card did not respond :("
If you see that message try to eject and reinsert the cam module after a
few seconds, perhaps you see a
"dvb_ca adapter 0: DVB CAM detected and initialised successfully"
afterwards in your dmesg.
- Jeroen
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] How do you know CAM is recognized ?
Op 12-feb-2007, om 22:55 heeft Kristof Pelckmans het volgende geschreven: Is this budget-av module also required for a Technotrend Premium card ? I tried inserting the module, but it doesn't seem to do much... Ah, I perhaps assumed to much. It might not be a 'budget' card. I tried figuring out mine by loading budget-av which made it work (at least dmesg started to show stuf), perhaps budget-ci or budget works for you if it is a budget card. - Jeroen smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C cam module not working on driver load
Hello, I tried to track the problem, and it is almost as if the CAM module isn't actually reset when the driver is unloaded/loaded. The CAM succesfully initializes if the CAM wasn't initialized . If the CAM was allready initialized once without being ejected the CAM will not initialize succesfully again when the driver loads. budget-av: ci interface initialised. budget-av: cam inserted A dvb_ca adaptor 0: PC card did not respond :( When trying to fix it myself it looked to me as if the CAM module was actually still running however,when sending an RS (Reset) to the Command register it didn't look like the CAM did respond correctly. If there was a bit set in the status register it got cleared, but the FR bit never got set. Does anyone know what could be happening here? - Jeroen smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C+, CineView v. 3.0 and Conax CAM: PC card did not respond
Hi. How can one get debugging information from the CI-module, CAM and the PC-card to see why the initialization fails? I added the following lines to my modprobe.conf for more debugging info: options dvb-core cam_debug=1,1 debug=1,1 options budget-core debug=1,1 - Jeroen smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C+, CineView v. 3.0 and Conax CAM: PC card did not respond
Op donderdag 22-02-2007 om 23:28 uur [tijdzone +0200], schreef [EMAIL PROTECTED]: > Inserting the Conax CAM with the Conax card gives these messages: > budget-av: cam inserted B > budget_av: ciintf_slot_reset(): ciintf_slot_reset > dvb_ca adaptor 0: PC card did not respond :( > > Removing it gives these messages: > budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown > budget-av: cam ejected 5 > dvb_ca_en50221_slot_shutdown > budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown > Slot 0 shutdown > > rmmod budget_av gives this message: > ACPI: PCI interrupt for device :04:08.0 disabled > > What can be learned from this? My guess (I am no DVB programmer) the software detects a card inserted and then it waits on the attribute adres for a value of 0x1D however it looks like this is never returned by the CAM. I don't know what 0x1D actually means though. I have the same problem when I load the budget-av driver while the CAM module is still inserted I only get it working by ejecting and reinserting the CAM module. Which also seems to fail for you. In my case it looked like the CAM module keeps in some kind of initialized state and doesn't output the value 0x1D. I don't know what the solution is though :( - Jeroen ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
