-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing firmware BCM4354A2-13d3-3485.hcd for BCM4354/BCM4356 chip #3
Comments
Just out of curiosity, i tried renaming the firmware file BCM4356A2-13d3-3485.hcd to BCM4354A2-13d3-3485.hcd and rebooted. |
Hello. First of all, firmware from this repository will not work with your device, it's total different chipset family. EDIT: and |
Thank you for the quick reply. Please find below the output of the lsusb and lspci commands. I guess the actual bluetooth device is part of the Broadcom wifi chip (last line).
|
That's weird. You have "ID 13d3:3485 IMC Networks" that threats as BCM4354A2, but it should be BCM4356A2. lspci shows too that there should be BCM4356. Can you please post output of these commands:
|
This is the full output of dmesg: https://pastebin.com/SES6sMyS
As far as I can tell, this is only the wifi (802.11) device, not the bluetooth device.
|
Well, here what I found. BCM4354A2 is actually BCM4356A2. It seems in Linux Kernel typo or bug. |
Ok. Did that. No more error messages during startup. But connections still did not work. Now comes the good part: After consulting the linux wireless pages at https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 (which are acutally about the corresponding wifi 802.11 device), I learned that in addition to the fireware some EFI NVRAM information may be required for this device. Following the instructions from that source, I executed the following commands as root:
Notice the .txt extenstion vs. the .bin extension of the wifi firmware file. Now after another reboot everything works as expected (currently tested with the presentation remoate and different bluetooth speakers: HSP and A2DP). Full dmesg output: https://pastebin.com/zPauTmbM
|
Great to hear that. Thank you for useful information. |
Added new Broadcom device BCM4350C5, changed BCM4354A2 to BCM4356A2. Based on Broadcom Windows drivers 001.003.015 should be BCM4356A2. I have user report that firmware name is misplaced (winterheart/broadcom-bt-firmware#3). Signed-off-by: Azamat H. Hackimov <[email protected]>
Added new Broadcom device BCM4350C5, changed BCM4354A2 to BCM4356A2. Based on Broadcom Windows drivers 001.003.015 should be BCM4356A2. I have user report that firmware name is misplaced (winterheart/broadcom-bt-firmware#3). Signed-off-by: Azamat H. Hackimov <[email protected]> Signed-off-by: Marcel Holtmann <[email protected]>
jira LE-1907 Rebuild_History Non-Buildable kernel-4.18.0-310.el8 commit-author Azamat H. Hackimov <[email protected]> commit bf0ddd1 Added new Broadcom device BCM4350C5, changed BCM4354A2 to BCM4356A2. Based on Broadcom Windows drivers 001.003.015 should be BCM4356A2. I have user report that firmware name is misplaced (winterheart/broadcom-bt-firmware#3). Signed-off-by: Azamat H. Hackimov <[email protected]> Signed-off-by: Marcel Holtmann <[email protected]> (cherry picked from commit bf0ddd1) Signed-off-by: Jonathan Maple <[email protected]>
My bluetooth fails with
bluetooth hci0: Direct firmware load for brcm/BCM4354A2-13d3-3485.hcd failed with error -2
The missing firmware file is not available here, so I assume it is correct to open a new issue for this.
The chip is installed in a Wortmann / terra mobile 360-11 netbook. Windows drivers can be downloaded from this page:
https://www.wortmann.de/de-de/systeminformation/R5105360.aspx
(in German; look for the item "Terra Mobile 360-11 Bluetooth Treiber")
However, there seems to be no .hex file, only some .bin files. Any hint on how to convert them to .hcd for use with linux (and for inclusion in this repository)?
The text was updated successfully, but these errors were encountered: