[linux-dvb] Descramble failure with VP1032 and Matrix Reborn

David Santinoli marauder at tiscali.it
Thu Nov 30 22:59:35 CET 2006

  I'm trying to descramble JSTV 1 (Japanese satellite television) from
Hotbird, which broadcasts both FTA programmes (which I receive
correctly) and encrypted (Cryptoworks) ones, depending on the time of

My setup includes
- a vanilla kernel,
- DVB-utils from the 2006-11-09 snapshot, 
- a Twinhan clone card (PCI ID: 1822:0001), recognized as VP1032 /
- a so-called "Matrix Reborn" CAM, programmed for Cryptoworks.

Here follows an excerpt from dmesg regarding the card detection:

  kernel: bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB functions.
  kernel: DVB: registering new adapter (bttv0).
  kernel: dst_get_device_id: Recognise [DSTMCI]
  kernel: DST type flags : 0x1 newtuner 0x10 firmware version = 2
  kernel: dst_get_mac: MAC Address=[00:08:ca:16:55:00]
  kernel: dst_fw_ver: Firmware Ver = 1.4 Build = 02, on 11:5, 22-2-2005
  kernel: dst_card_type: Device Model=[VP1032]
  kernel: dst_get_vendor: Vendor=[TWINHANç¼^A]
  kernel: dst_ca_attach: registering DST-CA device
  kernel: DVB: registering frontend 0 (DST DVB-S)...

When I try to tune in JSTV 1 using "zap" (is this the correct utility to
use?), descrambling fails and the following output is produced:

  Using frontend "DST DVB-S", type DVB-S
  en50221_app_ai_message: Received unexpected tag 164000

  Problem retrieving frontend information: Operation not supported
  status SCVYL | signal 3c00 | snr 168e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
  en50221_app_ai_message: Received unexpected tag 164000
  <... repeats many times>

  <my ctrl-C>
  Poll error
  en50221_app_ai_message: Received unexpected tag 7cd16

(sometimes a 0 replaces 164000).

Also note that often, when the CAM is inserted, even FTA programmes have
problems (artifacts appear here and there).

My questions:
Are there any known issues with this DVB-S card / CAM setup?  From
previous posts, it would seem so.  In this case, would it be better if I
switched to another CAM (for example the Philips Cryptoworks module)?
Or is it a fault of the DVB card?

Are there any other pieces of information I can provide to build more
context -- for example, more output from dmesg or some utility?

Thanks in advance,

More information about the linux-dvb mailing list