1

I have been working this issue for several days and have not been able to make any progress. I have searched this site and others without finding a resolution. 2.4Ghz & 5Ghz works fine on my laptop, 6Ghz work on my Samsung phone but not on my laptop. I can see the 6Ghz SSID but when I try to connect it fails. Laptop is up to date with latest updates as of this posting. Router firmware is latest edition. Country is USA.

Laptop - HP Victus 16 with Mediatek MT7922 WiFi module.
Router - Archer AXE5400 v1.0 Firmware Version 1.3.1 Build 20241101 rel.60873(5553)

Router 6Ghz settings: security: WPA3-Personal (other option is "Enhanced Open" Channel Width: 20/40/80/150 Mhz Channel: Auto Mode: 802.11ax only (grayed out, not able to change)

I ran the Wireless Info Script. Posted here: https://paste.ubuntu.com/p/8jMpbqkdJ4/. WOW...that captured a lot of data!

I never had 6Ghz working on this laptop. A fresh install of Ubuntu 24.04 was loaded after wiping hard drive. Ubuntu is the only OS on the laptop. I've been working with Ubuntu since the days of 10.04. I'm not an expert but can work around most issues. This one has me stumped.

I would really appreciate someone reviewing the linked script results and working with me to resolve this issue.

Thanks you!


David, Thanks for your reply.
Attempted all four possible setting mentioned above. No change. Can connect to 2.4Ghz and 5Ghz wifi. Cell phone can connect to 6Ghz. Ubuntu laptop can see the 6Ghz SSID but will not connect. Here are some additional annotated logs from dmesg:

Disconnecting from 5Ghz connecting to 2.4Ghz
[ 128.083069] wlo1: deauthenticating from ca:ae:30:6b:23:a4 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 133.106429] wlo1: authenticate with 72:ae:30:6b:23:a8 (local address=00:41:0e:98:5d:fb)
[ 133.272211] wlo1: send auth to 72:ae:30:6b:23:a8 (try 1/3)
[ 133.277324] wlo1: authenticated
[ 133.279057] wlo1: associate with 72:ae:30:6b:23:a8 (try 1/3)
[ 133.294952] wlo1: RX AssocResp from 72:ae:30:6b:23:a8 (capab=0x1411 status=0 aid=33)
[ 133.331894] wlo1: associated
[ 133.409149] wlo1: Limiting TX power to 30 (30 - 0) dBm as advertised by 72:ae:30:6b:23:a8

Disconnecting from 2.4Ghz connecting to 5Ghz
[ 171.919937] wlo1: deauthenticating from 72:ae:30:6b:23:a8 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 172.234696] wlo1: authenticate with ca:ae:30:6b:23:a4 (local address=00:41:0e:98:5d:fb)
[ 172.251746] wlo1: send auth to ca:ae:30:6b:23:a4 (try 1/3)
[ 172.253798] wlo1: authenticated
[ 172.254917] wlo1: associate with ca:ae:30:6b:23:a4 (try 1/3)
[ 172.266370] wlo1: RX AssocResp from ca:ae:30:6b:23:a4 (capab=0x1011 status=0 aid=32)
[ 172.298510] wlo1: associated
[ 172.339263] wlo1: Limiting TX power to 24 (24 - 0) dBm as advertised by ca:ae:30:6b:23:a4

Disconnecting from 5Ghz attempting to connect to 6Ghz – Failed back to 5Ghz
[ 214.917732] wlo1: deauthenticating from ca:ae:30:6b:23:a4 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 244.244968] wlo1: authenticate with ca:ae:30:6b:23:a4 (local address=00:41:0e:98:5d:fb)
[ 244.259167] wlo1: send auth to ca:ae:30:6b:23:a4 (try 1/3) [ 244.261972] wlo1: authenticated
[ 244.262731] wlo1: associate with ca:ae:30:6b:23:a4 (try 1/3)
[ 244.275134] wlo1: RX AssocResp from ca:ae:30:6b:23:a4 (capab=0x1011 status=0 aid=33)
[ 244.306846] wlo1: associated
[ 244.326192] wlo1: Limiting TX power to 24 (24 - 0) dBm as advertised by ca:ae:30:6b:23:a4

I'm not sure where to look for the reason it fails to connect to 6Ghz.

EDIT:
Dual booted my laptop with Win11. 6Ghz working on Win11 but not on Ubuntu 24.04.

EDIT 20250129:
Added journal logs: https://paste.ubuntu.com/p/yvTk8pQQkz/
These lines are concerning:
Jan 29 08:32:33 Victus NetworkManager[1376]: [1738161153.7439] device (wlo1): Activation: (wifi) association took too long, failing activation
Jan 29 08:32:33 Victus NetworkManager[1376]: [1738161153.7440] device (wlo1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jan 29 08:32:33 Victus NetworkManager[1376]: [1738161153.7443] manager: NetworkManager state is now DISCONNECTED
Jan 29 08:32:33 Victus NetworkManager[1376]: [1738161153.7446] device (wlo1): Activation: failed for connection 'woody_6G'

EDIT 20240201:
Significant progress!
In order to connect to the 6Ghz network I must issue “sudo iw reg set US” prior to a connection attempt. Once connected to the 6Ghz network I can then switch between 2.4Ghz, 5Ghz, and 6Ghz networks without any issues. This remains true until I reboot.

I verified Regulatory Domain setting prior to switching to 6Ghz. Attempted to connect....Connection failed.
ken@Victus:~$ sudo iw reg get
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

The above output does not change after issuing “sudo iw set US”.

Attempting to connect again after issuing “sudo iw reg set US” command.....connection was successful.
ken@Victus:~$ nmcli device wifi list
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
72:AE:30:6B:23:A8 woody_2G Infra 1 270 Mbit/s 97 ▂▄▆█ WPA2
CA:AE:30:6B:23:A4 woody_5G Infra 40 270 Mbit/s 84 ▂▄▆█ WPA2
"*" D2:AE:30:6B:23:A5 woody_6G Infra 0 0 Mbit/s 70 ▂▄▆_ WPA3
40:A3:6B:C7:3A:7F -- Infra 1 135 Mbit/s 69 ▂▄▆_ WPA2
F0:9F:C2:71:86:45 NETGEAR63 Infra 6 195 Mbit/s 30 ▂___ WPA2

I conducted a diff between the /etc/netplan/<6Ghz.yaml> file after connection failed, to the same file after it connected. There are no changes in the file, and there is only one 6Ghz .yaml file.

I rebooted system several times to confirm the routine, results are repeatable.

So now I remain puzzled. Why would Netplan, NetworkManager, WPA_Supplicant not pull the current regulatory domain setting? Where is it pulling it from? Is it set in multiple places?

1 Answers1

1

Resolution:
After reboot/restart, NetworkManager was setting the Regulatory Domain to WORLD. This prevented the ability to connect to the 6Ghz network, limiting me to 2.4Ghz and 5Ghz. Issuing “sudo iw reg set US” would temporarily correct the issue until the next reboot/restart. Based on the recommendations and the provided links from @david, I created a Global Netplan Configuration File: /etc/netplan/10-netplan_cfg.yaml with the following contents:

network:  
  version: 2  
  wifis:  
    wlo1:   #change to your interface ID  
      regulatory-domain: US   #change to required country code

The Regulatory Domain will be set to US after restarts, and remain set after deleting/forgetting any saved networks, or modification to network settings. Additionally this should remain in place after any kernel or system updates.

There is still the question of WHY NetworkManger is setting the the Regulatory Domain to WORLD. But that I will leave for another day.

David, Thank you for all your help and support. I learned a great deal and would not have come through this without your help.