On 3/26/08, Philip Pemberton <lists@xxxxxxxxxxxxx> wrote: > David Harvey wrote: > > MT2060: successfully identified (IF1 = 1220) > > [ 589.459712] input: IR-receiver inside an USB DVB receiver as > > /devices/pci0000:00/0000:00:13.2/usb3/3-8/input/input16 > > [ 589.470534] dvb-usb: schedule remote query interval to 150 msecs. > > [ 589.470540] dvb-usb: Hauppauge Nova-T Stick successfully initialized > > and connected. > > [ 606.300175] hub 3-0:1.0: port 8 disabled by hub (EMI?), re-enabling... > > [ 606.300181] usb 3-8: USB disconnect, address 11 > > [ 606.312990] mt2060 I2C write failed > > [ 608.563167] mt2060 I2C write failed > > [ 608.563243] mt2060 I2C write failed (len=2) > > [ 608.563246] mt2060 I2C write failed (len=6) > > ... > > Here's your problem: > > > 00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) > ... > > 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller > > 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller > > 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host > Controller > > USB2 on ATI chipsets is hopelessly, horrendously broken. A Cardbus USB2 card > (or in the case of a desktop, a PCI USB2 card) should fix this -- the NEC > chipset based boards are (from what I've heard) the best of the bunch, but > VIA > based boards aren't (too) bad. > it would be interesting to know what's wrong, especially since other usb 2.0 based devices work properly with those chipset (ATI, VIA, etc). Any idea if it is a current or protocol based problem? Aren't there similar devices from dibcom available which do not have that problem? If that's the case what's so different with the WinTV series? Hope someone can answer at least a few questions :) thanks, Markus _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
