100BaseTX does not work

Tue Sep 1 15:50:38 1998

Dear all,

recently I tried to create a 100 MBit network connection between
two computers, but I failed. Maybe someone on this list can help
me (I'm a newbie).

The two machines are:

1) PPro (200 MHz)                 2) 486 (33 MHz)
   PCI-bus                           ISA-bus
   SMC 9432 card (10/100 Mbps)       3c515 card (10/100 Mbps)

They are directly connected together by a CAT-5 wire (UTP, crossed).
I don't use a hub.

Both systems are running Linux (kernel 2.0.35). The network drivers
are loaded as modules. On the 486, the 3c515 is activated prior to
load the driver. The activation is done using the isapnp tool as
described in http://cesdis.gsfc.nasa.gov/linux/drivers/3c515.html

When I don't pass any command-line arguments to the drivers, the
network comes up in 10BaseT mode and everything works well. I tested
NFS, telnet, ftp, and Samba with no problems.
The FTP file transfer rate reaches approximately 1.0 Megabyte per sec.

But when I try to switch to 100BaseTX mode, I cannot get any connection
at all. The packet loss reported by ping is 100%.
Unfortunately, I did not observe any error messages, neither in the
system's log files nor on the console.

The problem exists, regardless which driver is loaded. I tried the
versions 1.03 and 1.04 of the epic100 module and version 0.03 of the
3c515 module.

Command-line arguments are passed to the driver according to
    http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
and http://cesdis.gsfc.nasa.gov/linux/drivers/3c515.html

But I'm still not sure, if I supplied the correct arguments. I do not
completely understand, which settings are changed by the argument
"options". The modules were loaded as follows:

1st system:     modprobe epic100 options=4
2nd system:     modprobe 3c515 options=4

The 3c515 module reports that 100BaseTX was selected. But the epic100
does not mention the media type. On either card the status LEDs show
the mode (100BaseTX) as selected.

I also tried explicitly enabling/disabling full duplex - with no success.

My questions:

- Does anybody know, what I did wrong?

- Possibly, is there a better (more verbose) description of the ethernet
  driver modules epic100 and 3c515 available?

- Do I need a hub to run 100BaseTX mode?

Thank you in advance for your help

	Martin

P.S.: Here is some more information which might be useful.

Machine 1
=========

copied from /proc/pci:
----------------------

  Bus  0, device  12, function  0:
    Ethernet controller: SMC 9432 TX (rev 6).
      Fast devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32.  Min Gnt=8.Max Lat=28.
      I/O at 0xd800.
      Non-prefetchable 32 bit memory at 0xf9800000.

loading epic100:
----------------

	/sbin/modprobe epic100 debug=2 options=4

dmesg:
------

epic100.c:v1.04 8/23/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/epic100.html
eth0: SMC EPIC/100 at 0xd800, IRQ 11, 00:e0:29:21:ac:9e.
eth0: EEPROM contents
 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000
 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000
 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000
 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000
eth0: MII transceiver #3 control 3000 status 7809.
eth0:  Autonegotiation advertising 01e1 link partner 0001.

mii-diag:
---------

Using the default interface 'eth0'.
Using the default interface 'eth0'.
MII PHY in use is 3.
 3000 782d 0181 4401 01e1 41e1 0001 ffff ffff ffff ffff ffff ffff ffff ffff ffff 0040 0018 ffff ffff ffff ffff ffff ffff ffff ffff ffff 003e ffff 0048 0000 1dd8

After configuring eth0 on the other machine,
additional messages given by dmesg are:
--------------------------------------------

eth0: Setting half-duplex based on MII xcvr 3 register read of 0001.
eth0: epic_open() ioaddr d800 IRQ 11 status 0512 half-duplex.
eth0: Setting full-duplex based on MII #3 link partner capability of 41e1.

...and the output of mii-diag changes to:
-----------------------------------------

Using the default interface 'eth0'.
Using the default interface 'eth0'.
MII PHY in use is 3.
 3000 782d 0181 4401 01e1 41e1 0001 ffff ffff ffff ffff ffff ffff ffff ffff ffff 0040 0018 ffff ffff ffff ffff ffff ffff ffff ffff ffff 003e ffff 0048 0000 1dd8

When the old driver (v1.03) is used,
mii-diag's report looks like this: 
------------------------------------

Using the default interface 'eth0'.
Using the default interface 'eth0'.
MII PHY in use is 3.
 3000 7809 0181 4401 01e1 0001 0000 ffff ffff ffff ffff ffff ffff ffff ffff ffff 0040 0018 ffff ffff ffff ffff ffff ffff ffff ffff ffff 003e ffff 0010 0000 0dc0

Machine 2
=========

loading 3c515:
--------------

	/sbin/modprobe 3c515 debug=2 options=4

dmesg:
------

3c515.c:v0.03 3/19/97 becker@cesdis.gsfc.nasa.gov
3c515 Resource configuraiton register 0x010f, DCR 1483.
eth0: 3Com 3c515 at 0x300, 00:10:4b:6e:e4:d2, DMA 3, IRQ 15
  Internal config register is 102001b, transceivers 0xf040.
  64K word-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
  Media override to transceiver type 4 (100baseTX).
1 3c515 cards found.

3c-515-diag:
------------

3c515-diag.c:v0.03 3/19/97 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Looking for card at 300.

A ISA Fast EtherLink III board was detected at I/O 0x300.
Window 0: 0000 0000 0000 0000 0000 0095 0000 0000.
Window 1: 6e4b 0000 0000 2002 8000 00ff 7ffc 2002.
Window 2: 1000 6e4b d2e4 0000 0000 0000 00da 4002.
Window 3: 001b 0142 0000 0000 f040 7fff 7fff 6002.
Window 4: 0000 06d0 2000 0c80 0002 8482 0000 8002.
Window 5: 1ffc 1ffc 00da 1ffc 0005 0298 00da a002.
Window 6: 0000 0000 0000 0000 0000 0000 0078 c002.
Window 7: 0000 0000 0000 0000 8000 00ff 0000 e002.
Operation registers: 0000 0000 0000 e002 8000 00ff 7ffc e002.
Boomerang registers: ffff ffff ffff ffff ffff ffff ffff ffff
  (at 0x700)       : ffff ffff ffff ffff ffff ffff ffff ffff.
Corkscrew registers: 1483 010f 0000 0000 0001 0197 00bc ffff.
EEPROM contents:
 0010 4b6e e4d2 010f c46f 0036 4c4d 6d50 1487 5150 0010 4b6e e4d2 3f10 0000 0000
 11c7 0000 001b 0161 0000 0003 0000 00bc 6d50 5150 e4d2 4b6e 0acb 1010 1782 3300
 6f43 206d 6146 7473 4520 6874 7265 694c 6b6e 4920 4153 5015 506d 0251 a822 2a9e
 06e8 0047 0280 03e0 2020 4079 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  64K word-wide RAM 1:1 Rx:Tx split, autoselect/100baseTX interface.
   Done card at 0x300.

 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
 |  body of the mail, include only the text:
 |   unsubscribe this-list-name youraddress@wherever.org
 | You will be unsubscribed as speedily as possible.