I have a feeling that steps 2, 7, 10, 15, & 18 are going to be a ongoing (as I
have already been doing so leading up to this point) occurrence. I ran the
first command that Andy provided and got the following.
$ v4l2-ctl --list-devices
WinTV PVR 500 (unit #1) (PCI:0000:02:08.0):
/dev/video0
/dev/video24
/dev/video32
/dev/vbi0
WinTV PVR 500 (unit #2) (PCI:0000:02:09.0):
/dev/video1
/dev/video25
/dev/video33
/dev/vbi1
To me this looks fine yet the second receiver just shows static. Now I am
wondering about the health of the PVR 500. Given all the postings about
getting one but not the other I hold on to some fantasy about this being and
configuration issue.
If anyone else has experience with this and can give any other pointers it
would be most appreciated.
Thanks,
Peter
On 2010-08-24, at 6:18 PM, Michael Cree wrote:
> On 25/08/2010, at 12:11 AM, Andy Walls wrote:
>> Setting up udev is a pain, in that it is best if you learn how to use
>> udevadm to snoop hotplug event so you can then write rules to them.
>>
>> Conceptually something like this:
>>
>> 1. man udevadm
>> 2. confusion & swearing
>
> I utterly agree. When I tried reading the udevadm man file (for some other
> reason) I was left utterly be-wildered and muttering WTF. On realising that
> I would be encountering the following steps:
>
>> 7. confusion & swearing
>> 10. confusion & swearing
>> 15. confusion & swearing
>> 18 confusion & swearing
>
> on a regular basis if a pursued my project, I abandoned what I was doing and
> moved on to something much more enthusing and uplifting.
>
> Cheers
> Michael.
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
