Bug 1622362
Summary: | missing brcmfmac43430a0_sdio.txt file (and manual workaround) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | GroovieMan <christian.groove> |
Component: | linux-firmware | Assignee: | David Woodhouse <dwmw2> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | christian.groove, dwmw2, jforbes, jwboyer, kernel-maint, labbott, pbrobinson |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | linux-firmware-20190213-93.git710963fe.fc29 linux-firmware-20190213-93.git710963fe.fc28 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-02-24 04:08:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
GroovieMan
2018-08-26 20:05:15 UTC
same issue in F29 (incl running workaround) We now ship a brcm/brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt and the driver supports loading device specific NVRAM files now so please test linux-firmware-20190213-93.git710963fe.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6 linux-firmware-20190213-93.git710963fe.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f27089e66c linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-42cbff0fd6 I'll gonna check it immediately. Ah, how to i get it ? linux-firmware-20190213-93.git710963fe.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. Got these firmware updates some minutes agon. Problem is not solved. The wifi still does not work until i perform a modeprobe brcmfmac Can you provide the contents of "dmesg | grep -i brcm" Of course, after update and reboot: $ dmesg | grep -i brcm (nothing) Then .. $ modprobe brcmfmac $ dmesg | grep -i brcm [ 728.039829] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430a0-sdio for chip BCM43430/0 [ 728.039970] usbcore: registered new interface driver brcmfmac [ 728.062704] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.TrekStor-SurfBook W2.txt failed with error -2 [ 728.161989] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430a0-sdio for chip BCM43430/0 [ 728.162077] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.clm_blob failed with error -2 [ 728.162082] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 728.166326] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/0 wl0: May 29 2017 00:03:43 version 7.13.53.9 (r664949) FWID 01-130000 > [ 728.062704] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.TrekStor-SurfBook W2.txt failed with error -2
Right so it's a different device to what we have upstream based on the "TrekStor-SurfBook W2" bit
linux-firmware-20190213-93.git710963fe.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. Please do not forget FC29 (In reply to GroovieMan from comment #14) > Please do not forget FC29 See comment 8, what exactly has been forgotten? Not sure what you mean. I am a running a F29 and the past f29 fix did not work! (In reply to GroovieMan from comment #16) > Not sure what you mean. I am a running a F29 and the past f29 fix did not > work! Please provide output of "dmesg|grep -i brcm" |