[mythtv-users] Can't get HD TV channels working

[Hika van den Hoven]

Hoi John,

Tuesday, April 28, 2015, 5:42:46 PM, you wrote:

> On 28/04/15 15:34, Hika van den Hoven wrote:
>> Hoi John,
>>
>> Tuesday, April 28, 2015, 4:21:07 PM, you wrote:
>>
>>> On 28/04/15 14:33, Hika van den Hoven wrote:
>>>> Hoi John,
>>>>
>>>> Tuesday, April 28, 2015, 3:21:24 PM, you wrote:
>>>>
>>>>> On 28/04/15 13:25, Hika van den Hoven wrote:
>>>>>> Hoi John,
>>>>>>
>>>>>> Tuesday, April 28, 2015, 1:45:04 PM, you wrote:
>>>>
>>>>>>
>>>>>>> ...and I think it might be worth checking that you really /are/ using
>>>>>>> the device that you intend to use.  At present a reboot still puts my
>>>>>>> tuners in quasi-random order and I have to unplug/replug my usb device,
>>>>>>> perhaps several times, to make sure it's properly initialised.  dmesg |
>>>>>>> grep adapter can be useful.
>>>>>>
>>>>>> Why not use udev to create them consistent? Even if you have two equal
>>>>>> devices you can distinguish them by pci or usb ID. You then of cause
>>>>>> have to plug them always in the same port!
>>>>
>>>>> Good question.  Because life's too short.  I believe I have my desired
>>>>> order set up in /etc/modprobe.d/dvb.conf, but it's not working.  With my
>>>>> current kernel (from SL7) the order does seem consistent, but not in
>>>>> accord with that and what I have mythtvsetup expecting.  I suspect dvb
>>>>> isn't much used at the Fermi National (USA) Accelerator Laboratory :-)
>>>>
>>>> If you give output to:
>>>> udevadm info --attribute-walk --name <your-device>
>>>> I'll give you a setup for a rule.
>>>>
>>
>>> That's a great offer, thanks. But I haven't found a name it likes.
>>
>>> Here's what dmesg finds:
>>
>>> saa7134 0000:07:04.0: DVB: registering adapter 0 frontend 0 (Philips
>>> TDA10046H DVB-T)...
>>> usb 2-2: DVB: registering adapter 1 frontend 0 (Kworld UB499-2T
>>> T09(IT9137)_1)...
>>> usb 2-2: DVB: registering adapter 2 frontend 0 (Kworld UB499-2T
>>> T09(IT9137)_2)...
>>
>>
>>> modprobe  saa7134_dvb
>>> modprobe dvb-usb-af9035
>>
>>> John
>>
>> <your-device> should be the full path to your devicenodes in /dev
>>
>> Alternatively you can try:
>> udevadm info --attribute-walk --path $(udevadm info --query path --name=<your-device>)
>>

> OK, so, in the first form, I have --name /dev/dvb/adapterN/frontend0 
> where N = 1 or 2 or 3, and each produces around a hundred lines of 
> output.  ISTR a long thread about this a few months ago, so I'll look at
> that rather than dump it all here.   It's working at present - and The
> biggest problem last time seemed to be initialising the USB device.

> Thanks again.

> John

If they are all different devices include the subsystem:
 SUBSYSTEM=="video4linux", or
 SUBSYSTEM=="dvb",

the IDs:
  ATTRS{idVendor}=="046d",
  ATTRS{idProduct}=="0825",

and for analog the kernel name replacing the number with *:
  KERNEL=="video*",

to identify by location add something like:
  KERNELS=="2-2.1:1.0",

You get the exact values from that output.

Then in the end for analog add the link you want:
  SYMLINK+="v4l/Winfast/video"

And for DVB add the directory where you want all the nodes for that
adapter:
  PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf dvb/adapter104/%%s $${K#*.}'", SYMLINK+="%c"

All on one line separated by , You can break the line by placing a
backslash at each linebreak.
Name the file something like: 61-private-v4l.rules and place it in:
/etc/udev/rules.d/
They are processed in the numeric order and 61 places it high enough
that it has been initialized.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens