[SOLVED] Unable to connect to a specific wifi network

unnilquadium · 2021-03-03 14:40:57

Today, after a system update, I was unable to connect to my home wifi through the adapter that I've used for the past 2-3 years.

The adapter is the following:

Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)

After the update, networkmanager still shows *some* wifi networks but not my own.

I guess this is somehow related to crda or the regulatory domains, because:

Prior to the update I was never able to set the reg domain to my country, it always defaulted to China. But, since it worked, I ignored it.

Now, after the update, I tried to set the reg domain again, but it remains stuck at country 00

#iw reg get shows this:

country 00: DFS-UNSET

I've tried downgrading crda, iw, wpa_supplicant and networkmanager, the kernel and the kernel-headers. None of those worked.
Ended up reverting the whole upgrade and it now works as before.

Any help or insight will be much appreciated.

Last edited by unnilquadium (2021-03-27 17:18:53)

seth · 2021-03-03 15:34:33

linux-firmware update?

You're probably running into the sanitizer now?
What's the EEPROM regdomain before and after the update?
(In doubt post the system journal from the current and the last bad boot)

https://bbs.archlinux.org/viewtopic.php?id=254535
https://github.com/torvalds/linux/commi … c3654a5423

unnilquadium · 2021-03-05 12:55:43

seth wrote:

linux-firmware update?

The problem started after a full system upgrade, so I assume everything was up to date.

seth wrote:

What's the EEPROM regdomain before and after the update?

In both instances the country is set to CN:

Relevant journal lines from a boot with the problem:

Mar 02 05:39:08 skylake kernel: ath: EEPROM regdomain: 0x809c
Mar 02 05:39:08 skylake kernel: ath: EEPROM indicates we should expect a country code
Mar 02 05:39:08 skylake kernel: ath: doing EEPROM country->regdmn map search
Mar 02 05:39:08 skylake kernel: ath: country maps to regdmn code: 0x52
Mar 02 05:39:08 skylake kernel: ath: Country alpha2 being used: CN
Mar 02 05:39:08 skylake kernel: ath: Regpair used: 0x52

Relevant journal lines from a boot without the problem:

Mar 04 06:37:07 skylake kernel: ath: EEPROM regdomain: 0x809c
Mar 04 06:37:07 skylake kernel: ath: EEPROM indicates we should expect a country code
Mar 04 06:37:07 skylake kernel: ath: doing EEPROM country->regdmn map search
Mar 04 06:37:07 skylake kernel: ath: country maps to regdmn code: 0x52
Mar 04 06:37:07 skylake kernel: ath: Country alpha2 being used: CN
Mar 04 06:37:07 skylake kernel: ath: Regpair used: 0x52

Both boots show the same information.
I try changing the country with "iw reg set" but it always remain set to CN.

Do you need the full journal for more information?

For the time being I'm just waiting to see if it gets fixed by a new kernel version or something else, but any advice is more then welcome!

seth · 2021-03-05 14:00:30

The idea was that an update to linux-firmware might have /caused/ this.

Do you need the full journal for more information?

Yes please.
Also stats on your home wifi (protocol, band (2.4/5GHz) and channel in use (they will not show up in the journal and you can't query them if the station can't be found, so you'll have look into the router or w/ a different system)

u666sa · 2021-03-17 20:39:35

We both using same driver, ath9k, but I don't have such problems.

[1] 0000:03:00.0 [RW] AR9462 Wireless Adapter (PCI-E) (168c:0034, 105b:e052)

[   12.692241] systemd[1]: Reached target Paths.
[   18.202232] usbcore: registered new interface driver ath3k
[   18.463183] ath: phy0: ASPM enabled: 0x43
[   18.463198] ath: EEPROM regdomain: 0x6c
[   18.463200] ath: EEPROM indicates we should expect a direct regpair map
[   18.463204] ath: Country alpha2 being used: 00
[   18.463205] ath: Regpair used: 0x6c
[   27.119951] ath: EEPROM regdomain: 0x8348
[   27.119956] ath: EEPROM indicates we should expect a country code
[   27.119958] ath: doing EEPROM country->regdmn map search
[   27.119959] ath: country maps to regdmn code: 0x3a
[   27.119960] ath: Country alpha2 being used: US
[   27.119961] ath: Regpair used: 0x3a
[   27.119962] ath: regdomain 0x8348 dynamically updated by country element

Thing is, I've updated my card's firmware, enabling n networking and world domain. Maybe this could help you.
https://drive.google.com/file/d/1cwlQsS … sp=sharing

You download and extract. Go to ...../iwleeprom/branches/atheros/
make
sudo ./iwleeprom -p
reboot

Then also, if you randomly lose connection, https://bbs.archlinux.org/viewtopic.php?id=161305

unnilquadium · 2021-03-27 17:19:29

This has since been resolved, so marking as solved.

Arch Linux

#1 2021-03-03 14:40:57

[SOLVED] Unable to connect to a specific wifi network

#2 2021-03-03 15:34:33

Re: [SOLVED] Unable to connect to a specific wifi network

#3 2021-03-05 12:55:43

Re: [SOLVED] Unable to connect to a specific wifi network

#4 2021-03-05 14:00:30

Re: [SOLVED] Unable to connect to a specific wifi network

#5 2021-03-17 20:39:35

Re: [SOLVED] Unable to connect to a specific wifi network

#6 2021-03-27 17:19:29

Re: [SOLVED] Unable to connect to a specific wifi network

Board footer