Subject: Re: Bad fcs?
To: None <wrstuden@loki.stanford.edu>
From: Ken Nakata <kenn@eden.rutgers.edu>
List: port-mac68k
Date: 06/27/1997 21:24:38
On Fri, 27 Jun 1997 17:34:29 -0700 (PDT),
wrstuden@loki.stanford.edu (Bill Studenmund) wrote:
> > 
> > Fcs stands for Frame Check Sequence.  A fancy name for a CRC.  So, I'd
> > guess the PB can't quite keep up with the data rate thus drops a char
> > here and there, making discripancies between calculated and received
> > fcs.
> 
> I'd bet the error's in the cable. If we were dropping characters,
> we'd generate fifo or ring overflows too. Or is logging set to
> ignore them?

Yeah, you're absolutely right!  But then again, the question is,
does the same cable work under MacOS, or anything other than pppd?

> > Make connection at a slower speed, like 19200 or something.  Or, fix
> > the linux serial driver so that it'll do hand-shake properly ;-)
> 
> Well, since we don't yet ask the other side to wait, it doesn't matter
> if they do handshaking. :-)

You mean we don't handshake either?   Didn't know that ;-)

Ken