[mythtv-users] Ceton Infinitv USB issues
michael helmer
micmizer at gmail.com
Sat Feb 23 22:28:09 UTC 2013
Wow... I clearly missed "infinitv_usbd is the user space linux driver for
the Ceton InfiniTV USB." in the README. I foolishly just did the
configure/make/make install. =/ Thanks Allen for pointing that out!
I am unfortunately still unable to watch/record TV in MythTV. I have also
tried capturing the infinitv client stream with netcat and that is still
producing 0 byte files. The last week I have been trying to get network
tuners working in Windows MCE and I havent had any luck with that either.
Normal tuner configuration works great though! My end goal would be to have
network tuners working in MCE so I can record copy once shows and have 3
tuners presented to MythTV.
In Windows I know the traffic is there on the wire as I captured a
wireshark trace and can see all of the UDP traffic going to port 5001. When
I run the client.py in Linux and capture on lo I am seeing some bizarre
malformed packets and destination unreachable for ICMP on the local
127.0.0.1.
This loops forever:
1 0.000000 192.168.180.3 192.168.180.3 YAMI 1370
[Malformed Packet]
2 0.000245 127.0.0.1 127.0.0.1 MPEG TS 1358 Source port:
43409 Destination port: irdmi
3 0.000264 127.0.0.1 127.0.0.1 ICMP 590 Destination
unreachable (Port unreachable)
It sure seems like a network issue or something blocking these ports. In
windows I uninstalled all antivirus software and disabled the firewall and
i see the same behaviour. The same is true for my Ubuntu box.
--
Michael
On Fri, Feb 22, 2013 at 1:42 PM, Krys Allen <allen.krys at gmail.com> wrote:
> Great info guys, ill see if I can't scratch something together.
>
>
> On Fri, Feb 22, 2013 at 12:51 PM, Mike Perkins <
> mikep at randomtraveller.org.uk> wrote:
>
>> On 22/02/13 18:00, Ronald Frazier wrote:
>>
>>> On Fri, Feb 22, 2013 at 12:56 PM, Kris Jensen <kris.jensen.knj at gmail.com>
>>> wrote:
>>>
>>>>
>>>> On Fri, Feb 22, 2013 at 12:48 PM, Kris Jensen <
>>>> kris.jensen.knj at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On Fri, Feb 22, 2013 at 12:38 PM, Krys Allen <allen.krys at gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> kris,
>>>>>> very interesting, thanks... any chance I could see the rule you wrote
>>>>>> for
>>>>>> yours?
>>>>>> thanks,
>>>>>> -Krys
>>>>>>
>>>>>>
>>>>>>
>>>>>> 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>
>>>>>>
>>>>>>
>>>>> Sure. Keep in mind I am using the internal card version of the Ceton
>>>>> Infinitv and not the USB version so the rule well differ (a lot).
>>>>>
>>>>> [/code_start]
>>>>>
>>>>> # MythTV Backend service
>>>>>
>>>>> description "MythTV Backend"
>>>>> author "Mario Limonciello <superm1 at ubuntu.com>"
>>>>>
>>>>> start on (local-filesystems and net-device-up IFACE!=br0 and
>>>>> ctn91xx-device-added KERNEL=ctn91xx_ctl1 and net-device-added
>>>>> INTERFACE=br0
>>>>> and started udev-finish)
>>>>> stop on runlevel [016]
>>>>>
>>>>> kill timeout 10
>>>>> respawn
>>>>> respawn limit 2 3600
>>>>>
>>>>> pre-start script
>>>>> [ -x /usr/sbin/mysqld ] || exit 0
>>>>> for i in `seq 1 30` ; do
>>>>> /usr/bin/mysqladmin --defaults-file=/etc/mysql/**debian.cnf
>>>>> ping &&
>>>>> exit 0
>>>>> sleep .5
>>>>> done
>>>>> end script
>>>>>
>>>>> script
>>>>> test -f /etc/default/locale && . /etc/default/locale || true
>>>>> LANG=$LANG exec /usr/bin/mythbackend --syslog local7 --user
>>>>> mythtv
>>>>> end script
>>>>>
>>>>>
>>>>> [/code_end}
>>>>>
>>>>> Hope it helps.
>>>>>
>>>>
>>>>
>>>> Sorry I just realized that's not actually the udev rule. Its my back end
>>>> start up script that I had to edit to start up the back end correctly
>>>> with
>>>> the Ceton card.
>>>>
>>>> the is the udev rule.
>>>>
>>>> [/code-start]
>>>>
>>>> KERNEL=="ctn91xx_*", SYMLINK+="ceton/%k",
>>>> MODE="0666",OWNER="root",**GROUP="root"
>>>>
>>>> [/Code_end]
>>>>
>>>>
>>>> Hope it helps.
>>>>
>>>>
>>> Note: that script will not work for the USB devices, as the ctn91xx*
>>> dev entries do not get created. Those entries are only created for the
>>> PCIe version. Now, there might be some alternate /dev entry you could
>>> use to detect it, but I don't know what it would be
>>>
>>> USB devices can always be picked out by subsystem and have an
>> identifying "subsystem_vendor" and "susbsystem_device" code which can be
>> used to nail them exactly. These codes are issued by the vendor so should
>> never change.
>>
>> To find them, check dmesg for when the USB subsystem picks them up during
>> boot. That will give you the values to use in your rule. There are example
>> rules in that web page I pointed you to which link USB tuners.
>>
>> --
>>
>> 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>
>>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
>
--
Michael Helmer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130223/19e65d13/attachment.html>
More information about the mythtv-users
mailing list