From owner-freebsd-questions@FreeBSD.ORG Fri Apr 18 11:15:44 2014 Return-Path: Delivered-To: freebsd-questions@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 A4E77E9D for ; Fri, 18 Apr 2014 11:15:44 +0000 (UTC) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 61FCC1381 for ; Fri, 18 Apr 2014 11:15:44 +0000 (UTC) Received: by mail-qg0-f48.google.com with SMTP id i50so1552344qgf.35 for ; Fri, 18 Apr 2014 04:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=dNC+Q4ciSGZVokbrQRAyEGXOkrT35Lb0lJy/8ugrO/M=; b=gM7xpl3JYax20VYpe2LFKIENxzKyf0dEMgy0XCnmCztA3taQWdLMZHFryB1rpL3iDi fjHeu6jX6mOM6IEraKZdJyAvY0lBrQ1yZ9oMxs1nf55+7Zeuq2d2LLoONbBTkVGBPAr9 Tk9c/7U3Qhw569Ljf7O3L+GSrMa76HAU1hcF8Wpn8y7Kl+AJTcijqWwwmtpL4YBTa50u BRH9O4o9ImFxxHuId5oaRaxRwKbo+6bi60wQTKsgA7lz3QvGktzdgfsh3K62FgV6OWsJ S34EAg9qQHPcCQPs1t2aK69VlvsXJwWlR7dFgV7p0tX3/Jxg793omy4RzHSPQQM/fitA GFZw== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr1762989qae.98.1397819743542; Fri, 18 Apr 2014 04:15:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 18 Apr 2014 04:15:43 -0700 (PDT) In-Reply-To: <5350780F.2070806@herveybayaustralia.com.au> References: <534B32FA.30500@herveybayaustralia.com.au> <534BC380.90608@herveybayaustralia.com.au> <534E80AB.4000007@herveybayaustralia.com.au> <5350780F.2070806@herveybayaustralia.com.au> Date: Fri, 18 Apr 2014 04:15:43 -0700 X-Google-Sender-Auth: n9el_c2Pt0RQo-duDYT3qJfGU7w Message-ID: Subject: Re: FBSD10 Atheros wifi not working From: Adrian Chadd To: Da Rock Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 11:15:44 -0000 On 17 April 2014 17:55, Da Rock wrote: > On 04/18/14 04:01, Adrian Chadd wrote: >> >> .. and unfortunately I've never been able to source the AR9285 variant >> you're using. :( > > Would you like me to send you mine through the channels? As long as you can > tell me one that does actually work without errors (probably the one you're > using ;) ). Well, what's the part number on it? :P I have a lot of AR9285's that work. It may be your actual laptop setup (antennas, noise inside the unit, etc.) >> >> >> -a >> >> On 17 April 2014 11:00, Adrian Chadd wrote: >>> >>> So, try eliminating the whole rc script mess for wpa_supplicant. >>> >>> * Don't put ath0/wlan0 in your startup config (rc.conf) >>> * Do it manually: >>> >>> # ifconfig wlan0 create wlandev ath0 >>> # wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf & >>> >>> see if that's more stable. > > Well I've been trying the standard treatment from the beginning, which is > why I gave it a shot in the list only after the attempt. It only works > intermittently; but I have noticed that killing wpa_supplicant does reduce > the error messages which probably shouldn't be a surprise. Running wpa again > and they come back yet again unless it decides it will work. Having said > that, even of it is wpa_supplicant not working from the beginning isn't that > a problem still? Every reboot you'd have to set it up manually again. > The rc scripts do something dumb sometimes and start wpa_supplicant twice. That seems to agitate things. -a