Hide Forgot
Created attachment 1131602 [details] output of `lspci -vnn' Description of problem: With the Linux 4.4 update, my laptop started using the bcma driver instead of broadcom-wl (yay!) for my BCM4352 device except that the new driver doesn't work (boo!). The bcma module doesn't load automatically, and when I manually do `modprobe bcma' I get in the dmesg: [ 480.954610] bcma-pci-bridge 0000:02:00.0: enabling device (0000 -> 0002) [ 480.954669] bcma: bus0: Found chip with id 0x4352, rev 0x03 and package 0x00 [ 480.954693] bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2B, class 0x0) [ 480.954706] bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2A, class 0x0) [ 480.954732] bcma: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x02, class 0x0) [ 480.954758] bcma: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x01, class 0x0) [ 480.954772] bcma: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x11, class 0x0) [ 481.011267] bcma: Unsupported SPROM revision: 11 [ 481.011270] bcma: bus0: Invalid SPROM read from the PCIe card, trying to use fallback SPROM [ 481.011271] bcma: bus0: Using fallback SPROM failed (err -2) [ 481.011272] bcma: bus0: No SPROM available [ 481.013444] bcma: bus0: Bus registered and no wireless (nothing shows up in ifconfig). Everything still works fine when I boot into 4.3. Version-Release number of selected component (if applicable): 4.4 How reproducible: 100% Steps to Reproduce: 1. Boot into 4.4 kernel Actual results: no wireless support Expected results: wireless support Additional info:
Created attachment 1131604 [details] full dmesg
Sorry, forgot to mention -- this is the 2015 model.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.