From owner-freebsd-stable@FreeBSD.ORG Thu Oct 2 10:13:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04E111065687 for ; Thu, 2 Oct 2008 10:13:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188]) by mx1.freebsd.org (Postfix) with ESMTP id 66F728FC0C for ; Thu, 2 Oct 2008 10:13:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so539414tid.3 for ; Thu, 02 Oct 2008 03:13:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=uKG1APcBXNpvH/MYoqpS8v3wO0IsS5IgSf0/ydhHyJo=; b=eKTbcTCoPyv1lx3yDS0bYXu6SrUUTXZXW80Bq3QAqLw5OktpsdA+NLHRethlpgMxjA 0a0/ZAFTLrTEvSMvpAx9IDNSeDwPeuXhOqiDF3ur+Mca2s9Y8lM++HNUQZvrIH9y4+9S Avlh8hb5VH5o0egbJOhcYE1PwVLn+cD+cPHng= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=csXunb6TaXK3/3RwBck6VV7NmZh6IlvXYM2ka8JiG/RSm7QzBPIw07XKh6v2VcPPfg QLbQMWQGgGBsswBV2DFOAOARxk62amTfNaiuG1DTcRxD/s8vU7PI7eb1EZF8eraTcS8C R4wT7v61gtnDS/Hxb0G0pzjUx6ODbwbNErn7c= Received: by 10.110.46.3 with SMTP id t3mr13723606tit.33.1222942413497; Thu, 02 Oct 2008 03:13:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id b4sm3539046tic.2.2008.10.02.03.13.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 03:13:31 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m92ABXDO068999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Oct 2008 19:11:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m92ABXKh068998; Thu, 2 Oct 2008 19:11:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 2 Oct 2008 19:11:33 +0900 From: Pyun YongHyeon To: "Sergey V. Dyatko" Message-ID: <20081002101133.GE67204@cdnetworks.co.kr> References: <20081002102600.45f407d2@notebook> <20081002084425.GD67204@cdnetworks.co.kr> <20081002120157.4e72b2f0@notebook> Mime-Version: 1.0 Content-Type: text/plain; charset=euc-kr Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081002120157.4e72b2f0@notebook> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: if_re is broken on RELENG_7 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2008 10:13:36 -0000 On Thu, Oct 02, 2008 at 12:01:57PM +0300, Sergey V. Dyatko wrote: > ¬£ Thu, 2 Oct 2008 17:44:25 +0900 > Pyun YongHyeon ¬á¬Ú¬ê¬Ö¬ä: > > > On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > > > Hi list, > > > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > > > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used > > > it. Than I started to enjoy BCM43XX wi-fi adapter and now I > > > recently decided to revert to the use of realtek adapter. But it > > > doesn't work. I'm just not running a network card or at all does > > > not work? > > > > > > some additional information: > > > ifconfig shows such information, regardless of whether the cable is > > > connected: > > > > > > %ifconfig re0 > > > re0: flags=8802 metric 0 mtu 1500 > > > options=389b > > > ether 00:1a:92:ca:b3:bc > > > media: Ethernet autoselect (10baseT/UTP ) > > > status: no carrier > > > > I don't see what's wrong in the output above. Because there is no > > "RUNNING" in flags field I guess you didn't up the interface. > > (e.g. either assign an IP address to the interface or run > > 'dhclient re0' if you want to get an IP address over DHCP). > > > Hmm, after command 'ifconfig re0 up' status changed to 'active', > media to '100baseTX ' and everything work fine (dhclient > re0). What time have I had to type "up" explicitly to make it work > since? You don't have to, just configure re0 interface(e.g. rc.conf) > > On my desktop with age(4): > without cable: > age0: flags=8802 metric 0 mtu 1500 > options=319b > ether 00:1b:fc:d4:7d:b3 > media: Ethernet autoselect (none) > status: no carrier > Now I'll plug cable into NIC: > > age0: flags=8802 metric 0 mtu 1500 > options=319b > ether 00:1b:fc:d4:7d:b3 > media: Ethernet autoselect (100baseTX ) > status: active > in that case I haven't "RUNNING" in flags field too, that flag and flag > 'UP' appeared after I assing IP to age0 > > age0: flags=8843 metric 0 > mtu1500 > options=319b > ether 00:1b:fc:d4:7d:b3 > inet 192.168.9.240 netmask 0xffffff00 broadcast 192.168.9.255 That depends on PHY driver, rgephy(4) for re(4). Some PHY hardware requires special mode/initialization to establish a valid link with link partner. It seems that atphy(4) doesn't require any special PHY hardware configuration to establish a link. Also you can say the link status is valid only after interface up. Normally PHY drivers will have to restart auto-negotiation to choose the highest common denominator ability in interface up time. The established link after auto-negotiation may/may not agree on the speed/duplex of the link you've seen before the initialization. -- Regards, Pyun YongHyeon