Re: [eepro100]sporadic hangups
Donald Becker <[email protected]>
| Newsgroups | gmane.linux.drivers.eepro100.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 9 Aug 2002, Brian Tilma wrote: > more thing. Below I've included the output of "mii-diag -v -D eth0", and I > was wondering if I needed to do anything regarding the connection speed. I > noticed that at the end, autonegotiation had not completed, but that a link > of some description was established. The communication does seem to be You link partner did not have Autonegotiation, so the transceiver fell back to sensing the link speed. Thus the two messages -you have link beat, but - negotiation did not complete See http://scyld.com/expert/NWay.html for the detailed story. > happening well enough, but I'd like to avoid potential problems. Do I need > to force a 10BaseT connection, or is the driver handling this just fine by > itself? Never force link speed or duplex unless you have a specific problem. That capability is provided only for non-standard installations. > mii-diag.c:v2.05 7/13/2002 Donald Becker ([email protected]) > Basic mode control register 0x3100: Auto-negotiation enabled. > You have link beat, and everything is working OK. > Your link partner is generating 10baseT link beat (no autonegotiation). ... > Link partner capability is 0021: 10baseT. > Negotiation did not complete. -- Donald Becker [email protected] Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993