Hi all,
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
But no initialization of my Conax CAM. It works perfectly with my normal FF setup. Is there a way to debug? If I remember Klaus had some debug lines some time ago, but now i can't find it. Vdr version is 1.3.29.
/t
Tomas Prybil wrote:
Hi all,
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
But no initialization of my Conax CAM. It works perfectly with my normal FF setup. Is there a way to debug? If I remember Klaus had some debug lines some time ago, but now i can't find it. Vdr version is 1.3.29.
I found 1.1.23 and Klaus notes about removing the comment to get debug output for the descriptors in eit.c. However I couldn't find that line. (and perhaps the interfaces now are obsolete?)
/t
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Cheers
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Nothing additional from syslog i'm afraid.
/t
Tomas Prybil wrote:
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Nothing additional from syslog i'm afraid.
I found Klaus debug lines in pat.c #define DEBUG_CA_DESCRIPTORS 1 and enabled it. /var/log/messages is dead silent regarding CAM: messages :(
Any other ideas?
/t
Tomas Prybil wrote:
Tomas Prybil wrote:
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Nothing additional from syslog i'm afraid.
I found Klaus debug lines in pat.c #define DEBUG_CA_DESCRIPTORS 1 and enabled it. /var/log/messages is dead silent regarding CAM: messages :(
Any other ideas?
Now I got something:
Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 998 0B00 0 - 09 04 0B 00 E0 42 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 904 0B00 0 - 09 04 0B 00 E0 41 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 995 0B00 0 - 09 04 0B 00 E0 44 Aug 27 13:23:59 localhost vdr[4281]: CAM: 800A 211247 143 0B00 0 - 09 04 0B 00 E0 43 Aug 27 13:24:00 localhost vdr[4281]: CAM: 800A 211247 4 0B00 0 - 09 04 0B 00 E0 34
Does it make any sense?
/t
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Your earlier post with patched ci.c gave me another clue:
Aug 27 20:38:40 localhost vdr[5853]: probing /dev/dvb/adapter0/frontend0 Aug 27 20:38:40 localhost vdr[5853]: ERROR (dvbdevice.c,107): Operation not permitted
Is the 107 referring to line 107 of dvbdevice.c? CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, SEC_VOLTAGE_13)); // must explicitly turn on LNB power
/t
Tomas Prybil wrote:
Tomas Prybil wrote:
Tomas Prybil wrote:
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
Aug 21 20:46:51 localhost kernel: saa7146: register extension 'budget_ci dvb'. Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem e09cb000 (revision 1, irq 209) (0x13c2,0x100c). Aug 21 20:46:51 localhost kernel: DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Nothing additional from syslog i'm afraid.
I found Klaus debug lines in pat.c #define DEBUG_CA_DESCRIPTORS 1 and enabled it. /var/log/messages is dead silent regarding CAM: messages :(
Any other ideas?
Now I got something:
Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 998 0B00 0 - 09 04 0B 00 E0 42 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 904 0B00 0 - 09 04 0B 00 E0 41 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 995 0B00 0 - 09 04 0B 00 E0 44 Aug 27 13:23:59 localhost vdr[4281]: CAM: 800A 211247 143 0B00 0 - 09 04 0B 00 E0 43 Aug 27 13:24:00 localhost vdr[4281]: CAM: 800A 211247 4 0B00 0 - 09 04 0B 00 E0 34
Does it make any sense?
Well, it means that VDR has found CA descriptors for some channels.
When you start VDR, do you get a message like
Aug 27 20:04:41 video vdr[10530]: CAM: AlphaCrypt, 01, 4A20, 4A20
or so in the log file? If not, VDR doesn't find the CAM. You could change the lines
static bool DumpTPDUDataTransfer = false; static bool DebugProtocol = false;
from 'false' to 'true' in VDR/ci.c to see whether there is any communication with the CI/CAM going on.
Klaus
Klaus Schmidinger wrote:
Tomas Prybil wrote:
Tomas Prybil wrote:
Tomas Prybil wrote:
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
I'm trying to get a budget card with CAM working. The card is reporting in /var/log/messages as having CI (or so I think)
> Aug 21 20:46:51 localhost kernel: saa7146: register extension > 'budget_ci dvb'. > Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt > 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 > Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem > e09cb000 (revision 1, irq 209) (0x13c2,0x100c). > Aug 21 20:46:51 localhost kernel: DVB: registering new adapter > (TT-Budget/WinTV-NOVA-CI PCI). > Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI > adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core module ?
Nothing additional from syslog i'm afraid.
I found Klaus debug lines in pat.c #define DEBUG_CA_DESCRIPTORS 1 and enabled it. /var/log/messages is dead silent regarding CAM: messages :(
Any other ideas?
Now I got something:
Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 998 0B00 0 - 09 04 0B 00 E0 42 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 904 0B00 0 - 09 04 0B 00 E0 41 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 995 0B00 0 - 09 04 0B 00 E0 44 Aug 27 13:23:59 localhost vdr[4281]: CAM: 800A 211247 143 0B00 0 - 09 04 0B 00 E0 43 Aug 27 13:24:00 localhost vdr[4281]: CAM: 800A 211247 4 0B00 0 - 09 04 0B 00 E0 34
Does it make any sense?
Well, it means that VDR has found CA descriptors for some channels.
When you start VDR, do you get a message like
Aug 27 20:04:41 video vdr[10530]: CAM: AlphaCrypt, 01, 4A20, 4A20
or so in the log file? If not, VDR doesn't find the CAM. You could change the lines
static bool DumpTPDUDataTransfer = false; static bool DebugProtocol = false;
from 'false' to 'true' in VDR/ci.c to see whether there is any communication with the CI/CAM going on.
I allready did that, but it's dead silent. The same CAM works perfectly ok with the FF card.
Dominique Dumont said something about a debug parameter for dvb_core. However the syslog reports that
Aug 27 12:58:33 localhost kernel: budget_core: Unknown parameter
`cam_debug'
I didn't succeed to find the proper parameter syntax from the kernel source.
/t
Tomas Prybil skrev:
Klaus Schmidinger wrote:
Tomas Prybil wrote:
Tomas Prybil wrote:
Tomas Prybil wrote:
Dominique Dumont wrote:
Tomas Prybil vdrmail@prybil.se writes:
> I'm trying to get a budget card with CAM working. The card is > reporting in /var/log/messages as having CI (or so I think) > > >> Aug 21 20:46:51 localhost kernel: saa7146: register extension >> 'budget_ci dvb'. >> Aug 21 20:46:51 localhost kernel: ACPI: PCI interrupt >> 0000:0b:05.0[A] -> GSI 22 (level, low) -> IRQ 209 >> Aug 21 20:46:51 localhost kernel: saa7146: found saa7146 @ mem >> e09cb000 (revision 1, irq 209) (0x13c2,0x100c). >> Aug 21 20:46:51 localhost kernel: DVB: registering new adapter >> (TT-Budget/WinTV-NOVA-CI PCI). >> Aug 21 20:46:51 localhost kernel: TT-Budget/WinTV-NOVA-CI PCI >> adapter 0 has MAC addr = 00:d0:5c:02:df:d0
Could you try with cam_debug parameter set to 1 for dvb-core
module ?
Nothing additional from syslog i'm afraid.
I found Klaus debug lines in pat.c #define DEBUG_CA_DESCRIPTORS 1 and enabled it. /var/log/messages is dead silent regarding CAM:
messages :(
Any other ideas?
Now I got something:
Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 998 0B00 0 - 09 04 0B 00 E0 42 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 904 0B00 0 - 09 04 0B 00 E0 41 Aug 27 13:23:58 localhost vdr[4281]: CAM: 800A 211247 995 0B00 0 - 09 04 0B 00 E0 44 Aug 27 13:23:59 localhost vdr[4281]: CAM: 800A 211247 143 0B00 0 - 09 04 0B 00 E0 43 Aug 27 13:24:00 localhost vdr[4281]: CAM: 800A 211247 4 0B00 0 - 09 04 0B 00 E0 34
Does it make any sense?
Well, it means that VDR has found CA descriptors for some channels.
When you start VDR, do you get a message like
Aug 27 20:04:41 video vdr[10530]: CAM: AlphaCrypt, 01, 4A20, 4A20
or so in the log file? If not, VDR doesn't find the CAM. You could change the lines
static bool DumpTPDUDataTransfer = false; static bool DebugProtocol = false;
from 'false' to 'true' in VDR/ci.c to see whether there is any communication with the CI/CAM going on.
I allready did that, but it's dead silent. The same CAM works perfectly ok with the FF card.
Dominique Dumont said something about a debug parameter for dvb_core. However the syslog reports that
Aug 27 12:58:33 localhost kernel: budget_core: Unknown parameter
`cam_debug'
I didn't succeed to find the proper parameter syntax from the kernel source.
Too old kernel, didn't work with 2.6.8 but did with 2.6.12.
/t
-
Dominique Dumont -
Klaus Schmidinger -
Tomas Prybil