LinHES Forums http://forum.linhes.org/ |
|
HD-5500 - pcHDTV and WinTV-PVR-USB2 - Solved http://forum.linhes.org/viewtopic.php?f=22&t=22383 |
Page 1 of 1 |
Author: | tscholl [ Sun Dec 25, 2011 4:50 pm ] |
Post subject: | HD-5500 - pcHDTV and WinTV-PVR-USB2 - Solved |
New system and fresh install of R7.1 I can configure the HD-5500 and PVR-USB2 (/dev/video0) correctly on initial configuration and they both work for awhile then the system just hangs nothing works, no keyboard can't ssh into it. When I reboot the machine the PVR-USB2 shows an error, and when I look at dmesg it shows that the PVR-USB2 is now at a different device number. Code: /dev/video0 is now /dev/video1 and I also have to reconfigure the Analog side of the HD-5500 as well. Then it will work for awhile but will eventually hang again. Seems like some kind of interrupt issue. That the 2 cards keep getting different device ids. If I remove the HD-5500 card. All works well and seems to be stable and the PVR-USB2 maintains the same device id. Any suggestions. |
Author: | tscholl [ Wed Mar 21, 2012 2:12 pm ] |
Post subject: | Re: HD-5500 - pcHDTV and WinTV-PVR-USB2 |
Well I have verified that I have the the same problem with similar hardware on a second F/B box. This one has a HD-3000 and a PVR-350 installed. On every reboot the PVR-350 changes it's ID Code: /dev/video0 is now /dev/video1 or goes the other way /dev/video1 is now /dev/video0 This started happening after upgrading to version 7 and occurs in both 7.1 and 7.2 Any ideas tjc? Any one? Thanks, Tim |
Author: | slowtolearn [ Wed Mar 21, 2012 3:07 pm ] |
Post subject: | Re: HD-5500 - pcHDTV and WinTV-PVR-USB2 |
tscholl wrote: Well I have verified that I have the the same problem with similar hardware on a second F/B box. This one has a HD-3000 and a PVR-350 installed. On every reboot the PVR-350 changes it's ID Code: /dev/video0 is now /dev/video1 or goes the other way /dev/video1 is now /dev/video0 This started happening after upgrading to version 7 and occurs in both 7.1 and 7.2 Any ideas tjc? Any one? Thanks, Tim Ahh yes, the joys of udev: http://linhes.org/projects/linhes/wiki/ ... using_udev is HD-PVR specific, but you can apply the same ideas. http://www.mythtv.org/wiki/Device_Filenames_and_udev provides examples for a number of capture devices. |
Author: | tscholl [ Thu Mar 22, 2012 12:04 pm ] |
Post subject: | Re: HD-5500 - pcHDTV and WinTV-PVR-USB2 |
slowtolearn, Thanks for pointing me in the right direction but I have a few questions. The wiki says to look for Code: E: ID_SERIAL_SHORT=xxxxxxxx But when I run the command "udevadm info --query=all --name=/dev/video0" I get Code: P: /devices/pci0000:00/0000:00:1e.0/0000:02:0c.0/video4linux/video0 N: video0 S: v4l/by-path/pci-0000:02:0c.0-video-index0 S: video E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:02:0c.0/video4linux/video0 E: MAJOR=81 E: MINOR=0 E: DEVNAME=/dev/video0 E: SUBSYSTEM=video4linux E: ID_V4L_VERSION=2 E: ID_V4L_PRODUCT=Hauppauge WinTV PVR-350 E: ID_V4L_CAPABILITIES=:capture:video_output:audio:tuner:radio: E: ID_PATH=pci-0000:02:0c.0 E: DEVLINKS=/dev/v4l/by-path/pci-0000:02:0c.0-video-index0 /dev/video E: TAGS=:udev-acl: When I run "udevadm info -a -p $(udevadm info -q path -n /dev/video0)" Code: KERNEL=="video0" SUBSYSTEM=="video4linux" DRIVER=="" ATTR{name}=="ivtv0 encoder MPG" ATTR{index}=="0" looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:02:0c.0': KERNELS=="0000:02:0c.0" SUBSYSTEMS=="pci" DRIVERS=="ivtv" ATTRS{vendor}=="0x4444" ATTRS{device}=="0x0803" ATTRS{subsystem_vendor}=="0x0070" ATTRS{subsystem_device}=="0x4000" ATTRS{class}=="0x040000" ATTRS{irq}=="20" ATTRS{local_cpus}=="ff" ATTRS{local_cpulist}=="0-7" ATTRS{dma_mask_bits}=="32" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{enable}=="1" ATTRS{broken_parity_status}=="0" ATTRS{msi_bus}=="" looking at parent device '/devices/pci0000:00/0000:00:1e.0': KERNELS=="0000:00:1e.0" SUBSYSTEMS=="pci" DRIVERS=="" ATTRS{vendor}=="0x8086" ATTRS{device}=="0x244e" ATTRS{subsystem_vendor}=="0x0000" ATTRS{subsystem_device}=="0x0000" ATTRS{class}=="0x060400" ATTRS{irq}=="0" ATTRS{local_cpus}=="ff" ATTRS{local_cpulist}=="0-7" ATTRS{dma_mask_bits}=="32" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{enable}=="1" ATTRS{broken_parity_status}=="0" ATTRS{msi_bus}=="1" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" None of the tags match up to any of the examples Code: KERNEL=="video[0-9]*" , ATTRS{product}=="Hauppauge HD PVR" , ATTRS{serial}=="xxxxxxxx" , NAME="v4l/video0", SYMLINK+="video0" KERNEL=="video[0-9]*" , ATTRS{product}=="Hauppauge HD PVR" , ATTRS{serial}=="yyyyyyyy" , NAME="v4l/video1", SYMLINK+="video1" How do I match up the information provided to the example? Thanks Tim |
Author: | slowtolearn [ Thu Mar 22, 2012 4:23 pm ] |
Post subject: | Re: HD-5500 - pcHDTV and WinTV-PVR-USB2 |
The idea is to pick tags that uniquely identify each card. For example, I have a PVR-150 and PVR-350 in my system: Code: udevadm info -a -p $(udevadm info -q path -n /dev/video0) ... ATTRS{vendor}=="0x4444" ATTRS{device}=="0x0016" ... and Code: udevadm info -a -p $(udevadm info -q path -n /dev/video1) ... ATTRS{vendor}=="0x4444" ATTRS{device}=="0x0803" ... So using the vendor and device tags should suffice for me (and maybe you). Admittedly I'm not sure why I don't see the same problem on my system running Mythbuntu, there is nothing in /etc/udev/rules.d for my cards. Without the serial number in the output I'm afraid you're out of luck if you have 2 or more of the same make/model in the same system, but in your case I don't think that's an issue. |
Author: | tscholl [ Fri Mar 23, 2012 5:48 pm ] |
Post subject: | Re: HD-5500 - pcHDTV and WinTV-PVR-USB2 |
I created a file in "/etc/udev/rules.d" called "10-local.rules" with the following: Code: KERNEL=="video0" , SUBSYSTEM=="video4linux" , ATTR{name}=="ivtv0 encoder MPG" , ATTRS{device}=="0x0803" So far (5 reboots) seems to be working. Tim |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |