From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 17 05:11:39 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 E8D9216A41F for ; Thu, 17 Nov 2005 05:11:39 +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 450DF43D6E for ; Thu, 17 Nov 2005 05:11: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 jAH54ZQu086694 for ; Wed, 16 Nov 2005 21:04:36 -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 jAH53aTC072123 for ; Wed, 16 Nov 2005 21:03:36 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jAH53aXp072122 for hardware@freebsd.org; Wed, 16 Nov 2005 21:03:36 -0800 (PST) (envelope-from jrhett) Date: Wed, 16 Nov 2005 21:03:36 -0800 From: Joe Rhett To: hardware@freebsd.org Message-ID: <20051117050336.GB67653@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: Subject: 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 05:11:40 -0000 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? I'm more than happy to gather debug. I have a toy server set aside just to play with this stuff. Tell me what you need. -- Joe Rhett senior geek SVcolo : Silicon Valley Colocation