[mythtv-users] How to make static device nodes for video capture cards in MythTV .22?

John Drescher drescherjm at gmail.com
Wed Dec 9 17:28:11 UTC 2009


On Wed, Dec 9, 2009 at 12:24 PM, Dave <dave at davestechshop.net> wrote:
>
>
> On Wed, Dec 9, 2009 at 12:03 PM, John Drescher <drescherjm at gmail.com> wrote:
>>
>> On Wed, Dec 9, 2009 at 11:58 AM, Dave <dave at davestechshop.net> wrote:
>> >
>> >
>> > On Wed, Dec 9, 2009 at 11:44 AM, Kevin Kuphal <kkuphal at gmail.com> wrote:
>> >>
>> >> On Wed, Dec 9, 2009 at 10:02 AM, Dave <dave at davestechshop.net> wrote:
>> >> >
>> >> > I am running Mythbuntu 9.10 with 1 PVR150 and 1 HVR850. When I
>> >> > reboot,
>> >> > the PVR150 is changing device nodes. I tried the script mentioned in
>> >> > this
>> >> > thread (http://ubuntuforums.org/showthread.php?t=753434) and I do get
>> >> > a
>> >> > symlink, but I do not see the new static device node as an option in
>> >> > myth
>> >> > backend setup.
>> >> >
>> >> > Does this "Ubuntu Jaunty" script work in Mythbuntu 9.10 / MythTV .22?
>> >> >
>> >> > Is there a better solution yet?
>> >> >
>> >> > What can I do now, other than not reboot? ;)
>> >>
>> >> The hard way: write udev rules
>> >> This has always troubled me
>> >>
>> >> Easy way (for me): Add an option line to your ivtv module in
>> >> modprobe.conf
>> >> options ivtv ivtv_first_minor=1
>> >>
>> >> This will cause ivtv to always take /dev/video1 (double check with a
>> >> google search to see if ivtv_first_minor is 0 based) and should leave
>> >> /dev/video0 for your other card
>> >>
>> >> Kevin
>> >>
>> > Thanks for your reply.
>> >
>> > I did already make a udev rule (using the python script at the link I
>> > provided).
>> >
>> > Here's my rule:
>> > KERNEL=="video*", ATTR{name}=="ivtv0 encoder MPG",
>> > ATTRS{vendor}=="0x4444",
>> > KERNELS=="0000:01:04.*", SYMLINK+="video_PVR150"
>> >
>> > I added this rule to /etc/udev/rules.d/60-symlinks.rules
>> >
>> > I expected to see /dev/video_PVR150 as a choice in myth backend setup.
>> > However, it is not there, even after a reboot.
>> >
>> > Can anyone say whether this is a MythTV .22 issue or a mistake in my
>> > rule or
>> > something else? Thanks.
>> >
>>
>> Here is what I have for my pvr500 to keep it from messing with my kworld
>> 115
>>
>> # cat 60-ivtv.rules
>> #DRIVER=="ivtv",KERNELS=="0000:02:08.0", SYMLINK+="pvr_150"
>>
>> ATTR{name}=="ivtv0 encoder MPG", SYMLINK+="pvr_150"
>> KERNEL=="video?",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv0 encoder
>> MPG", SYMLINK+="v4l/video0"
>> KERNEL=="video?",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv1 encoder
>> MPG", SYMLINK+="v4l/video1"
>> KERNEL=="video??",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv0 encoder
>> PCM", SYMLINK+="v4l/video24"
>> KERNEL=="video??",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv1 encoder
>> PCM", SYMLINK+="v4l/video25"
>> KERNEL=="video??",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv0 encoder
>> YUV", SYMLINK+="v4l/video32"
>> KERNEL=="video??",SUBSYSTEM=="video4linux",ATTR{name}=="ivtv1 encoder
>> YUV", SYMLINK+="v4l/video33"
>>
>> John
>>
>>
> Thanks. Based on what I see in your rules, I think I'll try changing mine to
> this:
>
> KERNEL=="video*", ATTR{name}=="ivtv0 encoder MPG", SYMLINK+="video_PVR150"
>
> It looks to me like you are saying your original (commented out) rule was
> too restrictive (too specific). Is that what you found?
>

I do not remember if that ever worked. I swapped my 3 capture cards
around a bit. The other rules do work with my pvr500 and also the
first tuner of my pvr150 if I swap that out instead of the pvr500.

John


More information about the mythtv-users mailing list