Setting up a Linksys Wireless-G card in SuSE 9.1 Personal Edition

[PICKhead155 0]

Does anyone know how I can get a Linksys Wireless-G card working in SuSE 9.1 Personal Edition? I am a Linux novice so please explain the technical stuff. Thank you!

[Dapper Dan 0]

Most of the cards that work with Linux are in the 802.11b class. "G" is relatively new. I have found the Linksys wireless G router is indeed backward compatible to some "b" cards but not all. I understand the Negear 511 can be made to work under Linux, but it isn't an easy process, especially for a new Linux user. I'm fairly certain the Linksys wireless G card is not yet capable of running under Linux.

Tell me about your router. Is it a Linksys wireless G? If so you may want to consider getting an Orinoco Gold Card. I know from experience it will work with "B" only routers and "G"s that are backward compatible.

[PICKhead155 0]

My router is a Linksys Wireless-G 2.4 GHz 802.11g

[Dapper Dan 0]

Then it is compatible with the Orinoco Classic Gold card which is 802.11b. One of these cards can be had for around $49.00, check it on Froogle. Unless they've changed something, and I don't think they have, this card works with your router.

 

Your other choices are to try an compile a kernel for the Netgear 511 which is 802.11g, or wait and hope someone will create drivers for your Linksys.

 

As a matter of information: I use 802.11b on a laptop, and with 2 PCs using the Netgear MA311. All are plenty fast for me..

[martouf 0]

a quick check of the wlan_adapters list from linux-wlan.com shows the Linksys Wireless-G

product uses a Broadcom chipset. Sorry, but there isn't an open source driver for that yet.

 

If you have the Linksys 802.11a/g product, then you're in better shape. It uses an

Atheros chipset.

 

On the other hand, if you're OK with buying software to make your Broadcom-based card

useful, take a look at DriverLoader by Linuxant. http://www.linuxant.com/driverloader/

 

Have a look at the 3Com 11g product (PrismGT) and the 11a/b/g product (Atheros),

part numbers 3CRWE154G72 and 3CRWE154A72, respectively.

 

Both are supported by either the wlan-ng or madwifi drivers included with the

2.6 kernel provided by SUSE 9.1.

 

You should probably get familiar and comfortable setting up a wired network to your

Linux box before you attempt setting up a wireless network.

 

[Dapper Dan 0]

Martouf, those cards you mention that are in the "G" class, Suse 9.1 already has the drivers to accomodate them so you can go 802.11g? No re-compiling kernels and stuff? If so, that's really good news!

 

Do you know if 802.11g is also supported by any of the other distros using the 2.6 kernel, or is it just Suse?

 

Thanks!

 

 

[martouf 0]

Yes, SUSE 9.1 includes the latest PrismGT and Atheros drivers as part of the

kernel-default package.

 

You'll find them in /lib/modules/2.6.4-52-default/extra

 

A quick check of places like kerneltraffic.org and the linux.kernel newsgroup (via Google)

indicates the linux-wlan-ng drivers were added to Debian stable, Fedora, and Slackware 10

as the version 2.6 kernel was released.

 

check your distro with:

find /lib/modules -name ath\*

find /lib/modules -name prism\*

find /lib/modules -name hostap\*

 

The best answer I can give you is "it depends" (the All Purpose Technical Answer[tm]).

 

I'll point out that lately there's fewer and fewer reasons to compile a kernel.

However, there's still plenty of reasons why you'll need to get the kernel source and

make all the preparations for building additional kernel modules.

('make oldconfig; make dep', that is) .. a topic for another thread, though.

[rogerg6ckr 0]

Hi.

Forgive me for jumping straight in.

But after a lot of googeling this is the the first thread I have seen where someone has actaully said they are running netgear MA111 devices on SuSE 9.1.

I would dearly like to know how.

Regards Roger

[Dapper Dan 0]

Forgive me, but I'm not seeing an MA111 in this post. I see the NetGear MA311, and the NetGear 511. Which one, if either were you refering to? Or are you refering to the MA111 wireless USB? According to this, it's suppose to work.

[rogerg6ckr 0]

ooops sorry.

I got here from a google. I must have changed fro, searching on MA111 to somthing a little wider, And It was past bed time so the eyes were geting tired.

Thanks for the link anyway I will check it out.

Roger

 

[OldSpiceAP 0]

There is a free open source alternative to using the Driverloader. Its called ndiswrapper. Download the source, unzip,compile and install it. Check the readme it comes with for instructions to be certain, but I believe its :

$ make

$ make install

 

Then get the windows driver for your card and out it in a folder - I called mine WPC54GDRV. Make sure the .inf file is there. Then simply go to a terminal and type:

$ ndiswrapper -i /pathtodriver/drivername.inf

then type :

$ ndiswrapper -l

 

you should see output like this:

 

ndiswrapper

 

nameofdriver.inf present

 

From here simply type

$ ifconfig wlan0 up

$ iwconfig wlan0 essid any

$ dhcpcd wlan0&

& dhcpcd wlan0

 

Now it should be functional - type

$ iwconfig

to confirm settings - use a program like Kwifimanager to monitor signal stregnth and such.

 

This is sort of thing is sort of obnoxious to type every time you turn your computer on, so activate it on startup with a script.

 

e-mail me at brantwatson@hotmail.com if you want help with this.

 

 

[motaguense 0]

I have done all of the above and when i do

ifconfig wlan0 up i get:

wlan0: unknown interface: No such device

 

 

any help would be appreciated

 

[martouf 0]

motaguense: OldSpiceAP provided a bunch of commands,

and not exactly in the right order.

 

try this:

 

1. configure the wlan radio (pick one of the following)

 

$ iwconfig wlan0 essid any

(assumes you're not using any encryption)

 

$ iwconfig wlan0 essid SSIDname mode managed key [1] xxxxxxxxxxxx

(if you're using WEP with a hexchar key)

 

2. confirm your radio has successfully linked to the AP radio

 

$ iwconfig wlan0

(make sure the AP addr isn't all zeroes)

 

3. obtain an IP addr (pick one of the following)

 

$ pump -i wlan0 &

(if your distro has pump)

 

$ dhcpcd wlan0 &

(if ...)

 

$ dhclient wlan0 &

 

(DHCP provides an IP addr and DNS config)

 

4. confirm your interface has an IP addr

 

$ ifconfig wlan0

(make sure the interface is UP and has an IP addr)

 

5. confirm your system has a default route

 

$ netstat -r

(make sure there is a 'default' route to the AP IP addr)

 

6. confirm your system has a DNS configuration

 

$ cat /etc/resolv.conf

 

7. enjoy!

 

 

[superx10 0]

Hi, I'm new here (and new to using wireless in linux..actually i'm kind of new to linux itself as well..)

Anyway, I've tried everything above, but I still get a message that says the same thing as what motaguense had (wlan0: unknown interface: No such device). I got ndiswrapper all installed, and got the driver installed just fine, but everything after that doesn't seem to work at all.

 

I mean, my card (linksys WMP11) is set up as wlan0 (i think... :x )

but it still says it isn't there when I do iwconfig and such.

 

PLEASE help if you can.. i can get screenshots and that sort of thing if you need them (sorry, i just started using SuSE today, so i'm not used to setting up devices and stuff with YaST2)

[martouf 0]

Step 0 (as root): "/sbin/modprobe ndiswrapper"

 

check ndiswrapper module load status with "dmesg | tail -8"

 

 

[OldSpiceAP 0]

martouf is correct - I posted the commands in the wrong order. - this may help clear things up (I also left out an important command).

 

First of all if you just switched to a 2.6 kernel (just in case you did ) it may be helpful to type at the command line :

 

$ modprobe yenya_socket

 

I needed this when I switched - because for some reason the pcmcia card services were not being activated at startup - this successfully activated them.

 

then type

 

$ niswrapper -M

 

This just does some automatic stuff in ndiswrapper - I don't know what it does exactly because mine seemed fine without it, but ndiswrapper says its needed so I always include it.

 

next

 

$ ifconfig wlan0 up

 

this activates the card as the systems networking device

 

next

 

$ iwconfig wlan0 essid any

 

substitute any with your essid if you are using some sort of encryption on you wireless connection.

 

$ dhcpcd wlan0&

 

followed by

 

$ dhcpcd wlan0

 

This obtains your ip address from the dhcpcd server.

 

You can roll it all into a script like this (if you want to use this just copy and paste it into a blank text document and save it as something like wlancfg. Then edit it to be executible - in kde you can actually just right click on the files icon and go to permissions and set it to executible.) - be sure you are logged in as root to do this.

 

start copy on the next line of text

 

echo "Welcome to the wlan0 configuration utility"

 

echo "Inserting ndiswrapper module....."

 

modprobe yenta_socket

 

modprobe ndiswrapper

 

echo "Activating wireless card as network device...."

 

ifconfig wlan0 up

 

echo "Setting essid..."

 

iwconfig wlan0 essid any

 

echo "Obtaining IP address via dhcp....."

 

dhcpcd wlan0&

 

dhcpcd wlan0

 

echo "Script completed successfully - your card should now be activated."

 

 

 

end copying above this line

 

 

Now place the file in your /bin file and voila - just run this from the console or shell or whatever command line interface you use and just type wlancfg (or whatever you named the script) and the rest is automatic.

 

Sorry about the confusion and left out commands - I was a bit tired...

 

P.S. I tested this on Suse 8.2 pro and 9.1 pro and on Yoper linux - it worked on all cases - and my hardware is the same as yours.

 

Good luck

 

 

-So Long and Thanks for All the Fish

 

[superx10 0]

grr! I've tried all of the above things but it still isn't recognizing it's even there!

Does it wake a difference that i'm using wireless on a desktop computer?

Should I try re-installing Suse?

EDIT- if I do, is there a certain way I should configure my card?

 

ndiswrapper -l says that my driver (wmp11nds) is installed.. should I try another one? I think that there were two different drivers on my card's driver CD...

 

I can do everything until "ifconfig wlan0 up" ... then it says wlan0 doesnt exist. I even tried using different names other than wlan0, like sit0, eth0, eth1, etc... but nothing works..

 

I'm sure it's not what you guys wanna hear but if I can't get this thing to work shortly -- I'm going to need to switch back to Windows.. ;(

[Edited by superx10 on 2004-08-19 20:57:53]

 

[motaguense 0]

Martouf,

thanks for the help. I got it running...really appreciate it. One thing though is that whenever I did

> dhcpcd wlan0 &

I got an error saying

 

wlan0 warning: using NO encryption

ERROR: command 'iwconfig wlan0 key off' returned

Error for wireless request "Set Encode" (8B2A) :

SET failed on device wlan0 ; Operation not permitted.

 

Still whenever I tried to connect..it worked so i guess its a dont care!

 

Dapper Dan,

I got the same wireless card as you and the CD I got had two different versions of .inf file. I was getting the same error as you when I was doing

ndiswrapper -i /pathtodriver/WMP11NDS.inf file

so I pointed to the other one the WMP11V27.inf file

you might want to try that

 

 

 

 

 

[martouf 0]

you want to be sure you're choosing the NDIS 5.1 driver (.inf + .sys) to use

with ndiswrapper.

 

Quote:

wlan0 warning: using NO encryption

ERROR: command 'iwconfig wlan0 key off' returned

Error for wireless request "Set Encode" (8B2A) :

SET failed on device wlan0 ; Operation not permitted.

 

means the command "iwconfig wlan0 key off" was issued at some point,

and the error message is from ndiswrapper.

 

I don't recall any such command in the list of commands from OldSpiceAP's

"How To" message. In any case, it's just a warning.

(you know you should be using 128bit WEP and MAC filtering, yes?)

 

 

 

 

[Brandon B 0]

HI guys im new to linux and have the same wireless g card and router I have same Linux version suse 9.1 home I downloaded the source tar and extracted it to a folder "ndiswrapper-0.10" then highlight folder with mouse and right click open terminal here

the terminal appears "guy@linux:ˉ/documents/ndiswrapper-0.10>"

i want to compile and install the the module and utilitys so ive tryied make and make install and all i get is "bash : make : command not found" so i ve read thought the read me "install" in the ndis folder it says as root use the command make install so i use the command "su" and log in as root enter pass ect. so now konsole looks like this "guy@linux:ˉ/documents/ndiswrapper-0.10#" and again i try make and make install and all i get is "bash : make : command not found" so being new to linux im lost am i doing something wrong cmds or some thing i just want to get my internet going so i can stop running up and down stairs to do research on linux. Any help or suggestions are appreciated thanks.

 

[Brandon B 0]

hey guys i did some researching and found a rmp of ndis wrapper for suse 9.xx if you want to try it hears the link still havent got my internet setup but i have a ndis wrapper installed

hears the link ftp://ftp.univie.ac.at/systems/linux/suse/i386/9.1/suse/i586/ndiswrapper-0.6-23.i586.rpm

[martouf 0]

brandon, hi..

 

you probably don't want to rely on ndiswrapper 0.6. There's been a great deal

of development done on the driver since then..

 

in order to help you along at a later step, please provide your 'uname -r' output.

 

in order to build the kernel module, you need the 'make' package installed.

if you don't also have 'gcc' and 'glibc' packages installed, you'll need them, too.

 

(you can grab them from the SuSE 9.1 Professional mirrors)

 

 

[ka1zex 0]

Just kind of a side note for anyone interested. I was recently trying to get my linksys wpc54gs card working under suse 9.1 no luck with ndiswrapper or anything so I tried my D-Link DWL-G650 AirPlus Xtreme G card and Suse 9.1 auto configred it and it worked fine so at least with Suse that card worked fine.

 

Ron

[OldSpiceAP 0]

I use SuSE 8.2 and the wpc54g card with ndiswrapper - where did it fail for you?