Doesn't detect networks in the 5ghz range

[pcvonz]

as of 4.2.0-17-generic. Not sure if you still keep this up-to-date, but it may be time to get another wireless card...

[mareksuscak]

@pcvonz There was a similar issue (#1) reported in the past but as far as I know this radio can't communicate in the 5ghz range. It's 2.4 Ghz only radio. So yes it's time to get another wireless card if you need 5 Ghz.

[pcvonz]

It is capable of communicating in the 5ghz range[1] and it was working in the 5ghz range up until now.

[1] http://www.asus.com/Networking/PCEN53/

[mareksuscak]

Oh, wow! Didn't even know about that. Now that I read the name of the card once again, it contains "Dual-band". Suddenly everything is clear.

If I find a patch somewhere I will gladly update the code and instructions here. Because neither the original code nor the patch was written by me which is stated in the readme. I just found a patch on the forums and put together the code, patch and instructions so that people can save some time.

I could try to fix it myself but due to my lack of knowledge of the code and driver programming it would take a while.

[gladstonedigital]

Any updates? I don't need 5GHz capability but it would be nice to have. It's disappointing that Asus doesn't maintain their drivers and requires community efforts like this. I'm probably about the same level as you re: driver programming but if you get the urge to tackle it let me know, maybe we could fix it.

[mareksuscak]

No idea how to fix it. If you figure that out, feel free to send a PR. I'll gladly accept it.

[gladstonedigital]

Well, I can't even get it to work at all under kernel 4.4. I give up

[mareksuscak]

@bgladx64 Can you try #4?

[mareksuscak]

So I just replicated this issue on Windows 10. Turns out that this wireless card has problems with high Wi-Fi control channels.

Changing the channel manually in the router settings to 48 fixed the problem. Previously it was automatically set to channel 52. Odd. Might help you guys out.

[Guite]

Like shown in https://forum.ubuntuusers.de/topic/ralink-rt2860-verbindung-zu-5-ghz-wlan-nicht-/ it seems that the WirelessMode setting is not correctly populated. You can try with iwpriv enp6s0 show WirelessMode (whereby enp6s0 is the device alias). In my case it reported 11B/G which corresponds to wireless mode 0 despite I set it to 5 in the configuration file. After I executed sudo iwpriv enp6s0 set WirelessMode=5 things began to work: 11A/B/G/N. Now the 5ghz networks show up in the network manager.

[SydCLu]

Tested working with the following command after activation on my Ubuntu 18.04 Kernel version 4.18 :

$ sudo lshw -C network
$ sudo ifconfig enp4s0 up
$ sudo iwlist scan
$ sudo service network-manager restart

Up to this stage the 2.4GHz should work but at an extremely low Mbps rate.
Then I executed as above sudo iwpriv enp6s0 set WirelessMode=5 but changed it to sudo iwpriv enp4s0 set WirelessMode=5 as enp6s0 was not found.
Magic happened with great net speed! :)

[awonnacott]

This fix isn't working for me. Specifically, setting WirelessMode=5 does not change anything and when I set WirelessMode=9 I get the correct result (11B/G/N), but no new networks are detected and if I sudo systemctl restart NetworkManager then the WirelessMode is reset to 11B/G.

[awonnacott]

Additionally, the link speed shows 54 Mb/s indicating it is using 802.11G to connect.

[mareksuscak]

@awonnacott are you able to pull down the patched version linked above this comment if you're looking on a laptop/desktop sized computer and try it on your machine, then let me know if it resolves this issue?

[awonnacott]

I am able to but not for the next few weeks

[EzraEdelman]

I used the fix from that patched version and I think it fixed the issue for me (on a desktop running arch). Link speed went from 54Mbs to 120Mbs, and now WirelessMode defaults to 11B/G/N. Strangely, all networks are still listed as 2.4Ghz, but my connection is much faster so I am not complaining.

[mareksuscak]

Thanks, @EzraEdelman! Let us know if you run into any issues. I'll keep the PR open for a few more days and then merge it.

[Guite]

How about merging this patch @EzraEdelman @mareksuscak ?

[mareksuscak]

@Guite thanks for the reminder. I just merged the pull request 🎉