Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
I have just received a new HP Pavilion DV6-3120sa laptop and installed slackware64 13.37 on it. All seems to work fine apart from the wireless network. The card seems to have the correct kernel module installed, because it's detected by ifconfig -a:
Have you had a look to see what modules are loaded (lsmod). I've seen quite a few posts where conflicting modules are loaded up for Ralink chipsets and you have to blacklist one or more.
Assuming this is a PCI card what does lspci -vv spit out?
What does dmesg tell you?
I'm going to have a go at compiling a new driver myself at some point but I've got ethernet for now. I haven't had a plethora of responses myself but then wireless in Linux can be a bit of an unknown. Small"ish" world too - just to the east of the Peak District here.
no matter though you answered the question. You've got 2860sta (from staging) and 2800 running. I'm pretty certain that only one should be. I've seen some people blacklisting 2860sta and others blacklisting 2800 though both I think are alledgedly intended for your chipset (just that 2860sta is from staging). I'm currently running 2800 but I'm not getting anywhere with it.
The blacklist lives in /etc/modprobe.d/blacklist.conf
The format is pretty simple, something like:
would do the job depending on which you want to run.
You could modprobe -r rt2860sta (or rt2800pci) to see if it runs with the conflicting module removed but you may need to restart the other module (so remove both with -r flag and insert back using modprobe without flags).
I should add I'm no expert and YMMV. I'm no novice either though, but it's rare that wifi has worked out of the box for me. I've always had a bit of scrap with it. It does look that that we are both trying to get the same driver working even though we are running slightly different chipsets.
OK, I managed to get this working. There were two things wrong.
The quick answer:
cp /lib/firmware/rt2860.bin /lib/firmware/rt3090.bin
and then add "blacklist rt2800pci" to /etc/modprobe.d/blacklist.conf
The full answer:
I noticed while doing "ifconfig -a" yesterday that the MAC address of the WLAN adapter was coming up all zeros (even though this wasn't the case in my original post for some reason - seems intermittent), but didn't think much of it. I tried Pscylo's suggestion of doing:
and WICD then picked up my WLAN card and connected fine, until reboot of course. Blacklisting rt2800pci made the fix permanent. It now works reliably every time.
NOTE: I experienced some instability in between the two fixes. After copying the firmware file the system was quite unstable while the rt2800pci module was still loaded. Any attempt to interact with the card while this module was loaded seemed to intermittently cause a full system lockup - so bad then even ALT+SYSRQ+B would not reboot the system. As soon as this module was removed with either rmmod or the blacklist it was fine.
@Pscylo: thanks so much for the help, it's very much appreciated. And yes, now that I look back it's quite clearly "vv" and not "w", I think I need my eyes tested. I have no idea if a similar fix will work for your system, but I hope it does, good luck!
Last edited by khinch; 05-26-2011 at 04:50 PM.
Reason: edit to fix typos