From owner-freebsd-current@FreeBSD.ORG Wed Apr 21 22:22:44 2004 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 5CC5316A4CE; Wed, 21 Apr 2004 22:22:44 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF80143D2D; Wed, 21 Apr 2004 22:22:43 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i3M5Mhgr058987; Wed, 21 Apr 2004 23:22:43 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 21 Apr 2004 23:22:48 -0600 (MDT) Message-Id: <20040421.232248.102959333.imp@bsdimp.com> To: tjr@freebsd.org From: "M. Warner Losh" In-Reply-To: <20040422024059.GA25992@cat.robbins.dropbear.id.au> References: <20040421171030.GA12125@profi.kharkov.ua> <20040422024059.GA25992@cat.robbins.dropbear.id.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: greg@profi.kharkov.ua cc: freebsd-current@freebsd.org Subject: Re: where is my sio1? 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, 22 Apr 2004 05:22:44 -0000 In message: <20040422024059.GA25992@cat.robbins.dropbear.id.au> Tim Robbins writes: : On Wed, Apr 21, 2004 at 08:10:30PM +0300, Gregory Edigarov wrote: : : > Hello, : > : > I have an Asus P4C800 with 2 integrated COM ports. : > They are enabled in BIOS and connected. However FreeBSD-current : > (today's build) was only able to found sio0. : > What can I do? They both are enabled in /boot/device.hints. : : Update your source tree and try again. Warner Losh has recently fixed : a PCI resource allocation bug that could cause this kind of behaviour. : If you're still having problems after that, post a verbose dmesg to the : list (boot -v or the equiv. option from the beastie menu.) I'm thinking that maybe it won't matter for this sort of thing... Warner