Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Tuning problems with the refactored drivers



> >insmod ./dvb-core.ko dvb_override_tune_delay=200
>
> Ok. I have now tested the tuning by loading dvb-core.ko with
> dvb_override_tune_delay=200 and that helped
> and driver was able to tune all channels.

Good! I'll commit that change later.

> Some of the channels are however still having problem to get locked.
>
> >>Btw. even I can now tune all channels ok, I have still problems to get
> >>some of the channels locked. (these from the 162 mhz)
> >>(Some others locks very fastly)
> >>
> >>[lamikr@aragorn szap]$ ./czap "YLE TV1"
> >>using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> >>reading channels from file '/home/lamikr/.czap/channels.conf'
> >> 19 YLE TV1:162000000:INVERSION_AUTO:6900000:FEC_NONE:QAM_128:512:650:17
> >> 19 YLE TV1: f 162000000, s 6900000, i 2, fec 0, qam 4, v 0x200, a 0x28a
> >
> >Does that channel have a low symbol rate? With DVB-S cards (STV0299B
> > based) I've had problems locking on with such channels (say < 10000000) -
> > can take a number of seconds to get a lock.
>
> Is there any tool I could use for finding out the symbol rate for the
> channels running in the 162 Mhz mux?
> Or some other place in the code where I could try to play in order to
> improve the locking.
> Currently the driver is able to get lock only for a couple of seconds
> even after couple of minutes.

I was thinking the "s 6900000" above was the symbol rate - its something you'd 
have to supply as a parameter to the tuning.

The only thing to be done now really is to mess about with ves1820.c - if you 
can find the docs that is. 




Home | Main Index | Thread Index