On Mon, 28 Jun 2004, Tommy Faasen wrote: > I gathered all the usb devices I could find and did the following (in > this order) > connect the usb hub to the motherboard > connect the wifi stick to the hub > connect the flash drive to the hub > connect the webcam to the hub > > everything works except the wifi stick > > Output below > > uhci_hcd 0000:00:07.2: port 2 portsc 008a > hub 1-0:1.0: port 2, status 0100, change 0003, 12 Mb/s > uhci_hcd 0000:00:07.2: port 2 portsc 0088 > hub 1-0:1.0: port 2 enable change, status 00000100 > uhci_hcd 0000:00:07.2: port 2 portsc 0093 > hub 1-0:1.0: port 2, status 0101, change 0001, 12 Mb/s > hub 1-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101 > usb 1-2: new full speed USB device using address 17 > usb 1-2: new device strings: Mfr=0, Product=1, SerialNumber=0 > usb 1-2: default language 0x0409 > usb 1-2: Product: USB Hub > usb 1-2: hotplug > usb 1-2: adding 1-2:1.0 (config #1, interface 0) > usb 1-2:1.0: hotplug > hub 1-2:1.0: usb_probe_interface > hub 1-2:1.0: usb_probe_interface - got id > hub 1-2:1.0: USB hub found > hub 1-2:1.0: 4 ports detected > hub 1-2:1.0: standalone hub > hub 1-2:1.0: individual port power switching > hub 1-2:1.0: individual port over-current protection > hub 1-2:1.0: power on to power good time: 100ms > hub 1-2:1.0: hub controller current requirement: 100mA > hub 1-2:1.0: 400mA bus power budget for children > hub 1-2:1.0: local power source is lost (inactive)
I wonder how reliable that last message is. Did you have your hub plugged into an external power source (i.e., a wall socket), or was it running on power supplied by the USB bus? > hub 1-2:1.0: enabling power on all ports > hub 1-2:1.0: port 1, status 0101, change 0001, 12 Mb/s > hub 1-2:1.0: debounce: port 1: delay 100ms stable 4 status 0x101 > usb 1-2.1: new full speed USB device using address 18 > uhci_hcd 0000:00:07.2: uhci_result_control: failed with status 440000 > [dbeb6240] link (1beb61e2) element (1bea1040) > 0: [dbea1040] link (1bea1100) e0 Stalled CRC/Timeo Length=7 MaxLen=7 > DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=03c09cc8) > 1: [dbea1100] link (00000001) e3 IOC Active Length=0 MaxLen=7ff DT1 > EndPt=0 Dev=0, PID=69(IN) (buf=00000000) It sure seems like your wifi stick just doesn't like the Set-Address message. Here's a possibility: Maybe the stick takes a long time to reply to the Setup packet -- just a little too long for the UHCI controller, which reports an error. Maybe the OHCI controller is a little more lenient and accepts the late reply. Unfortunately there's no way to change how long a UHCI controller will wait for a packet reply. Alas, this is one of those things where you can't tell without a bus analyzer. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
