From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 17 16:04:40 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CC0716A41F; Thu, 17 Nov 2005 16:04:40 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC1D43D46; Thu, 17 Nov 2005 16:04:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2123113 for multiple; Thu, 17 Nov 2005 11:04:41 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAHG4YTc022588; Thu, 17 Nov 2005 11:04:34 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 17 Nov 2005 10:30:35 -0500 User-Agent: KMail/1.8.2 References: <20051117050336.GB67653@svcolo.com> In-Reply-To: <20051117050336.GB67653@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171030.36633.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Joe Rhett , hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 16:04:40 -0000 On Thursday 17 November 2005 12:03 am, Joe Rhett wrote: > This is funny. This is true in both 5.4-RELEASE and 6.0-RELEASE > > 1. Plug serial connection into com1, configure as console > 2. Edit /etc/ttys, enable ttyd0 > 3. set console=comconsole in /boot/loader.conf > 4. Boot system (generic kernel) -- all output goes to com1 > 5. No login prompt... > > Edit /etc/ttys, enable ttyd1 > kill -HUP 1 > Login prompt > > devinfo -r shows > > sio0 > Interrupt request lines: > 0x3 > I/O ports: > 0x2f8-0x2ff > sio1 > Interrupt request lines: > 0x4 > I/O ports: > 0x3f8-0x3ff > > > So... so COM1 is sio0/ttyd0 until the system finishes booting, at which > time it swap with com2 and becomes sio1/ttyd1 ? > > NOTE: in the BIOS I've assigned 3f8/int4 to serial B, and 2f8/int3 to > serial A. But why would sio assignments be tied to the hardware order > instead of the io assignments? And better yet, why would they swap during > the boot process? The boot process has an I/O port (3f8) hardcoded by default. However, the kernel enumerates devices based on what the BIOS tells us, and since you have serial A setup as COM2 resources and serial B setup as COM1 resources, the BIOS will list serial A first, so sio0 will get serial A and thus COM2. Try fixing your BIOS to map serial A to COM1. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org