On Mon, Oct 13, 2008 at 9:27 PM, Arthur Konovalov <artlov@xxxxxxxxx> wrote:
Hi Arthur,klaas de waal wrote:Unfortunately still does not works with 386MHz, at least in my case.
> I have now put in a frequency map table tda827x_dvbc
> for DVB-C tuners only. This works OK for me and it should not modify the
> behaviour with other non-DVB-C demodulators.
No lock, no picture...
Is it possible that 386MHz and 388MHz are in different frequency
segments? Which values I should tune? Any hint, please.
AK
My first patch extended the frequency segment to above 388MHz so the 386MHz is in the same segment.
It is of course possible that 386MHz does not work but this is difficult to test for me.
Question: which provider do you have?
Assuming you use "zap" to tune, you have a configuration file like this (valid for some Dutch UPC regio's):
Ned1:386750000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:2001:2012:12141
Ned2:386750000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:2301:2312:12142
Ned3:386750000:INVERSION_AUTO:6900000:FEC_AUTO:QAM_64:2601:2612:12143
Hints:
- use the exact frequency. if it is 386.75 use that and not 386
- fill in the correct symbol rate: 6900000 for UPC, 6875000 for Ziggo
if this number is wrong you will not receive anything
- fill in the modulation exact, for both UPC and Ziggo this is QAM_64
Groetjes,
Klaas
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
