Hi Dave,
I bought a GeneSys Logic based cable and it is working fine. Thanks. It seems usbnet is not very happy with the Prolific chips, or viceversa. Incidentally, the packet loss percentage is actually rather hight (70 - 80%). Is that normal in USB-to-USB networks? thanks again Jaime 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! > > > 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. 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.) > > 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. > > - Dave > > _______________________________________________________________ > > 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 -- Dr Jaime V. Miro Sw and control systems analyst H2eye Ltd 24-28 Hatton Wall London EC1N 8JH Tel:020-7404 9600 Fax:020-7404 9490 [EMAIL PROTECTED] Copyright � H2Eye International Ltd. 2000/2001. All rights reserved. _______________________________________________________________ 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
