From: Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr>
To: Kalle Valo <kvalo@qca.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>
Cc: Patrick CARNEIRO RODRIGUEZ <p.carneiro@actiasodielec.fr>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: RE : load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
Date: Mon, 14 Apr 2014 17:49:21 +0200 [thread overview]
Message-ID: <EE97821C81277E459BEA5C6384C6F241012F06CC4838@srvexch01.SODIELEC.local> (raw)
In-Reply-To: <8738hgfi1k.fsf@kamboji.qca.qualcomm.com>
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)
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : lundi 14 avril 2014 10:10
À : Michal Kazior
Cc : Vu Hai NGUYEN; Patrick CARNEIRO RODRIGUEZ; ath10k@lists.infradead.org
Objet : Re: load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
Michal Kazior <michal.kazior@tieto.com> writes:
> On 11 April 2014 17:09, Vu Hai NGUYEN <vh.nguyen@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
modules.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-04-14 15:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 4:14 Crash during driver startup Ben Greear
2014-04-10 10:05 ` [PATCH] ath10k: double check bmi xfer pointers Michal Kazior
2014-04-10 10:05 ` Michal Kazior
2014-04-10 13:42 ` Ben Greear
2014-04-10 13:42 ` Ben Greear
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:47 ` Michal Kazior
2014-04-11 5:47 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 15:09 ` load module ath10k: ieee80211 phy0: Failed to initialize wep: -2 Vu Hai NGUYEN
2014-04-14 6:39 ` Michal Kazior
2014-04-14 8:10 ` Kalle Valo
2014-04-14 15:49 ` Vu Hai NGUYEN [this message]
2014-04-15 8:20 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
2014-04-15 11:02 ` Kalle Valo
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
2014-04-16 11:51 ` Vu Hai NGUYEN
2014-04-24 6:35 ` Kalle Valo
2014-04-24 9:03 ` RE : " Vu Hai NGUYEN
2014-04-24 9:41 ` Michal Kazior
2014-04-24 10:18 ` Yeoh Chun-Yeow
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
2014-05-07 7:48 ` Michal Kazior
2014-05-07 8:16 ` Yeoh Chun-Yeow
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
2014-05-07 9:26 ` Janusz Dziedzic
2014-05-07 14:11 ` Ben Greear
2014-05-07 14:21 ` Adrian Chadd
2014-05-07 14:33 ` Ben Greear
2014-05-07 14:50 ` Adrian Chadd
2014-05-07 15:09 ` Ben Greear
2014-04-14 8:05 ` [PATCH] ath10k: double check bmi xfer pointers Kalle Valo
2014-04-14 8:05 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EE97821C81277E459BEA5C6384C6F241012F06CC4838@srvexch01.SODIELEC.local \
--to=vh.nguyen@actiasodielec.fr \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=michal.kazior@tieto.com \
--cc=p.carneiro@actiasodielec.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.