Problem uploading data to a linux host with eepro100+

Mon Jan 24 23:52:45 2000

Ok, here's an update of my error report, with the output of diagnostic
tools.

----------------------------------------------------------------------------
-
[root@gimme eepro100-diag]# ./eepro-diag -a -f
eepro100-diag.c:v1.01 7/8/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Intel 82557 EtherExpressPro100B adapter at 0xa800.
i82557 chip registers at 0xa800:
  00000050 1f82e0e4 00000000 00080002 182545e1 00000600
  No interrupt sources are pending.
   The transmit unit state is 'Suspended'.
   The receive unit state is 'Ready'.
  This status is normal for an activated but idle interface.
----------------------------------------------------------------------------
-

Why does is say idle? I'm uploading a 1.6mb file at this point...
Some eeprom info:

----------------------------------------------------------------------------
-
[root@gimme eepro100-diag]# ./eepro100-diag -eef
eepro100-diag.c:v1.01 7/8/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Intel 82557 EtherExpressPro100B adapter at 0xa800.
EEPROM contents:
    00: 9000 c727 e492 0203 0000 0201 4701 0000
  0x08: 7213 8307 40a2 000c 8086 0000 0000 0000
      ...
  0x30: 0128 0000 0000 0000 0000 0000 0000 0000
  0x38: 0000 0000 0000 0000 0000 0000 0000 7c86
 The EEPROM checksum is correct.
Intel EtherExpress Pro 10/100 EEPROM contents:
  Station address 00:90:27:C7:92:E4.
  Board assembly 721383-007, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
----------------------------------------------------------------------------
-

Here's some mii-diag output:

----------------------------------------------------------------------------
-
[root@gimme eepro100-diag]# ./mii-diag -v
mii-diag.c:v1.07 10/14/99  Donald Becker (becker@cesdis.gsfc.nasa.gov)
Using the default interface 'eth0'.
 MII PHY #1 transceiver registers:
   0100 780d 02a8 0154 05e1 45e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0401 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x0100: Auto-negotiation disabled, with
 Speed fixed at 10 mbps, full-duplex.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT, w/ 802.3X flow control.
 MII PHY #1 transceiver registers:
   0100 780d 02a8 0154 05e1 45e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0401 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x0100: Auto-negotiation disabled!
   Speed fixed at 10 mbps, full-duplex.
 Basic mode status register 0x780d ... 780d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 00:aa:00:--:--:--, model 21 rev. 4.
   No specific information is known about this transceiver type.
 I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD
10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx
10baseT-FD 10baseT.
   Negotiation  completed.
----------------------------------------------------------------------------
-

Very strange that autoneg is off... The only module option i have is
debug=3.

Does this tell anyone what's going on?
I'm really fuzzed about the tranciever suspended stuff.

/Magnus Näslund

-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-eepro100-request@beowulf.org