Hi, > I'm sorry if This is the wrong place to post this, but I wasn't sure which > of the fedora lists was appropriate. I just bought myself a bluetooth usb > adaptor, since i got some really nice bluetooth headphones for christmas. I > plugged it into my fedora box and all seemed to go well. The bluetooth icon > showed up, I connected to the headset and ... no sound. > > I've done the following troubleshooting steps. I checked dmesg, and the > error I got was, hci0: autoload firmware brcm/bcm20702a1.hcd failed with > error -2. So this bluetooth adaptor, which said nothing about this on the > box, has a broadcom chip in it. If the firmware couldn't be loaded, how > could the device function? Does the linux btbcm module not require it? I've Basically if the firmware can't load it won't operate, the "autoload firmware brcm/bcm20702a1.hcd failed" means it's can't find the firmware at that path in /lib/firmware/ Looking at the latest linux-firmware package it's not there, there was a similar bug recently [1]. The firmware we distribute is only the firmware from the upstream firmware repository with firmware that meets the redistribution requirements. > also checked pulseaudio's config to see if maybe the bluetooth modules > weren't loaded, but in /etc/pulse/daemon.conf I see ifexists > module-bluetooth-discover.so > load-module module-bluetooth-discover.so. Same for bluetooth-policy, and > bluetooth-device. I would be checking lower levels than audio, check to see if: 1) you can see the bluetooth HCI (local device) with "hciconfig" and check for strings "UP RUNNING" in the output and a BD Address that isn't all zeros 2) scan to see if you can see bluetooth devices (you might need to put your audio device into pairing mode) "hcitool scan" If neither of those return appropriate output there's no chance anything higher up will work > I've read up on this, and saw that I also need to load > module-bluez5-device.so, but attempting this with pacmd gets me module load > failed. So I'm stumped. Linux seems to support this device, or the bluetooth > icon in gnome wouldn't have appeared. It can connect to the headset, there's > just no sound. As long as you have the pulseaudio-module-bluetooth installed you should be fine, a default gnome workstation comes with all the bits out of the box > i've verified that the a2dp profile is set in gnome's sound settings. I'm > using fedora 23, completely up to date as of five minutes ago, with a reboot > to see if that helps. One quirk of this dongle is that it doesn't seem to > work until I unplug and replug. Until I do, the text in gnome's bluetooth > settings reads as, available as "bastian's computer and available for > bluetooth file transfers. Transferred files are placed in the downloads > folder". Once I plug the device in, it changes to "available as tigger and > available for bluetooth file transfers. Transferred files are placed in the > downloads folder" Is this a quirk of gnome or the device? > > I've done some research, and saw some posts on the linux kernel mailing list > where another person was having the same problem with a different device > with the same broadcom chip, a bcm20702a1, although it was a different vid > and pid. Support for all broadcom bluetooth usb chips was supposed to be in > kernel since kernel 3.2. I've already posted this to the manjaro mailing > lists, and was instructed by phil to download a firmware file from amazon > s3, place it in /lib/firmware/brcm, but it didn't help. I'm completely > stumped. Personally I only ever buy CSR usb bluetooth modules, you can get them on amazon for less than $10, just search for "bluetooth csr 4 dongle" to get a BT4 module Peter [1] https://bugzilla.redhat.com/show_bug.cgi?id=1275122 -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/desktop@xxxxxxxxxxxxxxxxxxxxxxx
