All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Eric Cronin <ecronin@gizmolabs.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] HVR-1800 failing to detect any QAM256 channels
Date: Wed, 30 Apr 2008 20:20:43 -0400	[thread overview]
Message-ID: <48190CDB.3080307@linuxtv.org> (raw)
In-Reply-To: <B3017A65-6616-4FBF-BF82-30B3F69B6CAA@gizmolabs.org>

Eric Cronin wrote:
>
> On Apr 30, 2008, at 2:36 PM, Michael Krufky wrote:
>
>>>
>>> Eric,
>>>
>>> When you use the scan command to scan for QAM channels, you must
>>> specify -a2, to signify that you are scanning digital cable.
>>>
>>> Try that -- does that work?
>>
>>
>> My bad -- I meant, "-A 2"  (capitol A, space, 2) 

scan -A 2 -vvv dvb-apps/util/scan/atsc/us-Cable-Standard-whatever >
channels.conf

Is THAT what you're doing to scan ?


It looks like what you were doing was scan a tuned frequency for pids. 
If you want to do THAT, then you must actually be tuned to the given
frequency.  you need to azap SOME_CHANNEL -r, and keep that running
before attempting to run 'scan -c' ...  I think you should try the scan
command that I mentioned above.

HTH,

Mike

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

  reply	other threads:[~2008-05-01  0:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 17:03 [linux-dvb] HVR-1800 failing to detect any QAM256 channels Eric Cronin
2008-04-30 18:34 ` Michael Krufky
2008-04-30 18:36   ` Michael Krufky
2008-04-30 20:54     ` Eric Cronin
2008-05-01  0:20       ` Michael Krufky [this message]
2008-05-01  3:19         ` Eric Cronin
2008-05-01  3:24           ` Michael Krufky
2008-05-01 14:41             ` Eric Cronin
2008-04-30 18:55 ` Steven Toth

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=48190CDB.3080307@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=ecronin@gizmolabs.org \
    --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.