[mythtv-users] CoreContext dvbchannel.cpp:347 (CheckFrequency) DVBChan(23:/dev/dvb/adapter3/frontend0): Your frequency setting (10906000) is out of range. (min/max:950000/2150000)

Jksj jksjdevelop at gmail.com
Tue Nov 27 19:01:11 UTC 2012


On 27/11/12 13:41, Per Jessen wrote:
> Jksj wrote:
>
>> On 26/11/12 12:07, Per Jessen wrote:
>>> Karl Dietz wrote:
>>>
>>>> On 26.11.2012 10:26, Per Jessen wrote:
>>>>> This sounds like a '0' slipping somewhere - the frequency is
>>>>> correct 10.906000Ghz = 10906000kHz, so does the card/driver somehow
>>>>> report
>>>>> the wrong frequency range?  This is a Hauppauge Nova S Plus.  FWIW,
>>>>> reception seems to work fine, but I'm debugging some issues with
>>>>> frequently failing recordings.
>>>> I think you might be chasing a red herring as the test is likely
>>>> wrong for DVB-S and only correct for DVB-C/T. card
>>>>
>>>> see
>>>>
> http://en.wikipedia.org/wiki/Low-noise_block_downconverter#Block_downconversion
>>>> 10906000kHz is the received frequency which gets converted down to
>>>> an intermediate frequency of 950000kHz-2150000kHz by the LNB.
>>> Hi Karl
>>>
>>> thanks for the explanation.  Have I misconfigured something or should
>>> I
>>> just ignore that message?  The Hauppauge card is definitely DVB-S,
>>> not -C or -T.
>>>
>>>
>>> thanks
>>> Per
>>>
>>>
>>    I had this error message when I added a PCI based DVB-S2 card to a
>> system with a USB DVB-T2 card. Occasionally at start up the kernel
>> would swap the two card round causing myth to attempt to tune the
>> terrestial card using satellite frequencies. Using UDEV rules to fix
>> the ids sorted it - just a thought.
> I did have that issue with the device numbering initially (I have two
> Hauppauge and one other card), but I think I fixed that using
> the "adapter_nr" module parameter.
>
> Do you mind sharing your udev rules ?  I think I would prefer doing it
> that way.
>
>
> thanks
> Per
>
I followed the wiki at http://www.mythtv.org/wiki/Device_Filenames_and_udev.
You have to identify a unique feature of each device.
Display them using.

udevadm info -a -p $(udevadm info -q path -n /dev/dvb/adapter0/dvr0)
then
udevadm info -a -p $(udevadm info -q path -n /dev/dvb/adapter1/dvr0)
etc.
Then follow the  Example DVB udev Rules file in the wiki.
I ended up with :-# /etc/udev/rules.d/10-local.rules
# //www.mythtv.org/wiki/Device_Filenames_and_udev
# To Ientify serial nos etc for a Device call
# udevadm info -a -p $(udevadm info -q path -n /dev/dvb/adapter0/frontend0)
#

# Create a symlink /dev/dvb/adapter101 pointing to PCTV 290e with serial 00000006LL8C
SUBSYSTEM=="dvb", SUBSYSTEMS=="usb", ATTRS{manufacturer}=="PCTV Systems", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LL8C", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter101/%%s $${K#*.}'", SYMLINK+="%c"

# Create a symlink /dev/dvb/adapter102 pointing to PCTV 290e with serial 000000107993
SUBSYSTEM=="dvb", SUBSYSTEMS=="usb", ATTRS{manufacturer}=="PCTV Systems", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="000000107993", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter102/%%s $${K#*.}'", SYMLINK+="%c"

# Create a symlink /dev/dvb/adapter103 pointing to  s660
SUBSYSTEM=="dvb", SUBSYSTEMS=="usb", ATTRS{manufacturer}=="TBS-Tech", ATTRS{product}=="DVBS2BOX", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter103/%%s $${K#*.}'", SYMLINK+="%c"

# Create a symlink /dev/dvb/adapter104 pointing to  TBS 6920
SUBSYSTEM=="dvb", SUBSYSTEMS=="pci", DRIVERS=="cx23885", ATTRS{device}=="0x8852", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter104/%%s $${K#*.}'", SYMLINK+="%c"





More information about the mythtv-users mailing list