From owner-freebsd-questions@FreeBSD.ORG Fri Jun 25 14:52:50 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 14E4516A4CE for ; Fri, 25 Jun 2004 14:52:50 +0000 (GMT) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B13843D39 for ; Fri, 25 Jun 2004 14:52:49 +0000 (GMT) (envelope-from richard.williamson@u4eatech.com) Received: by mail.u4eatech.com (Postfix, from userid 503) id 134EB36079E; Fri, 25 Jun 2004 15:52:21 +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 7A93336079A; Fri, 25 Jun 2004 15:52:09 +0100 (BST) Message-Id: <6.1.1.1.2.20040625152908.027992a0@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Fri, 25 Jun 2004 15:45:58 +0100 To: Simon Barner , freebsd-questions@freebsd.org From: "Richard P. Williamson" In-Reply-To: <20040601143002.GB35382@zi025.glhnet.mhn.de> References: <20040601110940.GA65805@marvin.penguinpowered.org> <20040601115441.GA87441@zi025.glhnet.mhn.de> <6.1.0.6.2.20040601140015.0accf008@cygnus> <20040601143002.GB35382@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: Fri, 25 Jun 2004 14:52:50 -0000 Simon, All: At 15:30 01/06/2004. Simon Barner had this to say: >I just had a look at that older post of yours, and I saw that you are >still running FreeBSD 4.8. Could you consider upgrading to 4.10-RELEASE or >-STABLE? >... >IMO there's a really good chance that upgrading will make your onboard >NICs work properly. Sadly, no joy. To refresh, I'm using an adlink ebc-2000 (supplied by Ecrin Systems in France). It has 3 on-board NICs that are identified as by the kernel during boot (which agrees with adlink's datasheet for this device). The devices do not come up under the miibus device, however, and run in 'cripple-mode'. They work, but at 10Mb. If I try to change that by using ifconfig fxp0 media commands, I get: ifconfig: SIOCSIFMEDIA: Device not configured ifconfig fxp0 reports: fxp0: flags=8843 mtu 1500 inet x.y.z.188 netmask 0xffff0000 broadcast x.y.z.255 ether 00:30:64:gh:ij:kl media: Ethernet manual Additionally, there are two other fxp devices on a PCI plug-in card, and they come up happy. dmesg: Copyright (c) 1992-2004 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.10-RELEASE #1: Fri Jun 25 13:06:22 GMT 2004 rip@venus:/usr/src/sys/compile/MINI Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1266716809 Hz CPU: Intel(R) Pentium(R) III CPU family 1266MHz (1266.72-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff ... fxp0: port 0xd400-0xd43f mem 0xe7200000-0xe72fffff,0xe7302000-0xe7302fff irq 11 at device 8.0 on pci0 fxp0: Ethernet address 00:30:64:gh:ij:kl, 10Mbps fxp1: port 0xd800-0xd83f mem 0xe7000000-0xe70fffff,0xe7301000-0xe7301fff irq 5 at device 9.0 on pci0 fxp1: Ethernet address 00:30:64:gh:ij:kl, 10Mbps fxp2: port 0xdc00-0xdc3f mem 0xe7100000-0xe71fffff,0xe7300000-0xe7300fff irq 12 at device 10.0 on pci0 fxp2: Ethernet address 00:30:64:gh:ij:kl, 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:gh:ij:kl 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:gh:ij:kl inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ... pciconf -l reports: fxp0@pci0:8:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 fxp1@pci0:9:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 fxp2@pci0:10:0: class=0x020000 card=0x00000000 chip=0x12298086 rev=0x08 hdr=0x00 (note the card=0x00000000. Hm.) So, if you've read this far, 1) It says 'Ethernet manual'. Does that mean that there will be a method (ioctl or similar) in the driver that allows me to make explicit calls to the devices to configure 100Mb full duplex, for example, or even Auto if it is supported. Before you say 'look at the code yourself', assume that I'm doing so as you read this :> 2) Am I SOL, short of doing it myself in the fxp driver? TIA, rip -- Richard Williamson