Date: Mon, 22 Dec 2003 11:10:31 -0700 From: James Earl <james@icionline.ca> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: Continued problems with Aironet device and 5.2-RC Message-ID: <1072116630.576.4.camel@chero> In-Reply-To: <20031222.023045.32334013.imp@bsdimp.com> References: <20031222053002.GA872@cactus.homeunix.org> <20031222.012014.76871129.imp@bsdimp.com> <20031222092127.GA2355@cactus.homeunix.org> <20031222.023045.32334013.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2003-12-22 at 02:30, M. Warner Losh wrote: > In message: <20031222092127.GA2355@cactus.homeunix.org> > jqdkf@army.com writes: > : On Mon, Dec 22, 2003 at 01:20:14AM -0700, M. Warner Losh wrote: > : > In message: <20031222053002.GA872@cactus.homeunix.org> > : > jqdkf@army.com writes: > : > : cbb0: Unsupported card type detected > : > > : > This is typically a symptom of the resource allocation bugs I've been > : > fighting... > : > > : > : So are you suggesting that I should adjust the resource by myself, like > : irq numbers, for now? > > I have the unhelpful advice "make sure two devices aren't using the > same address." You'll likely have to decode all the BARs to make sure > that this is the case. So, would this be the reason why I haven't been able to get my an0 device to appear on it's own in the vmstat -i output? It seems the uhci2 device follows the an0 device to whatever irq I assign to it (an0) in the bios setup. James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1072116630.576.4.camel>