802.11n 5ghz Driver

0 views

Skip to first unread message

Lauro Pericles

unread,

Aug 3, 2024, 3:05:37 PM8/3/24

to foroliran

I have two Netgear R7800s running OpenWrt 21.02.3, with ath10k (non-CT) firmware on both, and a TP-Link Archer C7 v5, also running non-CT firmware. I have the same issues with CT firmware as well, but I switched to non-CT on all my APs because of better stability.

Screenshots of OpenWrt Web UI and Windows 10 WiFi settings are shown below. I have made no changes to the default Intel WiFi driver settings and I just did a clean install of Windows 10 on this particular laptop.

Try changing to channel 36 and see if the intel card connects at higher speeds. I would have thought any issues about detecting the regulatory domain would have been fixed since this linked report above (in openwrt, intel drivers, and/or windows 10). But I don't know for sure. Assuming you get higher speeds on channel 36, then start looking at which component (openwrt, windows, or intel or combinations of both) might be responsible.

Also, I think you may have to choose a different channel (i.e. 155153) depending on your location - at least in a place like China it looks like channels 100-144 are prohibited from use there so centering an 80 MHz width at 149 might lead to trouble. Sorry, I only have limited knowledge about this.

EDIT1 openwrt should "auto" center based on the width your client can connect at. I.e. setting channel 36 and 80 MHz width on openwrt, clients capable of connected at 80 MHz width are actually centered at channel 42. I would expect that same for setting channel 149 and 80 MHz width but you could try 153 just to see what happens.

This seems to have happened recently, possibly a bug introduced in one of Windows 10's cumulative updates and coincidentally occurred around the same time I switched to OpenWrt because ever since I did, none of the laptops can connect to any 5 GHz network at full speed.

I tried with a Synology RT2600ac and an TP-Link Archer AX10, both running stock firmware and the same issue occurs with both of those devices as well. In fact, if I set the Synology router to disable 802.11n on the 5 GHz band and force 'AC' only, Windows shows a 'Cant connect to this network' error message after entering the password.

Initially I thought it may have been the fact that none of my OpenWrt APs are providing 802.11d regulatory information, so I enabled that under the Wireless interface settings, but it made no difference whatsoever.

I came across several threads with the same issue and none of them have a solution since there is no way to disable Intel's stupid LAR feature on Windows. Intel and MSFT are both unhelpful and their support reps have the same copy-pasted answer in every thread that discusses this.

I bought a TP-Link Archer T6E PCI Express card for my PC today. I installed broadcom-wl-dkms, shut down the PC, installed the card, unplugged the Ethernet cable, booted up the system and nothing happened. The card was active, I could see it with ifconfig, it was up, the driver was loaded but Network Manager didn't see any networks. I checked the Arch Wiki and searched forums but couldn't find anything helpful. I even replaced Network Manager with Wicd temporarily but it did not work. Everything seemed okay yet I couldn't connect to my WLAN.

After some thinking I though I reboot the "router". After it booted up, the 5 GHz caught my attention, I switched it to 2.4 and a few seconds later the WLAN appeared in the menu of nm-applet. After clicking on it and typing in my password my PC was connected to Wi-Fi for the first time in her life.
According to its specs, the Archer T6E does work with 802.11n on 5 GHz, so what could be the problem on my end?

I'm fairly certain it's not the "router", my phone, others' phones and notebooks (running Windows) didn't have any problem with this WLAN setup.
At the moment I can't install Windows to see if it works so I have to ask: could this be a problem with either the driver, Arch or Linux itself?

Hi, just bought the T2u plus usb to get rid of some annoying cable, plugged it, installed win7 driver straight from tp-link website, and while it works, its in 802.11n capped @ 200mb/s
my box supports 5ghz, but even if it didn't, I think I should see the 802.11ac listed in supported radios, no ?

This is probably a very isolated issue, but I've got a couple brand-new ThinkPad T490s laptops with Intel 9560 WLAN cards in them. For whatever the reason, they have issues connecting to some of my 2802i/e APs using 802.11ac. I have to switch the cards to use 802.11n in order for them to utilize 5Ghz at all.

The weird part is that they'll connect to some of my 2802i APs using AC just fine, and not others, and I can't figure out why. Each of my APs are part of the same AP Group, and use the same RF Profiles. None of the other devices that we own with AC WLAN cards have any issues connecting using AC. The drivers for the Intel cards are up-to-date, and the APs are running 8.5.140. The laptops are running Win10 1903. Nothing in my logs seems to give me any indication of what could be going on.

I'm assuming that this is most likely a driver issue with the Intel cards, but before I give up on trying to make this work, I was curious if anyone else has run into this, or something similar. Is there anything in my controller config that could possibly cause this to occur that I should be looking at?

Do you have any logs or debug of the client or clients?, propably i means that is a wireless driver problem, on reddit are two or three post with people with same problem, and the solution is install all drivers version until that one run.

We found that disabling 802.11ac on the Thinkpad laptops running 9560 resolved the issue... so this looks like a 802.11ac negotiation issue between laptops w/ 9560 chip and Cisco AP... these laptops don't have same issue with 802.11ac w/ other APs, only seen with our Cisco 2802 APs.
We forced 802.11n via the following in Windows 10 in order to resolve:

It's also noteworthy that these clients DO NOT experience any issues when associated with their home WiFi APs or APs in a number of hotels they have visited which utilize Aruba devices... this problem looks to me to be specific to Cisco, possibly specific to the model 2802 AP.