All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Talbut <jt@dpets.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: Firmware loading with static kernel and initramfs
Date: Sun, 29 Jun 2014 20:19:01 +0100	[thread overview]
Message-ID: <53B066A5.4070003@dpets.co.uk> (raw)
In-Reply-To: <53B05B72.1010502@lwfinger.net>



On 29/06/14 19:31, Larry Finger wrote:
> On 06/29/2014 12:15 PM, John Talbut wrote:
>> There seems to be a general problem when using a static kernel and
>> initramfs in
>> that the wireless drivers try to load firmware before the disks are
>> mounted and
>> the /lib/firmware folder is available.  Various people seem to have
>> come across
>> problems with firmware not loading, some of which seem to relate to this
>> problem, which they have approached as if it is a problem with their
>> particular
>> driver.  However it seems to be a general problem and I have had it
>> with three
>> different drivers.
>>
>> There seems to be a number of possible approaches to this: loading the
>> firmware
>> in an initramfs; changing the sequence in which wireless drivers start
>> so that
>> they wait until the disks are mounted; compiling the firmware into the
>> kernel
>> and loading the firmware as part of ifup. I see that the latter has
>> been done
>> for one driver
>> (http://thread.gmane.org/gmane.linux.kernel.wireless.general/3390).
>>
>> What is the current situation with this problem and what needs doing?
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> What kernel version, and what wireless drivers have this problem?
>
> At one point, there was a timeout of 30 seconds for request_firmware()
> calls, and that led to problems even when the drivers were built as
> modules. That situation was handled in a number of wireless drivers by
> using request_firmware_nowait(); however, my understanding was that user
> space was fixed to avoid the timeout. I think udev was the component
> that changed. What version of that are you using?
>
> Larry
>
I originally had the problem with a Broadcom BCM43225 wireless.  This 
was with a 3.8 kernel.  This was solved by a patch to the kernel 
brcmsmac driver and this is still working with a 3.14 kernel.

Currently I have the problem with an Intel Centrino Wireless-N 130.  The 
problem was present with a 3.11 kernel and currently with a 3.14 kernel. 
  udev version 204-5linuxmint.

A friend seems to have the problem with a Realtek 8129se wireless but we 
are still checking out that this is the problem.

John

  reply	other threads:[~2014-06-29 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 17:15 Firmware loading with static kernel and initramfs John Talbut
2014-06-29 18:31 ` Larry Finger
2014-06-29 19:19   ` John Talbut [this message]
2014-06-29 22:11     ` Larry Finger
2014-06-30  5:09       ` John Talbut
2014-06-30  8:22         ` Arend van Spriel
2014-06-30  9:08           ` John Talbut

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=53B066A5.4070003@dpets.co.uk \
    --to=jt@dpets.co.uk \
    --cc=Larry.Finger@lwfinger.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 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.