From: Benoit Boissinot <bboissin@gmail.com>
To: Ed Sweetman <safemode@comcast.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ipw2200 Broken 2.6.13: "firmware_loading_store: unexpected value (0)"
Date: Thu, 22 Sep 2005 13:28:56 +0200 [thread overview]
Message-ID: <40f323d005092204283770b416@mail.gmail.com> (raw)
In-Reply-To: <43328C2B.8060302@comcast.net>
On 9/22/05, Ed Sweetman <safemode@comcast.net> wrote:
> I'm using 2.6.13-mm1, and i tried both 1.0.6 and the included driver
> (both matched with the appropriate ieee80211 driver) and I'm using
> debian unstable's version of hotplug Version: 0.0.20031013-2. I have
> very little installed on this computer as it's a WRAP board with mini
> pci intel 2915. Is anything in userspace required to load firmware
> besides hotplug? I dont use udev or devfs ...not sure if there are /dev
> entries or what.
>
> I'm getting this error constantly (thousands of times a second when
> modprobing the ipw2200 driver (any version)
>
> firmware_loading_store: unexpected value (0)
>
>
> I have the firmware available in every possible accepted location for
> firmware. I have no doubt that it's finding the firmware, but unable
> to load it. My sysfs driver directory for the pci device has no "data"
> file/directory in it, which I thought is where firmware is loaded.
>
> If any other info is required to figure this problem out. Just mention
> it. I'll provide everything. Attached is my config for the kernel in
> question.
>
you should upgrade to at least .13-mm3 or revert :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/broken-out/gregkh-driver-sysfs-strip_leading_trailing_whitespace-fix.patch
regards,
Benoit Boissinot
prev parent reply other threads:[~2005-09-22 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 10:49 ipw2200 Broken 2.6.13: "firmware_loading_store: unexpected value (0)" Ed Sweetman
2005-09-22 11:28 ` Benoit Boissinot [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=40f323d005092204283770b416@mail.gmail.com \
--to=bboissin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@comcast.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.