From owner-freebsd-net@FreeBSD.ORG Thu Sep 25 09:47:34 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 644EFADB; Thu, 25 Sep 2014 09:47:34 +0000 (UTC) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) by mx1.freebsd.org (Postfix) with ESMTP id 27238FD6; Thu, 25 Sep 2014 09:47:33 +0000 (UTC) Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id 76EA61414951; Thu, 25 Sep 2014 11:44:13 +0200 (CEST) Received: from asbach.renzel.net (unknown [10.2.0.7]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTP id 3C3EB98FA7; Thu, 25 Sep 2014 11:44:25 +0200 (CEST) Content-Type: text/plain; charset="ISO-8859-1" From: Nils Beyer Organization: VKF Renzel GmbH Date: Thu, 25 Sep 2014 11:44:24 +0200 User-Agent: KNode/4.12.5 Content-Transfer-Encoding: 7Bit Subject: Re: Success with Qualcomm Atheros QCA8171 To: freebsd-drivers@freebsd.org, freebsd-net@freebsd.org References: <3320661411119387@web21h.yandex.ru> Lines: 52 MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.98 at nijmegen.renzel.net X-Virus-Status: Clean X-Spam-Status: No, score=-6.5 required=7.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2014 09:47:34 -0000 Hi Gulyaev, Gulyaev Ghosh wrote: > Since I ask on the FreeBSD forums, there is a proposition to check > alx-freebsd and have initialized interface. > > So if someone have similar hardware, you can got your experience with > that project and share info. I've got an onboard "AR8161 Gigabit Ethernet" adapter. With your proposed GIT- repository and using its branch "master" I'm able to rudimentarily use the NIC. But only if the network cable is short (< 2m). Using longer cables gives me a "no carrier" status. When it is connected, speed is abysmal and functio- nality ceases as soon as I perform an "iperf" benchmark until I reboot. But for small data transfers (SSH, RSYNC, RDP) it's okay. Mark has done a good job so far: =============================================================================== #dmesg | grep alx alx0: port 0x2000-0x207f mem 0xd0400000-0xd043ffff irq 16 at device 0.0 on pci2 alx0: Ethernet address: 5c:f9:dd:55:c9:fb #ifconfig alx0 alx0: flags=8843 metric 0 mtu 1500 ether 5c:f9:dd:55:c9:fb inet6 fe80::5ef9:ddff:fe55:c9fb%alx0 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect status: no carrier #pciconf -evl | tail -13 alx0@pci0:2:0:0: class=0x020000 card=0x05621028 chip=0x10911969 rev=0x10 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR8161 Gigabit Ethernet' class = network subclass = ethernet PCI-e errors = Correctable Error Detected Non-Fatal Error Detected Unsupported Request Detected Non-fatal = Unsupported Request Corrected = Bad TLP Bad DLLP REPLAY_NUM Rollover Replay Timer Timeout =============================================================================== ... Regards, Nils