Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.

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.

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.

I'm trying to get the PCI CompUSA 802.11 B/G wireless card to work (Realtek 8185 chip). Mandriva Linux Control Center (Network & Internet) flashed *_VERY_* fast messages. Going to a console screen, "mcc" (and modprobe and insmod) tell me that the module r8180 does not exist (probably because the card didn't exist at the time of the Mandriva install). Choosing depmod -a doesn't create the module either. So I thought I would have to use an ndiswrapper solution.

I installed ndiswrapper and pointed it to the XP driver on my CD (this chip not on sourceforge's list). When I boot, here are the relevant lines from dmesg, numbered for your convenience:

After the message "Press 'I' to enter interactive startup", I see various things start up, including the following:

sit0: [OK]
wlan0: [OK]
wlandetect [OK]

I confirmed that the module ndiswrapper is loaded.
Also, /proc/net/wireless does in fact exist

My observations:

1) The output of lspci confirms device 00:0b.0 is the PCI card in question (line 6 above)
2) "lspci -n" gives the device code 10ec:8185, which we see in line 8 above.

When I start KDE, the symbol in the system tray that looks like a "plug" (one male and one female parallel port connectors) simply won't plug in, even when I right click and tell it to connect wlan0.

When I click on "configure the network", I think I've chosen correct settings. I'll try to come up with them in the next few days. When I go into "Mandriva Linux Control Center" and click on "Wireless", there is something there (it used to tell me "you don't have an interface, you need to set one up first" or something).

First, can anyone help me with depmod? I feel really stupid because it won't work.

Second, does line 9 mean that I *_MUST_* use encryption?

Third, can ndiswrapper work? I get the feeling I am so, very close to succeeding. On some level, the chips *_are_* detected. And yet I am so far away.

This is *_MY_* system and I am root. Root means I can delete ANYTHING I WANT. and I'm really pissed when my system doesn't obey me.

I tried ls -la, thinking maybe root had to be part of bin group, wheel group, or adm group. Nope, these remnants are owner root and group root.

I cannot delete the files or copy them to *.bak files, even after I use "chmod a+x", "chmod a+r", and "chmod a+w. Most perplexing.

Can anybody help me delete these remnants? When Windows says a file is in use, and thus cannot be deleted (i.e. spyware), I reboot into safe mode or use Linux to mount my FAT32 partition, and delete at will. But AFAIK Linux has no such restriction. If a file is in RAM and on the hard drive, I can delete the one on the drive. This one has me stumped. I read somewhere that Linux has a "read-only" bit that is different from -drwxrwxrwx, but cannot find it.

Do I need to boot from a rescue CD or DVD to delete these files? I'll try that next.

This is no longer about getting wireless to work. Just like when I beat cancer last year, this is about getting control back, even if I have to nuke half my install.

I thought my router ($2.99 after rebates at CompUSA, 1/1/2006) was trash. But someone suggested releasing the lease, so I did so (then shutting Win98 down). I rebooted into Linux, and the wired portion works. I'll probably put the router on a UPS, so the lease isn't lost if the power dies unexpectedly.

Would have been nice if they would have told me to release the lease in the documentation, but they didn't. It has been a rough 24 hours, but at least the wired portion works once again.

I've got 2 or three boxes I'm working on for friends right now (A/V, new harddrive). I have to put the wireless project on the back burner for now, but I'll be back.