From owner-freebsd-net@FreeBSD.ORG Sun Feb 21 23:53:41 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 BA0951065676 for ; Sun, 21 Feb 2010 23:53:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yx0-f199.google.com (mail-yx0-f199.google.com [209.85.210.199]) by mx1.freebsd.org (Postfix) with ESMTP id 633D98FC14 for ; Sun, 21 Feb 2010 23:53:41 +0000 (UTC) Received: by yxe37 with SMTP id 37so2540560yxe.27 for ; Sun, 21 Feb 2010 15:53:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=Od1LIJ8nUL8Op2w6MtsIK6MY7Iyz0cYkSZEOXK+nw4w=; b=rByMa3ig6fZAVhoq0MJ1Ua+sOTSvDSxa3FJryJAisXKh40EfKO2MqOkMdbu8qaufL8 ic+W1ywtNFOuxma3D77POxKB9gNjdzqS7BomOfr3k3iMZ6tbyMc74O2EEGKs5+z7Dw1x HY2/DTYD3HeYeu4KeFmuFGL2tnFcSxKhuOBPQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=f75zp1d7OuybPw4Owp3/zYAjMTCMAq1K2QG5o1cTVqyjc7wAH10DyNv47aqvogC9XD IZtDEcxTCNFLHws3qPFTW7rrdoz8RNenqqKlEmJPBPaJDRiQexjSAcoZLoXn5+/tXDzK gkT5Yfi6t6b+FsE68syFTcaOrzqNodmBNcFME= Received: by 10.101.5.12 with SMTP id h12mr4556630ani.52.1266796416521; Sun, 21 Feb 2010 15:53:36 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 15sm2724268gxk.14.2010.02.21.15.53.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 21 Feb 2010 15:53:35 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 21 Feb 2010 15:52:57 -0800 From: Pyun YongHyeon Date: Sun, 21 Feb 2010 15:52:57 -0800 To: Patrick Ale Message-ID: <20100221235257.GB1251@michelle.cdnetworks.com> References: <8d158e1f1002160429m747efaf1h478b6b9cf00b96c@mail.gmail.com> <20100216183531.GD1394@michelle.cdnetworks.com> <8d158e1f1002210228y3d46c146xe0fa0263f5c80c47@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8d158e1f1002210228y3d46c146xe0fa0263f5c80c47@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: Attansic L1 Gigabit discovered on install but no link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2010 23:53:41 -0000 On Sun, Feb 21, 2010 at 11:28:54AM +0100, Patrick Ale wrote: > Good morning! > > On Tue, Feb 16, 2010 at 7:35 PM, Pyun YongHyeon wrote: > > > I assume you're using age(4). > > age(4) is one of driver that still does full re-initialization while > > dhclient(8) is running, how about unplugging the UTP cable and > > replug it while DHCP is in progress? > > Actually it is the 'ale' driver (kinda funny when you look at my last > name ;-) ).. > And yes, you are right. When during the instalation I provide a static > IP address, the link comes up and I have TCP/IP connectivity. DHCP > always fails with 'no link' errors. > > > After you see the failure DHCP, unplug the UTP cable and wait 2-3 seconds and replug the UTP cable again. And execute "dhclient ale0", does it make any difference? > > There are several variants of L1 so please show me the dmesg > > output. > > This is a 'dmesg | grep ale' output when I configure a static IP address: > > ale0: port 0x3000-0x307f > mem 0xf6000000-0xf603ffff irq 16 at device 0.0 on pci2 > ale0: 960 Tx FIFO, 1024 Rx FIFO > ale0: Using 1 MSI messages. > ale0: 4GB boundary crossed, switching to 32bit DMA addressing mode. > miibus0: on ale0 > ale0: Ethernet address: 00:a0:d1:a5:b8:9a > ale0: [FILTER] > ale0: link state changed to UP > It seems you've removed PHY driver related message here. Show me the output of "devinfo -rv | grep phy". Also show me the output of "pciconf -lcv". > > So for now it is workable but I'd like to find out why DHCP is failing > and if I can help out trying to figure out what is going on :) > Last time I tried ale(4) it worked as expected. I have no longer access to ale(4) hardware so it would be hard to fix that but I'll see what I can do. > Thanks all for your time, > > Patrick