From owner-freebsd-stable@FreeBSD.ORG Fri Oct 27 21:24:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32F1816A417 for ; Fri, 27 Oct 2006 21:24:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9609043D55 for ; Fri, 27 Oct 2006 21:24:49 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id k9RLOnMA031379; Fri, 27 Oct 2006 17:24:49 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id k9RLOm35038512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Oct 2006 17:24:48 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200610272124.k9RLOm35038512@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 27 Oct 2006 17:22:50 -0400 To: "Jack Vogel" From: Mike Tancsa In-Reply-To: <2a41acea0610270933v687b91e8n1ffbf9e35e073eb6@mail.gmail.co m> References: <20061027160515.GH84252@home.c0mplx.org> <2a41acea0610270933v687b91e8n1ffbf9e35e073eb6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Intel device IDs (Intel S5000PAL board, onboard ether gige interfaces working?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 21:24:50 -0000 At 12:33 PM 10/27/2006, Jack Vogel wrote: >On 10/27/06, Kurt Jaeger wrote: >>Hi! >> >>Can someone report success with the onboard GigE ports of an >>Intel S5000PAL board ? >> >>Thanks for any report 8-} > >This is one of our new systems, the onboard NICs require either >the latest driver you can download from Intel, or the community >STABLE that is named after my Intel driver (6.1.4). Hi, Speaking of device IDs, I picked up a new Intel 946GZis MB that has an Intel 10/100 (I am guessing fxp?) thats not recognized by the stock fxp driver. Is it safe to just add the device IDs? The box part # says boxd946gzissl none3@pci4:8:0: class=0x020000 card=0x00018086 chip=0x10948086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet I am not sure if the name is quite right [r6-32bit]# diff -c if_fxp.c.orig if_fxp.c *** if_fxp.c.orig Fri Oct 27 17:02:21 2006 --- if_fxp.c Fri Oct 27 17:03:21 2006 *************** *** 179,184 **** --- 179,185 ---- { 0x1068, -1, "Intel 82801FBM (ICH6-M) Pro/100 VE Ethernet" }, { 0x1069, -1, "Intel 82562EM/EX/GX Pro/100 Ethernet" }, { 0x1092, -1, "Intel Pro/100 VE Network Connection" }, + { 0x1094, -1, "Intel Pro/100 946GZ (ICH7) Network Connection" }, { 0x1209, -1, "Intel 82559ER Embedded 10/100 Ethernet" }, { 0x1229, 0x01, "Intel 82557 Pro/100 Ethernet" }, { 0x1229, 0x02, "Intel 82557 Pro/100 Ethernet" }, [r6-32bit]# but it seems to work [r6-32bit]% grep -i fxp /var/run/dmesg.boot fxp0: port 0x1100-0x113f mem 0x90000000-0x90000fff irq 20 at device 8.0 on pci4 miibus1: on fxp0 fxp0: Ethernet address: 00:16:76:be:96:ce fxp0: link state changed to DOWN fxp0: link state changed to UP fxp0: port 0x1100-0x113f mem 0x90000000-0x90000fff irq 20 at device 8.0 on pci4 miibus1: on fxp0 fxp0: Ethernet address: 00:16:76:be:96:ce [r6-32bit]% [r6-32bit]% fxp0@pci4:8:0: class=0x020000 card=0x00018086 chip=0x10948086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet [r6-32bit]#