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!
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 am assuming that the OS is not seeing the wireless nic is because there are no drivers installed for it? The only problem with that is that lspci sees the devise. Confusing?
It is probably not showing up because you don't have firmware, the drivers are there, they are part of the kernel. Also, lspci shows everything on the PCI bus whether or not drivers exist for it or not, there is a little ID chip in every piece of modern hardware with number in it to tell the OS what it is. If you run "lspci -nn", you'll see the number it gives.
Post the output of "dmesg|grep -i b43", I think it will show the driver trying to load, then failing because of missing firmware.
I don't understand why this thread is still going.
IMHO you really don't want to be using b43 at all - read (and follow) the instructions in the link in post #3.
Use the STA instructions - simple if you have a wired connection. Pretty painless even if you don't.