You are not logged in.

Pages: 1

#1 2014-01-23 01:08:51

tenfoxes
Member
From: Pittsburgh, PA., USA
Registered: 2014-01-06
Posts: 11
Website

[SOLVED] Broadcom wireless card behaving very strangely

My wireless card has become unusable in an obscure fashion after a reboot. It may have been due to the recent kernel update, but I rebooted once after that update and the card was fine, so I'm not sure. Wireless was working without a hitch for months before this.

I have a Macbook Pro 9,1 with a Broadcom BCM4331 wireless card. I use the b43 firmware.

The firmware is being loaded on boot, but that vague "link is not ready" error appears every time the system attempts to load the firmware:

[   12.263906] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
[   12.264337] b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
[   12.264864] Broadcom 43xx driver loaded [ Features: PMNLS ]
[   12.728423] systemd-udevd[210]: renamed network interface wlan0 to wlp3s0
[   15.801790] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[   15.888891] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  186.474169] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[  186.561426] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  326.465714] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[  326.552778] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  683.592477] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[  683.679541] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1350.060493] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1350.147545] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1474.360067] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1474.447162] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1667.887393] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1667.967795] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 2110.770119] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 2110.857285] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready

When I try to use netctl to connect to my home network, I get the same error:

-- Unit netctl@home.service has begun starting up.
Jan 22 18:36:40 tenfoxes network[3072]: Starting network profile 'home'...
Jan 22 18:36:41 tenfoxes kernel: b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Jan 22 18:36:41 tenfoxes kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jan 22 18:36:56 tenfoxes network[3072]: WPA association/authentication failed for interface 'wlp3s0'
Jan 22 18:36:56 tenfoxes network[3072]: Failed to bring the network up for profile 'home'
Jan 22 18:36:56 tenfoxes systemd[1]: netctl@home.service: main process exited, code=exited, status=1/FAILURE
Jan 22 18:36:56 tenfoxes systemd[1]: Failed to start Networking for netctl profile home.

If I scan for networks using iw dev wlp3s0 scan, I get no output. Here's the debug output from that if it means anything to anyone—from the docs on netlink I read it doesn't seem to show anything unusual:

-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 26 <0x1a>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438118
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 33
    .version = 0
    .unused = 0
  [PAYLOAD] 16 octets
    08 00 03 00 03 00 00 00 08 00 2d 00 04 00 01 00 ..........-.....
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1390438118
    .port = 3698
  [ERRORMSG] 20 octets
    .error = 0 "Success"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 26 <0x1a>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438118
    .port = 3698
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438119
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 1
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 116
    .type = 16 <genl/family::nlctrl>
    .flags = 0 <>
    .seq = 1390438119
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 1
    .version = 2
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
  [ATTR 01] 2 octets
    10 00                                           ..
  [PADDING] 2 octets
    00 00                                           ..
  [ATTR 03] 4 octets
    02 00 00 00                                     ....
  [ATTR 04] 4 octets
    00 00 00 00                                     ....
  [ATTR 05] 4 octets
    07 00 00 00                                     ....
  [ATTR 06] 20 octets
    14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
    0e 00 00 00                                     ....
  [ATTR 07] 24 octets
    18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
    6e 6f 74 69 66 79 00 00                         notify..
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1390438119
    .port = 3698
  [ERRORMSG] 20 octets
    .error = 0 "Success"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 16 <0x10>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438119
    .port = 3698
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438120
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 0
    .unused = 0
  [ATTR 02] 8 octets
    6e 6c 38 30 32 31 31 00                         nl80211.
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438121
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 1
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 116
    .type = 16 <genl/family::nlctrl>
    .flags = 0 <>
    .seq = 1390438121
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 1
    .version = 2
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
  [ATTR 01] 2 octets
    10 00                                           ..
  [PADDING] 2 octets
    00 00                                           ..
  [ATTR 03] 4 octets
    02 00 00 00                                     ....
  [ATTR 04] 4 octets
    00 00 00 00                                     ....
  [ATTR 05] 4 octets
    07 00 00 00                                     ....
  [ATTR 06] 20 octets
    14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
    0e 00 00 00                                     ....
  [ATTR 07] 24 octets
    18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
    6e 6f 74 69 66 79 00 00                         notify..
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1390438121
    .port = 3698
  [ERRORMSG] 20 octets
    .error = 0 "Success"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 16 <0x10>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438121
    .port = 3698
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438122
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 0
    .unused = 0
  [ATTR 02] 8 octets
    6e 6c 38 30 32 31 31 00                         nl80211.
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438123
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 1
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 116
    .type = 16 <genl/family::nlctrl>
    .flags = 0 <>
    .seq = 1390438123
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 1
    .version = 2
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
  [ATTR 01] 2 octets
    10 00                                           ..
  [PADDING] 2 octets
    00 00                                           ..
  [ATTR 03] 4 octets
    02 00 00 00                                     ....
  [ATTR 04] 4 octets
    00 00 00 00                                     ....
  [ATTR 05] 4 octets
    07 00 00 00                                     ....
  [ATTR 06] 20 octets
    14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
    0e 00 00 00                                     ....
  [ATTR 07] 24 octets
    18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
    6e 6f 74 69 66 79 00 00                         notify..
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1390438123
    .port = 3698
  [ERRORMSG] 20 octets
    .error = 0 "Success"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 16 <0x10>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438123
    .port = 3698
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438124
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 0
    .unused = 0
  [ATTR 02] 8 octets
    6e 6c 38 30 32 31 31 00                         nl80211.
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438125
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 1
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 116
    .type = 16 <genl/family::nlctrl>
    .flags = 0 <>
    .seq = 1390438125
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 1
    .version = 2
    .unused = 0
  [ATTR 02] 7 octets
    6e 6c 63 74 72 6c 00                            nlctrl.
  [PADDING] 1 octets
    00                                              .
  [ATTR 01] 2 octets
    10 00                                           ..
  [PADDING] 2 octets
    00 00                                           ..
  [ATTR 03] 4 octets
    02 00 00 00                                     ....
  [ATTR 04] 4 octets
    00 00 00 00                                     ....
  [ATTR 05] 4 octets
    07 00 00 00                                     ....
  [ATTR 06] 20 octets
    14 00 01 00 08 00 01 00 03 00 00 00 08 00 02 00 ................
    0e 00 00 00                                     ....
  [ATTR 07] 24 octets
    18 00 01 00 08 00 02 00 10 00 00 00 0b 00 01 00 ................
    6e 6f 74 69 66 79 00 00                         notify..
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 36
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1390438125
    .port = 3698
  [ERRORMSG] 20 octets
    .error = 0 "Success"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 16 <0x10>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438125
    .port = 3698
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 32
    .type = 16 <genl/family::nlctrl>
    .flags = 5 <REQUEST,ACK>
    .seq = 1390438126
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 3
    .version = 0
    .unused = 0
  [ATTR 02] 8 octets
    6e 6c 38 30 32 31 31 00                         nl80211.
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 172
    .type = 26 <0x1a>
    .flags = 0 <>
    .seq = 0
    .port = 0
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 34
    .version = 1
    .unused = 0
  [PAYLOAD] 152 octets
    08 00 01 00 00 00 00 00 08 00 03 00 03 00 00 00 ................
    0c 00 99 00 01 00 00 00 00 00 00 00 08 00 2d 00 ..............-.
    04 00 00 00 74 00 2c 00 08 00 00 00 6c 09 00 00 ....t.,.....l...
    08 00 01 00 71 09 00 00 08 00 02 00 76 09 00 00 ....q.......v...
    08 00 03 00 7b 09 00 00 08 00 04 00 80 09 00 00 ....{...........
    08 00 05 00 85 09 00 00 08 00 06 00 8a 09 00 00 ................
    08 00 07 00 8f 09 00 00 08 00 08 00 94 09 00 00 ................
    08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 00 00 ................
    08 00 0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 ................
    08 00 0d 00 b4 09 00 00                         ........
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Sent Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 28
    .type = 26 <0x1a>
    .flags = 773 <REQUEST,ACK,ROOT,MATCH>
    .seq = 1390438127
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 32
    .version = 0
    .unused = 0
  [PAYLOAD] 8 octets
    08 00 03 00 03 00 00 00                         ........
---------------------------  END NETLINK MESSAGE   ---------------------------
-- Debug: Received Message:
--------------------------   BEGIN NETLINK MESSAGE ---------------------------
  [NETLINK HEADER] 16 octets
    .nlmsg_len = 20
    .type = 3 <DONE>
    .flags = 2 <MULTI>
    .seq = 1390438127
    .port = 3698
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 0
    .version = 0
    .unused = 0
---------------------------  END NETLINK MESSAGE   ---------------------------

If I try to use wpa-supplicant, it will say "Successfully initialized wpa_supplicant" as if it had properly made a connection, but it hasn't. Running iw dev wlp3s0 link will show that the card isn't connected to anything, and of course the internet still doesn't work.

I know it's not a hardware problem because the wireless works fine in Mac OS.

What gives? Is there a way I can investigate this further? It seems like a driver and/or kernel issue but I'm not really sure how to nail that down with confidence. I couldn't find any reports in the kernel bug tracker about this or anything, so maybe it's just me and I'm doing something wrong.

Thanks!

Last edited by tenfoxes (2014-01-24 02:44:16)

Offline

#2 2014-01-23 13:26:33

yassine
Member
Registered: 2013-07-17
Posts: 7

Re: [SOLVED] Broadcom wireless card behaving very strangely

Why not trying with the proprietary driver?
https://aur.archlinux.org/packages/broadcom-wl/

Last edited by yassine (2014-01-23 13:26:48)

Offline

#3 2014-01-24 02:43:55

tenfoxes
Member
From: Pittsburgh, PA., USA
Registered: 2014-01-06
Posts: 11
Website

Re: [SOLVED] Broadcom wireless card behaving very strangely

Yay, that worked!

I guess I really should've tried that initially, huh? tongue Since the wiki said not to use it unless you had an unsupported wireless card, I figured I shouldn't (b43 officially supports mine). Still, considering that it's easy to install/uninstall drivers, my caution was obviously unwarranted.

Thanks for your help!

Offline

Pages: 1

Board footer

Powered by FluxBB