[linux-dvb] Re: Understanding (widespread) TT DVB-T crash

["Edward Wildgoose" <ed@wildgooses.com>]

> Juri Haberland wrote:
> > Johannes Stezenbach wrote:
> >> You are confusing me. Does it tune (does tzap report FE_HAS_LOCK), or
> >> doesn't it? Do you have any error messages in the kernel log
> >> (dmesg or /var/log/...)?
> >
> > There is nothing in the logs. Tuning *seems* to work, but the output of
> > tzap doesn't change - even if you tune to a new channel.
> > Whether it reports FE_HAS_LOCK I cannot say at this point but the next
> > time it happens I'll double check and send a note.
>
> Ok, it happened again (sometimes every night, sometimes not for a week or
> so...).
>
> Here is the output of three tuning attempts - nothing in the logs:
>
> # ./tzap K33
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> tuning to 570000000 Hz
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |
> status 01 | signal 4f4f | snr 0000 | ber 00000000 | unc 00000000 |

...

Aha, my symptoms are very similar (no messages in the logs either).
However, I *DO* get FE_HAS_LOCK when I use tzap!  In your case it doesn't
look as thought the tuner is actually tuning?  In my case I get something
which does look somewhat like a normal tune (although attempts to read the
channel list in the mux, or watching the signal strength sit on a fixed
value, show that it hasn't quite tuned properly, or at least something after
the tuner has died)

Any ideas on how to debug further?

Ed W



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.