[tulip] Netgear FA310TX problem
David Winter
winter@nevis1.nevis.columbia.edu
Fri, 20 Oct 2000 13:01:53 -0400
i am guessing the error message you get from ping probably indicates a network
config problem in contrast to a driver/hardware problem...
This may be a silly question, but have you tried configuring eth0 thru the
control-panel interface? i am not familiar with the rh 7.0 dist, but at least
in 6.2 they still supplied the stripped-down yet easy to use control-panel
tcl/tk script. my experience has been that i have rarely been successful
trying to configure the interfaces manually, yet have had almost 100% success
with the tools that redhat supplies. another nice thing is that if you do use
control-panel (i guess linuxconf or netconf could be used also) you can test
the config with a simple "/etc/rc.d/init.d/network start".
another output you may want to post is that of "/sbin/route -n". this may
reveal routes that are missing.
dave
p.s. gong -- how's it going? i was wondering if you were the same guy i knew
from columbia...
On Fri, 20 Oct 2000, Paul Bombach wrote:
> I've tried a couple of things to get this network card going including
> running tulip-diag -r (Thanks John Hinks for the suggestion), but it is
> still having problems. I deleted the /sbin/route add 192.168.1.0 command. I
> issued the following commands to initialize my network.
>
> /sbin/ifconfig eth0 192.168.1.50 netmask 255.255.255.0 broadcast
> 192.168.1.255
> /sbin/route add default gw 192.168.1.1
>
> That seemed to work fine, so I tried to ping my router and got the following
> error:
>
> PING 192.168.1.1 (192.168.1.1) from 192.168.1.50 : 56(84) bytes of data.
> From 192.168.1.50: Destination Host Unreachable
>
> When I cat'ed the contents of /proc/arp, I got the following suprising
> results
>
> IP address HW type Flags HW address Mask
> Device
> 192.168.1.1 0x1 0x0 00:00:00:00:00:00 *
> eth0
>
> The last thing I did was to run tulip-diag. Unfortunately, I don't know how
> to interpret the output. Any help in diagnosing this problem would be
> greatly appreciated.
>
> The output of various tulip-diag commands is:
>
> tulip-diag -aa
>
> tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a Lite-On 82c168 PNIC adapter at 0xfc00.
> * A potential Tulip chip has been found, but it appears to be active.
> * Either shutdown the network, or use the '-f' flag to see all values.
> Port selection is MII, full-duplex.
> Transmit started, Receive started, full-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit threshold is 128.
>
> tulip-diag -ee
>
> tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a Lite-On 82c168 PNIC adapter at 0xfc00.
> Port selection is MII, full-duplex.
> Transmit started, Receive started, full-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit threshold is 128.
> A simplifed EEPROM data table was found.
> The EEPROM does not contain transceiver control information.
> EEPROM contents:
> 00a0 cc58 b627 f004 1385 00f1 0000 a8cc
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> ID block CRC 0xd2 (vs. 00).
> Full contents CRC 0x7c16 (read as 0x0000).
>
> tulip-diag -mm
>
> tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a Lite-On 82c168 PNIC adapter at 0xfc00.
> Port selection is MII, full-duplex.
> Transmit started, Receive started, full-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit threshold is 128.
> MII PHY found at address 1, status 0x782d.
> MII PHY #1 transceiver registers:
> 3000 782d 0040 6212 01e1 41e1 0003 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 5000 0300 0000 0000 0000 013e 0400 0000
> 003f 853e 0f00 ff00 002f 4000 80a0 000b.
> Basic mode control register 0x3000: Auto-negotiation enabled.
> Basic mode status register 0x782d ... 782d.
> Link status: established.
> Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
> Able to perform Auto-negotiation, negotiation complete.
> Vendor ID is 00:10:18:--:--:--, model 33 rev. 2.
> No specific information is known about this transceiver type.
> I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
> Advertising no additional info pages.
> IEEE 802.3 CSMA/CD protocol.
> Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD
> 10baseT.
> Negotiation completed.
>
>
> _______________________________________________
> tulip mailing list
> tulip@scyld.com
> http://www.scyld.com/mailman/listinfo/tulip
>
========================================================================
David L. Winter, Capt. USAF winter@alum.mit.edu
------------------------------------------------------------------------
Columbia University Nevis Laboratories AFRL/Rome Research Site
City of New York Irvington, NY Rome, NY
Phone: 212-854-4653 Phone: 914-591-2836 Phone: 315-330-3143
Fax: 212-854-3379 Fax: 914-591-8120 Fax: 315-330-7901
WWW: http://www.nevis.columbia.edu/~winter
Experiment 910 at the AGS: "Searching for a strange particle in an
even stranger land."
========================================================================