wireess connection fails after upgrade to 15.3

For a while before upgrading to 15.3 I had to run “iwlist scan” on my laptop after each boot, but after upgrading to 15.3 I cannot get wifi to connect at all.

The hardware is Intel Dual band AC8265 in a Lenovo Thinkpad X270 with kernel driver iwlwifi.

Some details:

xenakis:/etc # iwlist scan 
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:0D:0B:91:00:02
                    Channel:10
                    Frequency:2.457 GHz (Channel 10)
                    Quality=45/70  Signal level=-65 dBm  
                    Encryption key:on
                    ESSID:"CODEMIST"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=000021569abd180b
                    Extra: Last beacon: 84ms ago
                    IE: Unknown: 0008434F44454D495354
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010A
                    IE: Unknown: 2A0104
                    IE: Unknown: 2F0104
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD090010180204F0000000
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00

xenakis:/etc # rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: yes
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
xenakis:/etc # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=-2147483648 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
xenakis:/etc 

Where should I look next?

I have tried using ip to bring it up but it does not do anything I can detect.


 xenakis:/etc # ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 54:e1:ad:c8:7c:1a brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1492 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether e4:70:b8:6a:19:22 brd ff:ff:ff:ff:ff:ff
    altname wlp3s0
xenakis:/etc # ip link set wlan0 up
xenakis:/etc # ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 54:e1:ad:c8:7c:1a brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1492 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether e4:70:b8:6a:19:22 brd ff:ff:ff:ff:ff:ff
    altname wlp3s0
xenakis:/etc # 

Just to note I am not using KDE or gnome, window manager is fvwm with X.

Did you configure for your wireless network yet? Your opening post doesn’t explicitly tell us which steps you have taken yet.

If using wicked, then do so via YaST > System > Network Settings…

https://doc.opensuse.org/documentation/leap/reference/html/book-reference/cha-network.html#sec-network-yast

Alternatively, you can use NetworkManager if preferred…

https://doc.opensuse.org/documentation/leap/reference/html/book-reference/cha-network.html#sec-network-yast-netcard-global

The network was working before the upgrade but yes I have used “yast2 lan” many times to zero effect. I have also retyped the password in case it got corrupted. I also tried settiing the kernel driver from auto. I have looked for a log file but failed to find any error message.

The other machine that uses WiFi was ok after the same upgrade so I was not expecting any problems.

For test purposes can you try connecting via CLI using wpa_supplicant?
https://wiki.archlinux.org/title/wpa_supplicant
Refer ‘Configuration’ and ‘Connection’ steps.

This might also be helpful to gaining an understanding what is occurring (or not) at boot…

sudo journalctl -b | egrep "wicked|wpa|net"

Thanks for help fullpost try this site Gbwhatsapp Apk

I tried this. Not sure I understand where to look but it does say


Wlan0.     device-ready
wlan0.      setup-in-progress

Which looks hopeful.

I tried this but wpa_cli did not get to a prompt, saying it could not connect to wpa_supplicant.


Feb 18 19:57:03 xenakis kernel: audit: initializing netlink subsys (disabled)
Feb 18 19:57:03 xenakis kernel: drop_monitor: Initializing network drop monitor service
Feb 18 19:57:06 xenakis systemd-tmpfiles[413]: /usr/lib/tmpfiles.d/net-snmp.conf:1: Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
Feb 18 19:57:06 xenakis kernel: thinkpad_acpi: http://ibm-acpi.sf.net/
Feb 18 19:57:07 xenakis udevadm[418]: systemd-udev-settle.service is deprecated. Please fix wickedd.service not to pull it in.
Feb 18 19:57:08 xenakis systemd-tmpfiles[713]: /usr/lib/tmpfiles.d/net-snmp.conf:1: Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
Feb 18 19:57:08 xenakis nscd[997]: 997 monitoring file `/etc/netgroup` (7)
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked AutoIPv4 supplicant service...
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked DHCPv4 supplicant service...
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked DHCPv6 supplicant service...
Feb 18 19:57:08 xenakis kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 18 19:57:08 xenakis systemd[1]: Started wicked DHCPv6 supplicant service.
Feb 18 19:57:08 xenakis systemd[1]: Started wicked AutoIPv4 supplicant service.
Feb 18 19:57:08 xenakis systemd[1]: Started wicked DHCPv4 supplicant service.
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked network management service daemon...
Feb 18 19:57:08 xenakis systemd[1]: Started wicked network management service daemon.
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked network nanny service...
Feb 18 19:57:08 xenakis systemd[1]: Started wicked network nanny service.
Feb 18 19:57:08 xenakis systemd[1]: Starting wicked managed network interfaces...
Feb 18 19:57:13 xenakis wickedd[1051]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 172.14.4.42 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
Feb 18 19:57:38 xenakis wicked[1081]: lo              up
Feb 18 19:57:38 xenakis wicked[1081]: eth0            device-not-running
Feb 18 19:57:38 xenakis wicked[1081]: wlan0           setup-in-progress
Feb 18 19:57:38 xenakis wicked[1081]: usb1            no-device
Feb 18 19:57:38 xenakis systemd[1]: Finished wicked managed network interfaces.
Feb 18 19:57:38 xenakis start-ntpd[1367]: Starting network time protocol daemon (NTPD)

Can you show what is reported?

ip a
sudo wicked ifstatus all
  • Is wlan0 up and connected?

If not try…

sudo wicked ifup wlan0

Perhaps also show

ls -l /etc/sysconfig/network/ifcfg-*
sudo cat /etc/sysconfig/network/ifcfg-wlan0
  • You can obfuscate or remove the psk (or other) credentials before posting here

xenakis:~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 54:e1:ad:c8:7c:1a brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 172.16.4.16/16 brd 172.16.255.255 scope global eth0
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1492 qdisc noqueue state DOWN group default qlen 1000
    link/ether e4:70:b8:6a:19:22 brd ff:ff:ff:ff:ff:ff
    altname wlp3s0
xenakis:~ # 


xenakis:~ # wicked ifstatus all
lo              up
      link:     #1, state up
      type:     loopback
      config:   compat:suse:/etc/sysconfig/network/ifcfg-lo
      leases:   ipv4 static granted
      leases:   ipv6 static granted
      addr:     ipv4 127.0.0.1/8 [static]
      addr:     ipv6 ::1/128 [static]

eth0            device-not-running
      link:     #2, state up, mtu 1500
      type:     ethernet, hwaddr 54:e1:ad:c8:7c:1a
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth0
      leases:   ipv4 static failed
      addr:     ipv4 172.16.4.16/16 [static]

wlan0           setup-in-progress
      link:     #3, state device-up, mtu 1492
      type:     wireless, state not-associated
      config:   compat:suse:/etc/sysconfig/network/ifcfg-wlan0

usb1            no-device
xenakis:~ # 


xenakis:~ # wicked ifup wlan0
wlan0           setup-in-progress
xenakis:~ # 

after a long delay

I found an old thread I helped with which shows how to get some diagnostic output from wicked and wpa_supplicant (involved in the wireless authentication/association). These

https://forums.opensuse.org/showthread.php/504532-Activating-wifi-card?p=2692547#post2692547

Follow the steps there to get the debug output required from the respective daemons. In particular the wicked.log and /var/log/wpa_supplicant.log at least. As the output can be lengthy, consider uploading them to susepsate. You may need to install the ‘susepaste’ package first. It can be used like this…

susepaste -t "output_1" -e "never" -f "text" /var/log/wpa_supplicant.log

Post the link that it generates here.

Check for any firmware-related issues as well…

sudo dmesg|egrep "firm|wlan0"

Produced no outputv

Produced no output

I followed the recipe and have got the wicked.log and wpa_supplicant.log an they are big. Trouble is the susepaste says
“Paste failed :-(” for both files

OK; it had lost te routing (another problem)


https://susepaste.org/61600258
https://susepaste.org/34652581

Ok, I suggest reducing the verbosity by just using just one ‘d’…

ExecStart=/usr/sbin/wpa_supplicant -dt -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

then as root do

systemctl daemon-reload
systemctl restart wpa_supplicant

This wpa_supplicant diagnostic guide may be of value for identifying problems with the association process…

Maybe with a bit of prudent grepping of the log, you may be able to identify the issue at hand.

The wpa_supplicant log is full of repetitive connection disconnection cycles…

1596199885.044058: wlan0: Trying to associate with 00:0d:0b:91:00:02 (SSID='CODEMIST' freq=2457 MHz)
1596199885.079781: wlan0: Associated with 00:0d:0b:91:00:02
1596199885.115590: wlan0: WPA: Key negotiation completed with 00:0d:0b:91:00:02 [PTK=CCMP GTK=CCMP]
1596199885.115621: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:0d:0b:91:00:02 completed [id=0 id_str=]
1596206002.669809: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:0d:0b:91:00:02 reason=3 locally_generated=1
1596206002.728309: wlan0: CTRL-EVENT-TERMINATING

More investigation needed to understand underlying cause.