How to get my networkk to work?

Berthold =?iso-8859-1?Q?H=F6llmann?= se6y095@public.uni-hamburg.de
Wed Jan 27 04:01:49 1999


Hello,

I recently purchased two MX98715 / MX98725 based pci network adapters.
The vendor is a company named 4lan. I installed them into my two
computers. One is recognized by python as 

(from /proc/pci):

PCI devices found:
  Bus  0, device  10, function  0:
    Ethernet controller: Unknown vendor MX98715 / MX98725 (rev 32).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
      I/O at 0xa800.
      Non-prefetchable 32 bit memory at 0xe1000000.

(from demesg):

Found Macronix 98715 PMAC at I/O 0xa800.
tulip.c:v0.89H 5/23/98 becker@cesdis.gsfc.nasa.gov
eth0: Macronix 98715 PMAC at 0xa800, 00 00 e8 59 9e cc, IRQ 11.
read_eeprom:
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 59e8 cc9e 0000 59e8 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 cc9e 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
0014 0000 0000 0000 0000 ffff ffff 0000
  PCI latency timer (CFLT) is 0x20,  PCI command is 0087.
eth0: tulip_open() irq 11.
eth0: No media description table, assuming 100baseTx-FD transceiver,
CSR12 20ce.
eth0: Done tulip_open(), CSR0 fff84800, CSR5 e4520000 CSR6 38602202.
eth0: interrupt  csr5=0xe4570001 new csr5=0xe4560000.
eth0: interrupt  csr5=0xe4170001 new csr5=0xe4160000.
eth0: interrupt  csr5=0xe4170005 new csr5=0xe4160000.
eth0: interrupt  csr5=0xe4670004 new csr5=0xe4660000.
eth0: interrupt  csr5=0xe4660000 new csr5=0xe4660000.
eth0: exiting interrupt, csr5=0xe4660000.
eth0: interrupt  csr5=0xe4570001 new csr5=0xe4560000.
eth0: interrupt  csr5=0xe4670005 new csr5=0xe4660000.
eth0: interrupt  csr5=0xe4660000 new csr5=0xe4660000.
eth0: exiting interrupt, csr5=0xe4660000.
eth0: interrupt  csr5=0xe4570001 new csr5=0xe4560000.
eth0: interrupt  csr5=0xe4670005 new csr5=0xe4660000.
eth0: interrupt  csr5=0xe4660000 new csr5=0xe4660000.
eth0: exiting interrupt, csr5=0xe4660000.
eth0: MXIC negotiation status 000020ce.
 (followed my lots of negotiation status messages)

(by tulip-diag -p 0xa800 -a -f):

tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Digital DC21040 Tulip Tulip chip registers at 0xa800:
  fff84800 ffffffff ffffffff 00011028 00011228 e4660000 38602202
e7ffebef
  fffe0000 0fff87ff fffffbbf fffe0000 000020ce ffff0001 fffffff9
fff00000
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, full-duplex.
 The transmit unit is set to store-and-forward.
 Port selection is 10mpbs-serial, full-duplex.

The second card is recognized similar, except that the ioAddr is 0xe800
and the interrupt is 10. The cards are connected directly through a
crossed link cable.

One problem I have is the reported port selection. I have a line

options tulip      options=5 debug=6  

in /etc/conf.modules and I thought this would cause to select
100baseTx-FD, but anyway, because both cards are recognized this way, I
expected a simple ping to work after I set up the computers to use the
IP addresses 192.168.99.98 and 192.168.99.97, but a simple 

>ping 192.168.99.97

--- 192.168.99.97 ping statistics ---
54 packets transmitted, 0 packets received, 100% packet loss

just hangs. I have to use ^C to stop it.

I hope I double checked everything, but can't get my network to work. Do
you have any hints for me?

Thanks

Berthold
-- 
se6y095@public.uni-hamburg.de 
        It is unlawful to use this email address for unsolicited ads
        (USC Title 47 Sec.227). I will assess a US$500 charge for
        reviewing and deleting each unsolicited ad.