From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: kronos@kronoz.cjb.net
Cc: Keenan Pepper <keenanpepper@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: ipw2200 only works as a module?
Date: Mon, 26 Sep 2005 23:11:43 -0600 [thread overview]
Message-ID: <4338D48F.3090807@linuxwireless.org> (raw)
In-Reply-To: <20050926171220.GA9341@dreamland.darkstar.lan>
Luca wrote:
>Keenan Pepper <keenanpepper@gmail.com> ha scritto:
>
>
>>With CONFIG_IPW2200=y I get:
>>
>>ipw2200: ipw-2.2-boot.fw load failed: Reason -2
>>ipw2200: Unable to load firmware: 0xFFFFFFFE
>>
>>but with CONFIG_IPW2200=m it works fine. If it doesn't work when built into the
>>kernel, why even give people the option?
>>
>>BTW, a better error message than "Reason -2" would be nice. =)
>>
>>
>
>-2 is -ENOENT (no such file or directory). ipw2000 requests its firmware
>using a hotplug event, but when the driver is compiled into the kernel
>it gets loaded _before_ the root fs is mounted and of course the hotplug
>system and the firmware are not available.
>
>I suggest to stick with modular driver, otherwise you must create an
>initrd with hotplug + firmware.
>
>
I think I have seen this but in FC3 or FC4. We have had issues with them
loading things too soon and then making the driver to fail loading.
Try it with * built in and then once booted to load it. If it works,
then is a distro thing. It works for me here in Debian with Y or as a
module.
.Alejandro
>More on firmware loading here: http://lwn.net/Articles/32997/
>
>Luca
>
>
next prev parent reply other threads:[~2005-09-27 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 15:22 ipw2200 only works as a module? Keenan Pepper
2005-09-26 17:07 ` Bharath Ramesh
2005-09-26 17:12 ` Luca
2005-09-27 5:11 ` Alejandro Bonilla [this message]
2005-10-19 21:35 ` Rob Landley
2005-10-22 22:50 ` Alistair John Strachan
2005-10-23 22:19 ` Alejandro Bonilla Beeche
2005-10-24 6:17 ` Denis Vlasenko
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=4338D48F.3090807@linuxwireless.org \
--to=abonilla@linuxwireless.org \
--cc=keenanpepper@gmail.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@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.