tx/rx woes
Allen B. Cummings
abc@sep.com
Mon Aug 3 13:19:03 1998
I was wondering if anyone could help me with a problem I've recently
encountered...
First a little background:
I was running Slackware 3.4 with kernel version 2.0.33. I've got a
vortex card (3c590) and had all of the usual networking stuff configured
and everything was running correctly. (consequently, I've had this card
working since I first installed Slackware 3.0, upgrading pretty much as
soon as new kernels or versions of Slackware came out -- never had a
problem)
Last weekend, I got my Linux Developer's Resource subscription and decided
to upgrade to Slackware 3.5. (kernel version 2.0.34) When I set up all the
networking stuff and loaded the 3c59x module, everything seemed to be
working properly but the card wasn't transmitting or receiving.
At any rate, I got the following message:
The PCI BIOS has not enabled this device! Updating PCI command 0000->0005.
eth0: 3Com 3c590 Vortex 10Mbps at 0xff80, 00:20:af:f1:45:6e, IRQ 11
32K byte-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
eth0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248.
3c59x.c:v0.99E 5/12/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
checking /proc/net/dev, I got something like this:
Inter-| Receive | Transmit
face |packets errs drop fifo frame|packets errs drop fifo colls carrier
lo: 118 0 0 0 0 118 0 0 0 0 0
eth0: 0 0 0 0 0 61 0 0 0 0 61
ppp0: 5869 0 0 0 0 6540 0 0 0 0 0
Looking at ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:118 errors:0 dropped:0 overruns:0 frame:0
TX packets:118 errors:0 dropped:0 overruns:0 carrier:0 coll:0
eth0 Link encap:Ethernet HWaddr 00:20:AF:F1:45:6E
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:61 coll:0
Interrupt:11 Base address:0xff80
...
If anyone has any thoughts on this, please let me know.
Thnaks,
Allen