Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: 5 Months and counting
That may well seem like a dumb question, I mean why not just try and
see? But I did - and while it finds the devices and starts to scan now -
which it never did before - I get an error message saying:
raid517@2[scan]$ ./scan dvb-t/uk-Fenham
scanning dvb-t/uk-Fenham
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 509833333 0 1 0 1 0 0 0
>>> tune to:
509833333:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_1_2:FEC_NONE:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to:
509833333:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_1_2:FEC_NONE:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
(tuning failed)
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
>> Ahh... now we have some progress... I now can see that it finds all
the major components in the kernel and registers the correct front end
etc...
The only thing left that is still a little puzzling - though I'm not
sure if it's relevant is that when loading the various DVB components,
hotplug is still looking for something called dvb_ttpci_budget_ci.
Hotplug thinks I need it. But do I? And if so what is it?
The DVB-T file/transmitter it's scanning is uk-Fenham and is set out as
follows:
# Fenham
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 509833333 8MHz 1/2 NONE QAM16 2k 1/32 NONE
GJ
Home |
Main Index |
Thread Index