i downloaded ndis wrapper, installed it, installed the drivers for the card, and every time i do what the instractions say to do after that point does not work. heres what it says:
If you get no error the driver should now be loaded. You can verify this by checking system log produced by dmesg. If the driver is loaded successfully, you should see a message in the system log
ndiswrapper version <version> loadedMake sure the version <version> here matches the version of ndiswrapper package that you downloaded and installed. If you get a different version, you have old version of package, which you should Uninstall and go back to step 1.
If after modprob'ing, system is locked up no response to keyboard etc., it indicates that kernel has crashed. See Distributions and FAQ for hints on what may cause problems for your distribution/kernel.
If you have successfully installed windows drivers earlier with ndiswrapper -i INFfile, the ndiswrapper module will load them all. You should then see the following messages in system log
ndiswrapper: driver ''driver1'' addedfor each of the drivers. If you don't see these messages, it usually means that there are no usable drivers installed in /etc/ndiswrapper directory. Check if the /etc/ndiswrapper directory has one sub-directory for each driver and if in each driver's directory there are inf, sys and conf files. Otherwise, you may need to repeat step 2.
If this does not bring up the lights on the card, try ejecting it and re-inserting it.
If the system has a card that works with one of the loaded drivers, you should see the following message in the system log
wlan0: ndiswrapper ethernet device xx:xx:xx:xx:xx:xx
Use iwconfig to configure wireless network interface. First, see if the interface is available, with
iwconfigThis tool is not likely to be present on your system : it is part of the package Wireless Tools for Linux, which you should install. This will print the wireless interface e.g., wlan0. In the examples below wlan0 is used replace wlan0 with the interface reported by iwconfig above. The wireless configuration to be used should match what your Access Point AP uses. First, find out if you can see your access point (AP) with
iwlist wlan0 scanNote: You may have to set the network name before the scan can find your Access Point. If the scan does not find your AP, try issuing the command
iwconfig wlan0 essid ESSIDbefore the using the command
iwlist wlan0 scanIf this lists your AP, you can continue. Otherwise, you may have one of two problems: Your AP doesn't broadcast SSID see the FAQ for more information or the radio of the card is off again, see the FAQ for details. If you see the AP in scan above, set the operating mode of the interface according to your setup. In most cases, it is Managed
iwconfig wlan0 mode ManagedIf you use encryption WEP, set the key:
iwconfig wlan0 key restricted XXXXXXXXYou can use 10 hex digits for 40-bit encryption or 26 hex digits for 128-bit encryption. You may need to use open security mode instead of restricted depending on the setup of your AP. If you want to write the key in ASCII use s: e.g. iwconfig wlan0 key restricted s
assword. Set the network name
iwconfig wlan0 essid ESSIDReplace ESSID with the network name used by your AP.
At this point, check to make sure that ESSID is set in output of iwconfig wlan0. If you see the ESSID as you set, you can proceed to next step. If you see ESSID: off/any, then your card is not associated to AP. Check if WEP encryption is set exactly as used by AP and the AP broadcasts ESSID. See FAQ for more details. Until ESSID is set in output of iwconfig wlan0, you may not use wlan0 as network interface.
Now, setup the network parameters for the interface wlan0. This varies from distribution to distribution. Refer to your distribution's documents on how to do this. Once this is done, you can use network tools to bring up the network e.g.,
ifconfig wlan0 upor
Remember, if you have a firewall, to let it know that wlan0 is an external interface and allow it to pass traffic otherwise you won't even be able to ping your AP
Create module alias: Once everything works fine you can write the correct modprobe settings to load ndiswrapper automatically when wlan0 interface is used, by running
ndiswrapper -mNote that this doesn't automatically load ndiswrapper module at boot time. If you want the module to be loaded automatically at boot time, you should configure your module setup, which depends on the distrbution. Most distributions will load all modules listed in /etc/modules at boot time. Mandrake 10.x uses /etc/modprobe.preload. For them, you can add a line
WPA support: See WPA Wiki on how to use Wi-fi Protected Access with ndiswrapper
Retrieved from "http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation"
now, i didnt get any errors, so it should be fine, however, i have no clue where the system log files is so i cant go back and check it. anyone have any suggestions?