Trying to configure Linksys WMPCI54G (wireless-G pci adapter) in Slackware 10.1 Curre
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
So far, so good, but modprobe ndiswrapper gives an error:
Error inserting ndiswrapper. (/lib/modules/22.214.171.124/misc/ndiswrapper,ko), Unknown symbol in module, or unknown parameter (see dmesg)
I checked and found that it installed the module /lib/modules/126.96.36.199/misc/ndiswrapper.ko
I followed the other steps listed such as ndiswrapper -m which added the entry to modprobe.conf (for the 2.6 kernel). Added the specified entries to rc.local and modified rc.wireless.conf and made sure rc.local and rc.wireless start on boot.
Any idea on what I need to do to remove the modprobe error, since I do not think the ndiswrapper module is loading? Or do I have to buy the linuxant driver to use instead of ndiswrapper?
No message at all in dmesg, I can see where the onboard Broadcom ethernet controller loads, but no reference at all for the PCI adapter even though it shows up in lspci hardware list as Network Controller Broadcom Corporation BCM94306 802.11g (rev 03)
So you think I need to uninstall ndiswrapper, and repeat the install, using bcmwl5a.inf with the same .sys driver instead? Would a simple google search find it?
And a question for everyone. What controls automatically loading the ndiswrapper,ko module? Is it rc.local or rc.wireless as opposed rc.modules??
No, you don't need to remove ndiswrapper, just the driver you installed.
You can do that with a simple command:
ndiswrapper -e bcmwl5
both bcmwl5.inf and bcmwl5a.inf install the same .sys windows driver, just with different information. Give it a try. If you have the CD for the card, they'll be on there, other wise you may find bcmwl5a.inf in your windows files, or you can download it. The .sys file will be the same for either.
That means that the kernel doesn't know what the module is trying to do. The kernel is saying 'Unknown symbol wireless_send_event' which means that you probably left wireless network support out of the kernel when you configured it.
Just recompiled wireless support in the kernel. Rebooted on new kernel and presto, wlan0 appears with lsmod showing ndiswrapper module loaded.
Now I need to play around with the code in /etc/wireless.conf for my setup. Once I have it working with the router encryption turned off, I'm going to install the wpa supplicant package and try to enable WPA-PSK encryption. Thanks for putting me on the right track. Just never expanded the networking section of the config file that much.
Will let you know how the tweaking goes. I guess I need to disconnect the ethernet card connection to truly know when I have a good wireless connection!