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.
Well, everyting looks right except that neither wireless is showing up. One last suggestion: remove both drivers with
# ndiswrapper -r <driver>
and start over loading just a single driver. I would try the 8187B driver first because the steps I gave previously worked fine for me. Make sure you edit the .inf file for it as I described and load it again. If for any reason it does not work, remove it and try the linksys driver. It shouldn't, but since they are both USB drivers they may be conflicting with each other for some reason.
Fell like I've got a lot of information on the computer now, maybe some of it is conflicting. Is there some way to just start with a clean slate and reload a little bit of information at a time? How do I restart and attempt that?
You don't have to do anything except remove the drivers from ndiswrapper, and you can do that from the GUI for Windows drivers. Remove BOTH of them, and add the 8187B back to it by itself. Or, you can do it from the command line with ndiswrapper -r <driver name>. Remove both of them, and when you reload them, only reload ONE. I believe the 8187B will work for you because it is the exact same chip I have and it is working for me. Using the GUI, it should report to you that the device is present. Then, simply run modprobe ndiswrapper. Then, check the Network GUI and see if wlan0 is listed.
I also ran lsusb
Bus 006 Device 003: ID 0bda:8197 Realtek Semiconductor Corp.
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse
Bus 001 Device 001: ID 0000:0000
Did you do the editing to the inf file for the net8187b.inf file as described in my previous post? If you didn't the driver will not associate with the hardware. Double check and make sure that the edit has been made. Then, once again remove the drive with:
#ndiswrapper -e net8187b
Then, re-install it again. Then, run:
This will associate the driver with the hardware if the edit has been done to the inf file. If the association was successful, you will get a return something like:
alias already exits (exact wording may be different)
All of these commands must be run from the terminal as root. It WILL eventually work on this realtek chipset because it has worked for me.
Ok, I've reinstalled the driver after making sure it has the added line in it. Here are all the commands I've ran:
It shows the driver installed in the GUI but no hardware associated with it. ndiswrapper -m shows the alias directive, but ifconfig does not show any wireless configuration.