From: Lars <terraformers@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 034 wait_for_sysfs another one
Date: Tue, 12 Oct 2004 08:41:45 +0000 [thread overview]
Message-ID: <ckg5cf$8l3$1@sea.gmane.org> (raw)
In-Reply-To: <41689EDA.1050107@speakeasy.net>
yes, firmware is in /lib/firmware and worked nice before.
guess it went worse with the latest fedora rawhide updates.
maybe udev-034-2 is causing this.
thanks
lars
Greg KH wrote:
> On Mon, Oct 11, 2004 at 04:50:28PM +0200, Lars wrote:
>> nearly the same here with my wireless card,
>> after some time it starts working but i get:
>>
>> Oct 11 15:36:31 uptimegrrl kernel: prism54: request_firmware() failed for
>> 'isl3890'
>> Oct 11 15:36:31 uptimegrrl kernel: eth2: could not upload firmware
>> ('isl3890')
>
> Hm, do you have your firmware in /lib/firmware? That's where the latest
> hotplug scripts expect it to be.
>
>> Oct 11 15:37:58 uptimegrrl wait_for_sysfs[3567]: error: wait_for_sysfs
>> needs an update to handle the device '/class/firmware/0000:01:09.0'
>> properly, please report to <linux-hotplug-devel@lists.sourceforge.net>
>
> Thanks for the report. Because of this, the next version of udev should
> not report these errors. If it does, please let us know.
>
> thanks,
>
> greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-10-12 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 2:30 udev 034 wait_for_sysfs another one Andrew
2004-10-11 14:50 ` Lars
2004-10-11 22:40 ` Greg KH
2004-10-11 22:41 ` Greg KH
2004-10-12 8:41 ` Lars [this message]
2004-10-12 15:10 ` Greg KH
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='ckg5cf$8l3$1@sea.gmane.org' \
--to=terraformers@gmx.net \
--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).