FC3, ndiswrapper, dlink dwl-650+

[James Pifer]

On Tue, 2005-03-15 at 15:52, Michael D. Setzer II wrote:
> http://www.neowin.net/forum/lofiversion/index.php/t292721.html
> 
> 4.) Type: ndiswrapper -l <-- That's the letter 'L' by the way (not the 
> number one). This verifies the installation of the Windows driver
> 5.) Type: /sbin/modprobe ndiswrapper (hit enter)
> 6.) Type: ndiswrapper -m (hit enter)
> 7.) Type: /sbin/dhclient wlan0 (This activates the wireless 
> connection - FINALLY!)
> 
> This isn't the page I used earlier, but it is one I just found in a 
> search.
> 
> After Step 5 and 6, I use system setting/network then do a new, and 
> activate the wlan0.
> 

I tried it at first with only the internal Broadcom card. I also tried
it with my dlink card. No luck. 

Maybe I'm using the wrong drivers (but I don't think so). lspci shows me
both of my wireless cards:

02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212
802.11abg NIC (rev 01)


When I run /sbin/dhclient wlan0 I get:

[root at laptop ~]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
 
SIOCSIFADDR: No such device
wlan0: unknown interface: No such device
wlan0: unknown interface: No such device
Bind socket to interface: No such device
 
If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.
 
If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server at isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.
 
Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.
 
exiting.


Seems like it's close!

Thanks,
James