Bug#801084: bluez-firmware: Please include firmware for Broadcom Corp. BCM20702 Bluetooth 4.0

2021-03-07 Thread Gabriel Corona
Hi,

This is still an issue.

It works after manually copying the firmware found in [1]. However, the
README of this repository warns that those firmwares might have
vulnerabilities (such as CVE-2018-5383, CVE-2019-9506, CVE-2020-10135):
including them in Debian non-free, may not be a great idea.

[1] https://github.com/winterheart/broadcom-bt-firmware/tree/master/brcm

Gabriel



Bug#801084: bluez-firmware: Please include firmware for Broadcom Corp. BCM20702 Bluetooth 4.0

2019-07-14 Thread Malvin Gattinger
Hi,

after upgrading from stretch to buster with bluez-firmware 1.2-4 the
card stopped working for me, asking for brcm/BCM20702A0-0a5c-21e6.hcd.

After copying
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-0a5c-21e6.hcd
to /lib/firmware/brcm and shutting down it now works again.

~ $ sudo dmidecode -s bios-version; sudo dmidecode -s bios-release-date
8DET76WW (1.46 )
06/21/2018
~ $ lsusb | grep Blue
Bus 001 Device 005: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0
[ThinkPad]
~ $ uname -a
Linux hostname 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19)
x86_64 GNU/Linux

(This is a ThinkPad x220 where I replaced the bluetooth module.)

@nicoo: Do you maybe still have other firmware files lying around that
make it work?

best,
Malvin


On Wed, 2 Jan 2019 22:30:55 +0100 Nicolas Braud-Santoni
 wrote:
> Control: fixed -1 1.2-4
> Control: tag -1 + stretch
> 
> Hi,
> 
> The exact same controller works on Buster, with bluez-firmware/1.2-4,
> so I am marking it as fixed there.
> 
> 
> Best,
> 
>   nicoo



Bug#801084: bluez-firmware: Please include firmware for Broadcom Corp. BCM20702 Bluetooth 4.0

2019-01-02 Thread Nicolas Braud-Santoni
Control: fixed -1 1.2-4
Control: tag -1 + stretch

Hi,

The exact same controller works on Buster, with bluez-firmware/1.2-4,
so I am marking it as fixed there.


Best,

  nicoo


signature.asc
Description: PGP signature


Bug#801084: bluez-firmware: Please include firmware for Broadcom Corp. BCM20702 Bluetooth 4.0

2015-10-05 Thread Fabian Greffrath
Package: bluez-firmware
Version: 1.2-3
Severity: important

Hi there,

I have spent yesterday evening with trying to get my Bluetooth
working. After several attempts (e.g. adding my uid to the "lp" group,
because I got "DBusFailedError: No such file or directory" errors from
blueman) I found the following in my 'dmesg' output:

bluetooth hci0: Direct firmware load for brcm/BCM20702A0-0a5c-21e6.hcd
failed with error -2

Apparently, this file is missing for a proper operation of the
Bluetooth dongle on my system. However, it is not available in any
firmware package in Debian. Thus, I am asking you to add it to the
bluez-firmware package which I find most appropriate for this.

Having searched the web for this file name, I found the following site
with instructions on how to download and install it:

http://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux

Once I followed the instructions on this site, I could connect all my
Bluetooth devices to my laptop.

Some additional information:

I am using a Lenovo ThinkPad T430.

# dmidecode -s bios-version; dmidecode -s bios-release-date
G1ETA6WW (2.66 )
08/19/2014

$ lsusb | grep Blue
Bus 003 Device 007: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0
[ThinkPad]

$ uname -a
Linux kff50 4.2.0-1-amd64 #1 SMP Debian 4.2.1-2 (2015-09-27) x86_64
GNU/Linux

Please tell me if you think a different package (e.g.
firmware-linux-nonfree, CC:ed) is better suited to hold this firmware,
I will then re-assign this bug there.

Thanks!

 - Fabian

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information