[mythtv-users] Ceton Infinitv USB issues

[Ronald Frazier]

On Fri, Feb 22, 2013 at 10:20 AM, Krys Allen <allen.krys at gmail.com> 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.

Correct. With the USB device, it uses the linux ECM class driver to
automatically configure the virtual network connection without any
additional software. So if you just plug it in without installing
anything, myth will be able to see it, get info, change channels, etc.
The only part that is not supported by the ECM driver is the RTP part.
For that part to work, you need to install Ceton's usb driver and have
it running (the infinitv_usbd service you mentioned).

>
> 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.

It may just be that you need to start it later in the init.d chain. In
the old style init.d, scripts are launched in the order of their
numeric priority (default I think is 20 for start and 80 for kill, but
don't quote me). If you look in /etc/rc*.d you can see what each
scripts numeric priority is.

A few years ago the init.d process was changed (at least in debian) to
support a dependency ordering. You can create a special header comment
in your init.d script that identifies what other init.d services the
script is dependent on. Then init.d will make sure those services are
started first.

If it's not just an ordering issue, then you'll need to find some
other way. Either sleep for 30 seconds or something, or find a way to
detect that it's ready. Or have a loop that tries to start it, detects
the failure, waits 30 seconds, and tries again.

Sorry, not sure exactly the best way.

-- 
Ron Frazier