Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!brendan@illyria.wpd.sgi.com
From: brendan@illyria.wpd.sgi.com (Brendan Eich)
Newsgroups: comp.sys.sgi
Subject: Re: et0: transmit: no carrier messages to console?
Message-ID: <106184@sgi.sgi.com>
Date: 24 May 91 23:04:53 GMT
References: <9105232018.AA02803@ccfiris.aedc> <106109@sgi.sgi.com>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 17

In article <106109@sgi.sgi.com>, vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
> 
> "no carrier" usually means the ethernet cable is not connected or loose.
> 
> "late collision" means a long packet suffered a collision after the 1st
> 	64 bytes, which in turn means that your ethernet is mis-configured.
> 	A late collision means the distance between distant parts of the
> 	network is more than 64-byte times.  The most common error is
> 	using excessively long drop cables.  With at least some twisted
> 	pair transceivers, you're limited to 10 or 20 feet.  It is also
> 	easy to break thick net by using three or more 75 meter 
> 	drop cables.

By the way, ethernet(7) describes these and other error messages.  In 4.0,
the "no carrier" message reads "no carrier: check Ethernet cable".

/be