Bug 1528291 - Wifi that uses brcmfmac driver stops working with recent linux-firmware
Summary: Wifi that uses brcmfmac driver stops working with recent linux-firmware
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-21 13:13 UTC by OlliC
Modified: 2018-11-30 20:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 20:38:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description OlliC 2017-12-21 13:13:22 UTC
Description of problem:

So on my Thinkpad L460 laptop with Fedora 27 the wifi stopped working after a normal system update last week and now i have figured out where the problem is. 
The is in the new linux-firmware package 20171215-81.git2451bb22.fc27. If i downgrade that package to 20171009-78.gitbf04291.fc27 (the version that came with the Fedora Workstation Live CD/Installer) it works. 

The wifi controller shown by lspci is this: 
03:00.0 Network controller: Broadcom Limited BCM4356 802.11ac Wireless Network Adapter (rev 02)

The errors shown by dmesg is this: 

[    5.963195] usbcore: registered new interface driver brcmfmac
[    5.963264] brcmfmac 0000:03:00.0: enabling device (0000 -> 0002)
[    6.075119] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x000002
[    6.077952] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac4356-pcie.txt failed with error -2
[    8.543003] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
[    8.543009] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -5
[    8.543011] brcmfmac: brcmf_bus_started: failed: -5
[    8.543016] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding


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

linux-firmware-20171215-81.git2451bb22.fc27

How reproducible:

Steps to Reproduce:
1. Use a PC or Laptop with a wifi card that uses brcmfmac driver
2. Update your system

Actual results:

Wifi stops working

Expected results:

Wifi still working

Additional info:

None

Comment 1 OlliC 2018-03-04 12:48:09 UTC
It seems like i am the only one having this bug?! 

Its still present on my system and up to now i could circumvent it by downgrading the linux-firmware package. But now that does not work anymore. I don't know exactly whats going on but dnf seems to not find the package linux-firmware anymore. 

With the rpm command i still see the package: 

# rpm -qf /usr/lib/firmware/brcm/brcmfmac4356-pcie.bin
linux-firmware-20171215-82.git2451bb22.fc27.noarch

But with dnf its not present anymore: 

# dnf downgrade linux-firmware
Last metadata expiration check: 0:55:36 ago on Sun Mar  4 12:49:53 2018.
No package linux-firmware available.
Error: No packages marked for downgrade.

# dnf search linux-firmware
Last metadata expiration check: 0:57:28 ago on Sun Mar  4 12:49:53 2018.
No matches found.

Help?

Comment 2 OlliC 2018-03-04 18:35:53 UTC
Ok i forgot that i added: 

excludepkgs=linux-firmware

in /etc/dnf/dnf.conf. 

After commenting it out it works again by downgrading the linux-firmware package. 

Still hoping for a fix in recent version!

Comment 3 David Wells 2018-03-27 14:14:48 UTC
I have a similar issue on an old Gateway machine that has a Broadcom BCM4311 controller on the motherboard. This does not not work even when downgrading to the linux-firmware package mentioned above. I also have a usb connected linksys adapter connected to the machine, that uses a Broadcom BCM4320 and this was not working with Fedora 27 (fully updated) but does work once I downgrade the linux firmware as described above.

It would be good to have both chips supported in the latest linux-firmware package.

Comment 4 Ben Cotton 2018-11-27 16:27:25 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2018-11-30 20:38:32 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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