Hello,
I have in the company I'm working for problems to associate to an AP;
the entry in the /etc/wpa_supplicant.conf is:
network={
ssid=OCLCPublic
psk=XXX
key_mgmt=WPA-PSK
}
with the correct psk given from our local admin; when it tries to
associate, in most of the
Will do. I'm actually thinking about reverting my changes just to see if stock
ath(4) works (it's been a looong while since I played with bringing it up). I
still occasionally see the same behavior I saw before my changes.
I'm using a recent Linux kernel (which works out of the box) to get it
See, that's where it's odd:
| EepromWriteGpio: 16, WlanDisableGpio: 0, WlanLedGpio: 8
RxBandSelectGpio: 255 |
.. how'd you figure out it's GPIO 11?
-adrian
On 22 December 2014 at 11:39, Anthony Jenkins scoobi_...@yahoo.com wrote:
Logs attached.
Thanks,
Anthony
On 12/22/2014 11:21,
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course it
could have been 0x08 I saw, but neither of those would make it through the
function - both 0x0B and 0x08 are blocked).
Anthony
On 12/22/2014 14:51, Adrian Chadd wrote:
See, that's where it's odd:
|
On 22 December 2014 at 11:59, Anthony Jenkins scoobi_...@yahoo.com wrote:
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course
it could have been 0x08 I saw, but neither of those would make it through the
function - both 0x0B and 0x08 are blocked).
Please do. I'd like
On 12/22/2014 15:22, Adrian Chadd wrote:
On 22 December 2014 at 11:59, Anthony Jenkins scoobi_...@yahoo.com wrote:
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course
it could have been 0x08 I saw, but neither of those would make it through
the function - both 0x0B
On 22 December 2014 at 13:59, Anthony Jenkins scoobi_...@yahoo.com wrote:
On 12/22/2014 15:22, Adrian Chadd wrote:
On 22 December 2014 at 11:59, Anthony Jenkins scoobi_...@yahoo.com wrote:
I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of
course it could have been 0x08 I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193826
--- Comment #3 from Henry Hu henry.hu...@gmail.com ---
(In reply to Adrian Chadd from comment #2)
Hi!
I just fixed it in -HEAD. Please update and give it a whirl!
Thanks!
-adrian
I updated iwn and net80211 directory, and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193826
--- Comment #4 from Adrian Chadd adr...@freebsd.org ---
ok, this is a different bug. It seems like you hit an interesting corner case:
* the vap was scanning;
* you hit a firmware crash;
* the min dwell time was met - so the interface
