Hey all,

I recently put SlackWare 10.0 on my Dell 600m. I'm having problems setting up the wireless card. I got the drivers from the site recommended by the Installtion guide. After I install the .inf file, I type
I see from that the hardware is present. Then when I type "modprobe ndiswrapper" this is what outputs.

Any clues would be helpful. Its been shown that this Card can work with Linux if you use ndiswrapper, but I can't seem to get it to work correctly.

Thanks

These are the commands that I'm using from the shell

root@MyLaptop:~# ndiswrapper -i /root/bcmwl5a.inf
Installing bcmwl5a
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
root@MyLaptop:~# ndiswrapper -l
Installed ndis drivers:
bcmwl5a driver present, hardware present
root@MyLaptop:~# modprobe ndiswrapper
/lib/modules/2.4.26/misc/ndiswrapper.o: unresolved symbol ndiswrapper_remove_one
/lib/modules/2.4.26/misc/ndiswrapper.o: insmod /lib/modules/2.4.26/misc/ndiswrapper.o failed
/lib/modules/2.4.26/misc/ndiswrapper.o: insmod ndiswrapper failed
root@MyLaptop:~#

Just a thought....

Since you're using a 2.4 series kernel, you might want to jump to an earlier version of ndiswrapper (like 0.7 or so). Getting ndiswrapper to work can be an annoying trial and error of kernel version, ndiswrapper version and driver and I know the most recent versions of ndiswrapper were modified to allow it to function on 2.6.10 kernels. That may be goofing up ability on 2.4 kernels.

Thanks for the response, I'm actually trying to upgrade to the 2.6.10 kernel at the moment. For what I've read, APCI is built into it and should make my battery last a little long since I'm on a laptop. Also like you said ndiswrapper should run better.

I found this one site for a good linux recompile tutorial.

http://www.digitalhermit.com/linux/K...ild-HOWTO.html

But I'm having problems when trying to apply the patches to the source. RIght now I'm stuck at "Extract and Patch" on their guide. The message I get is that the patch was already detected. Does that mean I can skip that step?

I changed my mind about upgrading to the newer kernel. I just got ndiswrapper 0.7 and it is working fine, good call

Ok well, I got ndiswrapper working correctly. I added this to /etc/rc.d/rc.modules
/sbin/modprobe ndiswrapper

When my laptop boots up, it recongizes the hardware. Now how do I go about connecting to my AP. It has WEP enabled. Do I need to add more to rc.modules? Or can I configure KWifiManager? My WEP key is pretty long and it doesn't fit in the String box for the keys.

Ok, I added these lines to /etc/rc.d/rc.modules

iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted MY_WEP_KEY
iwconfig wlan0 essid MY_ESSID

When I log into a session, I can see from KWifiManager that I am connected to the router, but how do I get an IP

I also tried
dhcpcd wlan0

But that doesn't do anything

You can simply add the settings you want to /etc.rc.d/rc.wireless.conf. Example settings:
ESSID="your_essid"
MODE="Managed"
RATE="auto"
KEY="1234-abcd-gggg-9999..."

I'd put dhcpcd wlan0 in /etc/rc.d/rc.local.

As for not pulling an IP, any errors? Does the router have a log? If so, any hints there?

I haven't been able to get /etc/rc.d/rc.wireless.conf to work correctly but I'll look at that later. The way I have everything loading in rc.local is setting the ESSID and KEY. I can see the information about my router even the local mac address of it through KWifiManager. By using "dhcpcd wlan0" it isn't assigning an IP address to the interface. When I do route, I'm only seeing one entry and it is soemthing like 127.0.0.1. How else can I set this up?

Hey guys,

I finally got it working, and I figured out how to use /etc/rc.d/rc.wireless.conf. The only problem I had was I didn't put "open" where I define the key KEY="open XXXXX". Now it is working great. Thanks for the help