From: cmckay@abineau.com
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Direct firmware load failed with error 2
Date: Mon, 24 Oct 2016 16:59:22 -0400 (EDT) [thread overview]
Message-ID: <1477342762.945417468@apps.rackspace.com> (raw)
In-Reply-To: <8642a7dd-3612-ce8b-8c08-f4bd8f746764@candelatech.com>
Thanks Ben,
Got the location from the website:
root@apalis-imx6:/lib/firmware/ath10k/QCA988X/hw2.0# ls
firmware-2.bin firmware-5.bin
I'll figure out how to do some printk's (I'm a newbie).
Thanks,
Colin
-----Original Message-----
From: "Ben Greear" <greearb@candelatech.com>
Sent: Monday, October 24, 2016 4:11pm
To: cmckay@abineau.com, ath10k@lists.infradead.org
Subject: Re: Direct firmware load failed with error 2
Maybe add some printks in your driver to see exactly what it is trying to load?
Maybe firmware is in wrong location?
errno 2 == ENOENT, which probably means something like 'could not find file'.
Thanks,
Ben
On 10/24/2016 12:55 PM, cmckay@abineau.com wrote:
> Hi,
>
> I'm attempting to add a Silex PCEAC or Compex WLE900VX (both QCA9880) mini PCIe card to a Toradex Apalis iMX6 SOM on their Ixora card. I added a BSP layer to Toradex's standard build, simply adding the ath10k and noting more.
> I keep running into the following error:
>
> [ 7.063663] ath10k_pci 0000:01:00.0: BAR 0: assigned [mem 0x01000000-0x011ff]
> [ 7.172118] ath10k: pci irq MSI
> [ 7.198024] ath10k_pci 0000:01:00.0: Direct firmware load failed with error 2
> [ 7.209646] ath10k_pci 0000:01:00.0: Falling back to user helper
> [ 8.626488] ath10k: could not fetch board data (-2)
> [ 8.648471] ath10k_pci 0000:01:00.0: Direct firmware load failed with error 2
> [ 8.693701] ath10k_pci 0000:01:00.0: Falling back to user helper
> [ 8.712302] ath10k: could not fetch board data (-2)
> [ 8.722757] ath10k: could not fetch firmware files (-2)
> [ 8.781868] ath10k: could not probe fw (-2)
> [ 8.781874] ath10k: failed to register driver core: -2
> [ 8.782041] ath10k_pci: probe of 0000:01:00.0 failed with error -2
>
> I've tried the firmware-2, firmware-5 and Candella firmware. I can't find any information on what this error means or how to debug this issue. And the vendors are struggling to get me a solution.
> Any help would be greatly appreciated.
>
> Colin McKay
>
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-10-24 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 19:55 Direct firmware load failed with error 2 cmckay
2016-10-24 20:11 ` Ben Greear
2016-10-24 20:59 ` cmckay [this message]
2016-10-24 21:05 ` Ben Greear
2016-10-24 23:22 ` cmckay
2016-10-25 1:57 ` Ben Greear
2016-10-25 2:59 ` cmckay
2016-10-25 3:11 ` cmckay
2016-10-25 4:21 ` Ben Greear
2016-10-25 15:50 ` Marek Puzyniak
2016-10-27 22:43 ` Colin McKay
2016-10-27 16:04 ` Marek Puzyniak
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=1477342762.945417468@apps.rackspace.com \
--to=cmckay@abineau.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox