Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
I've been encountering similar problems lately, and came across this thread. However, in my case it is slightly worse. I have the Linksys WMP54G with the Raylink 2500 chipset. I have installed ndiswrapper (a relatively new version, I downloaded it a few months ago) and run modprobe, and everything looks fine. However, I can't set any parameters using iwconfig. Currently, the essid is listed as "off/any" and the mode is managed. I cannot change the mode, set the essid, set the key, anything. Any ideas?
I am running Suse 10.1, kernel 220.127.116.11-4. I ran lspci, and the output was rather large. Is there something in particular that you want to know, or should I post the entire transcript?
When I do ndiswrapper -l, it says that hardware and driver are present and installed. The module is loaded, and iwconfig wlan0 shows the configuration, with ESSID=any/off, and MODE=auto. I cannot change either of these. I have tried configuring Network Devices through Yast, but I think I must be doing something there because that has even less success than iwconfig.
Also, when I do iwlist wlan0 scan, it finds the network I am trying to connect to, but says the signal strength is 0/100. I know this is not true, because I am using that network right now in Windows (dual boot).
I would like to see the lines that say network. So if you want a smaller output you can just run lspci | grep network.
My output looks something like this 02:02.0 Network controller: RaLink RT2500 802.11g .
The reason I ask is because there may be a better way to get your card up and running if you have an identical chip in your card. If you have this same chipset then you could use the drivers from this http://rt2x00.serialmonkey.com/wiki/index.php/Downloads site. I've been using the drivers from this site in both 32bit and 64 bit systems for almost 2 years. They are rock solid and don't drop my connection like my windows drivers do. This would allow you to get away from using ndiswrapper if at all possible. ndiswrapper should only be used as a last resort as it can cause some serious stability issues to the kernel. I am currently using Debian as my distribution, but I believe last time I used Suse I was able to get the drivers source code as an RPM and setup the drivers easily.
Thanks for the advice. I do have that same chipset, and I actually have tried to install the drivers myself, but ran into trouble. I have been trying to use ndiswrapper on a friend's laptop with broadcom 4318 chipset, and have had some (limited) success, so I thought I'd try that on my desktop at home. However, I would prefer to use the native drivers if possible.
The problem I had before was with compiling the driver. As I recall, there were different instructions for kernel version 2.4.x and 2.6.x, and since I have 18.104.22.168-4, I used the latter. One of the arguments for make was the path to the kernel, which I gave, but I always got an error about a missing file. I don't remember the exact syntax now; I will look up that information and post the commands I entered as well as the output as soon as possible.
So last night I downloaded the newest Linux drivers for the Ralink RT2500 chipset. I tried to follow the instructions for compiling in the readme, but I got the same errors as before. The readme says:
For 2.6 series kernel:
a. run 'cd STA/Module'
'cp ./2.6.x/Makefile .'
'cp ./2.6.x/load .'
b. $make -C /path/to/source SUBDIRS=$PWD modules
Where /path/to/source is the path to the source directory for the (configured and built) target kernel.
So I typed:
make -C /usr/src/linux SUBDIRS=$PWD modules
and the output was:
make: Entering directory `/usr/src/linux-22.214.171.124-4'
Makefile:450: .config: No such file or directory
This was followed by a bunch of other warnings and errors as make apparently couldn't find what it was looking for.
So my question is, did I enter the command wrong, or am I missing files in my kernel source (or something else)?
WOOHOO!!!! I am writing this post via my very own wireless connection. I was finally able to install the driver, rather than using ndiswrapper. However, I did not use the ones from the Ralink website; instead, I got downloaded the driver from http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz. I also found a page which was very helpful in the installation process http://linux.wordpress.com/2006/05/1...-rt2500-wi-fi/, though I think the readme with this driver set would work just as well. After compiling the driver and inserting the module, I had to configure the card, which I did through the network card in Yast. After that I rebooted, and the device was brought up when Linux started. I still couldn't connect to the internet, even though I could see and connect to the network, so I ran "dhcpcd wlan0". I've been online ever since.
So the moral of the story is, if you have the Linksys WMP54G (or other wireless card based on the Ralink RT2500 chipset), you're much better off using the native Linux drivers than trying to get ndiswrapper to work. Furthermore, if you are running Suse 10.1, it seems that the drivers on the Ralink website might not work, so use the ones from serialmonkey.