Ralink Rt3290 Wifi Driver

[Marie Ota]

HelpWhen I updated to Windows 10, my Wi-Fi quit working. I have a good Wi-Fi connection for other devices in the house. In network & security, I can only see the ethernet option. I can see the Wi-Fi adapter is the Ralink RT-3290 802.11 bgn wi-fi driver which is a windows 7 driver. I tried updating the drivers in the HP assistant but the reply is that I have the latest drivers (that HP has....) I have looked everywhere and am unable to find the windows 10 driver. Thanks everybody. Jim

When i ran the .exe file you provided, it set up the C:SWSETUP folder. I wasn't sure what to do with the folder but ran the setup.exe. It started to execute then just went away. I restarted my computer just in case it worked but no luck with a wireless connection coming up in the Network&security and same ol drivers present on my system.

That was the one and only W10 driver they made for that card, and what is happening two years down the road, with all these new updates to W10, some hardware no longer works because the manufacturers won't update the drivers.

Appreciate your help and additional info, especially about the USB device if I need it. In your last post, you said to go to device manager >> network & security >>>then select my ralink wi-fi card. That is not a choice. All I have under that area is the following:

Your screenshot shows that the Ralink wifi card has completely disappeared from the device manager, which is a common problem with that wifi card, and any subsequent updates of W10 from the original version that came out in July of 2015.

If it still doesn't work, A great workaround would be is to buy a USB wireless dongle from Best Buy or Staples or from Amazon or e-bay and plug it to one of the USB ports of the computer. Then connect it to the router to go online. It is very economical and cost-effective and can be ordered for a song.

I also used to suffer from the same issue. I downloaded 10+ drivers, replaced WIFI adapter, asked support from "helpdesk" and from real professionals, without success. Then I bought a Dell Latitude laptop, it works properly, and now I am trying to sell this f**** HP, but no one wants to take it

You will see now 2 of the same Ralink drivers. I thought the last was after the windows 10 update, so i clicked the first. Install and fixed. After i Shut down my comp and restart it, it worked as before.

I have a HP laptop HP Split 13-m010tu x2 PC. Recently i upgraded internal from SSD 64GB to 512GB and i have to reinstall Win 10 Home 64bits. Next, i reinstalled RT3290 driver, i encontered problem and i cannot connect to wifi at all (cannot even detect the SSID). Anway, Ralink RT3290 only can support 2.4GHz wifi, it can't support 5GHz wifi.

My hp cannot detect my wifi at all (but all my smart phones can connect to the SSID). Then one day i happened to power recycle my home router and i notice that my HP laptop able to detect SSID and after i configured, it can detect and connected. I was happy. I started to do some investigation is that my router problem or is RAlink RT3290 wifi adapater problem.

If I use ch 2 or 5, i wll have some stabiliyt issue and may get disconnected easily. Well, I don't think this is interference issue although I am staying in high rise apartment and there are many wifi signal/ssid that I can detect.

Thus if you have Ralink RT3290 connection issue, please try changing your wifi router channel. By default we typically set to auto so that it can do auto sensing. However, it won't change the channel even you power on/off your wifi router if router didn't detect any interference ,so when you power on/off your wifi router, it may stay on the same channel. In case the auto mode is assinging a channel 12 or 13, then it can't even detect the SSID (the situation which i encountered).

after installing the file, go to the folder it unpacked to. do the setup. Then after completing it still didn't work for me, which seemed weird. Perhaps this was all it took for you to make it work, in which case, congrats.

I followed the steps given by phantom except step 5 as the previous program was already uninstalled from both device manager and windows program uninstall in step one itself. THe driver is installed but it is not able to connect to Windows 10. Using R074 TU noteback by HP and Windows 10. Any help here?

Also, I can add one step here: I was helped by this link to enable an Administrator account in Windows 10. My normal account, though having admin rights, was not allowed to install the program where the link was given by Phantom456 - trust useful for someone with same issue

I have try to do as you have write down but the driver do not help on my computer... but step 5 i dont know how to do.. when i install the new driver but i cant uninstall the previously installed ralink driver.... i have 4 on my computer there is in windows... but no program to uninstall. what do i do wrong?

I have an HP Pavillion Touch 14-N009LA with a Ralink RT3290 wireless card running Debian Jessie with kernel 3.12.9-1. This distro looks as if the wireless drivers were included, and from another post here it would look like it should work with the rt2800pci module, which is listed by lsmod and loads fine. However, whenever I issue ifconfig wlan0 up, I get SIOCSIFFLAGS: No such file or directory. I tried using the kernel.org compatibility sources from the previously linked post and they didn't work, after installing them I can't load the module and I must uninstall them and use the Debian-bundled module. I tried compiling the driver's sources from this other thread and they don't compile. I'm not sure if downloading the binary archive linked on that thread will be a good idea given that that one is for Ubuntu and I'm running Debian Testing. I tried to apply this fix here for Arch/Gentoo but couldn't find the right file.

So basically, it looks like I have to get the drivers to compile. I have build-essential and linux-headers-amd64 for my running version of the kernel, tried with HAS_WPA_SUPPLICANT=y and HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y as well as with only HAS_NATIVE_WPA_SUPPLICANT_SUPPORT on, and this is what I get:

So... this is really bizarre, and I can't guarantee it will work, but it worked for me and I wanted to put this information somewhere that a lot of people would end up seeing it and have something to try if they still can't get their rt3290 working.

I couldn't get the rt3290 working for the life of me under Debian Squeeze, no matter what I tried, installing the firmware-ralink package, trying to compile the drivers manually (to no avail because of missing dependencies that cause problems if forced into the system), etc.

Yeah. I don't get it either. I don't really have a lot of data with which to back up my answer other than the fact that my dongle is sitting unplugged next to me and I am connected with my rt3290, but if someone else 'solved' the problem this way, I would have loved to have seen this bizarre solution somewhere while I was struggling. So if there's anyone out there still having the same troubles I am, I hope you find this answer by way of google and give the TP-Link drivers a try.

if you are using debian 8 or debian 9, as well as ubuntu from 16 the drive will already be installed. The problem is that the drive can't handle the name that's given the interface. For the drive to work just rename the card. in the file "/ etc / default / grub" change lines so that it looks like this: GRUB_CMDLINE_LINUX = "net.ifnames = 0 biosdevname = 0" then run the following command: sudo grub-mkconfig -o /boot/grub/grub.cfg That's just restart the machine. That the drive will be working.

I am experiencing a very strange issue. My internal PCI Ralink RT3290 wifi adapter seems to be having hardware issues, in the sense that the adapter completely dies on me, lshw and related tools won't list it, and I cannot connect to it. When the adapter heads south, I get what seems to be a kernel panic. Every aspect of the system completely locks up, ctrl + alt +f1 does nothing. I have never been able to get the magic srsyrq keys to work but they don't reboot either. I can reboot (after mashing the power button) into a functional system, and have working USB wifi. Everything will be completely fine, just the Ralink adapter went bunk. The strange part is this issue has persisted across multiple kernels and linux distributions. It happens completely randomly, and I have no way at this time of figuring out what's causing the issue, short of hardware failure. The adapter sometimes works after a cold reboot (no battery in the laptop, no AC), or otherwise randomly comes back online. Note that after upgrading to arch, this issue has been present much more often.

When my adapter comes back online, I will post the above command outputs again. The randomness of the working/nonworking states are driving me insane. I will find the drivers it's using and blacklist them when it starts working again. That way at least my system *shouldnt* crash on me like this. If it is hardware failure, I will need to find a new internal card. One thats 110% supported by Arch and the Linux Kernel. This particular ralink card has really never worked well.

If anyone has any ideas on how to confirm my suspected hardware failure, let me know. I strongly suspect hardware failure because the *exact* same issue has been present when I was using Linux Mint running a 3.16 kernel. So it looks like I will be using my Belkin adapter for now.

I am really stumped by this odd behaviour. Complete intermittent failures. If anyone has any ideas, please let me know. I still suspect hardware failure because the same issue has persisted over different kernels and OS's altogether.

I want to keep troubleshooting this issue, but not at the current moment. I finally finished downloading a new game shooter game, Xonotic. I really want to try it out after fixing my sound. I hope it will be good, because I dont plan on installing steam on this box if at all possible.

Then I re-downloaded the rt3290sta-dkms file again. I re-installed with makepkg -sri. I disabled hostname changing for connman. Finally, after sudo systemctl enable dkms.service AND sudo systemctl start dkms.service, everyhing seems to be working. Chances are high I messsed up or missed a step when I first posted this topic. Just thought I'd post my solution for anyone else who comes across the same problem.

3a8082e126