FBSD10 Atheros wifi not working
freebsd-questions at herveybayaustralia.com.au
Fri Jul 25 13:50:08 UTC 2014
Dredging this back up as I finally have been able to get back to it with
a hiatus on the work levels.
Adrian, I have been fiddling with this and while the debug messages are
no more informative my observations are.
One thing has been rather prominent and that is that on boot the Atheros
card seems to want quite a bit of time to stabilise. WPA supplicant
comes in too early, and it will never stabilise until a reboot without
WPA kicking in. But even then it takes about 2-5mins before you can hit
This is a quad core machine; is it possible it cannot coordinate on smp?
The debug errors continue regardless even if wpa is off and it is given
time to stabilise. Once stable, though, the errors slowly die away.
Just hoping this may help if you need to get a patch in for the next
release. My own issues appear to run further than just network on this
release... xorg, kms, multi-vga, pkg.... fun fun fun :-D
Just let me know if you want more tests done.
On 04/20/14 17:36, Da Rock wrote:
> On 04/20/14 00:34, Adrian Chadd wrote:
>> On 18 April 2014 05:42, Da Rock
>> <freebsd-questions at herveybayaustralia.com.au> wrote:
>>> 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
>>> chipsets? I kind of expect some reconnection issues, but the
>>> hardware reset
>>> messages (from 9.x) were disconcerting - these current ones are
>>> And I meant to add: where do I go now? Should I send you the logs or
>> Well, I highly recommend rebuilding with debugging in your kernel
>> * ATH_DEBUG
>> * AH_DEBUG
>> * ATH_DIAGAPI
> Thats already been done, as per last (second to last?) post. All it
> really managed to do was crash the system.
>> And then figure out why you can't build the ath tools.
>> The output from athstats will likely be helpful.
>> The reset stuff is interesting - it means the NIC is taking way too
>> long to finish some task. Normally grabbing that lock doesn't take too
>> long, but something has your NIC angry.
>> Yes, please compile up athstats at least. :-)
> It'd have to be athstats, wouldn't it? Right where it stops compiling
> with an error (why would it be using gcc still?). I'll give it a shot...
> Thanks Adrian. And let me know if you want that mini pcie.
>> freebsd-questions at freebsd.org mailing list
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions