Modprobe ndiswrapper freezes my OpenSuse 10.2 with Netgear WN511T wireless card
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Modprobe ndiswrapper freezes my OpenSuse 10.2 with Netgear WN511T wireless card
I have an old Gateway 5300 laptop 750 Mhz. Pentium III with 256 Mb RAM and decided to install OpenSuse 10.2 (uname -a reads 'Linux linux-36li 126.96.36.199-0.9-default #1 SMP Sun Feb 10 22:48:05 UTC 2008 i686 i686 i386 GNU/Linux').
The problem I'm having is that I can't get my NetGear WN511T wireless card to work. I've downloaded and installed 'ndiswrapper 1.48-6.1 i586' from the OpenSuse page and the newest Windows XP drivers from the NetGear site.
I used 'ndiswrapper -i' with no errors
I run 'ndiswrapper -l' and it shows:
netmw14x : driver installed
device (11AB:2A02) present.
I run 'ndiswrapper -m' and it loads in the mod list ('lsmod').
But when I run 'modprobe ndiswrapper' my system freezes. Only a hard reset will get it running again.
I have noticed that when I run 'lsmod' again, 'ndiswrapper' doesn't show up in the list. I'm a newbie by the way. Any help would be much appreciated. Thanks.
When I type (lsmod | grep "netmw"), I get nothing.
Now let me back up. Sorry about not posting well. I was sure that ndiswrapper was loaded in the 'lsmod' list but I can't seem to find it now.
Typing 'ndiswrapper -m' gives the line:
'module configuration already contains alias directive'
Typing 'modprobe ndiswrapper' with the network card in, freezes the system. But if the card is out, it loads fine and then shows in the 'lsmod' list. If I plug in the card with the module loaded, it immediately freezes the system as well.
One other thing I'll post.
Typing 'ndiswrapper -v' gives this:
Well this is quite strange. Do you know what chipset the card is based on? I think it's an atheros deal but I'm not sure. It seems to me like there is a conflict between two drivers, namely ndiswrapper and whatever else is trying to run the card. You did try to get the card to work with native linux drivers first before you began ndiswrapper installation right? If not then maybe you should try keeping ndiswrapper off of the compy before you use your card.
Another thing, have you tried one of the newer (or older) versions of ndiswrapper?
When I run NetworkManager, the only card that comes up is the wired Intel card. I tried to add the wireless card manually but it didn't seem to work for me. That was when I started looking at ndiswrapper.
The Netgear WN511T card that I have has a Marvell chipset. 11ab:2a02. As I mentioned, I downloaded the latest drivers from the Netgear site.
I first tried the ndiswrapper that came with Suse 10.2 (Version 1.25****). That didn't work so I downloaded the latest version that was on the Suse update pages. (Version 1.48****) I guess I could download the latest from the ndiswrapper wiki page. But I would hardly think it would help.
Is there anyway to figure out if I have two different devices trying to access the card? I know that I have only one driver installed in ndiswrapper.
From what I understand, Marvell doesn't allow Linux drivers for their chipsets yet.
Any other clue as to why 'modprobe ndiswrapper' would lock up my system? I've basically followed intructions that I've found on various different sites as to how to set up ndiswrapper. But nobody else seems to have this problem.
Right. I had to install that as well as gcc to get ndiswrapper to install. After I had that installed, I used the commands 'make distclean' then 'make' then 'make install'. All seemed to go well, but it doesn't show up as installed in YaST. Is that normal? Will it still work OK?
I used the commands 'make distclean' then 'make' then 'make install'. All seemed to go well, but it doesn't show up as installed in YaST. Is that normal?
If there were no errors, then things are heading in the right direction. What you need to do now is follow the installation instructions and install your Windows driver (ndiswrapper -i). Once that is done, you can load the module (modprobe ndiswrapper) and then see if your card shows up in the output of iwconfig. If it does, you can configure it and request an IP address.
I've got the same scenario as before. When I 'modprobe ndiswrapper' with the network card inserted, my laptop freezes. I can modprobe and it loads fine with the card out. If I insert it, everything's a dead freeze.
I've now tried something else. I removed my driver from ndiswrapper and took out the network card. I ran 'modprobe ndiswrapper' and it loaded fine. Then I inserted the card and reinstalled the driver. Doing 'ndiswrapper -l' shows that the driver is loaded and 'lsmod' shows that ndiswrapper is running. But I get no connection even after configuring with YaST.
I'm starting to think that your Windows driver might not be compatible with ndiswrapper. I would visit the ndiswrapper wiki site and see if anyone has posted a link to a driver for your card. Hopefully that will take care of the issue. The other thing is to look in your log files (/var/log/syslog, /var/log/messages, and the output of dmesg) and see if there are any clue from ndiswrapper.
My apologies for not suggesting this before, but since you have a Marvel chipset, there is a native Linux driver. Apparently the OLPC project used the Marvel chipset, and the driver has been in the Linux kernel since 2.6.22. According to your first post, you have an older kernel, so you might try upgrading to 2.6.22 or later.
OK, I'll try the kernel upgrade. I found a site that showed how to back up the previous kernel and everything seemed to go well. And looking at this post about upgrading the kernel seems hopeful. Would it be what I need to do? I'll download a new kernel from kernel.org.
You've really got two options when you upgrade a kernel. The easier approach is to look in a Suse repository for a pre-compiled kernel and install that as you would any other RPM. If you go to kernel.org, you'll be taking a second approach, which would be to configure and compile your own kernel. If you go this direction, you'll want to do your homework on how that is done. I've got some basic instructions on my help site and there are literally dozens of other help sites just a google away. If you compile your own kernel, the biggest thing is to have a backup kernel available before you begin so that when the new kernel gets screwed up (and it will get screwed up, believe me) you still have a way to boot into your computer and fix things. I've lost count of how many times I've screwed up my kernel configuration, but the first time was the only time that I didn't have a good kernel in place in case of trouble. I ended up doing an OS reinstall that time.