From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 17 22:18:36 2005 Return-Path: X-Original-To: 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 D274116A420; Thu, 17 Nov 2005 22:18:36 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65BE943D46; Thu, 17 Nov 2005 22:18:36 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jAHM4jR4002927; Thu, 17 Nov 2005 14:04:47 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jAHM3waR066063; Thu, 17 Nov 2005 14:03:58 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jAHM3wRW066062; Thu, 17 Nov 2005 14:03:58 -0800 (PST) (envelope-from jrhett) Date: Thu, 17 Nov 2005 14:03:58 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051117220358.GA65127@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <200511171030.36633.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511171030.36633.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: hardware@freebsd.org, freebsd-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 22:18:37 -0000 We can't. Serial A is a 9pin serial port, and Serial B is the rj45 console port. This is how the motherboard is built. We need Serial B to be the console. /boot/device.hints clearly indicates that 3f8 should map to sio1. Why isn't it using these hints? On Thu, Nov 17, 2005 at 10:30:35AM -0500, John Baldwin wrote: > 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. > 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? -- Joe Rhett senior geek SVcolo : Silicon Valley Colocation