From owner-freebsd-current@FreeBSD.ORG Tue Sep 20 23:56:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 610BA16A41F; Tue, 20 Sep 2005 23:56:13 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBC0C43D48; Tue, 20 Sep 2005 23:56:12 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from [127.0.0.1] (c220-237-120-88.thorn1.nsw.optusnet.com.au [220.237.120.88]) by mail28.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j8KNu6J9015961; Wed, 21 Sep 2005 09:56:09 +1000 Message-ID: <4330A19B.6060905@mawer.org> Date: Wed, 21 Sep 2005 09:56:11 +1000 From: Antony Mawer User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Marcel Moolenaar References: <20050920110023.GA468@ip.net.ua> <6136.1127217196@critter.freebsd.dk> <20050920153044.GC468@ip.net.ua> <1127230793.30479.24.camel@buffy.york.ac.uk> <20050920172635.GA2811@ip.net.ua> <20050920211359.GA22676@ns1.xcllnt.net> In-Reply-To: <20050920211359.GA22676@ns1.xcllnt.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: serial ttys broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 20 Sep 2005 23:56:13 -0000 On 21/09/2005 7:13 AM, Marcel Moolenaar wrote: > On Tue, Sep 20, 2005 at 08:26:36PM +0300, Ruslan Ermilov wrote: >>> In my experience, you need to use: >>> >>> cuad0 "/usr/libexec/getty std.9600" dialup on secure >>> and not >>> ttyd0 "/usr/libexec/getty std.9600" dialup on secure >>> >>> in /etc/ttys to get a console on the serial port if you are not using -h >>> in /boot.config. I'm pretty sure it's been like this for a long time. >>> >>> What line have you got in /etc/ttys? >>> >> I've come to the same conclusion after also trying uart(4) instead >> of sio(4). > > Don't forget that DCD does not have to be asserted when the > serial line is used as serial console. When the serial line > is not used as serial console, DCD must be asserted. This > is not always the case with null-modem cables. > Change std.9600 to 3wire.9600 and don't use cua*. Use tty*. Thanks for this tip! I've been puzzling for a week now why my serial console wouldn't bring up a login prompt - using cuad0 works, but using 3wire.9600 with tty* instead of std.9600 also works. At some point I'll switch the main console over as well, but for the time being I just wanted to get a login via serial connection as a backup if I lose network connectivity for any reason (the machine runs headless). Cheers Antony