Date: Mon, 2 Oct 2000 12:48:02 -0400 (EDT) From: Thomas David Rivers <rivers@dignus.com> To: imp@village.org, rivers@dignus.com Cc: freebsd-stable@FreeBSD.ORG, jim@siteplus.net Subject: Re: 4.1-RELEASE pccard? Message-ID: <200010021648.MAA38436@lakes.dignus.com> In-Reply-To: <200010021644.KAA12130@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010021648.MAA38436>