Alpha 164UX

Grahame Jordan gbj@ob1.theforce.com.au
Tue Apr 27 06:44:11 1999


Hi

While pinging the other interface and running tulip-diag -e the result 
shows:

[root@pc878 /usr/local/src/tulip]# ./tulip-diag -f -e -e -a -m -m
tulip-diag.c:v1.10 4/12/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0x8000.
Digital DS21143 Tulip chip registers at 0x8000:
  ffa0e000 ffffffff ffffffff 402ff818 402ffa18 f0660000 b3862002 fbfffbff
  e0000000 ffffcbf8 ffffffff fffe0000 000000c6 ffff0001 fff80000 8ff5c008
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit started, Receive started, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
EEPROM contents:
  0000 0000 0000 0000 0000 0000 0000 0000
  00e1 0103 0000 51f0 1709 1e00 0000 0800
  8604 0002 08af 00a5 0286 af04 a508 8800
  0304 08af 00a5 8061 0488 af05 a508 6100
  0080 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 df49
 ID CRC 0xe1 (vs. 0xe1), complete CRC 6d04ef2c.
Ethernet MAC Station Address 00:00:F0:51:09:17.
EEPROM transceiver/media description for the Digital DS21143 Tulip chip.
Leaf node at offset 30, default media type 0800 (Autosense).
 4 transceiver description blocks:
  Media 10baseT, block type 2, length 6.
   Serial transceiver for 10baseT (media type 0).
    GP pin direction 08af  GP pin data 00a5.
  Media 10baseT-Full Duplex, block type 2, length 6.
   Serial transceiver for 10baseT-Full Duplex (media type 4).
    GP pin direction 08af  GP pin data 00a5.
  Media 100baseTx, block type 4, length 8.
   SYM transceiver for 100baseTx (media type 3).
    GP pin direction 08af  GP pin data 00a5.
    No media detection indication (command 80 61).
  Media 100baseTx Full Duplex, block type 4, length 8.
   SYM transceiver for 100baseTx Full Duplex (media type 5).
    GP pin direction 08af  GP pin data 00a5.
    No media detection indication (command 80 61).
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.


And a cat /proc/pci:

[root@pc878 /usr/local/src/tulip]# cat /proc/pci
PCI devices found:
  Bus  0, device  13, function  0:
    PCI bridge: DEC DC21052 (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.
Min Gnt=4.
  Bus  0, device  14, function  0:
    ISA bridge: Intel 82371SB PIIX3 ISA (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.
  Bus  0, device  14, function  1:
    IDE interface: Intel 82371SB PIIX3 IDE (rev 0).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.
      I/O at 0x8800 [0x8801].
  Bus  0, device  15, function  0:
    Ethernet controller: DEC DC21142 (rev 48).
      Medium devsel.  Fast back-to-back capable.  IRQ 44.  Master Capable.  Latency=32.  Min Gnt=20.Max Lat=40.
      I/O at 0x8000 [0x8001].
      Non-prefetchable 32 bit memory at 0x9800000 [0x9800000].
  Bus  0, device  17, function  0:
    VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 0).
      Medium devsel.  IRQ 43.
      Non-prefetchable 32 bit memory at 0x9000000 [0x9000000].
  Bus  1, device   8, function  0:
    Ethernet controller: Intel 82557 (rev 5).
      Medium devsel.  Fast back-to-back capable.  IRQ 19.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0xa100000 [0xa100008].
      I/O at 0xb800 [0xb801].
      Non-prefetchable 32 bit memory at 0xa200000 [0xa200000].
  Bus  1, device   9, function  0:
    Ethernet controller: Intel 82557 (rev 5).
      Medium devsel.  Fast back-to-back capable.  IRQ 31.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0x9f00000 [0x9f00008].
      I/O at 0xb000 [0xb001].
      Non-prefetchable 32 bit memory at 0xa000000 [0xa000000].
  Bus  1, device  10, function  0:
    Ethernet controller: Intel 82557 (rev 5).
      Medium devsel.  Fast back-to-back capable.  IRQ 27.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0x9d00000 [0x9d00008].
      I/O at 0xa800 [0xa801].
      Non-prefetchable 32 bit memory at 0x9e00000 [0x9e00000].
  Bus  1, device  11, function  0:
    Ethernet controller: Intel 82557 (rev 5).
      Medium devsel.  Fast back-to-back capable.  IRQ 39.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0x9b00000 [0x9b00008].
      I/O at 0xa000 [0xa001].
      Non-prefetchable 32 bit memory at 0x9c00000 [0x9c00000].
  Bus  1, device  12, function  0:
    Ethernet controller: Intel 82557 (rev 5).
      Medium devsel.  Fast back-to-back capable.  IRQ 35.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      Prefetchable 32 bit memory at 0x9902000 [0x9902008].
      I/O at 0x9800 [0x9801].
      Non-prefetchable 32 bit memory at 0x9a00000 [0x9a00000].
  Bus  1, device  13, function  0:
    SCSI storage controller: NCR 53c875 (rev 4).
      Medium devsel.  IRQ 20.  Master Capable.  Latency=32.  Min Gnt=17.Max Lat=64.
      I/O at 0x9000 [0x9001].
      Non-prefetchable 32 bit memory at 0x9900000 [0x9900000].
      Non-prefetchable 32 bit memory at 0x9901000 [0x9901000].                  


Don't you just love the interrupts :).  Ahh I just have a few extra ethernet cards in but
but these are not a factor in this problem.

I hope that this info is helpful.

Thanks

Grahame Jordan
"Do or do not; There is no try"
Yoda

On Tue, 27 Apr 1999, Donald Becker wrote:

> On Tue, 27 Apr 1999, Grahame Jordan wrote:
> 
> > I have a couple of Alpha 164UX mother boards that have on board DEC
> > At the moment they are wired back to back with a crossover cable in TX
> ..
> > options=12 they seem communicate quite happily at 10 MB/s. However if I
> ..
> > 2.2.3, but overcame the problem with an updated tulip.c, 0.90z.
> 
> Confirm -- 0.90z worked at 100mbps.  Or do I misunderstand?
> 
> > If I go through a 100Mhz TX hub and set options=5 the hub senses the
> > interfaces 
> > but the same problem as above.
> 
> Note that 5 is full duplex, while you should be using half duplex with a
> repeater.  But you should still be able to communicate.
> 
> > I have just tried the latest driver 0.91 with the same problem.
> 
> What does 'mii-diag' report?
> What about 'tulip-diag'?
>   http://cesdis.gsfc.nasa.gov/linux/diag/index.html
> 
> > and the HDD. What are the limitations and expected output of Gigabit
> > NICs? 
> 
> 30-40MB/sec using 'ttcp'.  A 64 bit data bus helps.
> 
> > can get ~20MB/s overall but this is hard to gauge with no real network
> 
> Hmmm, with good NICs you should be able to get about the same -- 30+MB/sec.
> 
> Donald Becker					  becker@cesdis.gsfc.nasa.gov
> USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
> Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
> 301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html
>