From owner-freebsd-questions@FreeBSD.ORG Fri Apr 18 12:42:48 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2315379D for ; Fri, 18 Apr 2014 12:42:48 +0000 (UTC) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8DE7A1B4B for ; Fri, 18 Apr 2014 12:42:47 +0000 (UTC) Received: from laptop2.herveybayaustralia.com.au (laptop2.herveybayaustralia.com.au [192.168.0.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 43EAE27332 for ; Fri, 18 Apr 2014 22:42:45 +1000 (EST) Message-ID: <53511DC2.6070501@herveybayaustralia.com.au> Date: Fri, 18 Apr 2014 22:42:42 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: FBSD10 Atheros wifi not working References: <534B32FA.30500@herveybayaustralia.com.au> <534BC380.90608@herveybayaustralia.com.au> <534E80AB.4000007@herveybayaustralia.com.au> <5350780F.2070806@herveybayaustralia.com.au> <535116CA.9060009@herveybayaustralia.com.au> In-Reply-To: <535116CA.9060009@herveybayaustralia.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 12:42:48 -0000 On 04/18/14 22:12, Da Rock wrote: > On 04/18/14 21:15, Adrian Chadd wrote: >> 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.) > Its out of a Compaq CQ series. Atheros - IC: 4104A-AR5B95H. Skipped another thought - I wouldn't have thought the laptop I have was too badly built, and how would the noise cause the error messages? I didn't have that many messages for the iwn in the m/c's prior, is it just the atheros chipsets? I kind of expect some reconnection issues, but the hardware reset messages (from 9.x) were disconcerting - these current ones are obviously worse. And I meant to add: where do I go now? Should I send you the logs or other errors? >> >>>> >>>> -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. > Hmmm. But that doesn't explain why it doesn't work when I manually set > it again after the rc has completed and screwed up. Sometimes it does, > sometimes it doesn't... >> >> >> -a >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"