Michael Krufky wrote: > Patrick Boettcher wrote: > >> [02:09]<mkrufky> pmp: i'm back ... do u have any advice for me with >> the atsc scan? Is it a better sign that i got 'tuning failed' and >> not 'pid timeout' ? I'm looking for any sign that this driver is >> working correctly on my board. >> >> No pid timeout would be a better sign. tuning failed means that no >> lock has been reached. Try atscsan -A1 -v. You'll get "lock status: >> 0x1f" for a lock or 0x00 for no lock or something in between. > > Patrick- > > You intended for me to use -A3, not -A1, right? I am using digital > QAM256 cable. > > What does lock status 0x0c, 0x0d, and 0x04 mean? These are what I am > mostly getting on each channel, along with (tuning failed). I'm sorry... it isn't saying lock status... it says tuning status.... like below: scanning atsc/us-ATSC-center-frequencies-QAM256 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' >>> tune to: 57028615:QAM_256 >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d >>> tuning status == 0x0d WARNING: >>> tuning failed!!! >>> tune to: 57028615:QAM_256 (tuning failed) ... >>> tune to: 69028615:QAM_256 >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x0c >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x04 >>> tuning status == 0x04 WARNING: >>> tuning failed!!! >>> tune to: 69028615:QAM_256 (tuning failed) ... ERROR: initial tuning failed dumping lists (0 services) Done. -- Michael Krufky
