From owner-freebsd-stable Wed Mar 27 13:23:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mighty.grot.org (mighty.grot.org [204.182.56.120]) by hub.freebsd.org (Postfix) with ESMTP id A8E0137B416 for ; Wed, 27 Mar 2002 13:23:35 -0800 (PST) Received: by mighty.grot.org (Postfix, from userid 515) id BA5C75E9F; Wed, 27 Mar 2002 13:23:29 -0800 (PST) Date: Wed, 27 Mar 2002 13:23:29 -0800 From: Aditya To: Doug White Cc: freebsd-stable@FreeBSD.ORG Subject: Re: serial console vs. serial terminal Message-ID: <20020327212329.GA19556@mighty.grot.org> Reply-To: Aditya References: <20020327014305.GA81311@mighty.grot.org> <20020327120918.A85588-100000@resnet.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020327120918.A85588-100000@resnet.uoregon.edu> X-PGP-Key: http://www.grot.org/pubkey.asc X-PGP-Key-ID: 0x6405D8D5 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, 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 > 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... Thanks, Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message