My original question:`
> Does anyone know exactly what causes the error "No carrier" on an
> Ethernet? I replaced a Sun386i that was working fine with a Sparc 2
> running 4.1.1B, and I can't get the new machine to work on the
> Ethernet. It keeps saying "No carrier".
The answer from the net is that there is an actual "carrier" pin on the
transceiver cable, and the most likely cause for the error is a bad
cable, connector, or transceiver. In my case I took everything apart,
and put it back together using a different port on our multi-port
transceiver and it worked perfectly, and I didn't go any further to try
to locate the original proble.
Thanks to all that replied. I've included a few interesting comments
here:
From: Dave <bianco@cs.odu.edu>
| Well, I assume the ethernet is actually working, so
| if you transceiver cable is ok, and so is your transceiver,
| check the ethernet fuse on the sparcstation... I'm not sure where
| it is on the SS2, but the SS1/1+ has it right by the ethernet
| port, on the motherboard...
and in the same vein...
From: Steve Swaney <steve@mapes>
| Have you tried checking the fuse on the eternet circuit. Its a small
| vertical cylnder with clear sided and a black top. There are 2 on the
| motherboard. One for the SCSI and one for the Ethernet.
From: Barry Shein <bzs@world.std.com>
| Another remote (so to speak) possibility is that the ethernet device
| was not configured properly by ifconfig on boot. Do a:
|
| # /etc/ifconfig le0
|
| and see if the info printed out looks reasonable (do this before
| lugging the thing around, I'd suggest.)
A little info on "heartbeat". Since both my systems were Sun's I
figured they probably hadn't changed the heartbeat requirement, but
this info could be useful to someone:
From: "Scott E. Townsend" <fsset@bach.lerc.nasa.gov>
| I can't say for sure (I don't have either flavor of Sun machine) but
| Ethernet tranceivers come in a few flavors. One flavor has a signal
| sometimes called 'heartbeat' which essentially tells the transmitter
| that the signal is indeed getting out to the wire. Some systems ignore
| this signal, some systems require it. The system I'm most familiar
| with would simply log 1 carrier loss per packet if you had a tranceiver
| which didn't give back a 'heartbeat'. Maybe 4.1.1B considers this a
| fatal error?
Thanks to:
Dave <bianco@cs.odu.edu>
"Pamela D. Hanes" <phanes@hal.com>
Brent Chivers <bchivers@smiley.mitre.org>
Kevin Sheehan {Consulting Poster Child} <kalli!kevin@fourx.aus.sun.com>
fabrice cuq <fabrice@yosemite.atmos.ucla.edu>
Barry Shein <bzs@world.std.com>
Ralph Merwin <ralph@swmerc.rain.com>
Antonis Kyriazis <antonis@intranet.gr>
Steve Swaney <steve@mapes>
Mark Sims - Central Region Technology Manager <para1!detroit!marks@uunet.uu.net>
Eckhard Rueggeberg <eckhard@ikarus.ts.go.dlr.de>
Marcel Bernards <bernards@ecn.nl>
Christian Candia White <synapsis!cristian@sun.com>
Lawson A S <tony@essex.ac.uk>
"Scott E. Townsend" <fsset@bach.lerc.nasa.gov>
Debbie McGlade <debbie@cs.odu.edu>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:34 CDT