On Fri, 27 Jul 2007, Olaf G. wrote: > I'm having problems with a Hauppauge Nova-T USB 2.0 stick on an SIS USB > Hostcontroller (Asus Pundit barebone): > Loading the module ehci_hcd with the stick plugged in leads to failures when > the stick has not yet been initialized: > > [...] > usb 1-1: new high speed USB device using ehci_hcd and address 3 > usb 1-1: khubd timed out on ep0in len=0/8 > usb 1-1: device descriptor read/8, error -110 > usb 1-1: khubd timed out on ep0in len=0/8 > usb 1-1: device descriptor read/8, error -110 > [...] > > When I unplug the stick and replug it AFTER the ehci_hcd is loaded everything > is fine - the stick is detected in "cold state", the firmware is load up and > everything works fine. > When I unload ehci_hcd after the stick has been initialized and reload > ehci_hcd again the stick is identified correctly and works fine. > When I unload ehci_hcd (not usbcore!), replug the stick and reload ehci_hcd > the stick is uninitialized again and I've got the error messages again! > > I tried several kernel versions (at the moment I'm using 2.6.21.1) with > several boot/module options (acpi=off, noapic, usbcore: > use_old_scheme_first=y) and the different USB slots but I always get the same > behavior. > When I try a different USB Controller (PCMCIA USB controller) everything > works > fine, so its not a general problem with the stick!
Actually it is. Apparently the stick won't work unless it receives some particular combination of signals and power on the USB lines. The PCMCIA controller provides what it wants and the EHCI controller doesn't -- at least, it doesn't until ehci-hcd is loaded and by then the stick has already "given up". But the problem still lies in the stick. Once the driver is loaded and the USB lines provide the correct signals, it ought to work -- even if it was getting the wrong signals before. It should never "give up". > But for optical reasons using the PCMCIA USB controller is no option for me. > And there are no free PCI slots - I cannot connect a PCI controller :( > Since I use this PC as a VCR it would be nice if I hadn't to replug the stick > manually after every reboot ;) > > > One more thing to mention: when ohci_hcd is loaded I get the same problems - > but this time from ohci_hcd. Replugging the stick leads to a correct > identification but the the ohci driver complains that this is  a USB 2.0 > only > device. There's no such thing. According to the spec, every USB 2.0 device is required to be compatible with a USB 1.1 host. It isn't required to provide full functionality -- but ohci-hcd won't complain if it sees a USB 2.0 device. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
