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.
Thanks!

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.

the best thing i can suggest is to switch to debian (since this was made/tested with debian woody) and try it then.

debian comes with KDE 2.2 and Gnome 1.4 (or 1.2 im not sure)

if u want to install KDE 3 its a whole nother ball game (best to just install debian and dont select to install KDE/Gnome in taskset) then follow directions here: http://www.kde.org/documentation/faq/install.html

I already tried Debian, in it modprobe wouldn't even load it. I removed it and replaced it with RH, since that's what I know best. Were you ever able to run wlanctl-ng?

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!

You might have one of the versions of the linksys USB adapter that is not actually a true prism2 chipset. What's the output of "dmesg" after you probe the prism2_usb module?

If its a different chipset, the module will load, but won't bind to anything.

Cheers,

Finegan

Debian was 3.0, i'm now running Redhat 7.3.
The module loaded and binded, finegan.
If it wasn't a prism2 chipset, what would you do? (I can try that)

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?

Cheers,

Finegan

When I plug it in, it says something about it not being claimed by any driver and then has something like 0x779/0x438

When I start the computer I get:
prism2_usb device does not seem to be present, delaying wla0 initialization

When I run modprobe I get: unresolved symbol: and then alot of links

When I run dmesg these are the USB messages:
hub.c: USB new device on bus 1/1 assigned device number 2
usb.c: USB device 2 (vend/prod 0x77b/0x2219) is not claimed by any active driver

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?

Cheers,

Finegan

I just checked the box, this is a WUSB11 2.6, not a 2.5.
Is there a way to get it working in Linux?

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.

Cheers,

Finegan

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?

From what I can tell, modprobe one of the following:

vnetusb
vnetusb3
vnetusbr
vnetusb5

Cheers,

Finegan