From: "Roman Jarosz" <roman.jarosz@gmail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVB-S Channel searching problem
Date: Sat, 03 Jan 2009 21:59:08 +0100 [thread overview]
Message-ID: <op.um68ku1qrj95b0@localhost> (raw)
In-Reply-To: <c74595dc0901031248h3c3d002j2422331c82249d78@mail.gmail.com>
On Sat, 03 Jan 2009 21:48:45 +0100, Alex Betis <alex.betis@gmail.com> wrote:
> On Sat, Jan 3, 2009 at 9:39 PM, Roman Jarosz <roman.jarosz@gmail.com>
> wrote:
>
>> On Sat, 03 Jan 2009 19:58:45 +0100, Alex Betis <alex.betis@gmail.com>
>> wrote:
>>
>> >> I use scan from dvb-apps, the command is
>> >> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
>> >> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"
>> >
>> > I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
>> > astra's maintainers and connect to any transponder is enough to get a
>> > list
>> > of all others. I personaly don't trust those maintainers since I saw
>> too
>> > many errors in NIT messages that specify the transponder, so I specify
>> > all
>> > the frequencies I want to scan. I don't have a dish to 19.2, but there
>> > were
>> > many errors with 5 other satellites I have.
>> > You can get a list of those frequencies here:
>> > http://www.lyngsat.com/astra19.html
>>
>> Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
>> it doesn't find anything.
>
> Try also scan-s2 with:
> S 12188000 H 27500000 3/4 AUTO QPSK
No luck :( http://kedge.wz.cz/dvb/scans2_2.txt
> Do you have a diseqc on the way?
No. I don't.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2009-01-03 20:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 16:42 [linux-dvb] DVB-S Channel searching problem Roman Jarosz
2009-01-03 17:01 ` Brice DUBOST
2009-01-03 17:14 ` BOUWSMA Barry
2009-01-03 17:15 ` Roman Jarosz
2009-01-03 17:28 ` Alex Betis
2009-01-03 18:11 ` Roman Jarosz
2009-01-03 18:58 ` Alex Betis
2009-01-03 19:37 ` Gregoire Favre
2009-01-04 8:14 ` Goga777
2009-01-04 8:29 ` hermann pitton
2009-01-04 10:37 ` Gregoire Favre
2009-01-04 16:06 ` hermann pitton
2009-01-04 16:37 ` Gregoire Favre
2009-01-04 17:15 ` hermann pitton
2009-01-04 18:24 ` Gregoire Favre
2009-01-08 2:20 ` hermann pitton
2009-01-04 10:35 ` Gregoire Favre
2009-01-04 10:58 ` Roman Jarosz
2009-01-04 12:42 ` Mika Laitio
2009-01-04 13:11 ` Roman Jarosz
2009-01-04 14:56 ` Goga777
2009-01-04 20:47 ` Roman Jarosz
2009-01-04 21:24 ` Goga777
2009-01-05 17:43 ` Roman Jarosz
2009-01-05 17:58 ` Roman Jarosz
2009-01-05 19:00 ` Goga777
2009-01-06 14:58 ` Mika Laitio
2009-01-03 19:39 ` Roman Jarosz
2009-01-03 20:48 ` Alex Betis
2009-01-03 20:59 ` Roman Jarosz [this message]
2009-01-03 21:01 ` Alex Betis
2009-01-04 3:52 ` BOUWSMA Barry
-- strict thread matches above, loose matches on Subject: below --
2009-01-04 19:46 Eduard Huguet
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=op.um68ku1qrj95b0@localhost \
--to=roman.jarosz@gmail.com \
--cc=kedgedev@centrum.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.