TR : ath10k: firmware crash in station mode

Ben Greear greearb at
Sat May 24 09:14:06 PDT 2014

On 05/23/2014 11:29 PM, Tim Harvey wrote:
> On Fri, May 23, 2014 at 9:03 AM, Ben Greear <greearb at> wrote:
>> On 05/23/2014 08:36 AM, Yeoh Chun-Yeow wrote:
>>> Based on my testing, due to firmware 636 is not able to support
>>> standalone monitor mode, and bridge requires promiscuous mode, it
>>> would crash. Then, I have tested with AP firmware and it works well.
>>> But then, I have not up the node for long time.
>>> By the way, I am associating the AP before setting "iw dev wlan0 set
>>> 4addr on" and bridge it.
>> Well, if nothing else, you could try my firmware, with a small patch to
>> make it work on standard kernels.  If you can crash it, send me the
>> firmware crash message and I'll see if I can fix it.
>> Current binary is non-commercial, but I will shortly have a free-for-whatever-use
>> binary that has everything except the multiple-vif-to-same-ap-with-encryption
>> feature.  Virtually no one except folks like us doing wifi testing equipment
>> needs that feature....
>> My firmware has been fairly well tested with my patched kernel and in
>> station and AP mode.  I'm sure there are still bugs, but I will try
>> to fix them, at least.
>> Thanks,
>> Ben
> Ben,
> I tried using your firmware on a 3.14 kernel without any luck. I don't
> see any errors, but the sta never associates nor see's any ap on scan.
> I followed step 4 and step 6 and
> did this on OpenWrt, so the udev stuff doesn't apply.

Skip step 6 unless you are using my kernel.  Just step 4 for upstream
kernels.  I need to make a separate page for folks just using my CT
firmware on normal kernels doing normal things...

No arguments with the rest of your email :)


Ben Greear <greearb at>
Candela Technologies Inc

More information about the ath10k mailing list