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.
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.
Is the hardware being detected? I am pretty sure you need to install the 2.6 kernel packages to support that device, but I never actually use the stock Slackware kernels myself, so I am not 100% sure on that.
netconfig will not help at this point, because even if the device has been detected by the kernel and the module has been loaded, you would still need to configure it against an AP before you could attempt to actually configure TCP/IP on the interface.
But we still do not know if the kernel has loaded the module for your hardware. You can check what modules have been loaded with "lsmod", but a quick way to tell if it is up and working is to look at the output of "iwconfig". If iwconfig says none of your interfaces have wireless extensions, then the kernel is not loading the module for it.