From owner-freebsd-current@FreeBSD.ORG Mon Mar 4 20:00:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E5B1F7FA; Mon, 4 Mar 2013 20:00:51 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [70.91.206.90]) by mx1.freebsd.org (Postfix) with ESMTP id AF8F9110F; Mon, 4 Mar 2013 20:00:51 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 04 Mar 2013 12:02:14 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.4/8.14.4) with ESMTP id r24Jxg6a076231; Mon, 4 Mar 2013 11:59:42 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.4/8.14.4/Submit) id r24Jxg3a076229; Mon, 4 Mar 2013 11:59:42 -0800 (PST) (envelope-from ambrisko) Date: Mon, 4 Mar 2013 11:59:42 -0800 From: Doug Ambrisko To: "Eggert, Lars" Subject: Re: serial console not accepting input? Message-ID: <20130304195942.GA56928@ambrisko.com> References: <51000A18.1020001@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "freebsd-current@freebsd.org" , Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Mar 2013 20:00:52 -0000 On Thu, Jan 24, 2013 at 01:23:50PM +0000, Eggert, Lars wrote: | Hi, | | On Jan 23, 2013, at 17:04, Dimitry Andric wrote: | > CTS/RTS hardware flow control, maybe? E.g. add ":hw" to the default | > settings in /etc/gettytab, or make a specific entry with an added ":hw" | > setting. | | nope, I don't even get a login prompt if I do that. | | > If it is a physical serial console, you could also simply have a bad | > cable. Try swapping it with working system. :) | | Spent the last few hours fiddling with the cabling and the various BIOS | serial redirection options (it's a Dell 2950). My best guess is that | the serial port on the box is physically broken. Try to do a {Ctrl}D to see if works. We've seen that the TX on reset hangs but input works fine. I'm not sure if we ran into this with uart(4) but had a problem with sio(4). Doug A.