From owner-freebsd-stable Mon Oct 2 8:37:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F285B37B502 for ; Mon, 2 Oct 2000 08:37:27 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e92FbQI02426; Mon, 2 Oct 2000 09:37:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA11448; Mon, 2 Oct 2000 09:37:26 -0600 (MDT) Message-Id: <200010021537.JAA11448@harmony.village.org> To: Jim Weeks Subject: Re: 4.1-RELEASE pccard? Cc: Thomas David Rivers , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Oct 2000 10:54:14 EDT." References: Date: Mon, 02 Oct 2000 09:37:25 -0600 From: Warner Losh 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message