[linux-dvb] [PATCH]Fix a bug in scan, which outputs the wrong frequency if the current tuned transponder is scanned only
alex.betis at gmail.com
Tue Dec 2 21:05:35 CET 2008
On Tue, Dec 2, 2008 at 9:43 PM, e9hack <e9hack at googlemail.com> wrote:
> Alex Betis schrieb:
> > I don't understand what's wrong with NIT advartised frequency?
> > For example, many satelite sites (such as lyngsat) have different
> > frequencies listed for the same channel, generally a difference of 1 MHz
> > here and there.
> If I do scan the tuned transponder only (parameter '-c'), scan will copy
> all NIT entries
> to the same transponder data. The output contains the last frequency, which
> was found. On
> DVB-C, the NIT contains the frequencies of all transponders. If VDR has
> tuned to the
> 113MHz transponder and I scan this transponder, I should got 113MHz and
> QAM64 modulation,
> but I get e.g. 466MHz and QAM256 modulation. The frequency changes on every
What driver and scan utility do you use?
If you use S2API driver, please try my scan-s2 from here:
I did several fixes in that area. If it still doesn't work, please run it
with "-vv" or "-vvv", (don't remember what level is needed) until you'll see
a HEX dump of the messages, send it to me and I'll take a look.
> linux-dvb mailing list
> linux-dvb at linuxtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linux-dvb