Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

From cold-start / reboot, one cannot associate to a WiFi-6e (6GHz) AP,
unless one already had a successful authentication to 6GHz since last
boot. The driver is being claimed to dismiss the authentication request.
On 5GHz and on 2.4GHz authnetication works on the same AP.

The log excerpt below shows a failing association request
to a 6GHz WiFi-6e AP. At this time, the WiFi NIC is already associated
to the same SSID on the 5GHz band of the same AP, thus the REGDOM is DE.

Please note that the REGDOM is being set to WORLD.

wpa_supplicant[1523]: wlp1s0: SME: Trying to authenticate with 82:8b:0b:ea:d0:8b (SSID='<REDACTED>' freq=6375 MHz)
wpa_supplicant[1523]: wlp1s0: SME: Authentication request to the driver failed
wpa_supplicant[1523]: BSSID 82:8b:0b:ea:d0:8b ignore list count incremented to 2, ignoring for 10 seconds
wpa_supplicant[1523]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

This behavior is reproducible after each boot.

Workaround:

1. Open another shell and spam correct REGDOM settings for your region:
   `while true; do sudo iw reg set DE; sleep 0.1; done;`
2. Initiate association on WiFi-6e AP
3. Association to 6GHz WiFi-6e successful!
4. Kill the while loop in the other shell.

Thank you for investigating!
-- Seb