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'm running RH 7.3. I have a Linksys wireless usb adapter, and it works fine in Windows. When I run it in Linux I follow the instructions, which are to type:
modprobe prism2_usb prism2_doreset=1
This loads the drivers, with no errors. Then I type:
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
When I type that it says 'wlanctl-ng: No such device'
Then I type:
wlanctl-ng wlan0 lnxreq_autojoin ssid=linksys authtype=opensystem
It gives me the no such device error again.
Does anyone know how to fix this? I compiled the latest verion of the drivers and tryed the RPMs, neither worked. Currently the compiled drivers are installed and not the RPMs.
you sound like me dude! lol i used to have the linksys WUSB11 version 2.5
i tried mine with mandrake however the docs say its worked with debian woody. the best thing for you is to go wired! i did that after a while of pursuading my parents. (try a couple months) i never got around the linksys prob but ethernet is the way to go! (honestly, i tried everyting to get that darned adapter workin too!)
Hmm... it's not possible for me to go wired, my RH box is in my room, and our cable modem and WAP are about as far away as they possibly could be. Did you try setting up an alias so that eth0 points to prism2_usb? I was debating whether or not to try that.
i got the same problem also, what i did was tried to see if my USB services were running etc. they were running and i couldn't figure out the prob, when i tried to stop and start the service again mandrake (the distro i was using @ the time) froze.
what version of Debian did you use? What version of RH are you using?
what i suggest is debian and when you install and get to the part where it says to install any other kernel packages etc, look for WLAN and find a generic prism chipset driver. sorry but thats all i can suggest. hope it works dude!
If it wasn't a prism2 chipset the module wouldn't have bound, there just would have been a mountain of errors in "dmesg". It just wouldn't necessarily have errored during a modprobe. Most importatly, what is the output from "dmesg" on module insertion?
If the driver isn't claiming it, it might not be a WUSB11 2.5. There were 3 other versions of that device marketed as WUSB11's, none of the others are actually a Prism chipset. Are you certain you have the right device?
Checking the repository of all Linux wireless knowledge, this puppy seems to be an Atmel chipset. To make certain you can check through /proc and poke around until you get a device read from the device... offhand I don't know where USB networking devices reister to in /proc.
If I'm right, and this thing is an Amtel, the drivers would be available from here
Oh great, I just found the link, v2.6: right here. Same VID and PID from above, yep that's it.
I tried those drivers, compiled it, and when I run the console file to set up it up (I can't remember the name of it) it said it couldn't find an Amtel device. I never ran modprobe, what would the command to run modprobe be?