DFE-570TX (21143) won't do 10BaseT w/10bT hub
Jarlath Burke
jburke@asitatech.ie
Thu Jul 15 05:12:56 1999
Craig,
I've seen that problem before as well. The reason I was having that problem
was because I hadn't compiled the driver with the correct command line
options as seen at the end of the file.
Try compiling with these options:
gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -c tulip.c `[ -f
/usr/include/linux/modversions.h ] && echo -DMODVERSIONS`
Jarlath.
-----Original Message-----
From: Craig Metz <cmetz@inner.net>
To: linux-tulip@cesdis1.gsfc.nasa.gov <linux-tulip@cesdis1.gsfc.nasa.gov>
Date: Thu Jul 15 05:12:56 1999
Subject: DFE-570TX (21143) won't do 10BaseT w/10bT hub
>
> I have a DFE-570TX quad-21143 board, which several people seem to be
having
>trouble with, and a Boca 10BaseT hub. Under BSD/OS, OpenBSD, NetBSD, and
>FreeBSD, the board will correctly autodetect that it's running 10BaseT and
>works fine, so there's no reason it can't work. Under Linux, with both the
>tulip and the de4x5 drivers, it doesn't correctly autodetect the speed, and
>attempts to force the media have not been at all successful.
>
> Note that the board has four 21143-TDs on it, and "DP83843BV3E" media
chips.
>
> With the 0.89H driver, the board gets detected as having four 21142s on
it,
>and, when I bring the interface up and try to transmit, the link and
collision
>lights flash on my hub, pulsing every couple of seconds. I can actually get
it
>to transmit some, but not much.
>
> With the 0.91E driver, the board gets detected as having four 21143s on
it,
>and, when I bring the interface up and try to transmit, the link light
flashes
>on my hub but not collision, pulsing every couple of seconds. Again, I can
>actually get it to transmit some, but not much.
>
> None of the full_duplex[] or options[] options seem to affect what the
board
>does in any substantial way.
>
> I've enclosed an example of what the 0.91E driver spits into the kernel
>message buffer; maybe it will say more to you all than it did to me.
>
> Can anyone suggest how to proceed trying to figure this out?
>
> -Craig
>
>[beginning got cut off, but it's all dupes of the eth3 info with different
MACs
>and different IRQs]
>Tulip rev 65 at 0xdc00, 00:80:C8:F8:71:DF, IRQ 15.
>eth3: EEPROM default media type Autosense.
>eth3: MII interface PHY 0, setup/reset sequences 0/0 long, capabilities e0
78.
>eth3: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
>eth3: Advertising 0001 on PHY 0 (0).
>eth3: Using media type MII, CSR12 is c6.
>eth3: MII transceiver #1 config 3100 status 7849 advertising 0001.
>eth0: tulip_open() irq 11.
>eth0: Advertising 0001 on PHY 0 (1).
>eth0: Using media type MII, CSR12 is c6.
>eth0: Using MII transceiver 1, status 7849.
>eth0: Done tulip_open(), CSR0 f8a08000, CSR5 f0320000 CSR6 b20e2002.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: 21143 negotiation status 000000c6, MII.
>eth0: MII status 7849, Link partner report 0000.
>eth0: No link beat on the MII interface, status 7849.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: Transmit error, Tx status 7fffbc00.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670040 new csr5=0xf0660000.
> In tulip_rx(), entry 0 00400320.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670040 new csr5=0xf0660000.
> In tulip_rx(), entry 1 00660320.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670040 new csr5=0xf0660000.
> In tulip_rx(), entry 2 00660320.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: Transmit error, Tx status 7fffbc00.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: Transmit error, Tx status 7fffbc00.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670005 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670040 new csr5=0xf0660000.
> In tulip_rx(), entry 3 00660320.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: Transmit error, Tx status 7fffbc00.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: Transmit error, Tx status 7fffbc00.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.
>eth0: Shutting down ethercard, status was f0360000.
>eth0: interrupt csr5=0xf0670004 new csr5=0xf0660000.
>eth0: interrupt csr5=0xf0660000 new csr5=0xf0660000.
>eth0: exiting interrupt, csr5=0xf0660000.