From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 16:04:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2726FF20 for ; Wed, 23 Jan 2013 16:04:49 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id DF37AD62 for ; Wed, 23 Jan 2013 16:04:48 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:2150:ab85:542c:b811] (unknown [IPv6:2001:7b8:3a7:0:2150:ab85:542c:b811]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A83065C43; Wed, 23 Jan 2013 17:04:40 +0100 (CET) Message-ID: <51000A18.1020001@FreeBSD.org> Date: Wed, 23 Jan 2013 17:04:40 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: "Eggert, Lars" , "freebsd-current@freebsd.org" Subject: Re: serial console not accepting input? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 23 Jan 2013 16:04:49 -0000 On 2013-01-23 16:43, Eggert, Lars wrote: > I'm embarrassed to ask this newbie question, but I'm at my wit's end: I've configured a serial console according to the handbook. I see the boot messages and get the login prompt. But at no point during the boot process does the console seem to accept any input, incl. when at the boot prompt. The same serial setup works fine with other boxes. > > Any ideas? 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. If it is a physical serial console, you could also simply have a bad cable. Try swapping it with working system. :)