From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 17 Oct 2004 11:10:33 +0000 Subject: Re: wait_for_sysfs needs an update to handle the device '/class/net/wlan0' properly Message-Id: <20041017111033.GB3649@vrfy.org> List-Id: References: <1097699112.416d8f28dae2b@mail.utca.hu> In-Reply-To: <1097699112.416d8f28dae2b@mail.utca.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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 > > 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