Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5380 comp.os.386bsd.development:1251 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!geraldo.cc.utexas.edu!sylvester.cc.utexas.edu!not-for-mail From: vax@sylvester.cc.utexas.edu (Vax) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.development Subject: Regarding Cables on com [NetBSD-0.9] Date: 26 Sep 1993 05:02:14 -0500 Organization: The University of Texas - Austin Lines: 37 Message-ID: <283pb6$ier@sylvester.cc.utexas.edu> NNTP-Posting-Host: sylvester.cc.utexas.edu Okay, I've had problems with both my com ports and lpt ports, first under 386BSD-0.1 + pk0.2.3, and now NetBSD-0.9. Until now, I keep getting the "are you sure all the lines run thru?" response. Yes. But not sure exactly whether they run to the right places or not. Here is the results of the continuity test, please, someone with experience and/or a reference manual handy, tell me if these are correct. "Com" port cable, 9-pin Female D-shell to 25-pin Male D-shell Counted from top right Counted from top left 1 8 (DCD) 2 3 (RXD) 3 2 (TXD) 4 20 (DTR) 5 7 (SGD) 6 6 (DSR) 7 4 (RTS) 8 5 (CTS) 9 22 (RNG) Symptoms: Under both NetBSD-0.9 and all pk levels of 386BSD-0.1, if data was sent "out" through FTP, (e.g. "put" when invoked locally, "get" when FTP invoked from foreign machine) then RD and SD lights blink like crazy, SD almost constant, RD only occasionally. Three seconds later, CTS goes out. RD and SD lights continue to blink like crazy. Six seconds later, CD EC and OH go out. Slip attempts to reopen the line (I can see SD/RD blink a few times) but then the machine crashes HARD. [RS]D=receive,send data CTS=clear to send CD=carrier detect EC=error correct OH=off hook lpt problem detailed in next article. -- Protect our endangered bandwidth - reply by email. NO BIG SIGS! VaX#n8 vax@ccwf.cc.utexas.edu - Don't blame me if the finger daemon is down