From: Newsy Paper <newspaperman_germany@yahoo.com>
To: Oleg Roitburd <oroitburd@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200
Date: Tue, 15 Dec 2009 19:44:30 +0000 (GMT) [thread overview]
Message-ID: <108905.8710.qm@web23208.mail.ird.yahoo.com> (raw)
In-Reply-To: <b42fca4d0912140407t3376959fhcc731b762979f37f@mail.gmail.com>
yes, this transponder is working again at blog.ors.at they say that they updated the modulator. It is working now again but driver still has this bug, so it's interesting what the update of the modulator changed exactly.
regards
Newsy
--- Oleg Roitburd <oroitburd@gmail.com> schrieb am Mo, 14.12.2009:
> Von: Oleg Roitburd <oroitburd@gmail.com>
> Betreff: Re: no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200
> An: "Newsy Paper" <newspaperman_germany@yahoo.com>
> CC: linux-media@vger.kernel.org
> Datum: Montag, 14. Dezember 2009, 13:07
> 2009/12/9 Newsy Paper <newspaperman_germany@yahoo.com>:
> > Hi,
> >
> > no matter if I use Igors or Manus driver, there's no
> lock on 11303 h 22000 2/3 8psk. Other users at vdr-portal
> report same problem.
> >
> > The strange thing is that all other transponders that
> use 22000 2/3 8psk do work but this transponder doesn't. It
> worked fine until december 3rd when uplink moved to Vienna.
> I think they changed a parameter like rolloff or inversion
> and the dvb-s2 part of stb6100 is buggy.
>
> It works again. Very strange.
>
> $ sudo ./scan-s2 -x -2 -O S19.2E ORF.ini
> API major 5, minor 0
> scanning ORF.ini
> using '/dev/dvb/adapter0/frontend0' and
> '/dev/dvb/adapter0/demux0'
> initial transponder DVB-S2 11303000 H 22000000 2/3 35 8PSK
> ----------------------------------> Using DVB-S2
> >>> tune to: 11303:hC23M5O35S1:S19.2E:22000:
> DVB-S IF freq is 1553000
> >>> parse_section, section number 0 out of 0...!
> service_id = 0x0
> service_id = 0x132F
> pmt_pid = 0x6B
> service_id = 0x1330
> pmt_pid = 0x6C
> service_id = 0x1331
> pmt_pid = 0x6D
> >>> parse_section, section number 0 out of 0...!
> VIDEO : PID 0x0DFF
> AUDIO : PID 0x0E00
> AUDIO : PID 0x0E01
> AC3 : PID 0x0E03
> TELETEXT : PID 0x0E04
> >>> parse_section, section number 0 out of 0...!
> CA ID : PID 0x0D05
> CA ID : PID 0x1702
> CA ID : PID 0x1833
> CA ID : PID 0x0648
> CA ID : PID 0x0D95
> CA ID : PID 0x09C4
> VIDEO : PID 0x0B68
> AUDIO : PID 0x0B69
> AC3 : PID 0x0B6B
> AUDIO : PID 0x0B6A
> TELETEXT : PID 0x0B6D
> >>> parse_section, section number 0 out of 0...!
> CA ID : PID 0x0D05
> CA ID : PID 0x1702
> CA ID : PID 0x1833
> CA ID : PID 0x0648
> CA ID : PID 0x0D95
> CA ID : PID 0x09C4
> VIDEO : PID 0x0780
> AUDIO : PID 0x0781
> AC3 : PID 0x0783
> AUDIO : PID 0x0782
> TELETEXT : PID 0x0785
> >>> parse_section, section number 0 out of 0...!
> 0x03EF 0x132F: pmt_pid 0x006B ORF -- ORF1 HD (running,
> scrambled)
> 0x03EF 0x1330: pmt_pid 0x006C ORF -- ORF2 HD (running,
> scrambled)
> 0x03EF 0x1331: pmt_pid 0x006D ServusTV -- Servus TV HD
> (running)
> >>> parse_section, section number 0 out of 0...!
> dumping lists (3 services)
> ORF1
> HD;ORF:11303:hC23M5O35S1:S19.2E:22000:1920:1921=ger,1922=ENG;1923=ger:1925:D05,1702,1833,648,D95,9C4:4911:1:1007:0
> ORF2
> HD;ORF:11303:hC23M5O35S1:S19.2E:22000:2920:2921=ger,2922=ENG;2923=ger:2925:D05,1702,1833,648,D95,9C4:4912:1:1007:0
> Servus TV
> HD;ServusTV:11303:hC23M5O35S1:S19.2E:22000:3583:3584=ger,3585=eng;3587=ger:3588:0:4913:1:1007:0
>
> Regards
>
> Oleg Roitburd
>
__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com
next prev parent reply other threads:[~2009-12-15 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:15 no locking on dvb-s2 22000 2/3 8PSK transponder on Astra 19.2E with tt s2-3200 Newsy Paper
2009-12-09 20:55 ` Matthias Wächter
2009-12-09 22:45 ` BOUWSMA Barry
2009-12-14 12:07 ` Oleg Roitburd
2009-12-15 19:44 ` Newsy Paper [this message]
2009-12-16 11:14 ` Matthias Wächter
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=108905.8710.qm@web23208.mail.ird.yahoo.com \
--to=newspaperman_germany@yahoo.com \
--cc=linux-media@vger.kernel.org \
--cc=oroitburd@gmail.com \
/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