[mythtv-users] Did Hauppauge replace one bad HD-PVR with another?

[John P Poet]

On Fri, Apr 29, 2011 at 9:50 PM, Christopher Meredith
<chmeredith at gmail.com> wrote:
> Had an HD-PVR for almost 2 years when suddenly the component
> passthrough stopped working, the device started throwing USB errors in
> dmesg, and the system no longer recognized it as an hdpvr. I tried
> several USB cables and two different computers, same result. So I
> RMA'ed it, and Hauppauge sent me a new box, an F2 revision. But this
> one is doing the exact same thing (though component passthrough works
> fine). I connected it to a Windows machine and successfully updated
> the driver to the latest one from the website. But whenever I plug it
> into a Linux box, this is what I get:
>
> [555704.191537] usb 4-4: new full speed USB device using ohci_hcd and address 6
> [555704.371692] usb 4-4: device descriptor read/64, error -62
> [555704.670027] usb 4-4: device descriptor read/64, error -62
> [555704.950860] usb 4-4: new full speed USB device using ohci_hcd and address 7
> [555705.132295] usb 4-4: device descriptor read/64, error -62
> [555705.420891] usb 4-4: device descriptor read/64, error -62
> [555705.710873] usb 4-4: new full speed USB device using ohci_hcd and address 8
> [555706.132254] usb 4-4: device not accepting address 8, error -62
> [555706.310874] usb 4-4: new full speed USB device using ohci_hcd and address 9
> [555706.740863] usb 4-4: device not accepting address 9, error -62
> [555706.740884] hub 4-0:1.0: unable to enumerate USB device on port 4
> [555710.590913] usb 2-4: new high speed USB device using ehci_hcd and address 5
>
> Did they send me another dud? What's up?

I remember some people talking about having to manually add new device
IDs to the driver, so it would recognize newer-model HD-PVRs.  That
may be your problem.


John
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?