Next-in-Thread Next Message

Question RBEM56G100 TX carrier errors on 100baseT network 

Forum: Xircom PCMCIA Ethernet Adapter Issues
Date: 2000, Sep 01
From: Stefan Kluth Stefan

Hi,

I recently got an upgraded network connection to 100baseT.
Now I get 100% TX packets carries errors, i.e. there is an
carier error for every TX packet. Here is the output of
ifconfig (I blanked my addresses):

lapkluth:/home/skluth# ifconfig
eth0      Link encap:Ethernet  HWaddr  
          inet addr: Bcast:  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20679 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:3185 dropped:0 overruns:0 carrier:3185
          collisions:0 

Then I got Donald Becker diagnostic programs and ran
tulip_diag.c (see output below). What I think is inconsistent
is that at the top we read:

"Port selection is MII, half-duplex"

while at the bottom we have

"Auto-negotiation complete, 100Mbps full duplex."

Any hints here?

cheers, Stefan


************************************************************

lapkluth:/home/skluth/scratch/pcidiag# ./tulip-diag -t 0 -p 0xa00 -mm -ee -aa 
tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Assuming a Digital Tulip series adapter at 0xa00.
Digital Tulip series chip registers at 0xa00:
  fea08000 ffffffff ffffffff 0009d810 0009da10 60000106 324c0000 e3fe0000
  e0000000 fffd8384 00000000 fffe0000 000000c4 ffff0000 ffffffff 880f0000
 Port selection is MII, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Stopped'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 72.
EEPROM size is 6.
  * An old-style EEPROM layout was found.
  * The old-style layout does not contain transceiver control information.
  * This board may not work, or may work only with a subset of transceiver
  * options or data rates.
EEPROM contents:
  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
  0000 0000 0000 0000 0000 0000 0000 0000
 ID block CRC 0xe3 (vs. 00).
  Full contents CRC 0x6523 (read as 0x0000).
 MII PHY found at address 0, status 0x782d.
 MII PHY #0 transceiver registers:
   3100 782d 0300 e54a 01e1 45e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0140 0000 0f00 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: 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:c0:39:--:--:--, model 20 rev. 10.
   Vendor/Part: TDK transceiver (unknown 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 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation  completed.
  TDK format vendor-specific registers 16..18 are 0x0140 0x0000 0x0f00
      Link polarity is detected as normal.
      Auto-negotiation complete, 100Mbps full duplex.
      Rx link in pass state, PLL slipped since last read.
      No new link status events.

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. None Fixed? by David Hinds, 2000, Sep 01
(_ None Re: Fixed? by Stefan Kluth, 2000, Sep 04

Add Message to: "RBEM56G100 TX carrier errors on 100baseT network"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10