The Q-n-D WiFi/NDISWrapper Mini-HOWTO:
I decided to install Ubuntu 7.04 a minute ago and had similar problems with no connection. Granted I do use a WEP key and I don't broadcast my ssid so this may be causing me some problems. Drilling holes in the house is starting to become more appealing by the minute though.
Look, once you have the .inf+.sys file for your WiFi card it's pretty much:
#### Let's say you have a Broadcom 43xx based Wi-Fi card like I do, just copy the bcmwl5.inf+bcmwl5.sys
#### into /root and run the following....
/usr/sbin/ndiswrapper -i bcmwl5.inf
#### The following displays whether the Windows driver installed correctly
#### You should see something like the following:
#### bcmwl5 : driver installed
#### device (14E4:4320) present (alternate driver: bcm43xx)
#### If not, try ndiswrapper -r bcmwl5 to remove the driver, then go back to the top for one more go
#### If you try a 'do over', do yourself a favor and remove ndiswrapper w/ 'modprobe -r ndiswrapper' after
#### removing the driver. If a do over doesn't boot WiFi, reboot and start at the top....
#### No one seems to recommend this exc the ndiswrapper people.... /sbin/depmod -a
#### The following shows what the new device name is....
/sbin/iwconfig eth1 channel 11
/sbin/iwconfig eth1 mode Managed
/sbin/iwconfig eth1 ap ap-mac-address
/sbin/iwconfig eth1 key restricted <wep-string-in-hex>
#### /sbin/iwconfig eth1 commit
/sbin/iwconfig eth1 essid "your-ap-name"
/sbin/ifconfig eth1 inet 192.168.3.100 broadcast 192.168.3.255 netmask 255.255.255.0
/sbin/ifconfig eth1 up
/sbin/route add default gw 192.168.3.1
#### or you could use dhcpcd -d -t 30 wlan0 for an automatic IP and skip the
#### 1st ifconfig and the route stmts
Above is an extract from the 2nd-gen script I use to fire up my WiFi-Wired router, so it's perfected. Actually, it's almost a verbatim rip from the NDISWrapper wiki. I literally got my Moto WPCI810G going in under an hour. It took about another day or so til I found the formula for turning the box into a WiFi-Wired router (basically a high-perf ICS PC), which talks to a Netgear wireless router, then out to the Net via the landlord's cable modem. Under (my) Knoppix, the WiFi device is always eth1, but under Slax it's always wlan0, as it's supposed to be. What's happening is:
1) Install the Windows driver
2) Display the driver's installation status
3) Load the NDISWrapper kernel module
4) Display the newly installed wireless device's name and params
5) Configure the wireless device
6) Setup the IP settings (via ifconfig) for a new network device
7) Turn it on
8) Manually setup the default gateway for Internetworking, altho dhcpcd does all of the IP stuf, if you use an auto IP from the AP/router.
I manually set the IP and default route bec I use port forwarding (from the Netgear) for P2P/RDP/VNC apps. Just to get started, one can skip those commands and simply bring up the device and prime it via dhcpcd. I wanted to go w/ disabled SSID broadcasts too, but I had to get the router working very quickly and simply couldn't coax Windows into dealing w/o a SSID. But I was able to get WPA-PSK going under Windows+Knoppix+Slax, which is much more robust than WEP, so I could live w/ the SSID broadcasts.
Where do the .inf/.sys files come from ? From the driver disc for the device, of course. You do have the driver disc ?
Well, assuming you don't, you can obviously go back to the card's vendor and d/l a driver kit or you can resort to digging into the bowels of the beast and extract them from Windows itself. The Windows Device Manager entry for the device has a Device tab w/ a Device Details button, which should give you the location of the .sys and .inf files. If the .inf isn't indicated, it's somewhere under \WINDOWS\INF.
For completeness sake, there are some built-in kernel modules that do WiFi directly. My bcm4306 is almost
supported w/ the bcm43xx kernel module under Knoppix. Almost, as it requires a slightly illegal util which extracts (cuts) downloadable firmware from the .sys file of the Windows driver and loads it via the bcm43xx kernel module. It was great until the great WPA migration weekend, at which time the bcm43xx kernel module decided it didn't grok WPA. WPA means wpa_supplicant, which is a matter for another post.
Truth is, unless you have one of a handful of wireless cards (don't ask, as I don't know other than the Orinoco cards), no distro does universal turnkey WiFi. More WiFi drivers are coming out w/ every kernel update but NDISWrapper really is our friend....Jet
PS: Kof, this wasn't exclusively for your benefit, but once I started typing, I figured I go ahead and make this into a mini-HOWTO for everyone else....
PPS: The Code box w/ the script uses full paths for the programs as installed on Knoppix
. Your mileage will
vary, in order to use it on another distro. As always, copy+paste w/ brain engaged.
Edited by jetman, 30 April 2007 - 09:07 PM.