From owner-freebsd-current@FreeBSD.ORG Wed Oct 7 18:04:18 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C24ED1065679 for ; Wed, 7 Oct 2009 18:04:18 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 457C58FC1E for ; Wed, 7 Oct 2009 18:04:17 +0000 (UTC) Received: by fxm22 with SMTP id 22so5027805fxm.36 for ; Wed, 07 Oct 2009 11:04:17 -0700 (PDT) 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=bZcv/NpDpu6YD4Vs0pw2r2UokRWpzIO9loz4jUG4HUs=; b=jMdo7Vf9fzZW+yxaduNGusQlZ3dXXWVZIkhXx+6xdmR5MYCwPWZ2yMQkLyfeoa/uBL zhKcY9rOU/j8dPbPf3nJ5hy0bzDii87QRDK+TnQ6JhSBgQhA4JEyuIpyX8tdCk/gPQjO aA1+SxyrSbiMEh6TE9CyrrZsyNF+7lW+y5A6E= 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=S3LysuHDdwhS5q3Yx3qvY8cySvcUjqWcnDDzuExFcmHTGjznApvn1U9ob6lK8qOISa AuRkgCVqO5pExjP9hNSS0cvmILcMATJHJpAQIChvCnYsDCC/duo0HXofRsekwPtp9G/Y AX1rtYcPdUBMxXEcVkdNgFz8bT8W6TchKCYXI= Received: by 10.103.84.15 with SMTP id m15mr76732mul.105.1254938656840; Wed, 07 Oct 2009 11:04:16 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id s10sm82233muh.54.2009.10.07.11.04.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 07 Oct 2009 11:04:11 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 7 Oct 2009 11:02:57 -0700 From: Pyun YongHyeon Date: Wed, 7 Oct 2009 11:02:57 -0700 To: Ian Freislich Message-ID: <20091007180257.GA3843@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: alc(4) link autoselect problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Oct 2009 18:04:18 -0000 On Wed, Oct 07, 2009 at 08:00:42AM +0200, Ian Freislich wrote: > Hi > > On my recently acquired netbook (compaq mini-110), the ethernet > doesn't autoselect the link speed properly. I think this is because > HP chose the cheapest ethernet controler and the cheapest PHY and Don't know it's cheapest controller but alc(4) hardwares would be better than ale(4) hardwares. Due to lack of documentation I'm not sure but alc(4) seems to have a header split feature which I don't know how to enable the feature. > there's a speed missmatch (or the PHY isn't correctly detected): > > alc0: port 0xec80-0xecff mem 0xfebc0000-0xfebfffff irq 17 at device 0.0 on pci2 > alc0: 15872 Tx FIFO, 15360 Rx FIFO > alc0: Using 1 MSI message(s). > miibus0: on alc0 > atphy0: PHY 0 on miibus0 > atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > alc0: Ethernet address: 00:25:b3:6f:ab:9a > alc0: [FILTER] > > alc0@pci0:2:0:0: class=0x020000 card=0x308f103c chip=0x10621969 rev=0xc0 hdr=0x00 > vendor = 'Attansic (Now owned by Atheros)' > class = network > subclass = ethernet > cap 01[40] = powerspec 3 supports D0 D3 current D0 > cap 05[48] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[58] = PCI-Express 1 endpoint max data 128(4096) link x1(x1) > cap 03[6c] = VPD > > The AR8132 is Fast Ethernet, but the Atheros F1 is gigabit capable. The atphy(4) recognizes PHY as F1 gigabit PHY because AR8132 uses the same PHY id of F1 gigabit PHY. There is no way to know whether it really has F1 gigabit PHY in driver's view. > If I set the media to 100BaseTX full-duplex it works. If link parter used auto-negotiation, this forced media selection shall make your link partner select half-duplex mode instead of full-duplex due to the nature of parallel detection. > I couldn't see link establishment issues on AR8132 sample board. Does link partner also see no link when you use auto-negotiation on alc(4)? Does your link partner support 1000baseT link? Can you see blinking LED of AR8132 when link was not established? How about unplugging UTP cable and then replug the cable after a couple of seconds? Does it make any difference? How about checking MIB statistics of controller? (sysctl dev.alc.0.stats)