From owner-freebsd-stable Fri Nov 24 0:33:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 2049D37B479 for ; Fri, 24 Nov 2000 00:33:22 -0800 (PST) Received: (from root@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id KAA16016; Fri, 24 Nov 2000 10:31:37 +0200 (SAST) From: User Support Message-Id: <200011240831.KAA16016@citadel.cequrux.com> Subject: Re: pccard woes In-Reply-To: <200011240358.UAA51466@harmony.village.org> from Warner Losh at "Nov 23, 0 08:58:48 pm" To: imp@village.org (Warner Losh) Date: Fri, 24 Nov 2000 10:31:37 +0200 (SAST) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sounds like a resource conflict introduced when you added the hard > disk. Do you have a demsg from before/after? It might also be a > conflict with memory. -1 is ff which is a common way things conflict. Actually it turned out I was wrong about it working under MS-Windows. Windows detected it as a 3Com OfficeConnect, but failed to bind an IP address to it. So it seemed to be getting further than FreeBSD, but there was still a problem. I opened up the machine to see if there were any damaged pins, but it looked okay. However, after I closed it back up the card started working. So it must just be a flaky connection somewhere. Sorry for the red herring regards gram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message