Hi,

------- Original Message -------
On Wednesday, November 2nd, 2022 at 21:42, Felix Lechner <felix.lechner@lease-up.com> wrote:


> 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.)

I'll try that next time.

 

> 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 forgot to use modprobe, but will do next time. I'm taking note.


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

Thanks for the help, Felix.

Cheers,