[SOLVED] Ralink RT5390 spotty WiFi performance on any kernel past 3.2.x series
SlackwareThis Forum is for the discussion of Slackware 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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ralink RT5390 spotty WiFi performance on any kernel past 3.2.x series
I know this should be posted in the hardware forums (maybe). But I think the Slackware community is the most knowledgeable and most likely to provide help in this case. Also, I am running Slackware. :-)
If I'm running Slackware -current with the 3.8.13 (smp) kernel, my WiFi performance is spotty (my laptop is an HP DV6.6135dx, for reference sake). This isn't distro specific, I have spotty performance on any other distro, and any kernel greater than 3.2.x. I'm not sure what changed from 3.2.x to current kernels in wireless modules but my WiFi cuts out a lot, or is slow (and using wicd, networkmanager, netcfg, netctl or even just pure wpa_supplicant does not help).
I have already tried:
- Disabling 'N' speeds on router
- Compiling driver from Ralink's website (it causes a kernel panic)
AFAIC, you won't get it any better than it is. Wifi just isn't quite 'there' yet in Linux, IMO. I was having the same troubles as you, with two different routers from two different companies and still had the trouble and wicd and networkmanager.
We just need more people to get in on the wifi thing with linux, like engineers and such, to help get it where it needs to be. Until then, I suggest going back to wired - it's fast, steady, reliable and 'just works'.
Meh...it happens, I suppose. I saw it with the module build for older Philips webcams when the kernel people suddenly said they didn't want it to be able to tap in, so for a long time us Philips owners got the shaft, then suddenly it's 'built in' in the kernel but doesn't work nearly as well as the old way of installing it and using it did, so I have a perfectly good (even if it is 'old' it's *still* got a better picture than most of the 'new' webcam pics I've seen) webcam gathering dust.
Hopefully word will get out about the newer kernels not working as well as older ones with wifi and things will 'get fixed'. Can't never tell though.
For drivers that use the rt2800lib module someone messed around with the tx power. It causes the rt2800pci (and probably other) drivers to revert to the bandwidth of smoke signals on a cloudy day. The patch here fixes it:
If you wanna report this to kernel.org that might help. I just have too many kernels hanging around on this system and this is starting to resemble "work".
Building a vanilla kernel is really not all that difficult.
- Download the source from ftp.kernel.org.
- Apply the patch "cat patchfile > patch -p1" (might be -p0 or p2 but I think p1 does it)
- copy in a .config file from another kernel build. Say, the one your distribution uses. On fedora they are stashed under /boot
- "make oldconfig; make; make modules_install; make install"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.