[SOLVED]can't connect to Wi-Fi network by once

buzhidao · 2016-03-19 22:27:03

I am using ArchLinux on macbook pro 13-inch early 2015, everything works fine but the wireless
I have to repeat connect multiple times to get wireless works
https://www.youtube.com/watch?v=KBrogX8 … e=youtu.be

dmesg:

[  720.742990] brcmfmac: brcmf_msgbuf_get_pktid: Invalid packet id 331 (not in use)
[  803.964490] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  809.597121] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  811.145220] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[  815.130003] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  815.633357] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  817.830328] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  819.439158] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[  823.374077] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  823.876127] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  826.997875] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  826.998691] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  827.045448] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  830.196286] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  831.828576] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[  835.755315] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  836.258790] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  837.484986] brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, bssidx=0
[  837.484997] brcmfmac: brcmf_fweh_event_worker: event handler failed (69)
[  837.486759] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  840.429386] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[  844.444855] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  844.949222] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  849.352067] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  850.872813] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[  853.121720] IPv6: ipv6_create_tempaddr: retry temporary address regeneration

how to solve this problem? thank you so much!

Last edited by buzhidao (2016-03-21 16:56:54)

Docbroke · 2016-03-21 09:58:40

looks like you are using broadcom card, kindly provide more details about your card, and how you are connecting. Have you tried alternate drivers, ? (if not you may want to check archwiki page on broadcom)

buzhidao · 2016-03-21 11:34:29

Docbroke wrote:

looks like you are using broadcom card, kindly provide more details about your card, and how you are connecting. Have you tried alternate drivers, ? (if not you may want to check archwiki page on broadcom)

03:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01)
	Subsystem: Apple Inc. Device [106b:0133]
	Flags: bus master, fast devsel, latency 0, IRQ 62
	Memory at c1400000 (64-bit, non-prefetchable) [size=32K]
	Memory at c1000000 (64-bit, non-prefetchable) [size=4M]
	Capabilities: [48] Power Management version 3
	Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+
	Capabilities: [68] Vendor Specific Information: Len=44 <?>
	Capabilities: [ac] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Device Serial Number **hidden**
	Capabilities: [150] Power Budgeting <?>
	Capabilities: [160] Virtual Channel
	Capabilities: [1b0] Latency Tolerance Reporting
	Capabilities: [220] #15
	Capabilities: [240] L1 PM Substates
	Kernel driver in use: brcmfmac
	Kernel modules: brcmfmac

i use NetworkManager to connect.
driver: brcm80211 Kernel driver open-source version
the wiki says

brcm80211

The kernel contains two built-in open-source drivers: brcmsmac for PCI backends and brcmfmac for SDIO/USB backends. They should be automatically loaded when booting.

i will try another driver.
thanks for your reply!

ewaller · 2016-03-21 14:40:38

... and, can you please post the output of find /etc/systemd ?

Trilby · 2016-03-21 14:51:30

I am pretty sure this is not a driver issue, you are using the right driver. I suspect this is relevant:

buzhidao wrote:

i use NetworkManager to connect.

I've never used NetworkManager, so I don't know if it is a fault of the software, or a common misconfiguration, but I do know there are frequent issues with users of NetworkManager having their interface not put "up" (e.g. ip link set <iface> up) prior to NetworkManager trying to connect. So the connection fails the first time.

This can be confirmed by trying a different method of connecting - for diagnostic purposes, I'd recommend connecting manually after (temporarily) disabling NM. Alternatively, this could also be tested by simply putting the interface up manually before trying to use NM. If this is the issue, then it can be solved by ... someone other than me - like I said, all I know of NM are the issues I see reported with it on these forums.

buzhidao · 2016-03-21 16:55:04

ewaller wrote:

... and, can you please post the output of find /etc/systemd ?

/etc/systemd
/etc/systemd/system.conf
/etc/systemd/user.conf
/etc/systemd/journald.conf
/etc/systemd/coredump.conf
/etc/systemd/bootchart.conf
/etc/systemd/logind.conf
/etc/systemd/journal-remote.conf
/etc/systemd/journal-upload.conf
/etc/systemd/timesyncd.conf
/etc/systemd/resolved.conf
/etc/systemd/network
/etc/systemd/system
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/pulseaudio.socket

Thanks!

buzhidao · 2016-03-21 16:56:34

Trilby wrote:

I am pretty sure this is not a driver issue, you are using the right driver. I suspect this is relevant:
buzhidao wrote:
i use NetworkManager to connect.
I've never used NetworkManager, so I don't know if it is a fault of the software, or a common misconfiguration, but I do know there are frequent issues with users of NetworkManager having their interface not put "up" (e.g. ip link set <iface> up) prior to NetworkManager trying to connect. So the connection fails the first time.
This can be confirmed by trying a different method of connecting - for diagnostic purposes, I'd recommend connecting manually after (temporarily) disabling NM. Alternatively, this could also be tested by simply putting the interface up manually before trying to use NM. If this is the issue, then it can be solved by ... someone other than me - like I said, all I know of NM are the issues I see reported with it on these forums.

you are right, if i manually if down then if up, it will back to normal..

looks like a NetworkManager's bug.

solved by put interface down then up in the startup.

thank you so much!

ewaller · 2016-03-21 19:16:20

Just following up on my request -- that all looks fine. I was checking for things that might be conflicting with NetworkManager.

Arch Linux

#1 2016-03-19 22:27:03

[SOLVED]can't connect to Wi-Fi network by once

#2 2016-03-21 09:58:40

Re: [SOLVED]can't connect to Wi-Fi network by once

#3 2016-03-21 11:34:29

Re: [SOLVED]can't connect to Wi-Fi network by once

#4 2016-03-21 14:40:38

Re: [SOLVED]can't connect to Wi-Fi network by once

#5 2016-03-21 14:51:30

Re: [SOLVED]can't connect to Wi-Fi network by once

#6 2016-03-21 16:55:04

Re: [SOLVED]can't connect to Wi-Fi network by once

#7 2016-03-21 16:56:34

Re: [SOLVED]can't connect to Wi-Fi network by once

#8 2016-03-21 19:16:20

Re: [SOLVED]can't connect to Wi-Fi network by once

Board footer