[vdr] Upgrading from 1.4.7 to 1.7.0 : enabling #define

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Sun May 4 17:59:13 CEST 2008


On 05/04/08 16:40, Pierre-Yves Paranthoen (PERSO) wrote:
> One part of the pb is that my cam module is ramdomly identified under 1.7.0
> that might be the reason why the info "Application Info" and "Ca Pmt Reply"
> is not in the log. 
> VDR-1.7.0 most gives CAM 2: module present & CAM 2: module ready instead of
> giving Aston Module 1.0300, 01, 0100,0100 (info taken from vdr-1.4.7).
> When it's correctly being identified and trying to access CAM informations
> under OSD, VDR-1.7 responds ERROR: Can't open CAM menu!
> A CAM reset gives then a basic information : 2 CAM ready and nothing else.
> Of course no decryption.
> 
> Here is the log of matching my explainations : 
> 
> May  4 16:07:49 localhost vdr: [8251] CAM 2: module present
> May  4 16:07:50 localhost vdr: [8251] CAM 1: no module present
> May  4 16:07:50 localhost vdr: [8251] CAM 2: module ready
> May  4 16:07:54 localhost vdr: [8251] Slot 2: <== Application Info (2)
> May  4 16:07:54 localhost vdr: [8251] CAM 2: Aston Module 1.0300, 01, 0100,
> 0100

So the "application information" is being received.
I'm afraid I was looking at the wrong lines when telling you which
'dbgprotocol's to change. Please also change the ones in lines

696:   dbgprotocol("Slot %d: <== Ca Info (%d)", Tc()->CamSlot()->SlotNumber(), SessionId());

702:   dbgprotocol(" %04X", id);

713:   dbgprotocol("\n");

Klaus



More information about the vdr mailing list