Laptop disassociating by local choice (reason=17)

Brent Taylor motobud at gmail.com
Wed Dec 3 09:26:25 PST 2014


On Wed, Dec 3, 2014 at 10:58 AM, Brent Taylor <motobud at gmail.com> wrote:
> On Wed, Dec 3, 2014 at 8:05 AM, Brent Taylor <motobud at gmail.com> wrote:
>> On Tue, Dec 2, 2014 at 11:37 PM, Kalle Valo <kvalo at qca.qualcomm.com> wrote:
>>> Brent Taylor <motobud at gmail.com> writes:
>>>
>>>> On Dec 2, 2014 11:24 PM, "Kalle Valo" <kvalo at qca.qualcomm.com> wrote:
>>>>>
>>>>> Brent Taylor <motobud at gmail.com> writes:
>>>>>
>>>>> >    I actually ran the wpa_supplicant with -ddddt as the parameter not
>>>>> > knowing how many 'd's I could put there before I hit the limit of the
>>>>> > debugging.  The wpa_supplicant on the ubuntu laptop is v0.7.3.  I'll
>>>>> > change the -ddddt to just -dddt and re-run the test again.
>>>>>
>>>>> IMHO 0.7.3 is ancient. Please use something more recent.
>>>>
>>>> Ancient it may be, but why would it work with the ath9k chip and not
>>>> the ath6kl chip?
>>>
>>> Because of a bug we are not aware of? ath6kl and ath9k are very
>>> different drivers and 0.7.3 might have some problem which only comes
>>> with ath6kl. Up to you, but I would not waste time testing on that old
>>> wpasupplicant.
>>>
>>> --
>>> Kalle Valo
>>
>> Apologies for my last reply not making it through the mailing lists, I
>> sent it from my phone and it was automatically formatted in HTML and
>> not Plain Text.
>>
>> The ultimate goal is to use an Android device to communicate with my
>> custom device being the Access Point.  The laptop is easier to debug
>> (at the moment) than an Android device.  I'm currently using a Samsung
>> S4 running 4.4.4 and it was not able to complete the authentication
>> step either.  This is when I turned to using the laptop.  Any idea
>> what version of the wpa_supplicant is running on Kit Kat?
>>
>> -- Brent Taylor
>
>
> Here is another log capture from the device and the laptop.  This time
> both were using -dddt as the debug parameter to wpa_supplicant.
>
> Laptop wpa_supplicant Log
>

-- snip last log data from 2014-12-03 --

I just found out that the Samsung S4 that we are testing with has
wpa_supplicant version v2.0-devel-4.2.2 which is not KitKat, but Jelly
Bean.  Does anyone know if the logging can be turned on without
rooting the phone?

-- Brent Taylor



More information about the ath6kl mailing list