From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ipw2100 firmware broken by 038
Date: Fri, 15 Oct 2004 17:31:06 +0000 [thread overview]
Message-ID: <20041015173106.GC6056@vrfy.org> (raw)
In-Reply-To: <1097852608.10640.14.camel@athena.fprintf.net>
On Fri, Oct 15, 2004 at 11:03:28AM -0400, Daniel Gryniewicz wrote:
> Hi, all
>
> My ipw2100 firmware loading was broken by the update to 038. I've since
> downgraded back to 036 and it's working again. Here's the error message
> from 036:
>
> Oct 14 18:38:50 athena wait_for_sysfs[13120]: error: wait_for_sysfs
> needs an update to handle
> the device '/class/firmware/0000:02:03.0' properly (4), please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
>
> And from 038:
>
> Oct 14 18:34:18 athena wait_for_sysfs[10790]: either wait_for_sysfs
> (udev 038) needs an update to handle the device
> '/class/firmware/0000:02:03.0' properly (4) or the sysfs-support of your
> device's driver needs to be fixed, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
>
> With 036, the firmware loads anyway, and the card comes up. With 038,
> the firmware fails to load with an error from the card of:
>
> Oct 14 18:34:18 athena eth1: Firmware 'ipw2100-1.3.fw' not available or
> load failed.
> Oct 14 18:34:18 athena eth1: ipw2100_get_firmware failed: -2
>
> The firmware is unchanged between the two installs. I'm running gentoo,
> with 2.6.9-rc4-ck2. I'll be happy to answer any necessary questions.
This happens because of the increased timeout of 10 seconds, which is
also the maximum time the driver will wait for the firmware. We are trying to
read a file in the firmware class to be sure, the kernel has it created
but that file is unreadable. I will post a patch to the list in the next
few minutes, that will change to a stat() instead of an open().
Thanks for the report,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-10-15 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 15:03 ipw2100 firmware broken by 038 Daniel Gryniewicz
2004-10-15 17:31 ` Kay Sievers [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=20041015173106.GC6056@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).