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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well, MadWifi is for Atheros cards, not Prism. So clearly that isn't getting you anywhere. For Prism you want to be either using HostAP or Prism54, depending on the hardware.
Could you be a little more specific about "no luck"? How did you install them, what happens when you try to load the driver when the device is connected, what do the system logs say, etc, etc.
Are you 100% sure it is Prism based? What information do you get from lsusb?
Maybe a deailed description of the device would be in place, and in addition information from dmesg/lsusb if there is any. It would be good to first make sure which chip the card is using, because that's what the driver selection depends on..and don't take the chip granted, it's known thing that (at least part of) manufacturers do change the chips used by some cadgets to win more for the price, and not alter the cadget name more than maybe one number or so (so for the customer it could be difficult to know which chipset that model means; it's not important if your OS is listed as "supported", but for Linux..well, you know). After this you can hunt down the right driver, or if there is no native driver, try out ndiswrapper which is may help you out if you only have Windows drivers. Note that ndiswrapper is not any better (usually only worse) than native drivers.
Just to mention, I've seen a few usb wlan cards/sticks that don't have Linux drivers, and though most of them have been working on Linux after all (trough ndiswrapper, for example), they haven't been the best pick-ups around. I recently bought an A-Link 54Mb wireless usb dongle (ZyDAS WLA-54L, driver zd1211rw), and it's the best I've seen; excellent signal quality (the other one I tried always stayed at half of that signal quality or lower), and the best of all, it started working less than a second after I plugged it in. No wonder the box said "Linux" was a supported operating system. And the price? A little over twenty euros, which makes it less than 30$. I'd say it's not bad price for this sort of thing that actually works - I rather pay a few extra coins than buy a cadget that is slightly cheaper and more than slightly less easily made working.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.