From owner-freebsd-current@FreeBSD.ORG Tue Sep 20 17:26:25 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 96E8716A41F for ; Tue, 20 Sep 2005 17:26:25 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F4543D46 for ; Tue, 20 Sep 2005 17:26:24 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j8KHQKDf040686; Tue, 20 Sep 2005 20:26:20 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 04671-04; Tue, 20 Sep 2005 20:26:20 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j8KHQJW2040683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Sep 2005 20:26:19 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.3/8.13.3) id j8KHQaNX002869; Tue, 20 Sep 2005 20:26:36 +0300 (EEST) (envelope-from ru) Date: Tue, 20 Sep 2005 20:26:36 +0300 From: Ruslan Ermilov To: Gavin Atkinson Message-ID: <20050920172635.GA2811@ip.net.ua> References: <20050920110023.GA468@ip.net.ua> <6136.1127217196@critter.freebsd.dk> <20050920153044.GC468@ip.net.ua> <1127230793.30479.24.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <1127230793.30479.24.camel@buffy.york.ac.uk> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua 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 17:26:25 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 20, 2005 at 04:39:53PM +0100, Gavin Atkinson wrote: > On Tue, 2005-09-20 at 18:30 +0300, Ruslan Ermilov wrote: > > On Tue, Sep 20, 2005 at 07:27:13AM -0700, othermark wrote: > > > Poul-Henning Kamp wrote: > > > > In message <20050920110023.GA468@ip.net.ua>, Ruslan Ermilov writes: > > > >=20 > > > >>I have the following issues with serial on today's -CURRENT: > > > >=20 > > > > Hmm, my box runs just as fine as always with serial console. > > > >=20 > > > >>2) If booted with -h, as most people are doing, but without > > > >> the recently added -S option to boot2, serial console > > > >> works in 9600 bps as advertised, but despite std.9600 in > > > >> /etc/ttys, the speed is set to 115200. > > > >> > > > >>My configuration is pretty much GENERIC. Rumors are that these > > > >>issues aren't new. > > > >=20 > > > > This is the first I hear about them... > > > >=20 > > > > I won't have time to look at it for the next several weeks > > > > (unless it happens on my machine and forces me to handle it). > > > >=20 > > >=20 > > > I probably should have piped up on -current, but yes, serial console = is > > > 'different' after the recent changes went into the boot loader. > > >=20 > > > -P in /boot.config and the following in /etc/make.conf > > >=20 > > > BOOT_COMCONSOLE_PORT=3D0x3F8 > > > BOOT_COMCONSOLE_SPEED=3D115200 > > >=20 > > > used to be enough for my boxes to work, but now (of course, only afte= r a > > > installworld for the bootloader) the following in /boot/loader.conf > > >=20 > > > console=3Dcomconsole > > > comconsole_speed=3D115200 > > >=20 > > > seems to be required for serial console to work. > > >=20 > > Serial console aside, can you PLEASE verify that you can get > > getty(8) working on the first serial port if it is NOT set up as > > a serial console? That is, with an empty /boot.config and > > default syscons console, can you get a login: prompt on a > > serial port? I cannot, on neither of my -current machines, > > nor i386 nor amd64. People I asked around report the same. >=20 > In my experience, you need to use: >=20 > cuad0 "/usr/libexec/getty std.9600" dialup on secure > and not > ttyd0 "/usr/libexec/getty std.9600" dialup on secure >=20 > 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. >=20 > What line have you got in /etc/ttys? >=20 I've come to the same conclusion after also trying uart(4) instead of sio(4). Odd, but I can confirm that getty works on cua* devices while tty* do not. Also, if at the getty prompt I press quickly, I consistently get the garbage. Do you also see it? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDMEZLqRfpzJluFF4RAsw/AJ0YwIoeXKgEHbcKmF9sF4ZxQ67uoQCfTuQH 7oIym82rv0FRFLH/+NxhOf0= =dWei -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--