From: Christian Lamparter <chunkeey@googlemail.com>
To: Chris C <chris.a.cremer@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Carl9170fw loading error
Date: Thu, 07 Aug 2014 20:08:50 +0200 [thread overview]
Message-ID: <1535534.mOj91phO2K@blech> (raw)
In-Reply-To: <CAMKDnrkHOsLqXz5p8ZjLRL26N14ZByyM5XQ9b=6a0cB5pPmfqw@mail.gmail.com>
Hi,
On Thursday, August 07, 2014 11:28:38 AM Chris C wrote:
> I am working on a project where I need to be able to modify a wireless
> adapter's firmware. I'm trying to use the Netgear WN111v2 with the
> carl9170 driver and firmware. Depending on the configurations I set
> when building the firmware, I get one of two errors when I try using
> the device: 1)failed to parse or 2)tainted. See below.
>
> Here are the errors:
>
> 1) If I select 'no' to all options during the autogen configuration,
> this is the error I get when inserting the device:
>
> [505796.810127] usb 1-1.4: driver API: 1.9.4 2011-08-15 [1-1]
> [505796.810132] usb 1-1.4: firmware API: 1.9.9 2013-10-25
> [505796.810135] usb 1-1.4: Unprotected firmware image.
> [505796.810138] usb 1-1.4: firmware does support mandatory features.
> [505796.810141] usb 1-1.4: failed to parse firmware (-125).
It's possible to build the firmware without support for
the radio chip (The radio support is quite big and not
needed for firmwares which (load) test the usb phy, ...).
So, this is expected (as the driver can not initialize the
radio).
> 2) If I select 'yes' to all options except the experimental
> extensions, this is the error I get when inserting the device:
> [...]
> [504006.523276] ------------[ cut here ]------------
> [504006.523286] WARNING: at
> /build/buildd/linux-3.2.0/net/wireless/core.c:436
> wiphy_verify_combinations+0x213/0x240 [cfg80211]()
> [504006.523289] Hardware name: OptiPlex 790
> [504006.523291] Modules linked in: carl9170(O) ... mei(C)
> [504006.523338] Pid: 30107, comm: firmware/carl91 Tainted: G WC
> O 3.2.0-67-generic #101-Ubuntu
> [504006.523434] ---[ end trace df0f0cb5a9397534 ]---
This has been fixed by: "carl9170: Only specify interface combinations if
more than one interface is possible". The patch is dated 2012-12-17, your
driver is from 2011-08-15. If you are interested (not necessary), you can
use the latest wireless-drivers as part of the Linux kernel backports
project [0].
The "Crap" flag is set by mei module.
> Also, the adapter works when I use the firmware from here:
> http://wireless.kernel.org/en/users/Drivers/carl9170#Firmware_binary
You didn't specify what you are working on, But if you are just
interested in the default options (which were used to build the
wiki firmware) you can just hit <Enter> instead of answering
the Y/N prompt for every option.
[Note: You have to delete the .config in the project's root
directory first. Otherwise the configuration utility will pick
the previous option instead of starting over].
> Please let me know if there is more useful information I should post.
Regards
Christian
[0] https://backports.wiki.kernel.org/index.php/Documentation
BTW: Thanks, I updated the firmware's README to include a sentence
about that. The "default" option is not that obvious.
next prev parent reply other threads:[~2014-08-07 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 15:28 Carl9170fw loading error Chris C
2014-08-07 18:08 ` Christian Lamparter [this message]
2014-08-08 15:19 ` Chris C
2014-08-08 16:22 ` Christian Lamparter
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=1535534.mOj91phO2K@blech \
--to=chunkeey@googlemail.com \
--cc=chris.a.cremer@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).