- #Broadcom bcm20702a0 driver install#
- #Broadcom bcm20702a0 driver zip file#
- #Broadcom bcm20702a0 driver drivers#
- #Broadcom bcm20702a0 driver driver#
- #Broadcom bcm20702a0 driver Patch#
#Broadcom bcm20702a0 driver driver#
To convert this firware to a format usable by the linux btusb driver you can use the hex2hcd tool. For all I know they're identical, but in this example we'd followed this best guess approach and it worked. if you're using AMD64 (a 64bit kernel) then use the Win64 version. Which tells us that for this particular hardware in my example, the firmware file we want is in the Win32/ or Win64/ directory and is called BCM20702A1_001.002. I don't offhand know that it matters, but I'd use the one that corresponds to your Debian OS version, i.e.
The output will look something like this. Hardware ids are 4 hex digits 0-F that represent the vendor and product in the format VEND:PROD since the driver will be for the vendor in question, you need only search for the PROD portion of the hardware ID. The 21e3 is the second half of the hardware id in the examples above which is the product id, you will need to replace that with your product id. The path above is what I've extracted the driver to in my example, /home/user/sp54245, you will replace that with where you've extracted your driver. name '*.inf' -type f -exec grep -A5 -i 21e3 - + | grep. inf files for the hardware id of your bluetooth with something like the following: cd /home/user/sp54245įind. inf files in the driver package and search them for your hardware id. In order to find the appropriate firmware file for your device you will need to locate the. You can then extract the files to a directory for example purposes I'll just call it /home/user/sp54245/
#Broadcom bcm20702a0 driver zip file#
You can open the file regardless if its an exe or zip file with engrampa or file-roller, KDE's ark will open zip files but as of this writing, in Debian 10 Buster, ark does not seem to be able to open exe files. I had to then click on a Choose a Different OS link, and select Windows 7 at which point it listed various driver categories, I expanded the Driver-Network category and selected Broadcom Bluetooth Software which then downloaded
#Broadcom bcm20702a0 driver drivers#
SKU Number: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240įor example purposes I am writing this wiki page after assisting a user with a HP Pavilion g6-1c60ca Notebook PC, and I went to HP's support website for laptops and typed in that model number in the search box and hit submit, and due to the fact that it auto detected I was on linux, it said no drivers found.
The output would look something like the following, I will edit out the unique identifiers: Getting SMBIOS data from sysfs.
#Broadcom bcm20702a0 driver install#
If that command is not installed you can install it with: pkexec apt install dmidecode If you do not know your system manufacturer or model number you can use the following command: pkexec dmidecode -t01 If you have it, copy it to your work directory and proceed at 'Converting the firmware' below. Mount your Window$ partition and do a 'find' on the filename, relacing the '.hcd' tag with '.hex'. You can obtain this by visiting the manufacturer's website and looking up your model number.īUT: Before getting wrapped around the axle getting the file from the manufacturer's website, if you are dual-booting a Window$ system, you may already have the. The complicated part of this is obtaining the firmware from a Windows(tm) driver package and converting it, you will first need a driver package for your card from your computer or hardware manufacturer which will likely come in the form of a windows executable file. You will need this filename such as brcm/BCM20702A1-0a5c-21e6.hcd.
#Broadcom bcm20702a0 driver Patch#
You can typically find the name of the missing firmware file by reading the kernel error message with one of the following commands: pkexec dmesg | grep -i bluetoothĪnd you will see an error message with the filename, for example: bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21e6.hcd (-2)īluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2īluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not found You will need this identifier such as 0a5c:21e6, shown above. See this wiki entry for more information on identifying USB devices.
Or Bus 004 Device 006: ID 0a5c:21e3 Broadcom Corp. Your Bluetooth card will likely be on the USB bus, for example: Bus 003 Device 016: ID 0a5c:21e6 Broadcom Corp. Your bluetooth adapter, while on the same card as your wifi will have a seperate hardware ID. You will need to identify both your Hardware ID and the name of the missing Firmware file.