From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs needs an update to handle the device '/class/net/wlan0' properly
Date: Sun, 17 Oct 2004 11:10:33 +0000 [thread overview]
Message-ID: <20041017111033.GB3649@vrfy.org> (raw)
In-Reply-To: <1097699112.416d8f28dae2b@mail.utca.hu>
On Sun, Oct 17, 2004 at 09:34:39AM +0200, Ralf Hildebrandt wrote:
> When using ndiswrapper to load a driver, I get:
>
> Oct 17 00:28:54 kasbah kernel: ndiswrapper version 0.11 loaded (preempt=yes,smp=no)
> Oct 17 00:28:54 kasbah loadndisdriver: loadndisdriver: main(479): version 0.11 started
> Oct 17 00:28:54 kasbah kernel: This driver (bcmwl5a) is not for your hardware. It's likely to work anyway but have it in mind if you have problem.
> Oct 17 00:28:54 kasbah kernel: ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 10 (level, low) -> IRQ 10
> Oct 17 00:28:54 kasbah kernel: ndiswrapper: using irq 10
> Oct 17 00:28:54 kasbah udev: creating device node '/dev/ndiswrapper'
> Oct 17 00:28:55 kasbah kernel: wlan0: ndiswrapper ethernet device 00:90:4b:57:40:c9 using driver bcmwl5a
> Oct 17 00:28:55 kasbah kernel: wlan0: encryption modes supported: WEP, WPA with TKIP
> Oct 17 00:28:55 kasbah kernel: ndiswrapper: driver bcmwl5a () added
> Oct 17 00:28:55 kasbah pumpd[4960]: starting at (uptime 0 days, 0:01:19) Sun Oct 17 00:28:55 2004
> Oct 17 00:28:55 kasbah pumpd[4960]: PUMP: sending discover
> Oct 17 00:29:00 kasbah pumpd[4960]: got dhcp offer
> Oct 17 00:29:00 kasbah pumpd[4960]: PUMP: sending second discover
> Oct 17 00:29:00 kasbah pumpd[4960]: PUMP: got an offer
> Oct 17 00:29:00 kasbah wait_for_sysfs[4956]: error: wait_for_sysfs needs an update to handle the device '/class/net/wlan0' properly, please report to <linux-hotplug-devel@lists.sourceforge.net>
>
> The card works, yet the warnign should probably be addressed anyway.
> 2.6.9-final
I expect that the ndiswrapper doesn't create a "device" symlink to the
physical device in the /class/net/wlan0 directory, so the driver should
be fixed.
Thanks,
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
next prev parent reply other threads:[~2004-10-17 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 20:25 wait_for_sysfs needs an update to handle the device properly Csan
2004-10-14 0:01 ` Greg KH
2004-10-15 9:50 ` wait_for_sysfs needs an update to handle the device '/class/drm/radeon' properly Peter Van Eynde
2004-10-15 11:10 ` Kay Sievers
2004-10-17 7:34 ` wait_for_sysfs needs an update to handle the device '/class/net/wlan0' properly Ralf Hildebrandt
2004-10-17 11:10 ` Kay Sievers [this message]
2004-10-29 0:45 ` wait_for_sysfs needs an update to handle the device '/class/capi/capi' Marc Schiffbauer
2004-10-29 1:05 ` wait_for_sysfs needs an update to handle the device '/class/firmware/0000:01:0d.0' Marc Schiffbauer
2004-10-30 3:17 ` Kay Sievers
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=20041017111033.GB3649@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).