From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 02:26:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4DFA129B for ; Sun, 27 Jan 2013 02:26:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ve0-f173.google.com (mail-ve0-f173.google.com [209.85.128.173]) by mx1.freebsd.org (Postfix) with ESMTP id E452FA73 for ; Sun, 27 Jan 2013 02:26:12 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id oz10so175951veb.18 for ; Sat, 26 Jan 2013 18:26:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=RgEYslhCP0pr3dAcyO15Fs6d0+so6VwdKaaOo/ePwmc=; b=M16xYGef/Y4uW2VRc+GHCN2u4zEYfYLmxA1ZRQmbOLdhr7hOOLt4+kCa+Fv4Btumwd gzkwo1cG1JjrpMgaXoZPRIzW1D5zr/lGMOMplm7rwxF3nY/zR1allVBFrltNFOYfU+4C /cffA2Nz/ugGsymlM1gY6OYD3/3XNUR9R/Mrc+YczeI5KtCzgpq1sTmqabz4TAey3yUA R0V596RMxAX3dJ/q0a7Eu6T0g5167Zm+qZzIYh2BTT2vUz3UvaCN2KecLeNMcXvY/AJP lSuM5ql8hFmB8HuIomxLcaisYaEJ8WpnStkEL3XaNWkH+sWB702NRAP9n7EGOKqMUIiB vebw== MIME-Version: 1.0 X-Received: by 10.52.155.205 with SMTP id vy13mr9597099vdb.119.1359253566079; Sat, 26 Jan 2013 18:26:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.58.206.105 with HTTP; Sat, 26 Jan 2013 18:26:05 -0800 (PST) In-Reply-To: <1359240382.8698.60.camel@eva02> References: <1359223263.8698.17.camel@eva02> <51042871.2090605@martenvijn.nl> <1359240382.8698.60.camel@eva02> Date: Sat, 26 Jan 2013 18:26:05 -0800 X-Google-Sender-Auth: SFUwm8PQjLGeI4TuhcoaddTDShI Message-ID: Subject: Re: stuck beacon hung wifi adapter AR5008 From: Adrian Chadd To: paranormal Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 02:26:13 -0000 Hi, So the AR5416 and later NICs almost all implement MIMO. The only exception is the AR9285 which is a 1x1 with the diversity implementation matching previous (pre-11n) NICs. Anyway, for MIMO, all the antennas are on by default. So yes, you need to connect all of the antennas. If you want to avoid this, you can override things. I _think_ it's: hint.dev.ath.0.rx_antenna=0x5 hint.dev.ath.0.tx_antenna=0x5 in /boot/loader.conf If it's not that, it's hint.ath.0.xxx .. Then connect antennas to the connectors marked "chain 0" and "chain 2". The boot messages should then say that the RX and TX chainmasks are being set. Otherwise - yes, connect all three! Adrian