Re: Can't reconnect to WiFi easily

[Felix Lechner]

Hi Felipe,

On Wed, Nov 2, 2022 at 12:45 PM Luis Felipe
<luis.felipe.la@protonmail.com> wrote:
>
> 2 11:18:55 localhost gnome-keyring-daemon[796]: couldn't access control 
> socket: /run/user/1001/keyring/control/: file or directory not found
> 2 11:18:55 localhost gnome-keyring-daemon[797]: couldn't access control 
> socket: /run/user/1001/keyring/control/: file or directory not found
> 2 11:18:55 localhost gnome-keyring-daemon[795]: couldn't access control 
> socket: /run/user/1001/keyring/control/: file or directory not found

I don't use Gnome anymore, but if your numerical user id is 1001 it
could be that Gnome cannot access your keyring, which may contain your
Wifi password.

Last time I checked, however, Gnome simply used NetworkManager.
Someone with more recent Gnome experience will be able to help you
better here.

> Then I changed to TTY2 and tried to reboot, but, as expected, "sudo reboot" 
> hanged.

I might issue those commands as 'sudo bash' and then separately, as
root, 'reboot'  to make sure the sudo isn't hanging. (It probably
isn't.)

> these are the messages of dmesg after the reboot:
...
> [   46.990655] cfg80211: Loading compiled-in X.509 certificates for 
> regulatory database
> [   46.991069] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> [   46.991103] platform regulatory.0: Direct firmware load for regulatory.db 
> failed with error -2
> [   46.991105] cfg80211: failed to load regulatory.db
...
> [   47.898322] ath9k 0000:02:00.0: enabling device (0100 -> 0102)
> [   47.898640] ath: phy0: WB335 2-ANT card detected
> [   47.898644] ath: phy0: Set BT/WLAN RX diversity capability
> [   47.911482] ath: phy0: Enable LNA combining
> [   47.912965] ath: phy0: ASPM enabled: 0x43
> [   47.912969] ath: EEPROM regdomain: 0x6c
> [   47.912971] ath: EEPROM indicates we should expect a direct regpair map
> [   47.912974] ath: Country alpha2 being used: 00
> [   47.912977] ath: Regpair used: 0x6c
> [   47.914204] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [   47.914965] ieee80211 phy0: Atheros AR9565 Rev:2 mem=0xffffaf3880880000, 
> irq=19
...
> [   95.653997] rfkill: input handler disabled
> [  120.124431] rfkill: input handler enabled
> [  120.918634] wlp2s0: authenticate with cc:03:fa:d7:16:e2
> [  120.918652] wlp2s0: bad VHT capabilities, disabling VHT
> [  120.918654] wlp2s0: 80 MHz not supported, disabling VHT
> [  120.937623] wlp2s0: send auth to cc:03:fa:d7:16:e2 (try 1/3)
> [  120.939749] wlp2s0: authenticated
> [  120.941984] wlp2s0: associate with cc:03:fa:d7:16:e2 (try 1/3)
> [  120.945808] wlp2s0: RX AssocResp from cc:03:fa:d7:16:e2 (capab=0x1411 
> status=0 aid=1)
> [  120.945982] wlp2s0: associated
...
> [  137.526271] rfkill: input handler disabled

When the system is stuck I would try to unload and reload the ath9k
kernel module. This can be done with 'modprobe' or, more aggressively,
with 'insmod' and 'rmmod'.

I once had a Wifi card, also an Atheros, that needed to be unloaded
when my system was suspended via ACPI.

Kind regards
Felix Lechner