load module ath10k: ieee80211 phy0: Failed to initialize wep: -2

Vu Hai NGUYEN vh.nguyen at actiasodielec.fr
Mon Apr 14 08:49:21 PDT 2014

Thank you guys,
My mistake, the interface is wlan0, not ath0 (which is created before from the driver Aquila supplied by Atheros)
And the problem about cfg80211/mac80211 is because that I didn't activate cfg80211 in my new kernel of linux when I re-compile my project. (I just take the modules ath10k that I compiled before from the kernel that I had modified to compile ath10k and then put in my new project)

Route de Mayres - B.P. 9

De : Kalle Valo [kvalo at qca.qualcomm.com]
Date d'envoi : lundi 14 avril 2014 10:10
À : Michal Kazior
Cc : Vu Hai NGUYEN; Patrick CARNEIRO RODRIGUEZ; ath10k at lists.infradead.org
Objet : Re: load module ath10k: ieee80211 phy0: Failed to initialize wep: -2

Michal Kazior <michal.kazior at tieto.com> writes:

> On 11 April 2014 17:09, Vu Hai NGUYEN <vh.nguyen at actiasodielec.fr> wrote:
>> Hello everyone,
>> I try to load the module of driver ath10k on a cpu marvell 370 which ran linux 3.2.36, my module wifi is  WLE900VX.
>> These modules was built from backport 3.13.2-1.
>> After loading the module, I use the command "lsmod" and saw that 6 modules was loaded.
>> But my "dmesg" show an error:
>> ieee80211 phy0: Failed to initialize wep: -2
>> And the interface ath0 can not be recognized.

ath0 interface? ath10k does not use interface names like that, that
smells like the proprietary driver.

>> Does any one have any idea about this problem????
> I'm guessing here, but I suspect you tried to load a backports driver
> against cfg80211/mac80211 modules from your distro kernel.

Another option is that there's a some sort of problem with the crypto

Kalle Valo

More information about the ath10k mailing list