[tulip] anyone get danpex afp1100 to do fdx?
Leo Wierzbowski
leow@ufl.edu
Fri, 23 Mar 2001 08:25:32 -0500
Donald Becker wrote:
>
> On Mon, 19 Mar 2001, Leo Wierzbowski wrote:
>
> [[ My apologies if this arrives late -- I'm at Linux World Expo in
> Singapore and I'm not certain when this message will leave my laptop. ]]
>
> > If you've gotten the Danpex AFP1100 NIC to do full duplex, please let me
> > know how. I'm using tulip v0.92 and no matter what option mix I
> > specify, the card only does 100Mbs HDX (options 0, with or without 0x200
> > added, with or without full_duplex=1 specified) or 10mbps-serial (any
> > other options, including ones that specify 100Mbs).
>
> Normally I would say that this is impossible. The full duplex flag
> should always override the media table.
So normally, would the following set two NICs to FDX?
insmod tulip.o full_duplex=1,1
I have two NICs in this Linux 2.2.18 box. The older model is eth0, the
newer eth1. With both of my NICs, the above results in MII HDX.
The older model will go into FDX only with an MII media type specified
in options (11 or 13) along with the full_duplex=1 flag. This older
model will also do so with options 0x20b and no full_duplex flag.
After many reboots I've discovered that the newer model will sometimes
go into FDX with options 0x20b. When it does so, tulip identifies the
NIC similarly as the old model (Media MII described by a 21142). When
it doesn't, the message below appears, and this is the normal case for
0x20b (and is always the case when I specify the MII media type or try
any other combo of anything):
> > Tulip reports on boot up:
> >
> > Index #0 - Media MII 100baseTx (#13) described by a 21140 non-MII (0) block.
>
> Ohhhh, that's bad. That appears to be an invalid media table entry.
> Please send the output of 'tulip-diag -ee' so that we can see the raw
> entry.
I can get different results on the NICs (MII HDX, 10mbs-serial FDX, when
lucky MII FDX on the new model) depending on the module options that I
specify. Which options would be the most helpful, or does it not make
any difference at this stage?
The below tulip-diag output is after booting with the following tulip
options. I've included both NICs for comparison:
options=11,11 full_duplex=1,1
# tulip-diag -ee
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0xe880.
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.
The NWay status register is 000000c6.
EEPROM 64 words, 6 address bits.
PCI Subsystem IDs, vendor 0000, device 0000.
CardBus Information Structure at offset 00000000.
Ethernet MAC Station Address 00:40:C7:A9:0F:10.
EEPROM transceiver/media description table.
Leaf node at offset 30, default media type 000d (MII 100baseTx).
1 transceiver description blocks:
Media MII, block type 3, length 13.
MII interface PHY 0 (media type 11).
21143 MII initialization sequence is 0 words:.
21143 MII reset sequence is 0 words:.
Media capabilities are 6000, advertising 0181.
Full-duplex map 4000, Threshold map 0000.
No MII interrupt.
EEPROM contents (64 words):
0x00: 0000 0000 0000 0000 0000 0000 0000 0000
0x08: 0000 0104 4000 a9c7 100f 1e00 0000 000d
0x10: 8d01 0003 0000 6000 0180 4000 0000 0000
0x18: 0000 0000 0000 0000 0000 0000 0000 0000
0x20: 0000 0000 0000 0000 0000 0000 0000 0000
0x28: 0000 0000 0000 0000 0000 0000 0000 0000
0x30: 0000 0000 0000 0000 0000 0000 0000 0000
0x38: 0000 0000 0000 0000 0000 0000 0000 01fd
ID block CRC 0xe3 (vs. 00).
Full contents CRC 0x01fd (read as 0x01fd).
MII PHY found at address 1, status 0x782d.
MII PHY #1 transceiver registers:
3100 782d 0302 d008 01e0 0080 0004 2801
0000 0000 0000 0000 0000 0000 0000 0000
0000 0001 0000 0000 0000 0912 0000 8062
2000 0421 0000 0000 0039 0000 0000 0000.
Internal autonegotiation state is 'Autonegotiation disabled'.
Index #2: Found a Digital DS21143 Tulip adapter at 0xe800.
Port selection is 10mpbs-serial, 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 72.
The NWay status register is 000000c6.
EEPROM 64 words, 6 address bits.
PCI Subsystem IDs, vendor 146c, device 1430.
CardBus Information Structure at offset 00000000.
Ethernet MAC Station Address 00:40:C7:AA:02:D7.
EEPROM transceiver/media description table.
Leaf node at offset 30, default media type ffff8800 (Autosense).
1 transceiver description blocks:
Media MII, block type 3, length 13.
MII interface PHY 0 (media type 11).
21143 MII initialization sequence is 0 words:.
21143 MII reset sequence is 0 words:.
Media capabilities are 6000, advertising 0181.
Full-duplex map 4000, Threshold map 0000.
MII interrupt on GPIO pin -1.
EEPROM contents (64 words):
0x00: 146c 1430 0000 0000 0000 0000 0000 0200
0x08: 48fd 0104 4000 aac7 d702 1e00 0000 8800
0x10: 8d01 0003 0000 6000 0180 4000 0000 0080
0x18: 0000 0000 0000 0000 0000 0000 0000 0000
0x20: 0000 0000 0000 0000 0000 0000 0000 0000
0x28: 0000 0000 0000 0000 0000 0000 0000 e151
0x30: 0000 0000 0000 4000 aac7 d702 0040 0000
0x38: 0000 0000 0000 0000 0000 0000 0000 000f
ID block CRC 0xfd (vs. 0xfd).
Full contents CRC 0xdc17 (read as 0x000f).
MII PHY found at address 1, status 0x782d.
MII PHY #1 transceiver registers:
3100 782d 0302 d008 01e0 0080 0004 2801
0000 0000 0000 0000 0000 0000 0000 0000
0000 0001 0000 0000 0000 a946 0000 8062
2000 0421 0000 0000 0039 0000 0000 0000.
Internal autonegotiation state is 'Autonegotiation disabled'.
Below is the /var/log/syslog output of tulip at bootup:
Mar 23 12:49:45 gatorouter kernel: tulip.c:v0.92 4/17/2000 Written by
Donald Becker <becker@scyld.com>
Mar 23 12:49:45 gatorouter kernel:
http://www.scyld.com/network/tulip.html
Mar 23 12:49:45 gatorouter kernel: eth0: Digital DS21143 Tulip rev 65 at
0xc4863c00, 00:40:C7:A9:0F:10, IRQ 10.
Mar 23 12:49:45 gatorouter kernel: eth0: EEPROM default media type MII
100baseTx.
Mar 23 12:49:45 gatorouter kernel: eth0: Index #0 - Media MII (#11)
described by a 21142 MII PHY (3) block.
Mar 23 12:49:45 gatorouter kernel: eth0: MII transceiver #1 config 3100
status 782d advertising 0181.
Mar 23 12:49:45 gatorouter kernel: eth0: Advertising 03e0 on PHY 1,
previously advertising 0181.
Mar 23 12:49:45 gatorouter kernel: eth1: Digital DS21143 Tulip rev 65 at
0xc4865800, 00:40:C7:AA:02:57, IRQ 11.
Mar 23 12:49:45 gatorouter kernel: eth1: EEPROM default media type
Autosense.
Mar 23 12:49:45 gatorouter kernel: eth1: Index #0 - Media MII 100baseTx
(#13) described by a 21140 non-MII (0) block.
Mar 23 12:49:45 gatorouter kernel: eth1: MII transceiver #1 config 3100
status 782d advertising 01e0.
Mar 23 12:49:45 gatorouter kernel: eth1: Advertising 03e0 on PHY 1,
previously advertising 01e0.
Mar 23 12:49:45 gatorouter kernel: br: enabling bridging function
Mar 23 12:49:45 gatorouter kernel: br: enabling port 1
Mar 23 12:49:45 gatorouter kernel: device eth0 entered promiscuous mode
Mar 23 12:49:45 gatorouter kernel: eth0: Using user-specified media MII.
Mar 23 12:49:45 gatorouter kernel: eth0: Promiscuous mode enabled.
Mar 23 12:49:45 gatorouter last message repeated 3 times
Mar 23 12:49:45 gatorouter kernel: br: enabling port 2
Mar 23 12:49:45 gatorouter kernel: device eth1 entered promiscuous mode
Mar 23 12:49:45 gatorouter kernel: eth1: Promiscuous mode enabled.
Mar 23 12:49:45 gatorouter last message repeated 3 times
Thanks for taking a look at this. I appreciate it very much.
--
Sincerely,
Leo Wierzbowski
"The University of Florida does not endorse or disendorse the
content of this document. It is the author's private opinion."
"Take heed therefore that the light which is in thee be not darkness."
(Luke 11:35)