From owner-freebsd-stable Mon Oct 2 10:24:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 3424137B503 for ; Mon, 2 Oct 2000 10:24:08 -0700 (PDT) Received: from veager.siteplus.net (user-38lc8vb.dialup.mindspring.com [209.86.35.235]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id KAA17394; Mon, 2 Oct 2000 10:23:47 -0700 (PDT) Date: Mon, 2 Oct 2000 13:23:42 -0400 (EDT) From: Jim Weeks To: Warner Losh Cc: Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: 4.1-RELEASE pccard? In-Reply-To: <200010021537.JAA11448@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I see that now. I original had the timeouts caused by ed0/ed1, but that must have been because I had ed0 specified in pccard.conf. It would appear that changing the line to "config auto "ed" any 0x30000" would have cured my problem without recompiling the kernel. Yet another reason we keep Warner around ;-) -- Jim Weeks On Mon, 2 Oct 2000, Warner Losh wrote: > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message