Date: Thu, 22 Apr 2004 17:34:37 +1000 From: Tim Robbins <tjr@freebsd.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: where is my sio1? Message-ID: <20040422073437.GA27099@cat.robbins.dropbear.id.au> In-Reply-To: <20040421.232248.102959333.imp@bsdimp.com> References: <20040421171030.GA12125@profi.kharkov.ua> <20040422024059.GA25992@cat.robbins.dropbear.id.au> <20040421.232248.102959333.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <tjr@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040422073437.GA27099>