Fedora 21 BCM4360 driver issues

[atgogggg]

Hello, I am running Fedora 21 on a new Macbook Pro Retina (not the newest one
with one USB port, but the version right before, without the force
touch pad and without a disc drive/Ethernet connection. I bought it brand new in late
February.

I'm having issues with the wireless driver. I isn't displaying anything WLAN related related in the network GUI.

I have a Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter
[14e4:43a0] (rev 03)

I've also created the .config file IAW http://forums.fedoraforum.org/showthread.php?t=296138. No joy

I have run yum update, installed the most recent Free and Nonfree
Repositories from RPM fusion, and installed broadcom-wl, akmod-wl, and kmod-wl to no joy.

lshw -class network gives me this output

[root@localhost michaellacks]# lshw -class network
*-usb:1
description: Ethernet interface
product: iPhone
vendor: Apple Inc.
physical id: 2
bus info: usb@2:2
logical name: enp0s20u2c4i2
version: 7.01
serial: 8caebe1f1e5aef2f87cde5f6c13997fc76f6e69b
capabilities: usb-2.00 ethernet physical
configuration: broadcast=yes driver=ipheth ip=172.20.10.3 link=yes maxpower=500mA multicast=yes speed=480Mbit/s
*-network UNCLAIMED
description: Network controller
product: BCM4360 802.11ac Wireless Network Adapter
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: 03
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:b0600000-b0607fff memory:b0400000-b05fffff

[chrismurphy]

http://linuxwireless.org/en/users/Drivers/b43/

Looks like 14e4:43a0 is not supported yet. I think you'll need to use the proprietary driver.

[atgogggg]

I'm having trouble locating the proprietary driver. It isn't listed on Broadcom's website per the instruction they provided.

https://www.broadcom.com/docs/linux_sta/README.txt

This is my first time looking for something like this; is this something that can be packaged up from an existing build and sent in an email?

Edit: Interestingly, the cached version of the website contained the driver. am now continuing with instructions.

[stevea]

BroadCrumb calls it the STA driver. I believe the current version (6.30.x) will support your chip.

Try the package 'kmod-wl' at rpmfusion.

[atgogggg]

BroadCrumb calls it the STA driver. I believe the current version (6.30.x) will support your chip.

Try the package 'kmod-wl' at rpmfusion.

I've tried this, I uninstalled it and re-installed it anyway. Installed with no issues and still no indication of a wireless card upon reboot.

At the moment I am attempting to compile the broadcom driver with no success. I've already installed the Kernel headers.

[atgoggggs@localhost Broadcom modjule]$ sudo yum install kernel-devel kernel-headers
Loaded plugins: langpacks
Package kernel-devel-3.19.7-200.fc21.x86_64 already installed and latest version
Package kernel-headers-3.19.7-200.fc21.x86_64 already installed and latest version
Nothing to do
[atgogggg@localhost Broadcom modjule]$


[atgogggg@localhost Downloads]$ cd Broadcom\ modjule/
[atgogggg@localhost Broadcom modjule]$ ls
lib Makefile src
[atgogggg@localhost Broadcom modjule]$ make
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: *** /lib/modules/3.17.4-301.fc21.x86_64/build: No such file or directory. Stop.
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

I noticed that the "set of numbers" for kernel-devel/kernel-headers and the modules are different, but I don't have the Linux vocabulary to know look up what they mean. looks like a version number. What this looks like to me is that I either have to downgrade my kernel to match the numbers on the module or upgrade the driver. I'll keep working on it but in the meantime I'll try my best.

Edit:2
Wow am I learning a lot. using this website

http://www.labtestproject.com/using_...ra_kernel.html

here's the output:

[atgogggg@localhost Broadcom modjule]$ rpm -qa | grep ^kernel
kernel-modules-3.17.4-301.fc21.x86_64
kernel-3.17.4-301.fc21.x86_64
kernel-debug-devel-3.19.7-200.fc21.x86_64
kernel-modules-3.19.7-200.fc21.x86_64
kernel-devel-3.19.7-200.fc21.x86_64
kernel-3.19.7-200.fc21.x86_64
kernel-headers-3.19.7-200.fc21.x86_64
kernel-core-3.19.7-200.fc21.x86_64
kernel-core-3.17.4-301.fc21.x86_64
[atgogggg@localhost Broadcom modjule]$ uname -r
3.17.4-301.fc21.x86_64
[atgogggg@localhost Broadcom modjule]$

So currently using the kernel that matches the driver (3.17.4-301.fc21.x86_64) I'm a little confused now. Feel like the driver should definitely be working now. While previously thought of as unrelated, upon start up I do have another boot option for fedora, but the keyboard doesn't work on it and I've never actually logged into it.

feeling brave and will go ahead and delete all of the kernel stuff being careful as not to delete the one that I am currently using. I don't understand the intimate relationship of a driver to a kernel/headers but anticipate that it may be getting confused

New edit (will start tracking edits) on a hunch I decided to put the output of the kernel versions into gedit and organize them:

kernel-modules-3.17.4-301.fc21.x86_64
kernel-3.17.4-301.fc21.x86_64
kernel-core-3.17.4-301.fc21.x86_64

kernel-debug-devel-3.19.7-200.fc21.x86_64
kernel-modules-3.19.7-200.fc21.x86_64
kernel-devel-3.19.7-200.fc21.x86_64
kernel-3.19.7-200.fc21.x86_64
kernel-headers-3.19.7-200.fc21.x86_64
kernel-core-3.19.7-200.fc21.x86_64

Looks like all of the troubleshooting/installations I have bee doing were for a kernel I'm not using. Because for some reason I am unable to use the keyboard booting into 3.19, I am going to now install the corresponding files that I have for 3.19.

Edit ...6:

Didn't end up deleting any kernels, however installing the kernel headers for 3.14.4 failed via the GUI Software Installer, as everything I have tried to install using it has. Looked for the 3.14.4 headers in the repository by using a yum search, and only found kmod-wl-3.17.4-301.fc21.x86_64.x86_64. Installed fine and zero wireless options in the network manager after restarting the network manager using "/etc/init.d/network restart". Going to restart the computer and take a break.

Edit 7

It Works!!! I love this place!!!

Long story short, install the kmod-wl for the kernel you are using. discover the kernel you are using either upon boot, or type "rpm -qa | grep ^kernel" in terminal.

I have updates to the thread sent to my email, so if anyone wants to ask me more about it please just post here.

Thank you everyone!!

[stevea]

1/ I'm a little surprised that a current 6.30 didn't work. Ubuntu claims that it does, but then again they make have patched the driver.

2/ Keep your driver build directory around. You'll need to make && sudo make install for every new kernel id installed (until support arrives).

3/ It's a reasonable idea to:
sudo yum groups install "Development Tools"
when building drivers (doesn't include kernel headers last I looked, but most everything else).