From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 23 18:18:39 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D012937B401 for ; Mon, 23 Jun 2003 18:18:39 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF02643FA3 for ; Mon, 23 Jun 2003 18:18:35 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-3.aaa.net.au [203.14.230.68]) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h5O1GvCt019200; Tue, 24 Jun 2003 11:16:58 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h5O1HgWO077848; Tue, 24 Jun 2003 11:17:48 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h5NMZUhS077709; Tue, 24 Jun 2003 08:35:30 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Tue, 24 Jun 2003 08:35:30 +1000 (EST) From: Andrew MacIntyre To: Menno V In-Reply-To: <20030623133730.31180.qmail@bsdmail.com> Message-ID: <20030624083141.K77684@bullseye.apana.org.au> References: <20030623133730.31180.qmail@bsdmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) cc: freebsd-hardware@freebsd.org Subject: Re: onboard intel pro 100 ve problems on 4.8 rel and 5.1 rel X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 01:18:40 -0000 [posted & mailed] On Mon, 23 Jun 2003, Menno V wrote: > On my Dell dimension 8300, I can't get my onboard intel pro 100 ve NIC > working on FreeBSD. Windows says it's an "Intel(R) PRO/100 VE Network > Connection". In Windows and Linux everything seems to work fine. When I > try to use it on FreeBSD it doesn't even show up in the dmesg output, > while I'm using a generic kernel (fxp is included). Looking through the dmesg output, there are a number of devices. At a guess, I would suggest that your NIC is one of these. You could try identifying which by the PCI ids, and then try adding that PCI id to the fxp source files and rebuild the kernel. If it works, send-pr a patch. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia