From owner-freebsd-net@FreeBSD.ORG Fri Dec 3 09:53:14 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CFCD1065696 for ; Fri, 3 Dec 2010 09:53:14 +0000 (UTC) (envelope-from gabor.radnai@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D4DA28FC24 for ; Fri, 3 Dec 2010 09:53:13 +0000 (UTC) Received: by fxm16 with SMTP id 16so7147736fxm.13 for ; Fri, 03 Dec 2010 01:53:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=Gu8eb4fIYT99N0jR/vZqFHIIk/yphyMETD1Gn7kFZbA=; b=O14CQ30p1lwqWFMnGGxH4idl/IFa4h41z3zK74I9HYAb73LtWyHtFGhWPt03daqABR 7av83pNVnDOqI2LjzL13/+YmJJkwIMkj3l9Za0QIUT/R0imAq7G/sFu66RyG8ik54cVH p7twCEyUdCeWD+Nyc/3CbasXXMv8iTGmFmK+s= 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=mtDRx5MaFNX1EWjWDbqS7lKEoG4VphraKWlRt1SVQdr1iHouUPm4ZDdA1RnLcEZCkV LjFXMh8m5bAKW1W3jkHgjl7QxgnXhVj0bC2ZSFNevoMYIUz9xvn0zaGyAxnb/y9AqaJL LDmJy7wn/WQfuXtmEKLGj2QvblxqM+PgfE+RE= Received: by 10.223.78.139 with SMTP id l11mr1879747fak.31.1291369992660; Fri, 03 Dec 2010 01:53:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.85.207 with HTTP; Fri, 3 Dec 2010 01:52:57 -0800 (PST) In-Reply-To: <20101202213028.GE13006@michelle.cdnetworks.com> References: <20101202213028.GE13006@michelle.cdnetworks.com> From: Gabor Radnai Date: Fri, 3 Dec 2010 10:52:57 +0100 Message-ID: To: pyunyh@gmail.com Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org Subject: Re: Problem with re0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2010 09:53:14 -0000 Hi, On Thu, Dec 2, 2010 at 10:30 PM, Pyun YongHyeon wrote: > > On Thu, Dec 02, 2010 at 09:56:42PM +0100, Gabor Radnai wrote: > > Hi, > > > > Could someone pls advise how to inject HEAD driver to stable release without > > full kernel rebuild (if possible)? > > > > If you have updated to stable/8, the driver code would be the same. > So need to replace driver with HEAD version. How exactly? What do you mean on 'replace': compile from source, just copy the binary from a snapshot image to /boot/kernel or ... ? > > > I tried this way but found no assurance/evidence actually kernel using the > > new driver: > > 1. download full HEAD source with help of csup > > 2. in /usr/src/sys/modules/re did make install which in turn compiled re > > driver and installed into default /boot/kernel > > 3. reboot > > > > So far so good but still re0 driver cannot properly handle rtl8111 chip > > seeing the very same symptoms as in case of > > the driver shipped with RELEASE. > > > > If my memory is correct, your controller is somewhat old 8168 PCIe > controller. I also have the same TP-Link TG-3468 PCIe network card > which seems to be the only stand-alone PCIe 8168 controller in > market. I don't see any problems using the controller so would you > summarize your issue again?(Sorry, if you already post it) If you check the original post I did all details there but a quick summary: I have two TP-Link TG-3468 PCIe network cards which is using Realtek 8168/8111 chip. re0: port 0xac00-0xacff mem 0xfdbff000-0xfdbfffff irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: d8:5d:4c:80:b4:88 re0: [FILTER] When I try to use it cannot process DHCP answer properly (sets IP address to 0.0.0.0/255.255.255.255), neither works if using fix IP. Link is up, cable is working but card simply cannot communicate. I switched back and forth all components I could: new cable, connect to different switch port, replace card, use the cable/switch port which is working for integrated motherboard NIC, disable integrated NIC ... no luck so far. Thanks.