From owner-freebsd-stable Mon Oct 2 9:48:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 97C8F37B502 for ; Mon, 2 Oct 2000 09:48:07 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.10.1/8.10.1) with ESMTP id e92Gm4116808; Mon, 2 Oct 2000 12:48:04 -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 MAA37557; Mon, 2 Oct 2000 12:48:03 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id MAA38436; Mon, 2 Oct 2000 12:48:02 -0400 (EDT) Date: Mon, 2 Oct 2000 12:48:02 -0400 (EDT) From: Thomas David Rivers Message-Id: <200010021648.MAA38436@lakes.dignus.com> To: imp@village.org, rivers@dignus.com Subject: Re: 4.1-RELEASE pccard? Cc: freebsd-stable@FreeBSD.ORG, jim@siteplus.net In-Reply-To: <200010021644.KAA12130@harmony.village.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <200010021638.MAA38314@lakes.dignus.com> Thomas David Rivers writes: > : 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.) > > Hmmm. There have been a couple of commits to -stable/-current to the > ed driver since 4.1-RELEASE. There's a small chance that this card > needed additional support to get its interrupts working properly. > > I'd double check the BIOS just to make sure there isn't a PnP device > that wasn't enabled in 3.4 but that is now enabled. OK, so it's a > longshot. Well - nothing has changed since this morning when it was running 3.4-RELEASE (almost nothing, I've turned off/on PNP-OS with no discernable difference.) > Oh, the unknown driver now doesn't report anything but > failures unless you've done a boot verbose. Maybe that might be a > clue on how to proceed. Hmm... It would be nice to be able to enable a boot -v; but I seem to be in the throws of the new boot manager. I can't enable/disable things from the "ok" prompt (I can do an ls on the file system, which is nice) - perhaps this is the GENERIC kernel that got installed? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message