From owner-freebsd-bugs Fri Mar 10 0: 0:20 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 51CB237B6F9 for ; Fri, 10 Mar 2000 00:00:14 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA45023; Fri, 10 Mar 2000 00:00:14 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Fri, 10 Mar 2000 00:00:14 -0800 (PST) Message-Id: <200003100800.AAA45023@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ted Mittelstaedt" Subject: Re: kern/15882: Etherexpress 16 doesn't work in 3.4 install Reply-To: "Ted Mittelstaedt" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15882; it has been noted by GNATS. From: "Ted Mittelstaedt" To: , Cc: Subject: Re: kern/15882: Etherexpress 16 doesn't work in 3.4 install Date: Thu, 9 Mar 2000 23:25:30 -0800 I have duplicated this behavior on FreeBSD 3.4 with the ie driver. The driver is recognizing the card, but it appears that it is not properly initializing the EtherExpress16 hardware. Link lights on the card that are normally lit are not. This was tested on a Win95 system that was being upgraded - the card worked fine when Win95 was running on the system. Also on the same hardware I have found that the 3com 3c507 is not being recognized by the driver, the driver reports an unknown board identifier error message, even though the driver lists support for it. I recommend combining this PR with PR i386/16214 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message