Bug 1072252 - Recent update prevents wicked wireless connections
Recent update prevents wicked wireless connections
Status: RESOLVED WORKSFORME
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Network
Current
Other Other
: P5 - None : Critical (vote)
: ---
Assigned To: wicked maintainers
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-11 21:33 UTC by John Shand
Modified: 2018-01-27 22:36 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
mt: needinfo? (jshand2013)


Attachments
dmesg (59.34 KB, text/plain)
2017-12-11 21:33 UTC, John Shand
Details
journal (130.70 KB, text/plain)
2017-12-11 21:34 UTC, John Shand
Details
lsmod (5.95 KB, text/plain)
2017-12-11 21:34 UTC, John Shand
Details
lspci (1.77 KB, text/plain)
2017-12-11 21:35 UTC, John Shand
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Shand 2017-12-11 21:33:29 UTC
Created attachment 752448 [details]
dmesg

When booting the wireless connection is not made with router.  i have included several files to help debug hopefully
Comment 1 John Shand 2017-12-11 21:34:16 UTC
Created attachment 752449 [details]
journal
Comment 2 John Shand 2017-12-11 21:34:46 UTC
Created attachment 752450 [details]
lsmod
Comment 3 John Shand 2017-12-11 21:35:12 UTC
Created attachment 752451 [details]
lspci
Comment 4 Massimo Burcheri 2017-12-13 09:27:35 UTC
Last TW update has broken WPA2 here as well. Trying to re-create the Wireless connection there is no item like "WPA2" in the Security listbox available, only None.
Comment 5 Massimo Burcheri 2017-12-14 06:50:16 UTC
(In reply to Massimo Burcheri from comment #4)
> Last TW update has broken WPA2 here as well....

Sorry for the wrong comment, the situation here is opposite. Wicked is working here but NetworkManager fails with WPA2. -> bug 1072789
Comment 6 Marius Tomaschewski 2018-01-19 11:59:22 UTC
Massimo said in comment 5 that wicked works for him. I've just updated
TW on my notebook and it still works for me:

[17834.440601] iwlwifi 0000:0c:00.0: Radio type=0x1-0x2-0x0
[17834.562387] iwlwifi 0000:0c:00.0: Radio type=0x1-0x2-0x0
[17834.593923] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17837.589100] wlan0: authenticate with 4c:5e:0c:e7:06:a3
[17837.592401] wlan0: send auth to 4c:5e:0c:e7:06:a3 (try 1/3)
[17837.593928] wlan0: authenticated
[17837.593938] wlan0: waiting for beacon from 4c:5e:0c:e7:06:a3
[17837.684321] wlan0: associate with 4c:5e:0c:e7:06:a3 (try 1/3)
[17837.687612] wlan0: RX AssocResp from 4c:5e:0c:e7:06:a3 (capab=0x431 status=0 aid=3)
[17837.690945] wlan0: associated
[17837.878390] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

In the dmseg/journal from comment 0 and comment 1 it does look like this
would be wicked specific but rather something in the underlying wpa-supp
or the b43 kernel driver.

Dec 12 09:53:53 localhost kernel: b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19)
Dec 12 09:53:56 localhost kernel: wlp2s0b1: authenticate with 18:f1:45:67:bc:0f
Dec 12 09:53:56 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 1/3)
Dec 12 09:53:56 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 2/3)
Dec 12 09:53:56 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 3/3)
Dec 12 09:53:57 localhost kernel: wlp2s0b1: authentication with 18:f1:45:67:bc:0f timed out
Dec 12 09:54:06 localhost kernel: wlp2s0b1: authenticate with 18:f1:45:67:bc:0f
Dec 12 09:54:06 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 1/3)
Dec 12 09:54:06 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 2/3)
Dec 12 09:54:06 localhost kernel: wlp2s0b1: send auth to 18:f1:45:67:bc:0f (try 3/3)
Dec 12 09:54:07 localhost kernel: wlp2s0b1: authentication with 18:f1:45:67:bc:0f timed out
Dec 12 09:54:23 localhost wicked[1222]: lo              up
Dec 12 09:54:23 localhost wicked[1222]: wlp2s0b1        setup-in-progress

This are the versions that work for me:

# rpm -q wpa_supplicant kernel-default kernel-firmware wicked
wpa_supplicant-2.6-4.2.x86_64
kernel-default-4.14.12-1.8.x86_64
kernel-firmware-20180104-1.2.noarch
wicked-0.6.43-2.2.x86_64

Maybe kernel-firmware-20180104 provides a more recent b43 firmware than
the one from 2012-08-15 21:35:19 ?

When not, I'd propose to enable debug in wicked and wpa-supplicant as
described at
   https://en.opensuse.org/openSUSE:Bugreport_wicked
restart both, the wpa-supplicant and wickedd (or reboot) and then we can
look for suspect msgs.
Comment 7 Marius Tomaschewski 2018-01-19 12:22:41 UTC
I see, there is a bcm43xx-firmware package as well as b43-fwcutter and
pullin-bcm43xx-firmware. I'd try to reinstall all of them, esp. the
pullin-bcm43xx-firmware package.
Comment 8 John Shand 2018-01-27 22:36:25 UTC
this issue has been resolved for me.  how about others?