From owner-freebsd-questions Mon Dec 21 15:56:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13698 for freebsd-questions-outgoing; Mon, 21 Dec 1998 15:56:02 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from outcast.media-net.net (outcast.media-net.net [206.52.136.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13673 for ; Mon, 21 Dec 1998 15:55:57 -0800 (PST) (envelope-from chrisj@outcast.media-net.net) Received: from localhost (chrisj@localhost) by outcast.media-net.net (8.8.8/8.8.8) with SMTP id SAA22841 for ; Mon, 21 Dec 1998 18:08:22 -0600 (CST) (envelope-from chrisj@outcast.media-net.net) Date: Mon, 21 Dec 1998 18:08:21 -0600 (CST) From: Chris To: freebsd-questions@FreeBSD.ORG Subject: EISA ethernet card 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 hello all. what i am working on doing is getting a 3com 3c509b-TP card to work in a 2.2.6 box in a EISA slot. in using the ep driver the box will panic and crash at boot with this driver compiled into the kernel. what i am wondering is this. are the bugs with the ep driver wigging out when something on the same i/o address worked out in 2.2.8-RELEASE. i know that the xl driver has been added to 2.2.8 but it is to my understanding that this is for the PCI version of this card. if im barking up the wrong tree or making thing alot harder for myself a brisk boot to the head would be apricated. Thanks for your time Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message