From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 12 04:14:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A1E937B408 for ; Thu, 12 Jun 2003 04:14:57 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F53543F3F for ; Thu, 12 Jun 2003 04:14:55 -0700 (PDT) (envelope-from alsbergt@cs.huji.ac.il) Received: from lurch.cs.huji.ac.il ([132.65.80.139] ident=exim) by cs.huji.ac.il with esmtp id 19QQ2g-0008ko-00 for freebsd-hackers@freebsd.org; Thu, 12 Jun 2003 14:14:54 +0300 Received: from alsbergt by lurch.cs.huji.ac.il with local (Exim 4.12) id 19QQ2g-00061C-00 for freebsd-hackers@freebsd.org; Thu, 12 Jun 2003 14:14:54 +0300 Date: Thu, 12 Jun 2003 14:14:53 +0300 From: Tom Alsberg To: FreeBSD Hackers List Message-ID: <20030612111453.GA23053@cs.huji.ac.il> Mail-Followup-To: Tom Alsberg , FreeBSD Hackers List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Face: "5"j@Y1Peoz1; ftTv>\|['ox-csmV+:_RDNdi/2lSe2x?0:HVAeVW~ajwQ7RfDlcb^18eJ; t,O,s5-aNdU/DJ2E8h1s,..4}N9$27u`pWmH|; s!zlqqVwr9R^_ji=1\3}Z6gQBYyQ]{gd5-V8s^fYf{$V2*_&S>eA|SH@Y\hOVUjd[5eah{EO@gCr.ydSpJHJIU[QsH~bC?$C@O:SzF=CaUxp80-iknM(]q(W List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2003 11:14:57 -0000 Having got a new machine here a few days ago, an Intel ICH D865 PERL board based Pentium IV machine, with an on-board Intel EtherExpress Pro 100 VE, it failed to detect the network adapter. Seeing that it is an EtherExpress Pro 100, I though the fxp module should work with it, and found out that the PCI ID (8086:1050) just isn't recognized as one (new chip or something, apparently). With the following patch to if_fxp.c: --- sys/dev/fxp/if_fxp.c.orig Thu Jun 12 14:08:22 2003 +++ sys/dev/fxp/if_fxp.c Thu Jun 12 13:29:37 2003 @@ -162,6 +162,7 @@ { 0x103C, "Intel 82801DB (ICH4) Pro/100 Ethernet" }, { 0x103D, "Intel 82801DB (ICH4) Pro/100 VE Ethernet" }, { 0x103E, "Intel 82801DB (ICH4) Pro/100 VM Ethernet" }, + { 0x1050, "Intel 82801BA (D865) Pro/100 VE Ethernet" }, { 0x1059, "Intel 82551QM Pro/100 M Mobile Connection" }, { 0x1209, "Intel 82559ER Embedded 10/100 Ethernet" }, { 0x1229, "Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet" }, it seems to work. I am not sure how reliable it is and whether other modifications should be made, but it worked fine for now. Of course, the ID string is also perhaps not the best - perhaps it needs to be changed. Anyway, I would like it to be added to the driver, so new machines with that adapter will work out of the box. Should I submit this trivial patch to anywhere else, or can it be picked up from this list? BTW, I had the same story with Linux (that's what they wanted on it, I was just diagnosing the problem) before, and a similar change to the Linux eepro100 driver worked as well - had it worked with Linux out of the box, I wouldn't probably try FreeBSD on it... Thanks, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.