Hi David,
David Brownell wrote: > > > Date: Mon, 20 May 2002 14:00:39 +0100 > > From: "Dr Jaime V. Miro" <[EMAIL PROTECTED]> > > > > When I boot up, it works fine. dmesg throws (on both machines) > > > > usb0: register usbnet 001/002, Prolific\PL-2301/PL-2302. > > So far so good, though I don't know where that backslash came > from! from a cut and paste line too long :-) > > however, if I try and configure the actual net address by running > > ifconfig usb0 10.0.0.1 up > > (and ifconfig usb0 10.0.0.2 up in the other machine) > > > > I get the following error: > > SIOCSIFFLAGS: Broken Pipe > > > > This is what /var/log/messages says: > > > > usb0: open reset fail (-32) usbnet 001/002, Prolific PL2301/PL-2302 > > Basically "-EPIPE" (-32) means the device stalled, so the > handshake protocol specified by Prolific didn't work on that > device. > > > And network does not work (ping says network unreachable). I think I > > must be doing something wrong, because it is exactly the same symptoms > > in both machines, but I do not what. Any ideas? > > I think the root cause of the problem is flakey hardware from Prolific. > > Some devices seem to fail the reset consistently, others succeed just > as often, but I don't think I've ever seen any of their PL-2301/2302 > devices acting like their chip spec says they'll act. Prolific also > has not responded to any of numerous requests for information, so it's > not clear that these problems could be resolved. I've been thinking > of making that particular "minidriver" be the only one in "usbnet" that's > labeled as "experimental". > > Some folk have reported success if they just comment out the "reset" > entry in the "prolific_info" struct. I'll try that. > You might have a revision of > their hardware for which that's an appropriate workaround. (Could > you send me the /proc/bus/usb/devices info for your device? It's > barely possible that they changed the revision info in their hardware > so that such a workaround could be automated.) (both host controller and prolific devices:) T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 0.00 S: Product=USB UHCI-alt Root Hub S: SerialNumber=6400 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=067b ProdID=0001 Rev= 0.00 S: Manufacturer=Prolific Technology Inc. C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbnet E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl= 1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms > An even better solution is to avoid those Prolific cables; that might > be a bit tricky since they're so widely available (cheap in all senses > of the word). I've never heard problem reports from users of Belkin, > ETek, Anchorchips, NetChip, Laplink, and so forth ... only Prolific. > Yep, it looks like the best option. thanks very much for your help. Jaime _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
