LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Linux Answers > Networking
User Name
Password

Notices

By Groovelab at 2004-12-02 13:47
Note: I have not only the Microsoft MN-730 Wireless G Card on an Athlon Desktop machine, but I also have the matching MN-700 "Base Station"/router.

Note 2: Microsoft networking cards use the broadcom chipset. So THEY WILL work in linux and work very well with strong signal.

OVERVIEW:
I) Get Microsoft drivers for your non linux supported wireless card, mn720-ankh.inf, mn720-50.sys (for both the mn 720/730)
II) Install Suse, duh :) Then place drivers in a folder somewhere, remember it.
III) Goto www.rpmfind.net, get the latest Suse build Ndiswrapper.RPM and associated libraries
IV) Install Ndiswrapper with YAST, get any more libraries if needed to complete install
V)

Step 1: NDISWRAPPER "Wraps itself around" any windows driver to operate a device for which no linux driver exists. Either installed on your windows partition (if you still have one) or can be downloaded from Microsoft.com or Google search you need to place the following files for MN-720/730 into a directory on your linux partition. Both use the same driver files:

MN720-ankh.inf (this is what ndiswrapper loads and then uses the .sys file)
MN720-50.sys

*** Since Windows doesn't recognize linux partitions, in Suse/KDE open the K-Menu by the clicking the little green round lizard button on the menu-bar. Use "Find Files", Named: = "mn720*.*" Look in: = "file:/". This will point to the root directory of your hard disk(s), and whatever you find just copy files mentioned above to a new directory wherever you like in linux.

Step 2: Collect the following information: SSID/ESSID (they are the same thing, it is a GIVEN name YOU made when installing your wireless base station, for the MN-700 base station Microsoft lovingly calls this the "WIRELESS NETWORK NAME" in its broadband utility.)

Step 3: Turn OFF your encryption, WPA, WEP, etc. on your base-station/router We will turn it on later once you're computer connects to your base station successfully. Right now it is one less variable to troubleshoot. Use your windows setup utility if need be, or just use the reset button with a small pen or whatnot, to reset it to the default (Security OFF and Channel 6).

Step 4: Goto www.RPMFIND.net or Google search for "ndiswrapper rpm Suse". Then get the newest ndiswrapper (non development version) rpm. Get the Suse version if at all possible for Suse version 9.x. Its pretty available on the net. The i586 version will work for Pentium 1 generation chips and beyond. Click the "Little Blue House" (that links to your user's home directory) on the menu-bar where most browser downloads are placed. You should see it there, but if it somehow wound up on your desktop, move it there.

Step5: Now click on your newly downloaded NdisWrapper RPM file. As long as its NOT on the desktop but in a regular file folder, the window will show you a button to automatically Install with YAST. Do this. Suse depending on your version, personal (like me), or pro like others may or may not comes with the needed "dependencies" which are files libraries used to compile the bastard :) Most likely is you are using the personal version you will need to also get the Suse RPMs for GCC, GLIBC, MAKE. They are all on RPMFIND.net, and if there is anything I missed, YAST will tell you, goto RPMFIND.net and get it too, install them in whatever order it likes, since one depends on another, then on another, etc.

Step 6: Once YAST has finished installing Ndiswrapper. Open a Konsole in super user mode, or just open a Konsole/Terminal and type in "su root", then enter your password from when you installed Suse. This puts you in root mode, otherwise known as super user. The following steps are done in the konsole mode as root.

Step 7: type in "ndiswrapper -i /path/to/mn720-ankh.inf" This tell ndiswrapper where the .inf and the associated .sys is.

Step 8: type in "ndiswrapper -l" This will display your installed "wrapped" Microsoft drivers.

Step 9: type "modprobe ndiswrapper" This is uses the modprobe command to load a driver into linux, which points to ndiswrapper as a driver, which in turn is controlling your windows driver for your device.

Step 10: type in "iwconfig wlan0 essid [SSID name goes here]" This is the iwconfig command, which displays or sets settings for your wireless extensions. wlan0 is the default if you only have one wireless card.

Step 11: If you didn't listen to me before and left your base station's security on (WEP), then type in "iwconfig wlan0 key restricted [enter key here]"

Step 12: type in "ndiswrapper -m" which will write an alias to to the modprobe config file.

*** Normally this would finish us off, but more than likely eth0, NOT wlan0 will dominate upon reboot.***
Type in "route" at the konsole as root and it will show you whether your system behaved well, a lot of times it won't. Two solutions are proposed, one creates a simple text file, one uses YAST. I used both to cover my butt :)

TEXT FILE:
A.) K-Menu, System, File Manager, File Manager - Super User Mode. Must be in super user.
B.) Browse "directories-folders" to /etc/sysconfig/network
C.) In that folder, look for a text file named "ifcfg-wlan0"

D.) If it exists, use Kwrite or whatever Editor from the "File" menu in the folder window, add the following lines.
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'

E.) If it doesn't exist, make one. It will look like the following:
BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
WIRELESS_AP=''
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_ESSID='pennstater'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
_nm_name='static-0'
DHCLIENT_MODIFY_RESOLV_CONF='yes'BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
WIRELESS_AP=''
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_ESSID='[enter your SSID here]'
WIRELESS_FREQUENCY=''
WIRELESS_KEY='[enter your WEP security key here]'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
_nm_name='static-0'
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'

F.) Save your file, as "ifcfg-wlan0" in the directory mentioned above. Linux will look for this as a mandatory network device upon bootup.

YAST Method:
A.) Open YAST, Network Devices, Network Card.

B.) Choose Configure button.
C.) Device Type = Wireless
Configuration Name = 0
Hardware Config. Name = static-0
Module Name = Ndiswrapper

D.) Click Wireless Settings Button
E.)Operating Mode = Managed or Auto
Network Name (ESSID) = [enter your chosen name, must match router-basestation]
Encryption Key = [Didn't I tell you to turn it off at the base station, until later????]

E.) Once done with that, use the NEXT button.
F.) Use ADVANCED, DHCP Client Options.
G.) Check the broadcast response box.






by thook on Wed, 2005-02-23 18:50
Hopefully i can find some help on this.

i've seen a couple discussions on installing MN-730 wireless cards. This one was geared to SuSE, another for FC3. The other thread dead ended with the instruction "Type: dhcpcd eth0" after doing the modprobe.

i got an error that the command doesn't exist. So i came to this thread, which instead uses iwconfig after modprobe.

This is still my roadblock, as i am told that the hardware doesn't exist.

As mentioned in the article, i am suffering from an onboard ethernet chip that Fedora wants to use. i've deleted its profile from my list of network hardware. Now i'm not sure where to pick up. Do i start over? i've added these lines to modprobe.conf:

Code:
options ndiswrapper if_name=wlan0 (which was eth0 in the original tutorial)
alias wlan0 ndiswrapper
Like i said, i didn't have any difficulty until after "modprobe ndiswrapper".

The original tutorial i was following is here

Can anyone help? i'm an absolute newbie here, so be gentle. Thanks
-joe

by zenora on Sat, 2005-07-09 18:03
I am having some serious trouble with ndiswrapper and modprobe on Fedora Core4. I installed ndiswrapper1.2 using yum-extend.

# ndiswrapper -l
bash: ndiswrapper: command not found

Figured that one...
/usr/sbin/ndiswrapper -l
Installed ndis drivers:
mn720-ankh driver present, hardware present

Then it was...
# modprobe ndiswrapper
bash: modprobe: command not found
# /sbin/modprobe ndiswrapper
FATAL: Module ndiswrapper not found.

Somewhere it said it is looking for the .ko file. That's in
/lib/modules/2.6.11-1.1369_FC4/misc/ndiswrapper.ko

But, this went through fine.
# /usr/sbin/ndiswrapper -l
Installed ndis drivers:
mn720-ankh driver present, hardware present

Does anyone know what's going on with "modprobe ndsiwrapper" command?

From Desktop/System Setting/Network I have the Network Configuration screen and I have in Tab:Hardware wlan0 with status configured. I did try to setup from there but there's more errors.

I guess I need to get "modprobe ndiswrapper" working. Could anyone please tell me what to do?

by zenora on Sat, 2005-07-09 18:25
Somewhere it said it is looking for the .ko file. That's in
/lib/modules/2.6.11-1.1369_FC4/misc/ndiswrapper.ko

Oh wait... I am using Kernel 2.6.12.1390_FC4. Is that why?

by master on Thu, 2005-10-27 08:56
Hello im running suse9.1 pro and i am trying to set up my wireless card following the instructions,but when i get to step 8.
Step 8: type in "ndiswrapper -l" This will display your installed "wrapped" Microsoft drivers.
i get error telling me "motorola_wn825_wpci810_6.0.3.exe" is an invalid driver.can any one tell me why it is invalid
because when i type "ndiswrapper -i motorola_wn825_wpci810_6.0.3.exe" i am told it is allready installed any ideas what i can do
Thanks nige


  



All times are GMT -5. The time now is 06:58 PM.

Main Menu
Advertisement

My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration