WiFi networks in channel 13 are not always shown when scanning, and even when they gets detected sometimes several connection tries are needed to really connect to the networks.
Forget to mention that the laptop is a Lenovo ideapad D330.
Can you provide the results of dmesg and wpa_supplicant logs? Also "iw reg get" could shed a light. Channels 12-13 are not allowed in some countries, so if the device doesn't know which country it is in, it will only work on those channels passively, until it can be sure that there are APs active there. This is something called "no-irradiation", which doesn't allow the device to transmit unless it receives something. This would cause longer periods to find APs and possibly connect.
Is in Spain, will provide the needed info as soon as possible, but, I have older iwlwifi cards and there is no such long times to discover, also the connecting time is practically instant. With 8265 I get sometimes lots of gnome messages saying could not connect to the network. Over Windows it behaves as spected.
Okay, let's investigate it then. Waiting for the logs.
Created attachment 284569 [details] iw reg get ouput
Created attachment 284571 [details] dmesg output masked serials and macs
Created attachment 284573 [details] wpa_supplicant and NetworkManager log macs masked
The logs are from boot to the first time the laptop connected. I have two SSIDs but doesn't matter one or another as both get connected and fails to connect in the same way. I have added NetworkManager log merged with the wpa_supplicant as with wpa_supplicant I could only see that region is set to ES a little time after wpa_supplicant is started but no more messages while connection fails. With NetworkManager log is possible to see that the could not connect to network errors happens because no authentication is done. I'm thinking about trying to deactivate anonymous mac generation when scanning to see if the bug could be related to it, but has to check where to disable it in NetworkManager. Will provide info about it.
Just to add a little information about the older card that works right. It's a 7260 and the main difference I see is in regulation, iw reg get shows only the global configuration and there is no phy#0 self-managed. I suppose that the older card follows the kernel global regulatory domain and the new 8265 makes it's own internal administration?
Thanks for the logs. I took a brief look and didn't see anything that would explain the problem, though I clearly see that we are not seeing the AP for a long time and connection times out. You are correct that the regulatory handling has changed between 7260 and 8265. More of it is done in the FW now. We'll assign someone to take a deeper look into this. And just to be sure, where did you buy this new card from? Different SKUs of the cards come with different "OTPs", which is a read-only data block with regulatory information for the country where it was sold.
The 8265 is integrated in the Lenovo ideapad D330, is a convertible so like a tablet. The model number is specific for Spain but if there is a way to read the data to check Lenovo didn't mistake with the regulatory rules I can do it and provide it.
It's very unlikely that they would use the wrong SKU. So this must be something else, but you could send us the regulatory data from your NIC by copying /sys/kernel/debug/iwlwifi/0000:02:00.0/iwlmvm/nvm_reg to a file and attaching it here.
Created attachment 284615 [details] nvm_reg as is Here is the content of /sys/kernel/debug/iwlwifi/0000:02:00.0/iwlmvm/nvm_reg
I have done some tests, leaving only one ssid (there were three from the router), changing to different channels below 12, setting 20 MHz instead 40 MHz... The results are the same, it takes time to discover the network and sometimes also to associate. I'm thinking more about an integration issue between the devices so, I leave now info about the router. The router is a TP-Link Archer C7 v2 using OpenWrt SNAPSHOT, I need SNAPSHOT for some packages but will finally end with the next stable to be released. The wifi card for 2.5GHz is an atheros one using linux kernel ath9k module. 5GHz is unused for AP. I want to try one more test that consists in activate another router in channel 13, the problem is that the ones I have available right now have the same 2.4 GHz radio, so will try to borrow one to see discard completely that channel 13 is not the issue here and it's a problem between iwlwifi and ath9k.
Forget to mention that despite connecting and associating is hard, setting up iwlwifi in monitor mode and dumping wireless data works as expected, the network appears instantly even in channel 13.
Comparing with other networks I had legacy rates disabled so tried enabling them, also the same. KRACK attack mitigation is also disabled.
I can confirm nowadays that this bug is invalid because the problem is not in iwlwifi. The issue has been solved by some patches and settings into ath9k.