[tulip] netgear's fa310-tx and d-link switch
Jaap Brink
brink@tiger.3dem.bioch.bcm.tmc.edu
Sun, 10 Dec 2000 16:53:49 -0600 (CST)
Dear Karl (and others reading this):
I've done some more checking and am still very confused. But, I tried to
do my homework, so here's the wrap on the story. My linux box masquarades
for my home network. It has a cheetah (rtl8193) and netgear (tulip).
Heres the info from the boot detection:
> eth0: Lite-On 82c168 PNIC rev 32 at 0xf800, 00:A0:CC:65:B9:99, IRQ 11.
> eth0: MII transceiver #1 config 3000 status 782d advertising 01e1.
Plugged this nic into a 10/100 switch (dlink dss8+) and verified that both
nic and switch are in full-duplex. Here's what tulip-diag and mii-diag
report:
host>./tulip-diag
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 0xf800.
Lite-On 82c168 PNIC chip registers at 0xf800:
00008000 01ff0000 00000000 00951810 00951a10 02000112 814c0200 00000000
00000000 00000000 00951ac0 01200a30 00000020 00000000 00000000 10000001
00000000 00000000 f0041385 000000bf 6086782d 00951810 00838010 0201f178
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Port selection is MII, full-duplex.
Transmit stopped, Receive stopped, full-duplex.
The Rx process state is 'Stopped'.
The Tx process state is 'Stopped'.
The transmit threshold is 72.
host>./mi-diag
Basic registers of MII PHY #1: 3000 782d 0040 6212 01e1 45e1 0003 0000.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT, w/ 802.3X flow control.
Problem was that this linux box couldn't see the home network. It could
still see the cable connection. So, I thought perhaps the nic in one of
the machine it failed to see was in half-duplex? Well, this is what
rtl8139-diag reported:
host>./rtl8139-diag
rtl8139-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a SMC1211TX EZCard 10/100 (RealTek RTL8139) adapter at
0xcc00.
The RealTek chip appears to be active, so some registers will not be read.
To see all register values use the '-f' flag.
RealTek chip registers at 0xcc00
0x000: 06b51000 0000a7f7 00000000 00000000 00002000 00002000 00002000
00002000
0x020: 06896000 06896600 06896c00 06897200 06780000 0d000000 0000fff0
0000c07f
0x040: 73000400 00009c0e ec78f23d 00000000 006c1000 00000000 0000c180
00100000
0x060: 1100000f 05e1782d 000145e1 00000001 00000004 000307c8 78fa8388
a538de43.
No interrupt sources are pending.
The chip configuration is 0x10 0x6c, MII full-duplex mode.
EEPROM size test returned 6, 0x204a4 / 0x2.
As you can see, both ends of the chain are in full-duplex. I've tried
several different nics in my linux box, plus different cable
runs. Everything to no avail. Could it be that the switch not in full
duplex? Seems to make little sense to me, but nothing right now has ;-)
Jaap
On Sat, 9 Dec 2000, Karl Hammar wrote:
>
> You might face the situation that the nic is using half-duplex, and the
> switch full-duplex.
> Check with tulip-diag or mii-diag:
>
> # ~karl/hw/tulip/tulip-diag -a
> tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a Lite-On 82c168 PNIC adapter at 0xc400.
> * 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.
> # ~karl/hw/tulip/diag/mii-diag
> Using the default interface 'eth0'.
> Basic registers of MII PHY #1: 3100 782d 0302 d008 01e1 45e1 0005 2001.
> Basic mode control register 0x3100: Auto-negotiation enabled.
> You have link beat, and everything is working OK.
> Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
>
> Regards,
> /Karl
>
> -----------------------------------------------------------------------
> Karl Hammar Aspö Data karl@kalle.csb.ki.se
> Lilla Aspö 2340 +46 173 140 57 Networks
> S-742 94 Östhammar +46 70 511 97 84 Computers
> Sweden Consulting
> -----------------------------------------------------------------------
>
> From: Jaap Brink <brink@tiger.3dem.bioch.bcm.tmc.edu>
> Subject: [tulip] netgear's fa310-tx and d-link switch
> Date: Fri, 8 Dec 2000 00:26:36 -0600 (CST)
>
> >
> > Hi people,
> >
> > I've been using a 10-baseT hub on my LAN which has a box with masquarading
> > linux distro (rh 6.0 with 2.2.16-3 kernel) and 2 nic's. They're Netgear's
> > FA310-TX and an Accton Cheetah, i.e. the distro is using the tulip and
> > rtl8139 drivers. Now, on this LAN everything's fine. Tonight, I plopped in
> > a D-link DSS8+ switch instead of mu trusty hub, I did a 'ifdown eth0'
> > followed by an 'ifup eth0' on all appropriate machines and verified that
> > on the switch I only see 100BaseT and full-duplex lights that are on. The
> > problem I'm having is that all of the machines behind the linux box can
> > see each other. None of them can see the linux box directly. Ping packets
> > seem to drop on the floor. Using other ports on the switch seemed to
> > indicate that the switch itself was fine. So, I'm having a hard time
> > understanding that there's actually a problem at all. I've looked around
> > if others have reported similar problems but I haven't seen anything. Can
> > somebody help out? Much appreciated.
> >
> > Jaap
> ...
>
> _______________________________________________
> tulip mailing list
> tulip@scyld.com
> http://www.scyld.com/mailman/listinfo/tulip
>
--
--
Jaap Brink, Ph.D., Biochemistry, One Baylor Plaza, Baylor College of
Medicine, Rm. N420 Alkek Building, Houston, TX 77030
Phone: (713)798-6989 -- Fax: (713)796-9438 -- Email: jbrink@bcm.tmc.edu
URL : http://ncmi.bioch.bcm.tmc.edu/~brink