From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 23:34:28 2003 Return-Path: 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 AB58E37B401 for ; Wed, 2 Apr 2003 23:34:28 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B75343FB1 for ; Wed, 2 Apr 2003 23:34:27 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA24798; Thu, 3 Apr 2003 17:34:15 +1000 Date: Thu, 3 Apr 2003 17:34:14 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Cagle, John (ISS-Houston)" In-Reply-To: Message-ID: <20030403172912.A29833@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: RE: sio problem in -current (COM1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 03 Apr 2003 07:34:29 -0000 On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: > Thanks! It was an ACPI-related problem. I disabled ACPI > (hint.acpi.0.disabled="1" in /boot/device.hints) and rebooted and now > both com ports show up properly as they did with FreeBSD 4.8. (These > are just standard com ports, btw.) We still don't know why acpi sometimes gets this wrong. > I didn't realize ACPI was involved in legacy com port detection. That's > weird. It seems to be used for most legacy ports. IIRC, it found all except 2 or 3 devices according to your boot messages, with the vga devices being an interesting exception (most vga devices are too new to even support pci). Bruce