3c509(a) 100BaseTX problems (fwd)

[Stacy Trippe]

Note: please reply directly, as I am not subscribed to this list.

I have a Linux RedHat 5.0 box running 2 3Com "Boomerang" 3c905's (first
revision).  Under the "old" 3c59x.o module, things load up and I'm able
to get the first card to run.  

eth0 - 3c905(a) running at (I/O 0x6400 IRQ 10) 10BaseT  connects fine

eth1 - 3c905(a) running at (I/O 0x6800 IRQ 11) 100BaseTX comes up, I get a 
link light (sometimes at 10, sometimes at 100--hub will show link when 100lnk
indicator is on the NIC), but I am unable to ping any other computers on 
that hub. 

I ran the 3c90xcfg utility (from DOS) and when i chose to "force"
100BaseTX, it gave warning saying 'Cannot detect 100BaseTX media'.
 
Cable is Cat-5 4-pair ...terminated properly (straight-through), as I was
able to connect a 10BaseT NIC PC to the other end and run fine to a 10BaseT
hub.
 
I'm booting single user and the following occurs:
When I run the "old" 3c59x.o module with no options
everything loads fine, and Linux sees both cards, however, I cannot ping 
anything on the second (eth1) card.
 
When I run the "new" 3c59x.o module with Options=0,4 (to force 1st card
to 10MB and second card to 100BaseTX), I get the following error on the
first card (10MB card):  PCI BIOS not enabled and PCI Adjust 00000 -> 00005 
(vaguely recalled).  I tried with no options, and still get the same 
thing.  Then when I boot, I can no longer ping anything on first card (eth0)
nor second card (eth1).

I get the same results if I run the boomerang.o module with same options,
or with no options.

The purpose for this is to run a Linux router, routing packets from the
eth1 to the eth0 network (from 100BaseTX to 10BaseT).  The 100BaseTX is
a private network 192.168.*.* that I want to NAT (address translate aka
firewall) to the 10BaseT network.

I've attached the output from `vortex-diag -aa`.
 
--------------14E5A72C54EF45F956CDAFA3
Content-Type: text/plain; charset=us-ascii; name="diag.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="diag.txt"

vortex-diag.c:v1.05 5/22/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Found a 3Com PCI Ethernet 3c905 rev 0 at 0x6800.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000.
  Window 1: FIFO FIFO 0000 2000 8000 00ff 13fc 2000.
  Window 2: 6000 ac08 fd8f 0000 0000 0000 00de 4000.
  Window 3: 02d8 0063 0000 0000 e040 0bff 13ff 6000.
  Window 4: 0000 06d0 0000 0cc0 0003 8802 0000 8000.
  Window 5: 1ffc fffc 00de 1ffc 0007 069e 00de a000.
  Window 6: 0000 0000 0000 0000 0000 0000 0000 c000.
  Window 7: 0000 0000 0000 0000 8000 00ff 0000 e000.
Vortex chip registers at 0x6800
  0x6810: **FIFO** **FIFO** 00008000 000013fc
  0x6820: 00000000 00000000 00000000 ff000000
  0x6830: 00000000 000016ca 00000000 00000000
 No interrupt sources are pending.
 Transceiver/media interfaces available:  MII.
 MAC settings: half-duplex.
Found a 3Com PCI Ethernet 3c905 rev 0 at 0x6400.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
initial window 7, registers values by window:
  Window 0: 0000 0000 0000 0000 0000 00bf ffff 0000.
  Window 1: FIFO FIFO 0000 2000 8000 00ff 13fc 2000.
  Window 2: 6000 ac08 1e90 0000 0000 0000 00de 4000.
  Window 3: 02d8 0063 0000 0000 e040 0bff 13ff 6000.
  Window 4: 0000 06d0 0000 0cc0 0003 8802 2000 8000.
  Window 5: 1ffc fffc 00de 1ffc 0007 069e 00de a000.
  Window 6: 0000 0000 0000 9701 1100 6c2b 1fd2 c000.
  Window 7: 0000 0000 0000 0000 8000 00ff 0000 e000.
Vortex chip registers at 0x6400
  0x6410: **FIFO** **FIFO** 00008000 000013fc
  0x6420: 00000000 00000000 00000000 ff000000
  0x6430: 00000000 0000cf7e 00000000 00000000
No interrupt sources are pending.
Transceiver/media interfaces available:  MII.
  MAC settings: half-duplex.

--------------14E5A72C54EF45F956CDAFA3--