ndiswrapper installed, driver installed. No device appears...
So I have just tried to compile ndiswrapper from source. The install went great but when I opened up my network configuration it wouldn't show the wlan(0) ndiswrapper device. Any ideas?
|
look for the ndiswrapper module in the "lsmod" listing.
Check if the driver is loaded: ndiswrapper -l Also, did you run the "ndiswrapper -m" step to update the depmod.conf file? Did you run "modprobe ndiswrapper" as root? Check if the kernel module exists. "ls /lib/modules/`uname -r`/misc/" Another thing that could have gone wrong is if you loaded the wrong ndis windows driver. Part of the build process runs "depmod -a". You could try running this manually as root, incase it wasn't done for some reason. Also, if the installation adds a library path, you could try running "ldconfig". Make sure that you have the "wireless-tools" and "wpa_supplicant" packages installed. The command from wireless-tools: "iwlist wlan0 scan" is a good way of seeing if the wireless device is operable. |
hmmm...
so my device shows, my kernel module is loaded, I can see my router, I just can't get a connection. please reference following outputs:
iwlist: Code:
wlan0 Scan completed : Code:
Module Size Used by I am compiling ndiswrapper 1.10 from source and installing the same broadcom inf that was working so beautifully for my FC4 build. I am running an x86_64 architecture in case that matters. I can see my networks but I can't connect (I am entering the right WEP key as well). One point of note is that wlan0 will not show up under ifconfig. dmesg seems to be showing everything loading just fine. As mellon-ticklers go this one's a honeydew for me. -Kurt |
Ndiswrapper seems to be loaded and working. You need to configure the interface for your network and encryption type. I don't know which wireless network is yours in the iwlist scan. The first one is using wpa encryption. Don't use WEP! Anyone can crack in in 30 minutes time. You have wireless-tools installed. How about wpa_supplicant?
However, I noticed a difference between your lsmod listing and mine: ndiswrapper 215784 0 usbcore 140596 5 usbhid,ehci_hcd,ohci_hcd,ndiswrapper This may not be important. The interface not showing up in ifconfig tells me that the interface isn't starting. For example, if I shutdown an interface ( In SuSE, by " sudo /sbin/rcnetwork stop wlan0", the interface will disappear from the ifconfig listing. ) I think in Fedora, you can run "ifup wlan0". There may be something like "service network start wlan0" but you will need to read your documentation to be sure. First try manually starting the interface, and then see if it shows up in ifconfig. Also look at the "iwconfig" output. If starting the interface manually causes it to be displayed in ifconfig, the restart the dhcp client and see if you get an IP address assigned. If that works, then look into why the interface isn't being started by the network service when you boot up. You will either have to turn off encryption at the router, to test the dhcp client, or setup encryption first. You will need to be able to associate before you will be assigned an IP address by dhcp. ---- Check in "sudo cat /proc/net/ndiswrapper/wlan0/hw" for a line like: encryption_modes=WEP; TKIP with WPA; AES/CCMP with WPA at the bottom of the listing. This will give the capabilities of ndiswrapper. If you don't see TKIP with WPA, install a newer version. This is what you would use at home. This uses a pre-shared key, that is entered for all wireless devices in your network. |
...And the saga continues
So I somehow got a connection but it configured very strangely. Somehow wlan0 won't find an IP but eth1 finds one, which is really amazing since eth1 is not physically connected to anything. See ifconfig output below.
ifconfig: Code:
eth0 Link encap:Ethernet HWaddr 00:0F:EA:89:04:49 |
Yes, sometimes the wireless is referred to as eth1. The wired NIC interface is eth0. You want to configure eth1.
You may need to shut down eth0 also before things work. Also it looks like you have an IP address. Did you configure it for dhcp. If so, then you are probably associated with the Access Point. Try pinging the router. Also check the /etc/resolv.conf file. With dhcp, the client will overwrite this file with the value of the DNS servers (nameservers). The output of "route" will display the routing table. You can determine if the default gateway is correct. If it is, you might only need to powercycle the router. It's also a dhcp client on the WAN side, and may need to restart the dhcp client on the ISP side before you can get on the internet. If you use KDE, I would recommend using KInternet. An icon shows up in the panel tray. You can simply click on it to reconnect to the AP. Also, you can right-click on it and select "wireless connection..." to check the status of the connection or to scan for other networks and select one to associate with. |
All times are GMT -5. The time now is 01:25 PM. |