Arch Linux

vlovich

Member

Registered: 2021-03-05

Posts: 22

[SOLVED] WiFi can't associate with a specific AP always prompting pwd

I'm not sure what it was, whether a connection of messing around trying to get tethering to work & breaking it or a software update gone wrong, but my wifi refuses to connect to any wifi and just constantly prompts for the password. Perhaps related, when I remove a wifi from my list of previously associated, it throws up a permission error.

I've previously connected succesfully to this router. I can connect to an unprotected network. Unclear if it's this router or protected networks in general.

My wifi is the one built into my Dell Inspiron Precision 5550 (comet lake wifi I think). lspci returns

00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi

The driver is iwlwifi

I'm on KDE / Plasma w/ NetworkManager. journalctl doesn't seem to have anything wifi related (i.e. when I try repeatedly to connect there's nothing new).

I do have gnome-keyring installed but I think it's always been even when the wifi was working.

Last edited by vlovich (2023-05-05 21:25:42)

Maniaxx

Member

Registered: 2014-05-14

Posts: 761

Re: [SOLVED] WiFi can't associate with a specific AP always prompting pwd

Log the connection attempt:
https://wiki.archlinux.org/title/Wpa_su … n_failures

You can increase verbosity up to '-ddd' if necessary.

---

sys2064

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,675

Re: [SOLVED] WiFi can't associate with a specific AP always prompting pwd

NM is actually very chatty and wets wpa_supplicant to debug as well, so I'd first simply look into the system journal.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

vlovich

Member

Registered: 2021-03-05

Posts: 22

Re: [SOLVED] WiFi can't associate with a specific AP always prompting pwd

Interesting. So what I did was completely remove all references to my AP in NetworkManager UI and then deleted it explicitly via sudo rm /etc/NetworkManager/system-connections/<AP>.nmconnection.

Now it started to work. Something got screwed up in NetworkManager's state it looks like.