14e4:43ba Wireless BCM43602 802.11ac cannot connec to to 5 GHz networks - MacBook Pro 11,5

[berglh]

What I expect to happen:
I expect to be able to scan 5 GHz channels and connect to them using the BCM43602 chipset in a MacBook Pro 11,5.

What happened:
I can see the 5 GHz SSIDs, but I am unable to connect to a working 5 GHz access point.

~$ iwlist wlp4s0 freq
wlp4s0 32 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Channel 36 : 5.18 GHz
          Channel 40 : 5.2 GHz
          Channel 44 : 5.22 GHz
          Channel 48 : 5.24 GHz
          Channel 52 : 5.26 GHz
          Channel 56 : 5.28 GHz
          Channel 60 : 5.3 GHz
          Channel 64 : 5.32 GHz
          Channel 100 : 5.5 GHz
          Channel 104 : 5.52 GHz
          Channel 108 : 5.54 GHz
          Channel 112 : 5.56 GHz
          Channel 116 : 5.58 GHz
          Channel 120 : 5.6 GHz
          Channel 124 : 5.62 GHz
          Channel 128 : 5.64 GHz
          Channel 132 : 5.66 GHz
          Channel 136 : 5.68 GHz
          Channel 140 : 5.7 GHz
          Current Frequency:2.462 GHz (Channel 11)

~$ sudo iwlist wlp4s0 scan | grep -e Freq -e SSID
                    Frequency:2.462 GHz (Channel 11)
                    ESSID:"Mistico"
                    Frequency:2.412 GHz (Channel 1)
                    ESSID:"Telstra1D5A"
                    Frequency:2.437 GHz (Channel 6)
                    ESSID:"HP-Print-42-Officejet Pro 8600"
                    Frequency:2.437 GHz (Channel 6)
                    ESSID:"Living room"

~$ iw phy [5 GHz Section]
  Frequencies:
   * 5170 MHz [34] (disabled)
   * 5180 MHz [36] (20.0 dBm)
   * 5190 MHz [38] (disabled)
   * 5200 MHz [40] (20.0 dBm)
   * 5210 MHz [42] (disabled)
   * 5220 MHz [44] (20.0 dBm)
   * 5230 MHz [46] (disabled)
   * 5240 MHz [48] (20.0 dBm)
   * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
     DFS state: usable (for 2969 sec)
     DFS CAC time: 60000 ms
   * 5720 MHz [144] (disabled)
   * 5745 MHz [149] (disabled)
   * 5765 MHz [153] (disabled)
   * 5785 MHz [157] (disabled)
   * 5805 MHz [161] (disabled)
   * 5825 MHz [165] (disabled)

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: uqblloy2 2250 F.... pulseaudio
 /dev/snd/controlC1: uqblloy2 2250 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sat Oct 24 17:06:10 2015
HibernationDevice: RESUME=UUID=8d3b6815-6d56-449c-866a-9787340e4ed9
InstallationDate: Installed on 2015-10-14 (10 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Apple Inc. MacBookPro11,5
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=98c832dd-51de-42a6-b626-ec8665cbc9c6 ro noprompt libata.force=noncq quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-16-generic N/A
 linux-backports-modules-4.2.0-16-generic N/A
 linux-firmware 1.149
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-23 (1 days ago)
dmi.bios.date: 07/31/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B05.1507311433
dmi.board.name: Mac-06F11F11946D27C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,5
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11F11946D27C5
dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B05.1507311433:bd07/31/2015:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
dmi.product.name: MacBookPro11,5
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Berg Lloyd-Haig, thank you for reporting this and helping make Ubuntu better.

Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[berglh (berglh)]

kernel-bug-exists-upstream-4.3-rc6

[penalvch (penalvch)]

Berg Lloyd-Haig, it is best to leave it as the linux package, given that the support in the firmware is already provided, and no evidence has been discussed noting this is confirmed a firmware issue, and not a kernel or other one.

Despite this, could you please advise to the manufacturer and firmware version of the wireless access point you are trying to connect to?

[berglh (berglh)]

@penalvch

TP-Link Archer C5_V1.20_150428 is the firmware on the access point. Other 5 GHz devices are connecting fine.

I'm currently at work and we have an enterprise 802.11x setup with Cisco AIR-CAP3602I-N-K9 APs with the AIR-RM3000AC-Z-K9 AC modules. I am unsure what firmware revision is on the Cisco APs, they are centrally managed by WISM controllers.

What is interesting at this point is that I can now see the networks advertised on the 5 GHz band, indicating that the scan for these networks is working.

My android device is definitely connecting on 5 GHz correctly. The MacBook Pro 11,5 with the broadcom chipset only connects to the 2.4 GHz endpoints.

[berglh (berglh)]

Just to confirm, I suspect the move to Kernel 4.3 rc6 has got the 5 GHz scanning working. For some reason the device just doesn't want to connect to 5 GHz. Not sure if I can make the adapter connect to explicitly connect to 5 GHz as the network is advertised on both frequency bands.

[berglh (berglh)]

Just ended up with a bunch of stuff in dmesg regarding 80211 cfg throwing errors.

[berglh (berglh)]

Tested with 4.3 rc7 and same behaviour still present.

[penalvch (penalvch)]

Berg Lloyd-Haig, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (TO: Arend van Spriel, Franky Lin, Hante Meuleman, Brett Rudley, and CC both brcm80211-dev-list and linux-wireless)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

[berglh (berglh)]

For some reason since the latest linux-firmware update (among others) that came through, I came through I am now able to connect to 5 GHz networks. I've been on 4.3rc7 for sometime which I saw now is 4.3 final. I haven't confirmed that it is OK on my home AP at the moment, but definitely is working on Cisco AP at work.