Bug 1483346 - Laptop with Broadcom network device does not load firmware
Summary: Laptop with Broadcom network device does not load firmware
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kmod
Version: 26
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: kmod development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-20 19:29 UTC by Paul Lambert
Modified: 2017-11-16 02:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-26 14:20:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Ubuntu Chilli555 modified (some) for Fedora (16.25 KB, application/x-shellscript)
2017-08-20 19:31 UTC, Paul Lambert
no flags Details
output of Chilli555 (19.02 KB, text/plain)
2017-08-20 19:32 UTC, Paul Lambert
no flags Details

Description Paul Lambert 2017-08-20 19:29:41 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Paul Lambert 2017-08-20 19:31:25 UTC
Created attachment 1316040 [details]
Ubuntu Chilli555 modified (some) for Fedora

Used this to generate diagnostics for network issue with Broadcom devcie

Comment 2 Paul Lambert 2017-08-20 19:32:43 UTC
Created attachment 1316041 [details]
output of Chilli555

Comment 3 Paul Lambert 2017-08-20 19:50:46 UTC
Moved hard drive with Fedora 25 from HP Pavilion to new HP Pavilion? 7-??  Booted it up and upgraded to Fedora 26.  All is good but wifi and bluetooth sort of.

This new HP laptop has Broadcom device for USB, USB wifi and wlan wifi.  The Bluetooth is running but loads with a patch does not load error.  Not focusing on this in this bug report

The Broadcom drivers are notorious for being difficult to get up and running.  In addition, the Broadcom device I have is fairly recent and is not yet supported as a firmware distribution.  Sort of.

Based on a lookup table I determined that my hardware device,14e4:4365, which is device type 4366.
I followed this link https://bugzilla.kernel.org/show_bug.cgi?id=135321 and scraped out a Windows 10 driver that is a brcmfmac4366c device driver .  There is a brcmfmac4366b firmware driver that is included as a firmware driver with the linux kernel.  However, it appears that this driver might actually be a 4366c but has been named incorrectly.  See the kernel.org bug report.  So, this leaves anyone with a Broadcom 4366 device type to use someone else's firmware until this bug at kernel.org is addressed.

My problem is this.  Most looks good but when I run rfkill list there is not wl device listed only bluetooth.
Modprobe output shows brcmfmac is loaded.  I have found 2 files that have brcmfmac blacklisted and removed the references.  I have edited the /usr/modprobe.d/open_fwwf.conf file to include options brcmfmac4366c nohwcrypt=1 qos=0

Comment 4 Paul Lambert 2017-08-26 04:16:55 UTC
This issue was resolved by replacing the kernel module brcmfmac with the kernel module wl.  Also, the bluetooth module loading errors disappeared too.

So currently, the Broadcom BCM4366 device type (14e4:4365) works using the brcmfmac4366c-pcie device driver with the wl kernel driver.

Please close.

Comment 5 Paul Lambert 2017-11-16 02:33:46 UTC
Just a follow up with new information.

I have scavenged the Internet and found various patches here and there for the Broacdcom 4365 (which is really the 4366 version) and found several patches for the brcm_hybrid driver software.  At this point I have eliminated all of the kernel crashes arising from the driver side.

Now I am getting errors arising from net/wireless/sam.c.  This software is not part of the Broadcom suite but looks to be kernel code for the OS.  I get various crashes and occasional kernel taints that all point to cfg80211_roamed at some line in sam.c, usally 880, 941 and a few more.

In searching the web I found this link that lists a kernel patch to sme.c.  This was posted on May 26.  Has this patch been applied to Fedora?  If not, do I need to open a new bug report?

https://github.com/raspberrypi/linux/issues/1988

diff --git a/net/wireless/scan.c b/net/wireless/scan.c
--- a/net/wireless/scan.c
+++ b/net/wireless/scan.c
@@ -544,6 +544,8 @@ static bool is_bss(struct cfg80211_bss *a, const u8 *bssid,
                return false;
        if (ssidie[1] != ssid_len)
                return false;
+       if (!ssidie[2]) /* Hidden AP */
+               return true;
        return memcmp(ssidie + 2, ssid, ssid_len) == 0;
 }


Note You need to log in before you can comment on or make changes to this bug.