On Wed, 16 Jul 2003 abower@thebowery.co.uk wrote:
have you considered using a 2.4 series kernel? usb networking has recently had some updates in the 2.4 series.
OK. I'm now the proud owner of a machine running kernel 2.4.18 through loadlin 1.6c.
Also what does the command ifconfig -a say when you have the module loaded? that should give you the device name.
Looks like it. The relevant bit of the output seems to be
usb0 Link encap:Ethernet HWaddr 7A:37:C8:F1:F9:5A BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Therefore, I tried
ifconfig usb0 192.168.0.1 pointopoint 192.168.0.2
which resulted in the error message
SIOCSIFFLAGS: Broken pipe
This appears to be a known issue. Someone anonymous says "I think the root cause of the problem is flakey hardware from Prolific." http://www.geocrawler.com/mail/msg.php3?msg_id=8713512&list=4563, and the general opinion in the linux-usb-users list seems to be that the best solution is to get a different cable. Anyone have other ideas?