Linksys WMP54G in FC3 using ndiswrapper. Hardware detected but what am I missing?

rhinoss · 12-12-2004, 12:08 AM

I'm currently trying to get my Linksys WMP54G wireless NIC to work under Fedora Core 3 using ndiswrapper. I believe the card to be the v2 card based on the Broadcom 4306 chipset (PCIID 14e4:4320 (rev 3).

I first downloaded and compiled the kernel/userland components of ndiswrapper.

Following instructions here (sourceforge.net) I believe my card to be detected, although when running iwconfig I get the following output.

Code:

[root@localhost ryan]# iwconfig
lo        no wireless extensions.
eth0      no wireless extensions.
sit0      no wireless extensions.

I have recompiled the kernel to insure that WLAN support is included, a suggestion from another set of instructions. Can someone please suggest what my next step might be?

Below is a history of steps performed

Downloaded and compiled ndiswrapper 0.12
Downloaded latest drivers from linksys site

Installed the driver via ndiswrapper

Code:

[root@localhost utils]# ./ndiswrapper -i /home/ryan/downloads/WMP54G/Drivers/WMP54Gv2/bcmwl5.inf
Installing bcmwl5

checked to insure driver was loaded and hardware was present:

Code:

[root@localhost utils]# ./ndiswrapper -l
Installed ndis drivers:
bcmwl5  driver present, hardware present

Inserted ndiswrapper via modprobe "modprobe ndiswrapper" Returned with no error
var/log/messges displays the following

Code:

Dec 11 16:43:53 localhost kernel: ndiswrapper version 0.12 loaded (preempt=no,smp=no)
Dec 11 16:43:53 localhost kernel: ndiswrapper: driver rt2500 (Cisco-Linksys ,LLC.,03/27/2004, 2.02.03.0000) added

At this point the instructions say I should now see a wlan0 device, although I do not.
Any help you can provide would be greatly appreciated. Thanks in advance.

rhinoss · 12-12-2004, 12:40 AM

This appears to be a very strange issue. I powered off the PC and restarted. It now appears to find the interface. I've seen issues with this card and occasional IRQ conflicts. I'm currently researching this issue now.

EDIT: I now have the card working properly. Once I get the time, I will document my process and hopefully give back to the community a little bit. It seems that this is a very problematic card for many people. There are only a few remaining issues that I have yet to work out.

gd2shoe · 12-12-2004, 02:07 AM

IRQ conflicts? I know that many systems today have a feature allowing pci cards to all share 1 IRQ (I think it's called "IRQ steering"). I could be wrong but I think that all systems after the first few with pci slots can do this. For example, my video and ethernet are both on IRQ 11.

This does not mean that you aren't having an IRQ conflict. Just don't jump to conclusions if you see some sharing going on. You may be having some sort of plug-and-play or hardware problem though.

You can use the following to get some information on your hardware:
lspci -v

rhinoss · 12-12-2004, 02:53 AM

gd2shoe, thanks for the reply. I will look into that further. So far, things are looking up. I haven't had any problems with it not being recognized since the first time I got the card to show up.

My current problems are twofold:
1.) I'm having difficulty getting the interface to come up on boot
2.) Once I bring wlan0 up, I am nolonger able to communicate with anything other than my local subnet. Even after the interface is brought back down.

Resolution 1.) I'm currently using this card to connect to a 802.11G linksys router with WPA and preshared keys
after loading ndiswrapper via modprobe, I need to run wpa_supplicant to connect to my router.
I need to somehow find a way to run this app before the network startup script for wlan0 runs

Resolution 2.) Unknown, potentially a problem with DHCP. If anyone would have any information about this, I would appreciate a reply.

current steps to get wlan card up:
1.) modprobe ndiswrapper
2.) ifconfig wlan0
3.) start wpa_supplicant
4.) dhclient wlan0

With eth0 still up I can ping anything on the local subnet, anything beyond yields “destination unreachable”

If possible, could someone explain, or point me to a resource to determine, what steps are typically needed to properly configure a NIC added after the OS install.

If it helps to diagnose, here is the output of ifconfig and iwconfig

Code:

wlan0     Link encap:Ethernet  HWaddr 00:0F:66:6F:04:40
          inet addr:192.168.1.107  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:66ff:fe6f:440/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1155 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:74717 (72.9 KiB)  TX bytes:2037 (1.9 KiB)
          Interrupt:11 Memory:ee000000-ee001fff

iwconfig

Code:

wlan0     IEEE 802.11g  ESSID:"****"
          Mode:Managed  Frequency:2.437GHz  Access Point: 00:0F:66:42:BE:B4
          Bit Rate:54Mb/s   Tx-Power:14 dBm
          RTS thr:2347 B   Fragment thr:2346 B
          Encryption key:***********
          Power Management:off
          Link Quality:100/100  Signal level:-62 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:3783   Missed beacon:0

DavidPhillips · 12-12-2004, 07:05 PM

it looks like dns is not working. Try an ip address on the internet like this one....

64.179.4.149

check /etc/resolv.conf and try to ping those addresses.

run this

dig linuxquestions.org

It could be your firewall is blocking DNS or your /etc/resolv.conf file is not getting updated properly.

KohlyKohl · 12-12-2004, 08:48 PM

Thanks for the help, I couldn't figure out how to get mine to work until I read this. I don't seem to be having the same problems with it as you are thankfully, works great and I can reach outside of the local network just fine.

rhinoss · 12-15-2004, 02:09 PM

After researching further, I've made progress, although I still have a few stumbling blocks in my way.

I've been able to get my card configured so that I can bring it up using ifconfig, and communicate with the local subnet. The two issues I have now, I believe to have a common problem.

When the interface is brought up via ifconfig , no routes are added. This is causing my problem with accessing only my local subnet.

When I try to use the command "ifup wlan0" it fails. I beleive that this uses the config script in "/etc/sysconfig/network-scripts" although I'm not 100% sure of what else I will have to add to get the gateway/default routes to be added automatically.

Are there any resources out there so that I would be able to research properly adding/configuring a NIC? I have done plenty of research and have only found ancient information (6 to 7 years old) or highly glossed over and not mentioning anything about how to configure it via a script to bring it up via init or the "ifup" command.

Any assistance on this front would be appreciated.

Thanks again for all your help.

rhinoss · 12-15-2004, 02:18 PM

Here is the command that fails when using ifup

Code:

[root@localhost network-scripts]# ifup wlan0
Determining IP information for wlan0... failed; no link present.  Check cable?

although I can bring it up using "ifconfig wlan0 up"

Code:

[root@localhost network-scripts]# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:0F:66:6F:04:40
          inet6 addr: fe80::20f:66ff:fe6f:440/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:214 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2660 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15246 (14.8 KiB)  TX bytes:898203 (877.1 KiB)
          Interrupt:11 Memory:ee000000-ee001fff

The contents of my "ifcfg-wlan0" file. It looks identical to my eth0, other than the device name.

Code:

[root@localhost network-scripts]# cat ifcfg-wlan0
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Ethernet

contents of route table after bringing up interface via ifconfig

Code:

[root@localhost network-scripts]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

KohlyKohl · 12-15-2004, 05:48 PM

I use Suse so I won't be of much help, but under Suse I needed to change Type=Ethernet to type=Wireless to get a wireless connection to work. Try that out see if it works.

rhinoss · 12-15-2004, 07:03 PM

KohlyKohl, thanks for the reply. I tried changing the type, although I don't believe it changed anything. I believe the card is actually working correctly. It is just my lack of manually configuring a network card that is holding me up.

Is there any way to find out what process the init is failing on?

after searching through /var/log/messages I found the following log from the wlan0 startup

Code:

Dec 15 19:21:39 localhost ifup: Determining IP information for wlan0...
Dec 15 19:21:45 localhost ifup:  failed; no link present.  Check cable?
Dec 15 19:21:45 localhost dhclient: receive_packet failed on wlan0: Network is down
Dec 15 19:21:45 localhost network: Bringing up interface wlan0:  failed
Dec 15 19:21:48 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Dec 15 19:21:48 localhost dhclient: send_packet: Network is down
Dec 15 19:21:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Dec 15 19:21:55 localhost dhclient: send_packet: Network is down
Dec 15 19:22:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Dec 15 19:22:07 localhost dhclient: send_packet: Network is down
Dec 15 19:22:17 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
Dec 15 19:22:17 localhost dhclient: send_packet: Network is down
Dec 15 19:22:34 localhost dhclient: No DHCPOFFERS received.
Dec 15 19:22:34 localhost dhclient: No working leases in persistent database - sleeping.

KohlyKohl · 12-15-2004, 07:33 PM

i manually modprobed the ndiswrapper in the script that runs the network. Its /etc/init.r/boot.ipconfig. if you run dhcpcd-test what is the output?

akshunj · 12-15-2004, 07:54 PM

Just a suggestion. Are you booting with eth0 enabled ALONG with wlan0? I have the same wireless chipset and experienced similar issues. I stopped BOTH interfaces from starting at boot time. IT has something to do with the /etc/resolve.conf file being overwritten for each interface. After I boot, I choose one and enable it.

modprobe ndiswrapper
iwconfig (to check that wlan0 has been created and found my router)
ifconfig wlan0 (to check if everything looks kosher)
dhcpcd wlan0

And that get's me the ip in 2 or 3 seconds. Then, I'm connected. I hope some of this helps.

--Akshun J

scowles · 12-15-2004, 08:01 PM

I can't tell, but are you using wpa_supplicant in your current test configuration? The reason I ask - I had a heck of a time implementing wpa_supplicant. Not because it doesn't work, but for some strange reason, I had to enable SSID broadcasting on my WAP before I could get an associatation to occur. So the timing of the intit scripts is critical. i.e.

1) start wpa_supplicant
2) wait for an assocation (like 5-10 seconds)
3) start the network.

If I did not follow the above startup order, then iwconfig/ifconfig would show correct output, but the system was unable to communicate on the network. To solve this timing problem, I had to write a wpa_supplicant init script (/etc/init.d/wpa_supplicant, linked as S09wpa_supplicant in /etc/rc5.d) that runs prior to the FC3 network init script (/etc/init.d/network, linked as S10network in /etc/rc5.d). Basically, I added a timer to the wpa_supplicant int script that waits for the wpa association to occur (wich could take 5-10 seconds) before exiting. This delays the network init script from kicking off prior to wpa association.

I can post the script if you're interested.

Good Luck

rhinoss · 12-15-2004, 09:03 PM

I am using wpa_supplicant, although I don't think I'm having any problems with it. Before I got it running I couldn't even get any rx packets from the router. Now that it is running, I'm passing traffic both ways. wpa_supplicant running in debug mode shows that key negotiation was successful.

Code:

WPA: Key negotiation completed with 00:0f:66:42:be:b4

after a reboot DHCP appeared to work properly

Code:

Dec 15 20:21:15 localhost dhclient: sit0: unknown hardware address type 776
Dec 15 20:21:16 localhost dhclient: sit0: unknown hardware address type 776
Dec 15 20:21:16 localhost dhclient: Listening on LPF/wlan0/00:0f:66:6f:04:40
Dec 15 20:21:16 localhost dhclient: Sending on   LPF/wlan0/00:0f:66:6f:04:40
Dec 15 20:21:16 localhost dhclient: Sending on   Socket/fallback
Dec 15 20:21:20 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Dec 15 20:21:21 localhost dhclient: DHCPOFFER from 192.168.1.1
Dec 15 20:21:21 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 15 20:21:21 localhost dhclient: DHCPACK from 192.168.1.1
Dec 15 20:21:21 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf
Dec 15 20:21:21 localhost dhclient: bound to 192.168.1.107 -- renewal in 34382 seconds.

I am, as well bringing up both interfaces on boot. My current network connection is via the eth0 interface. As soon as I get my wireless NIC working I wouldn't mind disabling eth0 on boot.
now I'm to the point again to where I'm pulling a DHCP address the resolv.conf file appears to be getting updated properly.

At what time should the route table be updated? I can bring the interface up via "ifconfig" and pull a correct DHCP address. This is the output of "route" right after I brought up the interface.

Code:

[root@localhost ryan]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 wlan0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

after bringing down the eth0 interface my route table looks like this

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 wlan0

Shouldn't I have a default gateway for my wlan0 interface?

gd2shoe · 12-15-2004, 09:14 PM

That last line looks almost right. In fact, it is right if you are connected through eth0.

Try:

Code:

route del default
route add default gw 192.168.1.1 wlan0

Anytime an interface is down and you bring it up (wanting to use it as the default) you need to remove the defaut route if it exists and add a new one. I suspect that the dhcp client is not using wlan0 as default because you are already using eh0. You can only have one default gateway.