From owner-freebsd-questions@FreeBSD.ORG Tue Jun 1 06:19:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EC5F16A4CE for ; Tue, 1 Jun 2004 06:19:54 -0700 (PDT) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC21943D39 for ; Tue, 1 Jun 2004 06:19:52 -0700 (PDT) (envelope-from richard.williamson@u4eatech.com) Received: by mail.u4eatech.com (Postfix, from userid 503) id 034713602ED; Tue, 1 Jun 2004 14:19:51 +0100 (BST) Received: from apus.u4eatech.com (apus.degree2.com [172.30.40.129]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.u4eatech.com (Postfix) with ESMTP id 068AE3602E7; Tue, 1 Jun 2004 14:19:47 +0100 (BST) Message-Id: <6.1.0.6.2.20040601140015.0accf008@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Tue, 01 Jun 2004 14:20:29 +0100 To: Simon Barner , freebsd-questions@freebsd.org From: "Richard P. Williamson" In-Reply-To: <20040601115441.GA87441@zi025.glhnet.mhn.de> References: <20040601110940.GA65805@marvin.penguinpowered.org> <20040601115441.GA87441@zi025.glhnet.mhn.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 Subject: Re: Intel Ethernet card not being detected X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 13:19:54 -0000 Hi Simon, At 12:54 01/06/2004. Simon Barner had this to say: >Wayne Pascoe wrote: >> Hi all, >> >> I just bought a server from DNUK . It claims to have the following >> Ethernet card combination: >> > >Probably only the device ID of the card is not listed in the fxp0 driver. > >Your case reminds of a very similar problem in c.o.f.m., where the >following made the card (also Intel) work (a PR has already been filed): > > >Try adding the following line into the following struct >static struct fxp_ident fxp_ident_table[] >(/usr/src/sys/dev/fxp/if_fxp.c) > > { 0x1051, -1, "Intel 82562ET Pro/100 Ethernet" }, > > >This was a Tyan S5102G3NR motherboard with 3 onboard NICs. Of course, >the correct name for your NIC might be different, but that shouldn't >bee too much of a problem. I'm having a similar problem, in fact I posted a query on freebsd-questions last week (subject: miibus and fxp motherboard devices). The on-board NICs are being seen, however they aren't being configured fully. I have a 3 onboard NIC motherboard; I've asked the supplier for the manufacturer's name of the motherboard. I've tried adding the 0x1051 line to my if_fxp.c file, but it did not have any effect. This is ifconfig for fxp0 and fxp3, being the first motherboard mounted and an external pci-card mounted version of the same chip: fxp0: flags=8843 mtu 1500 inet x.y.z.a netmask 0xffff0000 broadcast x.y.z.255 ether 00:30:64:01:86:ff media: Ethernet manual fxp3: flags=8802 mtu 1500 ether 00:30:64:01:81:18 media: Ethernet autoselect (none) status: no carrier This is the comparable dmesg: fxp0: port 0xd400-0xd43f mem \ 0xe7200000-0xe72fffff,0xe7302000-0xe7302fff irq 11 at device 8.0 on pci0 fxp0: Ethernet address 00:30:64:01:86:ff, 10Mbps fxp3: port 0xc000-0xc03f mem \ 0xe6000000-0xe60fffff,0xe6201000-0xe6201fff irq 10 at device 12.0 on pci3 fxp3: Ethernet address 00:30:64:01:81:18 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Note how the external is on the miibus while the on-board isn't, and that the supported media types list 10baseT etc whereas the on-board simply support 10Mbps (manual). This is pciconf: fxp0@pci0:8:0: class=0x020000 card=0x00000000 chip=0x12298086 \ rev=0x08 hdr=0x00 fxp3@pci3:12:0: class=0x020000 card=0x00018086 chip=0x12298086 \ rev=0x08 hdr=0x00 Aside from experimentation, is there a way to determine what the correct value is that should go into the if_fxp.c known-devices array, if that is in fact the problem? Thank you for your help, Regards, Richard Williamson dmesg: >Copyright (c) 1992-2003 The FreeBSD Project. >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. >FreeBSD 4.8-RELEASE #1: Fri May 28 16:56:45 BST 2004 > root@centauri:/usr/src/sys/compile/FFPRO_MINI >Timecounter "i8254" frequency 1193182 Hz >Timecounter "TSC" frequency 1266717239 Hz >CPU: Intel(R) Pentium(R) III CPU family 1266MHz (1266.72-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 > Features=0x383f9ff >real memory = 268369920 (262080K bytes) >avail memory = 208556032 (203668K bytes) >Preloaded elf kernel "kernel" at 0xc3297000. >Preloaded mfs_root "/mfsroot" at 0xc329709c. >Pentium Pro MTRR support enabled >md0: Preloaded image 50331648 bytes at 0xc0295794 >md1: Malloc disk >Using $PIR table, 9 entries at 0xc00fdee0 >npx0: on motherboard >npx0: INT 16 interface >pcib0: on motherboard >pci0: on pcib0 >pcib1: at device 1.0 on pci0 >pci1: on pcib1 >isab0: at device 7.0 on pci0 >isa0: on isab0 >atapci0: port 0xe000-0xe00f at device 7.1 on pci0 >ata0: at 0x1f0 irq 14 on atapci0 >ata1: at 0x170 irq 15 on atapci0 >pci0: at 7.2 irq 10 >pci0: (vendor=0x1106, dev=0x3057) at 7.4 >fxp0: port 0xd400-0xd43f mem 0xe7200000-0xe72fffff,0xe7302000-0xe7302fff irq 11 at device 8.0 on pci0 >fxp0: Ethernet address 00:30:64:01:86:ff, 10Mbps >fxp1: port 0xd800-0xd83f mem 0xe7000000-0xe70fffff,0xe7301000-0xe7301fff irq 5 at device 9.0 on pci0 >fxp1: Ethernet address 00:30:64:01:94:00, 10Mbps >fxp2: port 0xdc00-0xdc3f mem 0xe7100000-0xe71fffff,0xe7300000-0xe7300fff irq 12 at device 10.0 on pci0 >fxp2: Ethernet address 00:30:64:01:94:01, 10Mbps >pcib2: at device 13.0 on pci0 >pci2: on pcib2 >pcib3: at device 15.0 on pci2 >pci3: on pcib3 >fxp3: port 0xc000-0xc03f mem 0xe6000000-0xe60fffff,0xe6201000-0xe6201fff irq 10 at device 12.0 on pci3 >fxp3: Ethernet address 00:30:64:01:81:18 >inphy0: on miibus0 >inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >fxp4: port 0xc400-0xc43f mem 0xe6100000-0xe61fffff,0xe6200000-0xe6200fff irq 11 at device 13.0 on pci3 >fxp4: Ethernet address 00:30:64:01:81:19 >inphy1: on miibus1 >inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >vt0 on isa0 >vt0: mda, mono, 8 scr, unknown kbd, [R3.20-b24] >vt0: driver is using old-style compatability shims >atkbdc0: at port 0x60,0x64 on isa0 >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >sio0: type 16550A, console >sio1 at port 0x2f8-0x2ff irq 3 on isa0 >sio1: type 16550A >sio2: configured irq 5 not in bitmap of probed irqs 0 >vga0: at port 0x3b0-0x3bb iomem 0xb0000-0xb7fff on isa0 >ad0: 30MB [490/4/32] at ata0-master PIO1 pciconf -lv: >chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x06911106 rev=0xc4 hdr=0x00 > class = bridge > subclass = HOST-PCI >pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0x85981106 rev=0x00 hdr=0x01 > class = bridge > subclass = PCI-PCI >isab0@pci0:7:0: class=0x060100 card=0x00001106 chip=0x06861106 rev=0x40 hdr=0x00 > class = bridge > subclass = PCI-ISA >atapci0@pci0:7:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x06 hdr=0x00 > class = mass storage > subclass = ATA >none0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x1a hdr=0x00 > class = serial bus > subclass = USB >none1@pci0:7:4: class=0x068000 card=0x30571106 chip=0x30571106 rev=0x40 hdr=0x00 > class = bridge > subclass = PCI-unknown >fxp0@pci0:8:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 > class = network > subclass = ethernet >fxp1@pci0:9:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 > class = network > subclass = ethernet >fxp2@pci0:10:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 > class = network > subclass = ethernet >pcib2@pci0:13:0: class=0x060400 card=0x000000dc chip=0x00241011 rev=0x03 hdr=0x01 > class = bridge > subclass = PCI-PCI >pcib3@pci2:15:0: class=0x060400 card=0x000000dc chip=0xb1548086 rev=0x00 hdr=0x01 > class = bridge > subclass = PCI-PCI >fxp3@pci3:12:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x08 hdr=0x00 > class = network > subclass = ethernet >fxp4@pci3:13:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x08 hdr=0x00 > class = network > subclass = ethernet