From owner-freebsd-current@FreeBSD.ORG Wed Apr 21 23:31:34 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 AB8FD16A4CE for ; Wed, 21 Apr 2004 23:31:34 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3A3443D46 for ; Wed, 21 Apr 2004 23:31:33 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.217.162) by smtp01.syd.iprimus.net.au (7.0.024) id 402BA92701A53B05; Thu, 22 Apr 2004 16:31:23 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id D071841C9; Thu, 22 Apr 2004 17:34:37 +1000 (EST) Date: Thu, 22 Apr 2004 17:34:37 +1000 From: Tim Robbins To: "M. Warner Losh" Message-ID: <20040422073437.GA27099@cat.robbins.dropbear.id.au> References: <20040421171030.GA12125@profi.kharkov.ua> <20040422024059.GA25992@cat.robbins.dropbear.id.au> <20040421.232248.102959333.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040421.232248.102959333.imp@bsdimp.com> User-Agent: Mutt/1.4.1i 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 06:31:34 -0000 On Wed, Apr 21, 2004 at 11:22:48PM -0600, M. Warner Losh wrote: > 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... I thought atapci could have been stealing the I/O ports from sio, like what it was doing to fdc. Tim