From owner-freebsd-questions@FreeBSD.ORG Tue Jun 2 22:22:08 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20EC41065675 for ; Tue, 2 Jun 2009 22:22:08 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id CBF678FC1B for ; Tue, 2 Jun 2009 22:22:07 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so4641617qwe.7 for ; Tue, 02 Jun 2009 15:22:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=bmd6Und2RAQW8vM8ZgzBSV9dlue9FDdDJbT6nK/rY7w=; b=hTja6dn+g/YqUNZvqNon1Za0QqpVnq3oOtKsNRsqnuT5p9C6ZdY8SSzsMq3X8fnehJ GGEmvYKdEcJL0vp6qwR7FDVy9rMnDVl/UmHpNA1OGP/RxO3vqnP0yQWzwPIcjEADRtol lUxWv82La3dtSpXsA5AiGeFUYCRagBNf5NDzA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=KmjqDhK8aJMXCfeuYEkRCWa2+x3HU+XJrYVwvHtnbFrnxOCQp79npBo30ufkBhBUPc cA+k+g+F+p69I3i5rfo7+MjIjIk8ZRoz3WxYSNIgwSquHLV8gPai0yYm3shK3YgxfS1a pu4pYXIBhM6hHAVUa7hfbFExfjbo3BBYIUFnY= MIME-Version: 1.0 Received: by 10.220.77.17 with SMTP id e17mr325318vck.3.1243981327164; Tue, 02 Jun 2009 15:22:07 -0700 (PDT) In-Reply-To: <20090602220709.GA24465@owl.midgard.homeip.net> References: <01FB8F39BAD0BD49A6D0DA8F7897392956DF@Mercury.galaxy.lan.lcl> <20090602220709.GA24465@owl.midgard.homeip.net> From: Tim Judd Date: Tue, 2 Jun 2009 16:21:47 -0600 Message-ID: To: Erik Trulsson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Intel NIC issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 22:22:08 -0000 On Tue, Jun 2, 2009 at 4:07 PM, Erik Trulsson wrote: > On Tue, Jun 02, 2009 at 09:56:01PM +0100, Graeme Dargie wrote: > > Hi all > > > > > > > > Ok lets not go to war over this I just need some advice. > > > > > > > > I have a 1u rack system that has one of these motherboards > > http://www.supermicro.com/products/motherboard/Xeon/E7501/X5DPR-iG2+.cfm > > Are you *sure* that you actually have that particular motherboard? > > As you can see if you look through their product listings > ( http://www.supermicro.com/products/motherboard/Xeon1333/#e7501 ) > Supermicro has > several other similar models, some of which are equipped with one Gigabit > NIC and one 100Mbit NIC much like you seem to have.. > > > > > > > > > Now according to where I got the server and that page it is supposed to > > have dual gigabit nics on board. > > > > > > > > Dmesg shows the following > > > > > > > > em0: port 0x3000-0x301f mem > > 0xfc220000-0xfc23ffff,0xfc200000-0xfc21ffff irq 31 at device 4.0 on pci3 > > > > em0: [FILTER] > > > > em0: Ethernet address: 00:30:48:24:84:f2 > > > > > > > > fxp0: port 0x4400-0x443f mem > > 0xfc321000-0xfc321fff,0xfc300000-0xfc31ffff irq 17 at device 2.0 on pci4 > > > > miibus0: on fxp0 > > > > inphy0: PHY 1 on miibus0 > > > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > fxp0: Ethernet address: 00:30:48:24:84:f3 > > > > fxp0: [ITHREAD] > > > > > > Now for reasons I can not fathom, one nic is showing just fine and the > > other is using a different driver and only speeds of upto 100mbs. > > The obvious reason is that there is two different ethernet controllers > on that board - one Gigabit and one 100Mbit. > > It is worth noting that according to the above, they are found on different > PCI-buses, while the dual-gigabit controller you thought you had is a > single > chip where obviously both ports would be connected to the same bus. > > > > > > > > > I have tried both 7.1 and 7.2 So is the information on the board wrong > > or is there something I am missing. > > Most likely you have a different motherboard than you think you have. > The *complete* dmesg output as well as the output of 'pciconf -lv' might > be useful in determining what you actually have. (Opening the box and > checking for any useful labels on the motherboard can also of course be > useful, but is not something we can help you doing.) > Using kenv smbios.system.product might be a good indication of what you have too. Good luck. Nothing like troubleshooting a piece of hardware from remote. :)