From owner-freebsd-current@FreeBSD.ORG Tue Sep 20 17:48:52 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 07CFF16A420; Tue, 20 Sep 2005 17:48:52 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACEEE43D73; Tue, 20 Sep 2005 17:48:43 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id j8KHmecN027534; Tue, 20 Sep 2005 18:48:40 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id j8KHmeVr032497; Tue, 20 Sep 2005 18:48:40 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id j8KHmdOB032496; Tue, 20 Sep 2005 18:48:39 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Ruslan Ermilov In-Reply-To: <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> <20050920172635.GA2811@ip.net.ua> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 20 Sep 2005 18:48:39 +0100 Message-Id: <1127238519.30479.35.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk 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:48:52 -0000 On Tue, 2005-09-20 at 20:26 +0300, Ruslan Ermilov wrote: > 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: > > > > > > > > > >>I have the following issues with serial on today's -CURRENT: > > > > > > > > > > Hmm, my box runs just as fine as always with serial console. > > > > > > > > > >>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. > > > > > > > > > > This is the first I hear about them... > > > > > > > > > > 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). > > > > > > > > > > > > > I probably should have piped up on -current, but yes, serial console is > > > > 'different' after the recent changes went into the boot loader. > > > > > > > > -P in /boot.config and the following in /etc/make.conf > > > > > > > > BOOT_COMCONSOLE_PORT=0x3F8 > > > > BOOT_COMCONSOLE_SPEED=115200 > > > > > > > > used to be enough for my boxes to work, but now (of course, only after a > > > > installworld for the bootloader) the following in /boot/loader.conf > > > > > > > > console=comconsole > > > > comconsole_speed=115200 > > > > > > > > seems to be required for serial console to work. > > > > > > > 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. > > > > 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). 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? FreeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: FreeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: HWV*Q)kB BJjHVKCCeeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: FreeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: CCreeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: FreeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: CCeeBSD/i386 (buffy.york.ac.uk) (ttyd0) login: Yes. And that's with ttyd0, not cuaa0, and a Windows machine at the far end of a 9600 baud link. A configuration which I'm pretty sure should perform better. No matter how hard I try, I can't manage to reproduce the corruption once logged in, unless I explicitly run /usr/libexec/getty from the shell, in which case the corruption is even worse: loi:cCreeBSDi36(ff.or.c.(tt0 loi: reeBSDi36(ff.or.c.(tt0 loi: reeBSDi36(ff.or.c.(tt0 loi: reeBSDi36(ff.or.c.(tt0loi: reeBSDi36(ff.or.c.(tt0 loi:cCeeBSDi36(ff.or.c.(tt0 Guess there may be some issue with getty? Gavin