From owner-freebsd-stable@FreeBSD.ORG Mon Sep 23 18:17:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C254AD30 for ; Mon, 23 Sep 2013 18:17:05 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from galore.getmail.no (galore.getmail.no [84.210.184.6]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3C02F91 for ; Mon, 23 Sep 2013 18:17:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by galore.getmail.no (Postfix) with ESMTP id A2F8E14D5EF for ; Mon, 23 Sep 2013 20:16:53 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -2.99 X-Spam-Level: X-Spam-Status: No, score=-2.99 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_KHOP_THREADED=-0.01, T_NICE_REPLY_A=0.01, T_UNKNOWN_ORIGIN=0.01] autolearn=ham Authentication-Results: galore.get.c.bitbit.net (amavisd-new); dkim=pass (1024-bit key) header.d=getmail.no Received: from galore.getmail.no ([127.0.0.1]) by localhost (galore.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Kgv5hhiZqR-U for ; Mon, 23 Sep 2013 20:16:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by galore.getmail.no (Postfix) with ESMTP id 45A5F14D5F6 for ; Mon, 23 Sep 2013 20:16:53 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.7.1 galore.getmail.no 45A5F14D5F6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1379960213; bh=nkOg3fCOMLxu2DwJi9+Ts2pfnXM5fI3hCives/HAbIg=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=E0y+QTQ/yRyNEsloNKh1b7TgNR/vE9XEbSRCztH3OES+050Vh/0CLh8XpA+YRmqh5 STFg0KVJ23Oyeka9Rky3z0MoqZAjM4cDxVt6p3G3O08Zlr1ivsK6nIgMhUz1dj4OP+ mrKXK48XKT0xbdrl7qqTn8sEJT50II8BcYlKm9H8= X-Virus-Scanned: amavisd-new at Received: from galore.getmail.no ([127.0.0.1]) by localhost (galore.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FmbWmYtoiDu4 for ; Mon, 23 Sep 2013 20:16:53 +0200 (CEST) Received: from kg-core1.kg4.no (cm-84.215.180.206.getinternet.no [84.215.180.206]) by galore.getmail.no (Postfix) with ESMTPSA id 224FE14D5EF for ; Mon, 23 Sep 2013 20:16:53 +0200 (CEST) Date: Mon, 23 Sep 2013 20:16:52 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Subject: Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard Message-Id: <20130923201652.6077480310595862fc9df015@getmail.no> In-Reply-To: References: X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd8.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 18:17:05 -0000 On Sun, 22 Sep 2013 20:28:08 +0000 "Thomas Mueller" wrote: > I've been unable to establish Internet connection from a new computer with Realtek 811E Ethernet despite this Ethernet chip working on another computer with another MSI motherboard. In additiin to the information you have already provided, you should also provide relevant output from pciconf, like so: root@kg-core1# pciconf -lv | grep -A 4 re0 re0@pci0:2:0:0: class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet (substitute the name of your interface for "re0") and also ifconfig output like this: root@kg-core1# ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=8209b ether 50:46:5d:8b:a2:ea inet 10.1.150.50 netmask 0xffff0000 broadcast 10.1.255.255 media: Ethernet autoselect (1000baseT ) status: active (again, substitute the name of your interface for "re0") As far as fault-finding "tricks" go, here is one that have helped me on several occasions in the past: before doing anything with a network interface (in other words, before starting DHCP), try doing a 'ifconfig up' for example ifconfig re0 up After that, use the interface normally. If it works, you have found a bug related to the driver and the specific hardware revsion of you card. Create a PR for it. HTH -- Torfinn Ingolfsen