From owner-freebsd-stable Mon Oct 2 9:39: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id BFA9937B66D for ; Mon, 2 Oct 2000 09:39:06 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e92Gd2O19933; Mon, 2 Oct 2000 12:39:02 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id MAA37529; Mon, 2 Oct 2000 12:39:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id MAA38314; Mon, 2 Oct 2000 12:38:59 -0400 (EDT) Date: Mon, 2 Oct 2000 12:38:59 -0400 (EDT) From: Thomas David Rivers Message-Id: <200010021638.MAA38314@lakes.dignus.com> To: imp@village.org, jim@siteplus.net Subject: Re: 4.1-RELEASE pccard? Cc: freebsd-stable@FreeBSD.ORG, rivers@dignus.com In-Reply-To: <200010021537.JAA11448@harmony.village.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Jim Weeks writes: > : After you recompile the kernel this will cause the device to be recognized > : as ed0, the first device rather than ed1 that is being recognized now. > > This isn't a ed0 vs ed1 problem. He's got the device recognized, but > it is failing to generate interrupts (vmstat -i is your friend here, > btw). That's caused almost always by an attempt to use an interrupt > that another hunk of hardware, possibly w/o a driver, is using. > > Warner > I agree - this is most likely an interrupt problem. I don't _think_ anything is on 3 or 5... and I can't use 10 or 11. And, remember FreeBSD 3.4-RELEASE with PAO was able to handle this hardware just fine - just earlier this morning. I'm building a kernel with USB disabled - perhaps that contributes to the problem (i.e. stealing an interrupt.) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message