Peter Van Lone wrote:
cvl:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:08:A1:23:26:6E inet addr:192.168.2.198 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::208:a1ff:fe23:266e/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:399 errors:2406 dropped:0 overruns:0 frame:0 TX packets:7 errors:12 dropped:0 overruns:0 carrier:12 collisions:0 txqueuelen:1000 RX bytes:44957 (43.9 Kb) TX bytes:735 (735.0 b) Interrupt:9 Base address:0xd800
Looks good except for the many errors.
no that would be the ip address it had at the time. And then I looked later, and no ip address showed up ... so I did an ipconfig eth0 down, and then ifconfig eth0 up --- to no avail. Still showing no IP addr for eth0. So, I manually added the IP address you see above .. and the gateway and dns servers and subnet addr ... and I can now ping loopback, but cannot ping the df gateway or anything beyond. And another device on the network cannot ping this machine.
dmesg is filled to the brim with the tulip_stop_rxtx( ) failed messages
That seems to be the problem after all. Try googling for tulip_stop_rxtx - you'll get quite a few hits. I can't quite see if a problem has been fixed, but it might be worth updating your kernel to the most recent kernel-of-the-day (YOU). Per