Strange problems with USB ethernet card

[Gregory Richards]

I'm running Mandake GNU/Linux 9.2, and have a D-Link USB-H3ETX USB network 
card.  It uses the pegasus module.  For some reason, my network connection 
goes up and down.  It never did under Windows.  To display what I mean, 
here's the log of a ping:
ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=150 time=1.23 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=150 time=1.28 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=150 time=1.15 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=150 time=2.02 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=150 time=1.84 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=150 time=1.65 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=150 time=1.47 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=150 time=1.11 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.1.1: icmp_seq=15 ttl=150 time=0.940 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=150 time=1.71 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=150 time=1.78 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=150 time=1.50 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=150 time=1.34 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=150 time=2.06 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=150 time=1.84 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=150 time=1.71 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=150 time=1.42 ms
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
64 bytes from 192.168.1.1: icmp_seq=33 ttl=150 time=0.773 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=150 time=1.65 ms

--- 192.168.1.1 ping statistics ---
34 packets transmitted, 19 received, 44% packet loss, time 33186ms
rtt min/avg/max/mdev = 0.773/1.501/2.060/0.351 ms


As you can see, it goes up and down erradically.  Here's my ifconfig:
eth0      Link encap:Ethernet  HWaddr 00:50:BA:8A:94:54
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:24779 errors:0 dropped:0 overruns:0 frame:0
         TX packets:20370 errors:14390 dropped:0 overruns:0 carrier:14390
         collisions:0 txqueuelen:100
         RX bytes:5505240 (5.2 Mb)  TX bytes:2342698 (2.2 Mb)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:24987 errors:0 dropped:0 overruns:0 frame:0
         TX packets:24987 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1766076 (1.6 Mb)  TX bytes:1766076 (1.6 Mb)


I've been googling for info, but I'm not really sure what keywords to look 
for, and haven't found anything.  Does anybody have any words of wisdom to 
keep my network up?

If you need more info, what should I include?

BTW, this is with no network activity whatsoever.  I don't think that it 
goes up or down any more irregularly, however, whether there is net activity 
or not.

- Gregory Richards

Please ignore the following promotional message from Micro$oft:

_________________________________________________________________
Working moms: Find helpful tips here on managing kids, home, work ?  and 
yourself.   http://special.msn.com/msnbc/workingmom.armx

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html