[mythtv-users] Ceton Infinitv USB issues

[Krys Allen]

kris,
very interesting, thanks... any chance I could see the rule you wrote for
yours?
thanks,
-Krys


On Fri, Feb 22, 2013 at 11:22 AM, Mike Perkins <mikep at randomtraveller.org.uk
> wrote:

> On 22/02/13 16:54, Krys Allen wrote:
>
>> On Fri, Feb 22, 2013 at 9:59 AM, Mike Perkins wrote:
>>
>>> On 22/02/13 15:20, Krys Allen wrote:
>>>
>>>  infinitv_usbd is the service that has to be running, but come to think
>>>> of it mythbackend starts up fine even if this service isn't running it
>>>> just wont tune to any channel.
>>>>
>>>> I tried to make my own init script (there isnt one with the driver as
>>>> far as I could tell), but it needs some tweaking. The init script works
>>>> if I run it after my system is booted, but when run at boot it says it
>>>> cant find my tuning device. I assume that the init script is trying to
>>>> run before the usb port has found my device, I am just not sure how to
>>>> make it wait. Is there any options in mythbackend to have it start a
>>>> tuner card service?
>>>>
>>>> my init script --> http://pastebin.com/f3RtgUka (if you know how to
>>>> make
>>>> it wait on usb let me know)
>>>>
>>>> no I am not using a tuning adapter, but that varies based on your cable
>>>> provider.
>>>>
>>>> What you probably need is a udev rule that kicks in when the USB device
>>>>
>>> is recognized. That way everything happens in the right order.
>>>
>>>  What you probably need is a udev rule that kicks in when the USB device
>> is
>> recognized. That way everything happens in the right order
>>
>> Sorry, not sure what this entails... so would the udev rule be what starts
>> the infinitv_usdb service?
>>
>>  (Fixed quoting, sort of.)
>
> Yes, that's right. I'm not sure I can give you the exact details because I
> don't have your device but this page probably is what you need to look at:
>
> http://www.mythtv.org/wiki/**Device_Filenames_and_udev<http://www.mythtv.org/wiki/Device_Filenames_and_udev>
>
> What you will have to do is find out how your device is identified and
> write a rule to match it. The action you'll need won't be a SYMLINK one
> like a lot of the examples but a PROGRAM one which will run a script when
> your device gets detected.
>
> udev has a testing option so that you can see what it will attempt to do.
> You can use this to get your rule working.
>
>
> --
>
> Mike Perkins
>
> ______________________________**_________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/**listinfo/mythtv-users<http://www.mythtv.org/mailman/listinfo/mythtv-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130222/fb345a2e/attachment.html>