linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [QUERY] Intel Centrino Wireless-N 100 modules vs built-in
Date: Wed, 12 Jun 2013 13:00:08 +0100	[thread overview]
Message-ID: <20130612120008.GA10459@sauron> (raw)
In-Reply-To: <1371037816.8601.13.camel@jlt4.sipsolutions.net>

Hi Johannes,

On Wed, Jun 12, 2013 at 01:50:16PM +0200, Johannes Berg wrote:
> Nick,
> 
> > Device Drivers->Network Device Support->Wireless LAN
> > 
> > <M>   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
> > -M-   Intel Wireless WiFi DVM Firmware support
> > 
> > all is hucky dory.  But if I build-in these drivers into kernel (<*>), on boot dmesg reports:
> > 
> > [2.347954] iwlwifi 0000:05:00.0: request for firmware file 'iwlwifi-100-5.ucode' failed.
> > [2.351885] iwlwifi 0000:05:00.0: no suitable firmware found!
> > 
> > Am I missing something here - I don't quite understand why this happens?
> 
> The driver has to request firmware when the device is bound to it, so it
> can then register correctly with mac80211. Newer versions of udev don't
> respond negatively if they don't have the firmware while running from
> initrd/initramfs, and will leave the driver's request pending to be
> answered once the real filesystem is mounted. You seem to not be running
> a version of udev with this logic.
> 
> To work around it, you could include the firmware in the
> initrd/initramfs.
> 
> Alternatively, you could unbind/re-bind the driver after the system has
> full booted, like this:
> 
> # echo 0000:05:00.0 > /sys/module/iwlwifi/drivers/pci\:iwlwifi/unbind
> # echo 0000:05:00.0 > /sys/module/iwlwifi/drivers/pci\:iwlwifi/bind
> 
> This will force it to attempt to load the firmware from disk again.

Thank you very much for a comprehensive reply.

I am using Linux-Mint on this machines, so at the moment am using the 'debian fakeroot make-kpkg...' stuff, so the build is dumbed down for the user ('tis easy on my Slackware box!).

So, reading what you said, I think I will leave 'as is'.

Again, thank you for the reply, and 'sorry for the noise!'

Nick
-- 
Free Software Foundation Associate Member 5508
http://linicks.net/

      parent reply	other threads:[~2013-06-12 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 11:23 [QUERY] Intel Centrino Wireless-N 100 modules vs built-in Nick Warne
2013-06-12 11:50 ` Johannes Berg
2013-06-12 11:55   ` Johannes Berg
2013-06-12 12:01     ` Nick Warne
2013-06-12 12:00   ` Nick Warne [this message]

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=20130612120008.GA10459@sauron \
    --to=nick@linicks.net \
    --cc=johannes@sipsolutions.net \
    --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).