FS#44821 - [linux] WIFI not working after upgrading to kernel 4.0.1

Attached to Project: Arch Linux
Opened by Sushovan Mandal (enlighter) - Sunday, 03 May 2015, 04:16 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 02 October 2017, 20:31 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: WIFI not working after upgrading to kernel 4.0.1


Additional info:
Upstream bug track:
https://bugzilla.kernel.org/show_bug.cgi?id=96831
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 02 October 2017, 20:31 GMT
Reason for closing:  Not a bug
Additional comments about closing:  user error solved by uninstalling broadcom-wl
Comment by Sushovan Mandal (enlighter) - Sunday, 03 May 2015, 04:20 GMT
This is probably a related problem reported in the archlinux forums:
https://bbs.archlinux.org/viewtopic.php?id=196813
Comment by David López (David López) - Tuesday, 05 May 2015, 07:45 GMT
I'm not completely sure that my problem is exactly the same, but after updating linux to 4.0.1 my wifi card cannot connect to my net, network manager asks me for my password (although the password is obviously well typed). Downgrading linux to 3.18.6 solves the problem and internet connection works

I've compared dmesg and journalctl between both, 3.18.6 and 4.0.1 kernels.

dmesg-4.0.1: http://pastebin.com/ZyMvnmKm
journalctl-4.0.1: http://pastebin.com/r0r5Hd4z

dmesg-3.18.6: http://pastebin.com/1f18z9rh
journalctl-3.18.6: http://pastebin.com/HZkFASGw

I've found a warning in journalctl in 4.0.1 kernel that could be related with my problem

abr 30 14:58:53 surface NetworkManager[276]: <info> (mlan0): Activation: Stage 2 of 5 (Device Configure) complete.
abr 30 14:58:53 surface NetworkManager[276]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
abr 30 14:58:53 surface NetworkManager[276]: <info> Config: set interface ap_scan to 1
abr 30 14:58:55 surface NetworkManager[276]: <info> (mlan0): supplicant interface state: scanning -> associating
abr 30 14:58:55 surface NetworkManager[276]: <info> (mlan0): supplicant interface state: associating -> 4-way handshake
abr 30 14:59:01 surface NetworkManager[276]: <warn> Connection disconnected (reason 15)

PD: my machine is a Surface Pro and its wifi card has TONS of problems in linux, see https://bugs.archlinux.org/task/44269 and https://bugzilla.kernel.org/show_bug.cgi?id=69661 . However I believe that this problem is not related with those older bugs
Comment by Sushovan Mandal (enlighter) - Wednesday, 06 May 2015, 06:00 GMT
There is no 'reason 15' in my journalctl.

However, for linux 3.19.3, there is 4-way handshake completed messages:

May 02 14:42:58 Archenlighter NetworkManager[340]: <info> (wlo1): supplicant interface state: associating -> 4-way handshake
May 02 14:42:58 Archenlighter NetworkManager[340]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
May 02 14:58:51 Archenlighter NetworkManager[354]: <info> (wlo1): supplicant interface state: associating -> 4-way handshake
May 02 14:58:51 Archenlighter NetworkManager[354]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed
May 02 18:20:12 Archenlighter NetworkManager[354]: <info> (wlo1): supplicant interface state: associated -> 4-way handshake
May 02 18:20:13 Archenlighter NetworkManager[354]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed

But during the time linux 4.0.1 kernel was active there is no 4-way handshake message, however I found the following messages in journalctl during the time linux 4.0.1 kernel was in play:

May 02 14:52:49 Archenlighter avahi-daemon[336]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.137.100.
May 02 14:52:49 Archenlighter wpa_supplicant[381]: wlo1: CTRL-EVENT-DISCONNECTED bssid=ec:f3:5b:3b:14:4a reason=3 locally_generated=1
May 02 14:52:49 Archenlighter kernel: wl0: link down (wlo1)
May 02 14:52:49 Archenlighter wpa_supplicant[381]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
May 02 14:52:49 Archenlighter wpa_supplicant[381]: wlo1: CTRL-EVENT-TERMINATING
May 02 14:52:49 Archenlighter NetworkManager[340]: <info> (wlo1): device state change: activated -> deactivating (reason 'removed') [100 110 36]
May 02 14:52:50 Archenlighter NetworkManager[340]: <info> (wlo1): device state change: deactivating -> unmanaged (reason 'removed') [110 10 36]
May 02 14:52:50 Archenlighter NetworkManager[340]: <info> (wlo1): deactivating device (reason 'removed') [36]
May 02 14:52:50 Archenlighter NetworkManager[340]: <info> (wlo1): canceled DHCP transaction, DHCP client pid 396
May 02 14:52:50 Archenlighter NetworkManager[340]: <info> (wlo1): DHCPv4 state changed bound -> done
May 02 14:52:50 Archenlighter kernel: IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
May 02 14:58:38 Archenlighter kernel: wl 0000:0d:00.0 wlo1: renamed from wlan0
Comment by Sushovan Mandal (enlighter) - Wednesday, 06 May 2015, 10:15 GMT
Solved for me!

Apparently the problem in my system was arising due to some conflict because of the 'broadcom-wl' package being installed.

It came to notice when the broadcom-wl package was upgraded and then the same problem arose as that due to upgrade to linux-4.0.1 kernel.

I have now removed the 'broadcom-wl' package and upgraded the system to linux-4.0.1 kernel and my wifi is working again.

Loading...