From: Pierre Gronlier <ticapix@gmail.com>
To: lotway@nildram.co.uk
Cc: linux-media@vger.kernel.org
Subject: Re: TT S2-3200 and CAMs
Date: Wed, 04 Mar 2009 18:23:40 +0100 [thread overview]
Message-ID: <49AEB91C.6010804@gmail.com> (raw)
In-Reply-To: <49AE8BB3.3010501@nildram.co.uk>
Lou Otway wrote:
> Hi,
>
> I've been testing the TT S2-3200 card and while it performs well for FTA
> services I have been unable to get it working with encrypted services using
> the CI slot.
>
> With VLC I am able to tune to the transponder and pick up all the services
> but they are not decrypted, unencrypted services work fine.
>
> Using a DVB-S card with CI I am able to tune successfully, proving the CAMs
> are valid. This leads me to believe there may be a problem with the drivers
> for the S2-3200.
>
> Has anyone managed to get CAMs working with this card?
>
yes, I manage to decrypt a entire dvb-s transponder using a powercam and
mumudvb for streaming channels.
I'm using the v4l-dvb driver from the hg repository.
For mumudvb, I made a checkout of the git repository
http://mumudvbgit.braice.net/mumudvb.git and compiled the source with
LIBDVBEN50221=1 make (you need the dvb-apps to be installed)
But using this card, I didn't manage to lock on my second lnd head, so I
manage to lock on astra 19.2E but not on hotbird 13.0E.
Pierre
> Any advice gratefully recieved.
>
> Many thanks,
>
> Lou
> --
> Lou Otway
> mailto:lotway@nildram.co.uk
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-03-04 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 14:09 TT S2-3200 and CAMs Lou Otway
2009-03-04 14:52 ` Re : " Manu
2009-03-04 17:23 ` Pierre Gronlier [this message]
2009-03-06 15:48 ` Lou Otway
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49AEB91C.6010804@gmail.com \
--to=ticapix@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=lotway@nildram.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox