[pvrusb2] PVR USB2 - how to check if it's dead?
Helmut Jarausch
jarausch at skynet.be
Mon Dec 10 11:06:11 CST 2012
On 12/10/2012 05:36:30 PM, Mike Isely wrote:
>
> The "compliance tests" only tell you about the driver not the
> hardware.
> And the results you show are not surprising since the driver likely
> predates the test(s) by a long time.
>
> Probably the easiest way to quickly check the health of the hardware
> is
> to look at your kernel message log after the device is plugged into
> your
> system. If all goes well, it should be detected, loaded with firmware
> and configured to be ready for use. The fact that you have a
> /dev/video0 is fairly strong evidence that the driver thinks the
> hardware is OK. But still, a lot can be gleaned from the kernel log
> when the hardware is initialized.
>
> The 29xxx series is indeed pretty old but the pvrusb2 driver should
> still be able to handle it just fine. I don't know of any
> incompatible
> changes in V4L which might risk screwing it up.
>
> I have however seen a couple cases where the 29xxx device's USB
> interface simply fails to operate correctly against specific kernel
> versions on specific PC hardware. Yet that same exact PC
> hardware/software combination was able to operate a 24xxx device.
> I've
> never been able to track that down; it "smells" like somebody is
> violating the USB spec but if that's the case there's little I can do
> about it in the pvrusb2 driver.
>
> If you'd like, I can this weekend set up a test on the latest kernel
> with one of my 29xxx devices here. I have no reason to suspect any
> trouble, but it has been a while...
>
Thanks Mike!
Here is the part of dmesg after connecting the device,
hopefully it tells you something.
[13227.695126] usb 2-3: new high-speed USB device number 5 using
ehci_hcd
[13227.810635] usb 2-3: New USB device found, idVendor=2040,
idProduct=2900
[13227.810643] usb 2-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[13227.810648] usb 2-3: Product: USB Device
[13227.810652] usb 2-3: Manufacturer: Hauppauge
[13227.811088] pvrusb2: Hardware description: WinTV PVR USB2 Model 29xxx
[13227.813065] pvrusb2: Binding ir_video to i2c address 0x18.
[13227.846690] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42
(pvrusb2_a)
[13227.998182] pvrusb2: Attached sub-driver saa7115
[13228.013624] msp3400 0-0040: MSP3415G-B8 found @ 0x80 (pvrusb2_a)
[13228.013629] msp3400 0-0040: msp3400 supports nicam and radio, mode
is autodetect and autoselect
[13228.013708] pvrusb2: Attached sub-driver msp3400
[13228.050014] tuner 0-0061: Tuner -1 found with type(s) Radio TV.
[13228.050029] pvrusb2: Attached sub-driver tuner
[13228.059046] tda9887 0-0043: creating new instance
[13228.059050] tda9887 0-0043: tda988[5/6/7] found
[13228.060160] tuner 0-0043: Tuner 74 found with type(s) Radio TV.
[13228.060177] pvrusb2: Attached sub-driver tuner
[13228.082631] tveeprom 0-0050: Hauppauge model 29039, rev D160,
serial# 8039400
[13228.082638] tveeprom 0-0050: tuner model is LG S001D MK3 (idx 60,
type 38)
[13228.082643] tveeprom 0-0050: TV standards PAL(B/G) PAL(I)
SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
[13228.082646] tveeprom 0-0050: audio processor is MSP3415 (idx 6)
[13228.082650] tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
[13228.082653] tveeprom 0-0050: has radio, has IR receiver, has no IR
transmitter
[13228.082665] pvrusb2: Supported video standard(s) reported available
in hardware: PAL-B/B1/D/D1/G/H/I/K;SECAM-B/D/G/H/K/K
[13228.082685] pvrusb2: Device initialization completed successfully.
[13228.082805] pvrusb2: registered device video0 [mpeg]
[13228.360466] tuner-simple 0-0061: creating new instance
[13228.360474] tuner-simple 0-0061: type set to 38 (Philips PAL/SECAM
multi (FM1216ME MK3))
[13228.502504] pvrusb2: registered device radio0 [mpeg]
More information about the pvrusb2
mailing list