Mark Howells wrote: > I'm still struggling with this stick. I have now compiled the modules > for a second P4 based system (my primary requirement is on a Arm based > system) and see identical results. I have also placed this device behing > a powered USB hub and I still get "recv bulk" errors (-71, -110, -75...) > each time I try and use it. A second attempt at tuning _always_ results > in a system freeze.So, one card, two PC's, with or without a hub and I > get reproduceable (bad) results. > > Is this likely to be a driver or hardware error? Mark, I see the same error: usb 5-7: new high speed USB device using ehci_hcd and address 14 usb 5-7: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-wt220u-zl0353-01.fw' usbcore: registered new driver dvb_usb_dtt200u usb 5-7: USB disconnect, address 14 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 5-7: new high speed USB device using ehci_hcd and address 15 usb 5-7: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (based on ZL353)). DVB: registering frontend 0 (WideView USB DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input8 dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (based on ZL353) successfully initialized and connected. dvb-usb: recv bulk message failed: -110 The thing is, this used to work. It's got broken in the course of an upgrade over the last month or two. Perhaps I should regress to an earlier kernel version? R. _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
