Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

WiFi detected but not connecting on Thinkpad X280

Need help with peripherals or devices?
Post Reply
Message
Author
gaglia
Posts: 16
Joined: 2009-08-30 21:54

WiFi detected but not connecting on Thinkpad X280

#1 Post by gaglia »

Hello, I have a strange problem, not sure exactly when it started because I use regularly my laptop connected via ethernet. This is a Lenovo Thinkpad X280 with Debian testing and Gnome.

Code: Select all

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
Connection to any WiFi network fails with no apparent reason. The card is turned on, in fact I can scan existing WiFi's but whenever I try to connect it fails. I am dual-booting with Windows and the problem does not appear there, so I guess it's not a hardware problem but I was unsure of the right forum section to post about.

Where do I start debugging?

Thanks in advance :)
Top
User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2044
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 151 times
Been thanked: 213 times

Re: WiFi detected but not connecting on Thinkpad X280

#2 Post by Hallvor »

Try this:

Code: Select all

# journalctl -f
Then try to connect. Any errors in the output?
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Top
User avatar
sunrat
Administrator
Administrator
Posts: 6542
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 119 times
Been thanked: 499 times

Re: WiFi detected but not connecting on Thinkpad X280

#3 Post by sunrat »

Telling us what your wifi device is would help a lot.

Code: Select all

lspci |grep -i wireless
or better if you have inxi installed

Code: Select all

inxi -Nxx
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Top
gaglia
Posts: 16
Joined: 2009-08-30 21:54

Re: WiFi detected but not connecting on Thinkpad X280

#4 Post by gaglia »

Hallvor wrote:try to connect. Any errors in the output?
Thank you, here is the log:

Code: Select all

May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4929] device (wlp59s0): Activation: starting connection 'WiFi_mySSID' (0123abcd-just-00an-uuid-0123456789ab)
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4930] audit: op="connection-add-activate" uuid="0123abcd-just-00an-uuid-0123456789ab" name="WiFi_mySSID" pid=957 uid=1000 result="success"
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4954] device (wlp59s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4958] manager: NetworkManager state is now CONNECTING
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4962] device (wlp59s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4966] device (wlp59s0): Activation: (wifi) access point 'WiFi_mySSID' has security, but secrets are required.
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4966] device (wlp59s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.4968] sup-iface[0123456789abcdef,0,wlp59s0]: wps: type pbc start...
May 21 18:01:30 myhostname wpa_supplicant[655]: wlp59s0: WPS-PBC-ACTIVE
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.5077] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:01:30 myhostname NetworkManager[639]: <info>  [1621591290.5077] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7216] device (wlp59s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7221] device (wlp59s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7223] device (wlp59s0): Activation: (wifi) connection 'WiFi_mySSID' has security, and secrets exist.  No new secrets needed.
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'ssid' value 'WiFi_mySSID'
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'scan_ssid' value '1'
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'bgscan' value 'simple:30:-70:86400'
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'auth_alg' value 'OPEN'
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7224] Config: added 'psk' value '<hidden>'
May 21 18:01:55 myhostname wpa_supplicant[655]: wlp59s0: SME: Trying to authenticate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:01:55 myhostname kernel: wlp59s0: authenticate with 00:ff:aa:55:00:ff
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7474] device (wlp59s0): supplicant interface state: scanning -> authenticating
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7475] device (p2p-dev-wlp59s0): supplicant management interface state: scanning -> authenticating
May 21 18:01:55 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 1/3)
May 21 18:01:55 myhostname wpa_supplicant[655]: wlp59s0: Trying to associate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7629] device (wlp59s0): supplicant interface state: authenticating -> associating
May 21 18:01:55 myhostname NetworkManager[639]: <info>  [1621591315.7630] device (p2p-dev-wlp59s0): supplicant management interface state: authenticating -> associating
May 21 18:01:55 myhostname kernel: wlp59s0: authenticated
May 21 18:01:55 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 1/3)
May 21 18:01:55 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 2/3)
May 21 18:01:55 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 3/3)
May 21 18:01:56 myhostname kernel: wlp59s0: association with 00:ff:aa:55:00:ff timed out
May 21 18:01:56 myhostname NetworkManager[639]: <info>  [1621591316.1218] device (wlp59s0): supplicant interface state: associating -> disconnected
May 21 18:01:56 myhostname NetworkManager[639]: <info>  [1621591316.1219] device (p2p-dev-wlp59s0): supplicant management interface state: associating -> disconnected
May 21 18:01:56 myhostname NetworkManager[639]: <info>  [1621591316.2220] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:01:56 myhostname NetworkManager[639]: <info>  [1621591316.2222] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:01:57 myhostname wpa_supplicant[655]: wlp59s0: SME: Trying to authenticate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:01:57 myhostname kernel: wlp59s0: authenticate with 00:ff:aa:55:00:ff
May 21 18:01:57 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 1/3)
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.0932] device (wlp59s0): supplicant interface state: scanning -> authenticating
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.0933] device (p2p-dev-wlp59s0): supplicant management interface state: scanning -> authenticating
May 21 18:01:57 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 2/3)
May 21 18:01:57 myhostname wpa_supplicant[655]: wlp59s0: Trying to associate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:01:57 myhostname kernel: wlp59s0: authenticated
May 21 18:01:57 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 1/3)
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.2081] device (wlp59s0): supplicant interface state: authenticating -> associating
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.2082] device (p2p-dev-wlp59s0): supplicant management interface state: authenticating -> associating
May 21 18:01:57 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 2/3)
May 21 18:01:57 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 3/3)
May 21 18:01:57 myhostname kernel: wlp59s0: association with 00:ff:aa:55:00:ff timed out
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.5597] device (wlp59s0): supplicant interface state: associating -> disconnected
May 21 18:01:57 myhostname NetworkManager[639]: <info>  [1621591317.5598] device (p2p-dev-wlp59s0): supplicant management interface state: associating -> disconnected
May 21 18:01:58 myhostname NetworkManager[639]: <info>  [1621591318.0601] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:01:58 myhostname NetworkManager[639]: <info>  [1621591318.0602] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:02:00 myhostname wpa_supplicant[655]: wlp59s0: SME: Trying to authenticate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:00 myhostname kernel: wlp59s0: authenticate with 00:ff:aa:55:00:ff
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.3059] device (wlp59s0): supplicant interface state: scanning -> authenticating
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.3060] device (p2p-dev-wlp59s0): supplicant management interface state: scanning -> authenticating
May 21 18:02:00 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:00 myhostname wpa_supplicant[655]: wlp59s0: Trying to associate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.3382] device (wlp59s0): supplicant interface state: authenticating -> associating
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.3383] device (p2p-dev-wlp59s0): supplicant management interface state: authenticating -> associating
May 21 18:02:00 myhostname kernel: wlp59s0: authenticated
May 21 18:02:00 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:00 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 2/3)
May 21 18:02:00 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 3/3)
May 21 18:02:00 myhostname kernel: wlp59s0: association with 00:ff:aa:55:00:ff timed out
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.6867] device (wlp59s0): supplicant interface state: associating -> disconnected
May 21 18:02:00 myhostname NetworkManager[639]: <info>  [1621591320.6868] device (p2p-dev-wlp59s0): supplicant management interface state: associating -> disconnected
May 21 18:02:01 myhostname NetworkManager[639]: <info>  [1621591321.6878] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:02:01 myhostname NetworkManager[639]: <info>  [1621591321.6879] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:02:02 myhostname wpa_supplicant[655]: wlp59s0: SME: Trying to authenticate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:02 myhostname kernel: wlp59s0: authenticate with 00:ff:aa:55:00:ff
May 21 18:02:02 myhostname NetworkManager[639]: <info>  [1621591322.5432] device (wlp59s0): supplicant interface state: scanning -> authenticating
May 21 18:02:02 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:02 myhostname NetworkManager[639]: <info>  [1621591322.5434] device (p2p-dev-wlp59s0): supplicant management interface state: scanning -> authenticating
May 21 18:02:02 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 2/3)
May 21 18:02:02 myhostname wpa_supplicant[655]: wlp59s0: Trying to associate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:02 myhostname kernel: wlp59s0: authenticated
May 21 18:02:02 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:02 myhostname NetworkManager[639]: <info>  [1621591322.6565] device (wlp59s0): supplicant interface state: authenticating -> associating
May 21 18:02:02 myhostname NetworkManager[639]: <info>  [1621591322.6566] device (p2p-dev-wlp59s0): supplicant management interface state: authenticating -> associating
May 21 18:02:02 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 2/3)
May 21 18:02:02 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 3/3)
May 21 18:02:02 myhostname kernel: wlp59s0: association with 00:ff:aa:55:00:ff timed out
May 21 18:02:03 myhostname wpa_supplicant[655]: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WiFi_mySSID" auth_failures=1 duration=10 reason=CONN_FAILED
May 21 18:02:03 myhostname NetworkManager[639]: <info>  [1621591323.0070] device (wlp59s0): supplicant interface state: associating -> disconnected
May 21 18:02:03 myhostname NetworkManager[639]: <info>  [1621591323.0071] device (p2p-dev-wlp59s0): supplicant management interface state: associating -> disconnected
May 21 18:02:08 myhostname NetworkManager[639]: <info>  [1621591328.0109] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:02:08 myhostname NetworkManager[639]: <info>  [1621591328.0110] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:02:12 myhostname wpa_supplicant[655]: wlp59s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WiFi_mySSID"
May 21 18:02:12 myhostname wpa_supplicant[655]: wlp59s0: SME: Trying to authenticate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:12 myhostname kernel: wlp59s0: authenticate with 00:ff:aa:55:00:ff
May 21 18:02:12 myhostname NetworkManager[639]: <info>  [1621591332.8656] device (wlp59s0): supplicant interface state: scanning -> authenticating
May 21 18:02:12 myhostname NetworkManager[639]: <info>  [1621591332.8657] device (p2p-dev-wlp59s0): supplicant management interface state: scanning -> authenticating
May 21 18:02:12 myhostname kernel: wlp59s0: send auth to 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:12 myhostname wpa_supplicant[655]: wlp59s0: Trying to associate with 00:ff:aa:55:00:ff (SSID='WiFi_mySSID' freq=2412 MHz)
May 21 18:02:12 myhostname kernel: wlp59s0: authenticated
May 21 18:02:12 myhostname NetworkManager[639]: <info>  [1621591332.8776] device (wlp59s0): supplicant interface state: authenticating -> associating
May 21 18:02:12 myhostname NetworkManager[639]: <info>  [1621591332.8777] device (p2p-dev-wlp59s0): supplicant management interface state: authenticating -> associating
May 21 18:02:12 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 1/3)
May 21 18:02:12 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 2/3)
May 21 18:02:13 myhostname kernel: wlp59s0: associate with 00:ff:aa:55:00:ff (try 3/3)
May 21 18:02:13 myhostname kernel: wlp59s0: association with 00:ff:aa:55:00:ff timed out
May 21 18:02:13 myhostname wpa_supplicant[655]: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WiFi_mySSID" auth_failures=2 duration=20 reason=CONN_FAILED
May 21 18:02:13 myhostname NetworkManager[639]: <info>  [1621591333.2213] device (wlp59s0): supplicant interface state: associating -> disconnected
May 21 18:02:13 myhostname NetworkManager[639]: <info>  [1621591333.2213] device (p2p-dev-wlp59s0): supplicant management interface state: associating -> disconnected
May 21 18:02:20 myhostname NetworkManager[639]: <warn>  [1621591340.5697] device (wlp59s0): Activation: (wifi) association took too long
May 21 18:02:20 myhostname NetworkManager[639]: <info>  [1621591340.5698] device (wlp59s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May 21 18:02:20 myhostname NetworkManager[639]: <info>  [1621591340.5707] sup-iface[0123456789abcdef,0,wlp59s0]: wps: type pbc start...
May 21 18:02:20 myhostname NetworkManager[639]: <warn>  [1621591340.5734] device (wlp59s0): Activation: (wifi) asking for new secrets
May 21 18:02:20 myhostname wpa_supplicant[655]: wlp59s0: WPS-PBC-ACTIVE
May 21 18:02:20 myhostname NetworkManager[639]: <info>  [1621591340.5854] device (wlp59s0): supplicant interface state: disconnected -> scanning
May 21 18:02:20 myhostname NetworkManager[639]: <info>  [1621591340.5855] device (p2p-dev-wlp59s0): supplicant management interface state: disconnected -> scanning
May 21 18:02:22 myhostname NetworkManager[639]: <warn>  [1621591342.7709] device (wlp59s0): no secrets: User canceled the secrets request.
May 21 18:02:22 myhostname NetworkManager[639]: <info>  [1621591342.7710] device (wlp59s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
May 21 18:02:22 myhostname NetworkManager[639]: <info>  [1621591342.7726] manager: NetworkManager state is now DISCONNECTED
May 21 18:02:22 myhostname NetworkManager[639]: <warn>  [1621591342.7751] device (wlp59s0): Activation: failed for connection 'WiFi_mySSID'
May 21 18:02:22 myhostname NetworkManager[639]: <info>  [1621591342.7756] device (wlp59s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
May 21 18:02:22 myhostname wpa_supplicant[655]: wlp59s0: Reject scan trigger since one is already pending
sunrat wrote:Telling us what your wifi device is would help a lot.

Code: Select all

lspci |grep -i wireless
Thank you, here it is:

Code: Select all

3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Top
User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2044
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 151 times
Been thanked: 213 times

Re: WiFi detected but not connecting on Thinkpad X280

#5 Post by Hallvor »

It looks like the password has failed.

Code: Select all

May 21 18:02:03 myhostname wpa_supplicant[655]: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WiFi_mySSID" auth_failures=1 duration=10 reason=CONN_FAILED
May 21 18:02:03 myhostname NetworkManager[639]: <info>  [1621591323.0070] device (wlp59s0): supplicant interface state: associating -> disconnected
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Top
gaglia
Posts: 16
Joined: 2009-08-30 21:54

Re: WiFi detected but not connecting on Thinkpad X280

#6 Post by gaglia »

Hallvor wrote:It looks like the password has failed.

Code: Select all

May 21 18:02:03 myhostname wpa_supplicant[655]: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WiFi_mySSID" auth_failures=1 duration=10 reason=CONN_FAILED
May 21 18:02:03 myhostname NetworkManager[639]: <info>  [1621591323.0070] device (wlp59s0): supplicant interface state: associating -> disconnected
I noticed that but I can swear the password is correct, it's the same I use from other devices and I tried many different times.
Top
User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2044
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 151 times
Been thanked: 213 times

Re: WiFi detected but not connecting on Thinkpad X280

#7 Post by Hallvor »

You are apparently not alone: https://duckduckgo.com/?t=ffab&q=auth_f ... LED&ia=web See if you can find the solution there.
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Top
gaglia
Posts: 16
Joined: 2009-08-30 21:54

Re: WiFi detected but not connecting on Thinkpad X280

#8 Post by gaglia »

Hallvor wrote:You are apparently not alone: https://duckduckgo.com/?t=ffab&q=auth_f ... LED&ia=web See if you can find the solution there.
Hi, thanks for the hint and sorry for the late reply, I had a medical emergency, still in the hospital but doing fine.

So, as far as I've read the issue might be caused by the MAC randomization feature in the new (new? since 2017...) Network Manager module. It should have been fixed long ago anyway so I'm not sure this applies here. Regardless, I disabled this (useful) feature as suggested, by editing /etc/NetworkManager/NetworkManager.conf and adding

Code: Select all

[device]
wifi.scan-rand-mac-address=no
Unfortunately that didn't fix the issue. Any idea where I can report this?
Top
gaglia
Posts: 16
Joined: 2009-08-30 21:54

Re: WiFi detected but not connecting on Thinkpad X280

#9 Post by gaglia »

Forgot to mention, I even apt purged the whole network-manager and reinstalled both network-manager and network-manager-gnome but nothing changed (I also re-removed the MAC randomization thing afterward)
Top
User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2044
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 151 times
Been thanked: 213 times

Re: WiFi detected but not connecting on Thinkpad X280

#10 Post by Hallvor »

You could try filing a bug report: https://www.debian.org/Bugs/Reporting
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Top
User avatar
NorthEast
Posts: 352
Joined: 2018-11-18 04:35
Has thanked: 12 times
Been thanked: 30 times

Re: WiFi detected but not connecting on Thinkpad X280

#11 Post by NorthEast »

In this situation I would have a crack at manually configuring wireless using wpa_supplicant as outlined in: https://wiki.debian.org/WiFi/HowToUse.
I didn't have to use the configs mentioned there in relation to "wpa_supplicant v2.6" but the rest worked fine for me when I had what sounds like a similar problem.
I don't however use NetworkManager, but just networking.
Top
Post Reply

Return to “Hardware”