From owner-freebsd-stable Thu Mar 28 11:56:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 53C0837B400 for ; Thu, 28 Mar 2002 11:56:11 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g2SJuig34492; Thu, 28 Mar 2002 11:56:44 -0800 (PST) Date: Thu, 28 Mar 2002 11:56:43 -0800 (PST) From: Doug White To: Aditya Cc: freebsd-stable@FreeBSD.ORG Subject: Re: serial console vs. serial terminal In-Reply-To: <20020327212329.GA19556@mighty.grot.org> Message-ID: <20020328115551.R33831-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 27 Mar 2002, Aditya wrote: > On Wed, Mar 27, 2002 at 12:14:14PM -0800, Doug White wrote: > > > however, if I connect to them from a Cyclades T2000 terminal server using a > > > cat5 patch cable and a RJ45-DB9F modular adapter I can't type anything in but > > > I do see output (ie. from syslog). The most bizzare thing is if I reboot with: > > > > That sounds like the getty isn't coming up. It isn't complaining about > > cycling endlessly, is it? > > it isn't complaining and getty is definitely coming up as I can take a stock > db9-db9 null modem and interact fine... > > > Also make sure you're using the right pinout on your cable; the Cyclades > > pins aren't the same as Cisco's. We usually custom-build them. > > This is probably part of the "problem" -- using a patch cable I'm using the > following pinouts (essentially DCE), do you have a better set?: > > Pin # Signal Color > 2 TxD Black > - 3 RxD Yellow > 5 Gnd Red You should probably try a fully wired adapter. Unfortuantely I don't have the pinouts in front of me. > > It seems that your serial port(s) are locking up; the console output > > "wakes them up." Can you try connecting to the port with cu (in internal > > console, not serial) on the FreeBSD machine, ssh in to the TS2000 on the > > other, and talk between yourselves? > > yup, did that and when I type on either side I don't get a "local" echo but > see the output on the "remote" side... > > > AFAIK FreeBSD doesn't require carrier to be asserted for getty to wake up. > > If you hit a few times on the tty it should give you a login > > prompt. > > It's not taking input, but if I set syslogd to send *.err to * and then use > logger to syslog something, then it shows up... But you still can't get getty to wake up? It so happens we have a spare TS2000 in the office today, I'll try rigging it up. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message