SlackwareThis Forum is for the discussion of Slackware 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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
Thanks ponce, I think i might have done it with guanxs's drivers that he indicated. Thanks guanx. But still I have one question: why the device is ra0 and not wlan0? Still I must test it that it works with wicd, and then set it as AP. But I hope it works, although it seems to have his own's configurations, and I hope it dosn't interfere with Slackware's configurations.
... So, there is no firmware, maybe your version differs.
Yes there is. With the official Linux driver and not the manufacturer driver you need the firmware. The firmware link is misspelled as "rmware" on the manufacturer's webpage. The first two letters of "Firmware" are missing. The official Linux driver for RT5370 is RT2800USB (module "rt2800usb.ko").
I have never tried and never suggested to use the manufacturer's driver. But since you are already using that, could you try if you can bring up multiple virtual interfaces at the same time, with different ESSIDs? If yes, then the manufacturer's driver is worth trying.
I have managed to make the TP-Link TL-WN727N wireless adapter work with the linux drivers. It was right, the drivers existed, they only needed the firmware update (like drmozes suggested) from slackwarearm patches directory, only that when I updated the firmware, before that, I messed with the modules so this is the reason that it didn't work. Now, I installed slackwarearm again and it works.
Also, ponce, maybe you should know that your last install image has a problem: after finishing the install, somehow when rebooting it mounts the / partition rw when it needs to be ro for checking. There it gives some errors, I think.