Re: Problem with connection of EtherExpress Pro100 to a 10/100 switch

Donald Becker <[email protected]> Thu, 16 Oct 2003 12:31:46 -0400 (EDT)
Newsgroups gmane.linux.drivers.eepro100.devel
Message-ID <[email protected]>
On Thu, 16 Oct 2003, Ricardo Jorge da Fonseca Marques Ferreira wrote:

> -----BEGIN PGP SIGNED MESSAGE-----

Please don't sign messages to the lists:
   they look like spam
   I must manually moderate and check every email with an attachment
   it doesn't do any good,
   it results in ugly archives and digests

> I'm running linux 2.4.22 and recently moved from a longshine 8 port 10/100 
> switch to a 16 port 10/100 switch also from longshine. I reconnected all my 
> rtl8139 based cards with no problems. I also reconnected a EtherExpress 
> Pro100 to it and it reports from mii-tool:
> 
> eth0: negotiated 100baseTx-FD flow-control, link ok

What does 'mii-diag' report?
The 'mii-tool' program uses code from 'mii-diag', but there is a real
reason why I wrote 'mii-diag' to produce the output that it does.

> ... but when i reconnected my other EtherExpress Pro100 (this one is an 
> onboard one), it apparently cant autonegotiate with the switch no matter how 
> much time i give it. The only way to get link is forcing the speed to 
> 100BaseTx-FD. It works fine after that, desconnecting and reconnecting the 
> cable. Except, the problem comes back when i power off & on the system.

If it works fine forced to full duplex, then the link partner is forced
to full duplex.  Forcing speed or full duplex turns off autonegotiation,
which explains what you are seeing.

> These cards are on different machines. I'm using the kernel driver eepro100.o

What driver version?
Is there a reason the driver version was omitted from your message?

> eth0: Intel Corp. 82557 [Ethernet Pro 100], 00:90:27:35:CF:56, IRQ 9.
>   Board assembly 689661-004, Physical connectors present: RJ45
..
> The card that doesnt:
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:10:DC:C0:27:9B, IRQ 11.
>   Board assembly 727095-004, Physical connectors present: RJ45
...
> This is the output of mii-diag -v on the non-working card (after i fixed the 
> speed): 

What was it before you forced the speed (and thus disabled
autonegotiation)?

The output of 'mii-diag --watch eth0', while re-plugging the cable, might
be useful here. 

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993