public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel ALLAUD <eallaud@yahoo.fr>
To: Linux DVB Mailing List <linux-dvb@linuxtv.org>
Subject: [linux-dvb] TT 3200: S2 transponder kind of locks with multiproto but not at all with S2 API
Date: Thu, 11 Dec 2008 15:21:32 -0400	[thread overview]
Message-ID: <1229023292.21398.0@manu-laptop> (raw)

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

	Hi all,
OK what the subject does not say: I want to tune to a DVB-S2 
transponder on intelsat-903 (~34 W). FEC is said to be 5/6.
OK so with a rather oldy multiproto driver I am getting kind of a lock 
"DVB-S2 demod lock" (see the dmesg log) using simpledvbtune but it does 
not seem to lock properly though as I dont get the viterbi lock and 
everything.
With S2API rather recent: nothing, no demod lock.

BTW using szap2 with multiproto driver gives me no demod lock either!?

Anyway if anyone can make some sense out of this or gives me some more 
things to test out I'd be glad to try (yes I desperatly want to see 
those HD channels ;-).
Thx
Bye
Manu

[-- Attachment #2: dvbs2-multiproto-demod-lock-dmesg.txt.bz2 --]
[-- Type: application/x-bzip, Size: 7724 bytes --]

[-- Attachment #3: dvbs2-S2API-demod-nolock-dmesg.txt.bz2 --]
[-- Type: application/x-bzip, Size: 12319 bytes --]

[-- Attachment #4: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-12-11 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 19:21 Emmanuel ALLAUD [this message]
2008-12-17 23:11 ` [linux-dvb] TT 3200: S2 transponder kind of locks with multiproto but not at all with S2 API Newsy Paper
2008-12-18  1:36   ` [linux-dvb] Re : " Emmanuel ALLAUD

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=1229023292.21398.0@manu-laptop \
    --to=eallaud@yahoo.fr \
    --cc=linux-dvb@linuxtv.org \
    /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