[tulip] PowerPC SBC with PMC ethernet - can't get it to work
Nicholas, John S
John.Nicholas@PSS.Boeing.com
Thu, 1 Feb 2001 07:52:20 -0800
Hi,
We are having problems trying to get an Ethernet PMC card to work
on a Synergy board (VME chassis). We are adding a second Ethernet
port the synergy board.
We have tried both the "tulip" and "de4x5" drivers, neither worked right.
With both, we get the LINK light on (GOOD) and the ACT light flickers.
Both of these indications seem to point to normal operation.
We were mostly testing as modules, but tried building them into the
kernel too with no change in behavior.
Do you know which driver we should be using?
Do you know what our problem might be with the tulip driver?
Details follow:
=========================================================================
System Configuration
--------------------------------------------------------------------------
CPU: PowerPC in VME Backplane
Synergy VGM5-F
433MHz
Memory: 256MB
PCI Config:
Bus Idsel Vendor Device ID Rev Class Sub-Class Part Name
0 0 1057 2 40 6 0 Motorola Grackle
0 11 1014 46 0 FF 0 IBM MPIC
0 12 1000 D 2 1 0 Symbios 885 SCSI
0 12.1 1000 701 2 2 0 Symbios 885 Ethernet
0 15 1011 26 2 6 4 DEC 21154 Bridge
1 18 1011 19 41 2 0 *** UNKNOWN ***
0 17 10E3 0 2 6 80 Tundra Universe II
0 18 1011 46 1 6 80 DEC 21554 Bridge
* The device "UNKNOWN" is the PMC Ethernet card in question.
Ethernet Card:
PMC/Fast Eathernet/21143
Board manufactured by Force Computers
Placed on mezzanine board so IRQ would not conflict with VME
Universe driver. In this location, the board had an IRQ of 9
as reported by driver.
Linux:
Yellow dog Version 2.2.15-a
=========================================================================
Network Setup
--------------------------------------------------------------------------
1) Hub (10baseT)
2) PC Ethernet analyzer - hooked to hub
3) PC - hooked to hub (IP 192.168.0.10)
4) Synergy CPU (with 2 Ethernet ports)
a. eth0 - on CPU Ethernet adapter ("Symbios 885 Ethernet") was hooked up
to company network
b. eth1 - PMC Ethernet card was hooked to hub. (IP 192.168.0.1)
=========================================================================
DE4X5:
This driver seemed to work on transmit.
OUTPUT From Driver:
eth1: DC21143 at 0xfe801000 (PCI bus 1, device 2), h/w address 00:c0:8b:03:38:48,
and requires IRQ9 (provided by PCI BIOS).
de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
When we "ping"ed from VME CPU to the PC, we could see the ARP request being
broadcast. We know it went out the eth1 port, it had the H/W address of
the PMC card. The PC then sent an ARP Reply to the PMC card, but the PMC
card never saw it. The ping returns :
"From 192.168.0.1: Destination Host Unreachable"
When we "ping"ed from the PC to the PMC card, we could see the ARP request
but never a reply from the PMC card.
It seems that the PMC card is transmitting OK, but not receiving (neither
a ping from the PC nor a reply from a ping from the PC).
We tried many different parameters:
* args - fdx, no fdx
* args - with and without "autosense=10MB"
* with and without "dec_only=1"
They did not seem to change behavior.
TULIP:
With this driver, we first tried not setting any parameters. Then we mostly
used media type of 12 (Serial 10baseT(no autoselect)).
---------------------------
message log summary with following command
insmod tulip debug=0x1ff
eth1: Digital DS21143 Tulip rev 65 at 0xfe801000, 00:C0:8B:03:38:48, IRQ 9.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth1: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
eth1: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
eth1: Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
eth1: Restarting 21143 autonegotiation, 0003ffff.
eth1: tulip_open() irq 9.
eth1: Restarting 21143 autonegotiation, 0003ffff.
eth1: Done tulip_open(), CSR0 f8a08000, CSR5 f0320000 CSR6 b2422202.
eth1: 21143 negotiation status 000052ca, 10baseT.
eth1: Tx hung, 7 vs. 0.
eth1: 21140 transmit timed out, status f4678054, SIA 000052ca ffff0001 fffbffff cff0c000, resetting...
eth1: 21143 non-MII 100baseTx-FD transceiver control 08af/00a5.
eth1: Setting CSR15 to 08af0008/00a50008.
eth1: Using media type 100baseTx-FD, CSR12 is ca.
eth1: transmit timed out, switching to 100baseTx-FD media.
eth1: 21143 negotiation status 000052ca, 100baseTx-FD.
eth1: Tx hung, 9 vs. 0.
eth1: 21140 transmit timed out, status f4678056, SIA 000052ca ffff0001 fffbffff 8ff5c008, resetting...
eth1: 21143 non-MII 10baseT-FD transceiver control 08af/00a5.
eth1: Setting CSR15 to 08af0008/00a50008.
eth1: Using media type 10baseT-FD, CSR12 is ca.
eth1: transmit timed out, switching to 10baseT-FD media.
Behavior:
Constant tranmit timeouts and switching to different media type.
Garbage seems to be tranmitted on network.
---------------------------
message log summary with following command
insmod tulip debug=0x1ff options=12
eth1: Digital DS21143 Tulip rev 65 at 0xfe801000, 00:C0:8B:03:38:48, IRQ 9.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth1: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
eth1: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
eth1: Index #3 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
eth1: Restarting 21143 autonegotiation, 0003ffff.
eth1: tulip_open() irq 9.
eth1: Using user-specified media 10baseT(forced).
eth1: 21143 non-MII 10baseT transceiver control 08af/00a5.
eth1: Setting CSR15 to 08af0008/00a50008.
eth1: Using media type 10baseT, CSR12 is c6.
eth1: Done tulip_open(), CSR0 f8a08000, CSR5 f0320000 CSR6 b2422002.
eth1: 21143 negotiation status 000052ca, 10baseT.
eth1: Tx hung, 7 vs. 0.
eth1: 21140 transmit timed out, status f0678014, SIA 000052ca ffff0001 fff8ffff 8ffdc008, resetting...
Behavior:
Constant messages (1/sec):
eth1: 21140 transmit timed out, status f06980d7, SIA 000052ca ffff0001 fff8ffff 8ffdc008, resetting...
ping seems to go out on network (arp request from 192.168.0.1 to 192.168.0.10)
Never a response from 192.168.0.10. (de4x5 got an ARP reply)
ping from PC is never seen by eth1 (no replay is sent).
Any help would be greatly appreaciated!
-----------------------------------------------------------------------------------------------
John S. Nicholas The Boeing Company
Stable: john.s.nicholas@boeing.com Phone: 206-662-0298
-----------------------------------------------------------------------------------------------