From owner-freebsd-questions@FreeBSD.ORG Tue Apr 15 02:16:50 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 C0DAC60F for ; Tue, 15 Apr 2014 02:16:50 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (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 811BB1905 for ; Tue, 15 Apr 2014 02:16:50 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so9158047qgd.15 for ; Mon, 14 Apr 2014 19:16:49 -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=n4zZBOF6sBG7B9PVveuDVTvLn7tmpaFMoIA9cg9y2ec=; b=hNKziVlMe5gThPppDZvRFT2Q5qrkws38/tcFcMqtTbiA5Nhs+dCNKcjcc5s/lYwBl2 BLDJxXo8h7BRf1Y3d/G/HoMD60hqZfRGOFHxwMatHWHPzAAJ0SOpkLn83oXLmaTBlylT xesP5DVhhl5eVe1nU1hNzWRkgnzucYzpIRMqHiOSEFnrv4sKpyXrlf/9L2HfjpCLLsC4 +Uk/uGIyw71t0C1CKsDg2XLupDS6PrFz5tjBKGxQnNBK925WO859VgzwewT1U9uMD1QE y6o9B3ZV5ihdKIJb72N831eQgQov8eiLQlxddlW+qlExp9WCR7Tc/HNp+LiczOI2Jbbg gcJQ== MIME-Version: 1.0 X-Received: by 10.224.13.142 with SMTP id c14mr24738912qaa.76.1397528209455; Mon, 14 Apr 2014 19:16:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Mon, 14 Apr 2014 19:16:49 -0700 (PDT) In-Reply-To: <534BC380.90608@herveybayaustralia.com.au> References: <534B32FA.30500@herveybayaustralia.com.au> <534BC380.90608@herveybayaustralia.com.au> Date: Mon, 14 Apr 2014 19:16:49 -0700 X-Google-Sender-Auth: 0NjCwwdJAT23huurI3_Gb9FDNJE 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: Tue, 15 Apr 2014 02:16:50 -0000 Wait, you don't have this problem on the install image when running from USB? -a On 14 April 2014 04:16, Da Rock wrote: > Finally got the email client working again on the walking dead system :) > > On 04/14/14 13:57, Adrian Chadd wrote: >> >> Hi! > > I was hoping you were tuned in. If you can get this thing sorted again I'll > owe you one! > >> >> You never said exactly what hardware it is Can you include a dmesg of >> the relevant bits during boot? > > Sorry, that was a bit remiss wasn't it? I had the info to put in too... its > the AR9285 atheros chipset. > > dmesg is a bit harder being on a different system. I'll try and get the info > in order though, at the time I was reading off the scrolling output from > vt1. The error(s) are repetitive though, so I'll just offer one cycle. It > doesn't seem to necessarily follow any real order though, from my > observation. > > ath0: ath_reset_grablock: didn't finish after 10 iterations > ath0: ath_reset_grablock: warning, recursive reset path! > ath0: ath_reset: concurrent reset! danger! > ath0: ath_reset: unable to reset hardware; hal status 14 > ath0: ath_chanset: unable to reset channel , hal status 14 > ... > ath0: ath_reset: unable to reset hardware; hal status 14 > >> >> Anything like the above kinda indicates there's some bigger issue going >> on. > > I can't imagine its a hardware issue as it seems to work with other systems > (like the install memdisk). I thought with the hal debug sysctl being > available it would offer more info, but it seems it may not even be in the > kernel although there is a sysctl. I tried compiling a new kernel with the > debug options, but the backup battery is not working properly so it depends > on ntpd to set the correct time, and the make requires the correct time set; > so I'll have to address that before I can continue that course. > > Argh! The joys of Murphy and his damned laws! > >> >> >> -a >> >> >> >> On 13 April 2014 17:59, Da Rock >> wrote: >>> >>> The subject line may not be very descriptive, but I'm not sure exactly >>> where >>> to point as to the problem. All other similar issues are a few years old >>> now, and on 8,9, some 7's. >>> >>> Long story short I'm just installing 10 (finally) on my laptop, and I >>> need >>> to get it back up and running asap as I am swamped in work. I didn't >>> think >>> it would be an issue as 9 had a decent working ath driver and I thought >>> it >>> could only get better. I'm now emailing using yet another system with the >>> same device on 9, but a dying hdd which obviously also needs a reinstall >>> on >>> new hdd. Wired is no good as we aren't equipped. >>> >>> So in bsdinstall, all works well and it sets up wifi easily. Reboot into >>> the >>> new system an it has a coronary with messages from ath_reset_grablock, >>> ath_reset, ath_raw_xmit, ath_chan_set, ath_legacy_rx_tasklet: >>> >>> ath_reset: concurrent reset! danger! >>> >>> ath_reset_grablock: didn't finish after 10 iterations >>> ath_reset_grablock: warning, recursive reset path! >>> >>> ath_chan_set: concurrent reset! danger! >>> >>> ath_raw_xmit: sc_inreset_cnt > 0; bailing >>> >>> ath_legacy_rx_tasklet: sc_inreset_cnt > 0; bailing >>> >>> Scanning doesn't work; ath0 says it is associated, but wlan0 says no >>> channel. >>> >>> I've set dev.ath.0.hal.debug=1, but there is no ath.0.debug either under >>> dev >>> or hw. I tried compiling the tools but it failed for lack of gcc. >>> >>> TIA guys, but I am really under the pump here as I thought this would be >>> a >>> quick up and go now with the pkgng system as well in play. Now I'm up the >>> proverbial creek without a paddle. >>> >>> Cheers >>> _______________________________________________ >>> 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" > > > _______________________________________________ > 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"