In /lib/firmware/brcm/ I currently have: -rw-r--r-- 1 root root 34700 Oct 24 2018 BCM20702A0-0a5c-21e8.hcd~ -rw-r--r-- 1 root root 34997 Dec 23 23:07 BCM20702A1-05ac-21e1.hcd -rw-r--r-- 1 root root 35042 Dec 23 23:07 BCM20702A1-0a5c-21e6.hcd -rw-r--r-- 1 root root 35934 Oct 24 2018 BCM20702A1-0a5c-21e8.hcd~ -rw-r--r-- 1 root root 35000 Dec 23 23:07 BCM20702A1-0b05-17cb.hcd -rw-r--r-- 1 root root 35127 Dec 23 23:07 BCM20702A1-0b05-17cf.hcd where the ones without the tilde are from package bcm20702a1-firmware . I use one of them, BCM20702A1-0b05-17cb.hcd, with an ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth dongle, and it works fine, excepting occasional weird interactions with an Android phone. I may want to get into that later. The other two are an attempt to provide firmware to a Broadcom Corp. BCM20702A0 Bluetooth 4.0 dongle. The A0 version is old; I don't remember where I got it; it may have come out of the box, but no matter, because there is no attempt made to load it, even when untilded. The A1 version comes from https://github.com/winterheart/broadcom-bt-firmware/ blob/master/brcm/BCM20702A1-0a5c-21e8.hcd . That one loads just fine, and disables the Bluetooth dongle as shown by: sgt:/lib/firmware/brcm # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:02:72:DA:29:9C ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:3380 acl:0 sco:0 events:410 errors:0 TX bytes:36343 acl:0 sco:0 commands:409 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT hci1: Type: Primary Bus: USB BD Address: 5C:F3:70:80:A0:29 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:263513266 acl:907311 sco:1675 events:233331 errors:0 TX bytes:50912616 acl:465265 sco:1671 commands:254 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'sgt.decathlon.org' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x15bb LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) and sgt:/lib/firmware/brcm # hciconfig hci0 up Can't init device hci0: Invalid request code (56) However, if I disable the firmware (with the tilde), then the dongle appears to work: sgt:/lib/firmware/brcm # hciconfig -a hci1: Type: Primary Bus: USB BD Address: 00:02:72:DA:29:9C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4018971 acl:17398 sco:0 events:6779 errors:0 TX bytes:1500425 acl:13379 sco:1 commands:55 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'sgt.decathlon.org' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:80:A0:29 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:4750 acl:54 sco:0 events:305 errors:0 TX bytes:37328 acl:60 sco:0 commands:238 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'sgt.decathlon.org #1' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x15bb LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) This is despite the message from the log: May 04 17:36:54 sgt.decathlon.org kernel: bluetooth hci1: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 So I guess my first burning question is, is firmware loading necessary to the operation of my bluetooth dongle, or is it only necessary if you want up-to- date firmware. :-) Some other questions revolve around whether the bluetooth stack (and KDE, which I typically use) are up to handling two dongles, since the unplugging of the Broadcom dongle seems to disrupt the operation of the ASUSTek dongle. But that's enough for now. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org