From owner-freebsd-questions Thu Dec 30 14:43:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from greg.ad9.com (greg.ad9.com [209.233.225.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C9F1153C0 for ; Thu, 30 Dec 1999 14:43:14 -0800 (PST) (envelope-from nepolon@systray.com) Received: from greg.ad9.com (nepolon@greg.ad9.com [209.233.225.5]) by greg.ad9.com (8.9.1a/8.9.1) with ESMTP id OAA28715 for ; Thu, 30 Dec 1999 14:55:51 -0800 (PST) Date: Thu, 30 Dec 1999 14:55:51 -0800 (PST) From: Steve Lewis X-Sender: nepolon@greg.ad9.com To: freebsd-questions@FreeBSD.ORG Subject: Re: repeat: pci problem w/ de0 NIC In-Reply-To: <199912302229.XAA24368@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Oliver Fromme wrote: > The de0 driver supports only PCI cards. Hardware resources for > PCI cards (interrupt, memory ranges etc.) are allocated that's what I thought. > If you're _really_ sure that the chip on that card is 100% > hardware compatible with DEC 21x4x, you could hack the de0 > driver to accept that particular vendor/device IDs. Then > rebuild your kernel, reboot, and see what happens... I will need some assistance to get me going in the right direction if I choose to go this route but for the time being I am going to do a net install of (likely) 3.4 over the 3c509 which was working fine on the LAN in 2.2.8 > You could also avoid all of that hassle and just buy a real > DEC card (or some reasonable clone, like the Macronix MX) for > ~ $20. not an option anytime soon unfortunately. The only other thing I can do is scrounge another 3c509TP but I would rather avoid that option. --Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message