|
... I ended up debugging the thing.
I found it not to be a 64 bit issue this time
;)
Looks like an issue with my CAM (an IceCrypt
Black). I don't know what to think of it since it reacts ok when working with TT
drivers/firmware for windows.
If you look at my sequece bellow, you will notice
that I get a request to form a CA Session by the time I should have recieved the
answer to the profile enquire.
Naturally, VDR's state machine is not ready to
handle such a bizzare behaviour (and neither am I). So, from there on, nothing
makes sense.
Any sugestions (please!)...
Module ready in slot 0
Creating connection: slot 0, tcid 1 --> 00 01 82 01 01 <-- 00 01 83 01 01 80 02 01 80 . . . . . . . . . --> 00 01 81 01 01 <-- 00 01 A0 07 01 91 04 00 01 00 41 80 02 01 80 . . . . . . . . . A . . . . OpenSession 00010041 New Resource Manager (session id 1) --> 00 01 A0 0A 01 92 07 00 00 01 00 41 00 00 <-- 00 01 80 02 01 80 . . . . . . 1: ==> Profile Enq --> 00 01 A0 09 01 90 02 00 01 9F 80 10 00 <-- 00 01 80 02 01 80 . . . . . . --> 00 01 81 01 01 <-- 00 01 A0 07 01 91 04 00 03 00 41 80 02 01 00 . . . . . . . . . A . . . . OpenSession 00030041 New Conditional Access Support (session id 2) --> 00 01 A0 0A 01 92 07 00 00 03 00 41 00 00 <-- 00 01 80 02 01 00 . . . . . . 2: ==> Ca Info Enq --> 00 01 A0 09 01 90 02 00 02 9F 80 30 00 <-- 00 01 80 02 01 00 . . . . . . --> 00 01 A0 01 01 <-- 00 01 80 02 01 00 . . . . . . --> 00 01 A0 01 01 <-- 00 01 80 02 01 00 |