Can't connect to WiFi, keep getting prompted for password

User Support General
1

Hi,

I have a X230 running QubesOS. When I’m at home I can connect to Wi-Fi without any problems, but when I’m at the office I can’t connect. I’m not sure why, but when I open up network connections, select the Wi-Fi and enter the password, it tries to connect, fails, prompts again for a password.

I’ve went over the points addressed in this post, but it didn’t solve my problem.

lspci -k has this output

Network controller:XXXXX
Subsystem: XXXXX
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

and lspci -v has this additional line

Capabilities: access denied

So, Access denied doesn’t sound good :grinning: Do I need to fix this, and how?

I have restarted the NetworkManager and then sudo rmmod iwldvm followed by sudo modprobe iwldvm. Restarts everything and then the password prompt appears again.

(I was able to connect to the wireless network at the office one time only.)

Thank you for helping me with this problem.

2

I can’t help here, but to me this problem looks like a non-Qubes-specific one, i.e., you might have a better luck searching Fedora or Debian forums.

1 Like
3

I had this situation on another laptop used primarily for testing. The same thing was happening with my home network.
The solution was… to just try again and again until it succeeded.

I don’t know why this happens and only on that specific laptop but as of today this is the only advice I would give: don’t give up.

1 Like
4

Just to add to this: When I run journalctl -f -u NetworkManager it tells me that there is a timeout when trying to connect

Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4614] Config: added 'ssid' value 'xxxxxxx'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4614] Config: added 'scan_ssid' value '1'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4615] Config: added 'bgscan' value 'simple:xx:-xxxx:xxxx'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4615] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4615] Config: added 'auth_alg' value 'OPEN'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4615] Config: added 'psk' value '<hidden>'
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4698] device (wls6): supplicant interface state: interface_disabled -> inactive
Nov 02 19:59:55 sys-net NetworkManager[1829]: <info>  [1667415595.4930] device (wls6): supplicant interface state: inactive -> authenticating
Nov 02 19:59:57 sys-net NetworkManager[1829]: <info>  [1667415597.7440] device (wls6): supplicant interface state: authenticating -> disconnected
Nov 02 20:00:07 sys-net NetworkManager[1829]: <info>  [1667415607.7505] device (wls6): supplicant interface state: disconnected -> scanning
Nov 02 20:00:10 sys-net NetworkManager[1829]: <info>  [1667415610.8068] device (wls6): supplicant interface state: scanning -> authenticating
Nov 02 20:00:12 sys-net NetworkManager[1829]: <info>  [1667415612.9805] device (wls6): supplicant interface state: authenticating -> disconnected
**Nov 02 20:00:21 sys-net NetworkManager[1829]: <warn>  [1667415621.1409] device (wls6): Activation: (wifi) association took too long, failing activation**
5

Have found the solution. The issue was that the router offered mixed-mode and my card couldn’t deal with that, just gave up. Created a separate wifi, WPA2-only, works like a charm. Posting in case somebody else stumbles across a similar issue.

2 Likes
6