Richard Heycock (crob@zip.com.au)
Wed, 3 Mar 1999 15:39:36 +1100 (EST)
I'm having a few problems with ethernet connections between two machines.
One is a XL300 the other is a Cyrix i686 running at 200MHz. The XL300 is
running 2.2.0-pre8 compiled with egcs-1.0.3 and the i686 is running the
same kernel compiled with gcc 2.7.2.3. Both are compiled as modules.The
ethernet card for the XL300 is the onboard DC21040 chip, /proc/pci:
PCI devices found:
Bus 0, device 6, function 0:
Ethernet controller: DEC DC21040 (rev 36).
Medium devsel. Fast back-to-back capable. IRQ 29. Master Capable. Latency=96.
I/O at 0x9000 [0x9001].
Non-prefetchable 32 bit memory at 0x9000000 [0x9000000].
And the card for the i686 is an Accton Cheetah Fast ethernet, /proc/pci:
Bus 0, device 15, function 0:
Ethernet controller: DEC DC21142 (rev 48).
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=64. Min Gnt=20.Max Lat=40.
I/O at 0xf400 [0xf401].
Non-prefetchable 32 bit memory at 0xffae7f80 [0xffae7f80].
I have at one stage had these cards working quite well together (approx
1Mbyte/s) but it seems it was just luck (and I can't remember how I did
it).
If I use the de4x5 driver on the XL300 and the tulip (the de4x5 doesn't
work on the i686) I can eventaully get them up and running by loading and
unloading the module while the other machine is pinging it. At the moment
I'm getting about 750 KBytes/s. I just swapped the tulip driver for the
de4x5 driver and it still works with about same transfer rate. It seems to
make a difference which machine is up first. If I then try to use the
XL300 as an NFS serve, the client reports:
nfs: server mort not responding, still trying
nfs: task 82 can't get a request slot
This is reported when trying to open an 8192 byte file.
I've set /etc/conf.modules to contain the following on both machines:
alias eth0 tulip
options tulip options=12
There is no change if I change the options to 9 or 11.
On the i686 the driver (I assume it's the driver as it's not in
/var/log/messages nor `dmesg`) reports that the media is fixed at 10baseT
(since this is a 10/100Mbit card) on the XL300 this is not reported.
tulip-diag (on the XL300 reports);
tulip-diag.c:v1.08 2/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DC21040 Tulip adapter at 0x9000.
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 unit is set to store-and-forward.
Use '-a' to show device registers,
'-e' to show EEPROM contents,
or '-m' to show MII management registers.
This always seems to be the output whether the two boxes can ping each
other or not. Does anyone know if this program actually works?
On the i686 tulip-diag reports
tulip-diag.c:v1.08 2/28/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0xf400.
Port selection is 10mpbs-serial, full-duplex.
Transmit started, Receive started, full-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
Use '-a' to show device registers,
'-e' to show EEPROM contents,
or '-m' to show MII management registers.
Which seems fine.
And one last thing I have tried the following tulip drivers:
v0.89H v0.90 & v90q
and for the de4x5:
V0.543
Does anybody have any idea as to what is going on.
regards
Richard Heycock
-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail 2.0b3 on Tue Mar 02 1999 - 21:00:10 PST