From: Mourad De Clerck <bugs-wireless@aquazul.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: firmware loading fails for b43 using linux 3.4?
Date: Thu, 24 May 2012 06:38:32 +0200 [thread overview]
Message-ID: <4FBDBB48.8080004@aquazul.com> (raw)
In-Reply-To: <4FBDA4FE.6040603@lwfinger.net>
On 24/05/12 05:03, Larry Finger wrote:
> The second solution is to make multiple tries of the read of the first
> firmware file. If the driver is a module, the first read will succeed,
> thus there is no penalty for that case. If the read fails, the code
> sleeps for 2000 ms, then retries the read. On my system, the 3rd try
> works, thus the loop count is set to 10.
>
> Please try the patch below on your system. If it works, please report
> the number in the line from the dmesg output that states "**********
> loop count at exit 2".
Well, I just tried it. It kinda works, but it seems a bit brittle.
Just after recompiling and rebooting, by chance my system needed a fsck,
which seemed to delay it enough for it to go beyond the loop count, and
it failed to load the firmware.
(Even without the fsck, my laptop could hang around indefinitely in
early userspace waiting for me to type in my cryptoroot password)
Anyway, the second time I rebooted, it was fast enough (without the
fsck) to load the firmware.
dmesg reported "********** loop count at exit 5" in that case.
-- M
next prev parent reply other threads:[~2012-05-24 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 23:49 firmware loading fails for b43 using linux 3.4? Mourad De Clerck
2012-05-24 1:13 ` Larry Finger
2012-05-24 2:44 ` Mourad De Clerck
2012-05-24 3:03 ` Larry Finger
2012-05-24 4:38 ` Mourad De Clerck [this message]
2012-05-24 13:25 ` Larry Finger
2012-05-24 16:41 ` Mourad De Clerck
2012-05-24 16:43 ` Arend van Spriel
2012-05-24 19:36 ` Larry Finger
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=4FBDBB48.8080004@aquazul.com \
--to=bugs-wireless@aquazul.com \
--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 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).