On Sat, 10 Sep 2005, Giridhar Pemmasani wrote: > I am trying to get Netgear MA111v2 wireless USB card which uses SIS163u > chipset to work with ndiswrapper (tt doesn't have a native driver or > specs). After much reworking of USB layer
What did you do to the USB layer? > and other support added for it in > ndiswrapper, the device seems to initialize partially (shows proper MAC > address etc.). However, after exchanging lot of URBs, the device seems to > have died. Close inspection reveals that when reading a URB it fails with > EILSEQ. At that time, I see following message from kernel: > > [ 1794.952000] uhci_hcd 0000:00:1d.1: uhci_result_control: failed with > status 440000 > [ 1794.952000] [d44121a0] link (14412142) element (1107b140) > [ 1794.952000] Element != First TD > [ 1794.952000] 0: [d107b0c0] link (1107b100) e3 Length=7 MaxLen=7 DT0 > EndPt=0 Dev=3, PID=2d(SETUP) (buf=122638e0) > [ 1794.952000] 1: [d107b100] link (1107b140) e3 Length=3 MaxLen=3 DT1 > EndPt=0 Dev=3, PID=e1(OUT) (buf=1fa57cd0) > [ 1794.952000] 2: [d107b140] link (00000001) e0 IOC Stalled CRC/Timeo > Length=7ff MaxLen=7ff DT1 EndPt=0 Dev=3, PID=69(IN) (buf=00000000) > [ 1794.952000] These messages mean that the device did not respond to a 4-byte control-OUT URB. For an explanation of the error codes, read Documentation/usb/error-codes.txt. > After that a few more (4 or 5) URBs fail with the same error then the rest > fail with EPROTO error, at which time I get following message from kernel: > > [ 1795.004000] uhci_hcd 0000:00:1d.1: uhci_result_control: failed with > status 440000 > [ 1795.004000] [d44121a0] link (14412142) element (1107b980) > [ 1795.004000] 0: [d107b980] link (1107b9c0) e0 Stalled CRC/Timeo Length=7 > MaxLen=7 DT0 EndPt=0 Dev=3, PID=2d(SETUP) (buf=128bd880) > [ 1795.004000] 1: [d107b9c0] link (1107ba00) e3 SPD Active Length=0 > MaxLen=3DT1 EndPt=0 Dev=3, PID=69(IN) (buf=12fd9f58) > [ 1795.004000] 2: [d107ba00] link (00000001) e3 IOC Active Length=0 > MaxLen=7ff DT1 EndPt=0 Dev=3, PID=e1(OUT) (buf=00000000) These means that the device did not respond to a control-IN URB. In fact, from your description it sounds like the device has stopped responding almost entirely. > When I plugin the device with both ehci-hcd and uhci-hcd are loaded, I get > the following messages: > > [ 1793.224000] hub 4-0:1.0: state 5 ports 6 chg 0000 evt 0008 > [ 1793.224000] ehci_hcd 0000:00:1d.7: GetStatus port 3 status 001803 POWER > sig=j CSC CONNECT > [ 1793.224000] hub 4-0:1.0: port 3, status 0501, change 0001, 480 Mb/s > [ 1793.352000] hub 4-0:1.0: debounce: port 3: total 100ms stable 100ms > status 0x501 > [ 1793.408000] ehci_hcd 0000:00:1d.7: port 3 full speed --> companion > [ 1793.408000] ehci_hcd 0000:00:1d.7: GetStatus port 3 status 003801 POWER > OWNER sig=j CONNECT > [ 1793.408000] uhci_hcd 0000:00:1d.1: wakeup_rh (auto-start) > [ 1793.408000] hub 4-0:1.0: port_wait_reset: err = -107 > [ 1793.408000] hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0002 > [ 1793.408000] uhci_hcd 0000:00:1d.1: port 1 portsc 0093,00 > [ 1793.408000] hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s > [ 1793.536000] hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms > status 0x101 > [ 1793.608000] usb 2-1: new full speed USB device using uhci_hcd and address > 3 > [ 1793.700000] usb 2-1: new device strings: Mfr=0, Product=0, SerialNumber=0 > [ 1793.700000] usb 2-1: hotplug > [ 1793.704000] usb 2-1: adding 2-1:1.0 (config #1, interface 0) > [ 1793.704000] usb 2-1:1.0: hotplug Those are all perfectly normal. > I have played with use_both_schemes and old_scheme_first options with the > same effect. When ehci-hcd is not loaded, I don't get the initialization > errors, but submitting URBs result with the same errors. > > Although the device driver binary (Windows driver), I can provide dump of > any URBs that are received from/sent to the driver with ndiswrapper. If you > need any further info, please let me know. This looks like a hardware problem either in the device or in your computer's USB controller. On the other hand, it's always possible that your computer is sending an URB that the device doesn't understand, causing it to crash. One way or another, the USB packets aren't going back and forth correctly. Alan Stern ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
