Bug ID | 1169771 |
---|---|
Summary | Bug in install-brcmfmac.sh [pkg bcm43xx-firmware] |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.1 |
Hardware | armv7 |
OS | Other |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Network |
Assignee | screening-team-bugs@suse.de |
Reporter | alessio.adamo@gmail.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Hi everybody, I was trying to achieve Bluetooth activation on my cubox-i, and while tinkering I realized a putative bug in the script 'install-brcmfmac.sh' used by the package 'bcm43xx-firmware'. The script parses the file '/sys/firmware/devicetree/base/compatible' looking for 'solidrun,cubox-i', however it is not successful, because in my personal case it actually retrieves 'solidrun,cubox-i/q'. Because of this, the symbolic link '/lib/firmware/brcm/brcmfmac4330-sdio.txt' is not created and brcmfmac fails with the following error messages: [ 21.774391] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4 [ 21.833131] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.solidrun,cubox-i/q.txt failed with error -2 [ 21.833205] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.txt failed with error -2 The content of '/sys/firmware/devicetree/base/compatible' is: solidrun,cubox-i/q^@fsl,imx6q^@ I think that's probably because it's a Cubox-i Pro Quad Core. Changing the pattern for case statement into solidrun,cubox-i|solidrun,cubox-i/q) fixes the issue. The issue affects all Leap 15 versions. Regards, Alessio