On Mon, 2004-05-03 at 20:35, Andrew de Quincey wrote: > [...] > > > That happens only when my smart card (italian sky) is inside the cam, > > otherwise I only get: > > > > ./cam_set > > Found 1CAM(s) > > Using /dev/dvb/adapter0/ca0 > > Found 1 slots > > CAM: ASTON, 01, 0100, 0100 > > > > > > And then an infinite loop: > > > > > > [...] > > May 3 18:47:01 victor kernel: FR/DA IRQ slot:0 > > May 3 18:47:01 victor kernel: dvb_ca_en50221_thread_wakeup > > May 3 18:47:01 victor kernel: dvb_ca_en50221_read_data > > May 3 18:47:01 victor kernel: dvb_ca_en50221_read_data > > May 3 18:47:01 victor kernel: dvb_ca_en50221_io_poll > > May 3 18:47:01 victor kernel: dvb_ca_en50221_io_read > > May 3 18:47:01 victor kernel: dvb_ca_en50221_io_write > > May 3 18:47:01 victor kernel: dvb_ca_en50221_write_data > > May 3 18:47:01 victor kernel: dvb_ca_en50221_io_poll > [...] > > Thats ok - that looks like the CI library polling the CAM module for data, > which is the correct operation. > >
OK, i figured out a bit how the module works looking at the sources; and, OOPS, the error below was my fault (i'm a newbie in dvb-s): the smart card was inserted into cam in wrong side (but i can't understand why the cam complains for an error where the smartcard is misplaced and not when it is not inserted at all...). > [...] > > --> 00 01 81 01 01 > > <-- 00 01 A0 82 00 49 01 90 02 00 05 9F 88 0C 40 01 9F 88 03 10 41 73 74 > > 6F 6E 43 72 79 70 74 20 56 31 2E 30 35 9F 88 03 00 9F 88 03 00 9F 88 03 > > 1F 41 6E 20 65 72 72 6F 72 20 6F 63 63 75 72 65 20 77 69 74 68 20 79 6F > > 75 72 20 63 61 72 64 2E 80 02 01 00 > > . . . . . I . . . . . . . . @ . . . . . A s t > > o n C r y p t V 1 . 0 5 . . . . . . . . . . . > > . A n e r r o r o c c u r e w i t h y o > > u r c a r d . . . . . > > 5: <== Menu Last > > 5: <== Text Last 'AstonCrypt V1.05' > > 5: <== Text Last '' > > 5: <== Text Last '' > > 5: <== Text Last 'An error occure with your card.' > > That seems to be an error from the CAM itself - the CI interface appears to be > functioning correctly. It _could_ be a problem with the defragmenter in the > driver however, but I would have thought something like that to have shown up > before now. > > I know some people have got it to work with an Aston CAM. > Now cam_set & cam_test seem to work fine, i can also explore cam menu with cam_menu; however, channels aren't descrambled yet. That's cam_set output: Found 1CAM(s) Using /dev/dvb/adapter0/ca0 Found 1 slots CAM: ASTON, 01, 0100, 0100 New connection established. CI HANDLER: connection established CI HANDLER: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 | 0x9 0xf 0x5 0x0 0xe1 0xcc 0x10 0x1 0x0 0x13 0x1 0x20 0x14 0x3 0x0 0x7c 0x8 ok SysID 500 Slot 0 checking 100 CI HANDLER: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 | 0x9 0xf 0x5 0x0 0xe1 0xd1 0x10 0x1 0x0 0x13 0x1 0x20 0x14 0x3 0x1 0x50 0x8 ok SysID 500 Slot 0 checking 100 CI HANDLER: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 | 0x9 0xf 0x5 0x0 0xe1 0xd4 0x10 0x1 0x0 0x13 0x1 0x20 0x14 0x3 0x2 0x0 0x8 ok SysID 500 Slot 0 checking 100 state: CAM CI HANDLER: client hung up and that's cam_test output: ./cam_test -q 10834000 -l V -r 27500000 -t 430 -i 1104 -d Warning: TP already defined: ID: 1 SATID: 1 Channel: Eurosport apid: 0x1ae vpid: 0x1a4 ttpid: 0xffff CAM Test: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 CAM Test: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 CAM Test: 0x450 0x1a4 0x1ae 0x0 0xffff 0x11 note: the output of cam_test is the SAME, being the smartcard in the cam or not. Using cam_menu, i verified that the cam knows my smartcard is enabled to see that channel... Sorry for my english, and thanks for any help! Guido -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
