All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Nick Warne <nick@linicks.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:50:16 +0200	[thread overview]
Message-ID: <1371037816.8601.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130612112326.GA10313@sauron> (sfid-20130612_133412_709863_242F03A2)

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.

johannes


  reply	other threads:[~2013-06-12 11:50 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 [this message]
2013-06-12 11:55   ` Johannes Berg
2013-06-12 12:01     ` Nick Warne
2013-06-12 12:00   ` Nick Warne

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=1371037816.8601.13.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nick@linicks.net \
    /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.