Bluetooth
Bluetooth... seems
to be a nightmare on most of the Linux's. You can get it installed and
paired, but then it won't connect. Seems to be a lot of trouble with Pulseaudio and Broadcom.
But then I find this and the 'real' reason:
ArchWiki - Bluetooth
Well, shoot, put in the jump without stating what to look for!! Even I had to study it for a while. Anywho, the jump
to Arch Linux is to tell you about the "Dual Boot" multiple system problem. It seems that some devices can not handle
multiple pairings.
My HP700-530 .
Well, that ain't all. I have had one hell of a time getting this Bluetooth
headset set up. It really shouldn't be that hard -but- we have the problem of people NOT wanting to share again. And some for
the very valid reason that people screw up what they share. Right now, 27 Jun 2017/2:17am, I have my Bluetooth
headset working. Who knows what will happen the next time I turn it on -or- shutdown my system and fire it back up. Another reason
for running the 'puter 24/7... -AND NOT- UpDating!!!
September 23rd, 2017/9:58am
Well, sports fans, we Re-Installed the system... again!
Broadcom WIDCOMM® Bluetooth devices
Bluetooth not Detecting devices and can't be detected
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-0a5c-216c.hcd
Place required .hcd file to /lib/firmware/brcm. After inserting Broadcom Bluetooth device you will see that firmware successfully loaded:
Initial search: openSuSE broadcom BCM43142 Bluetooth
Later search: BCM43142A0*.hcd 14e4:4365
Re: Bluetooth not Detecting devices and cant be detected
OK, an easy one
Code:wget https://www.dropbox.com/s/r6q9zt59darq80n/BCM43142A0-0a5c-216c.hcdCode:sudo cp BCM43142A0-0a5c-216c.hcd /lib/firmware/brcm/BCM43142A0-0a5c-216c.hcdCode:sudo modprobe -r btusbAnd it should workCode:sudo modprobe btusb
May 31st, 2017/4:50am -- thru June xx, 2017 Well, it broke... sorta. Got some
"UpDates" to SuSE -and- my new Bluetooth
quit working!! So far I have not found a combo that will work. I am going to try to "Un-Install" all of the Bluetooth
code and maybe even some of the Broadcom code.... and then Re-Install it.
Annnddd... this is where I blew it... in conjunction with the fact that somehow, someway... the Windows 10
section of my "Dual Boot" got its Bluetooth
enabled and turned back on!!
In order to auto-connect a2dp for some devices, add this to /etc/pulse/default.pa:
load-module module-switch-on-connect
Refer: https://wiki.debian.org/BluetoothUser/a2dp
Also check out: /etc/dbus-1/system.d/bluetooth.conf
Arch Bluetooth Keyboard and
Arch Bluetooth and
Arch Bluetooth Headset
broadcom_wireless and
bluetooth-broadcom-43142-isnt-working
-- Headset: 30:CB:F8:04:7C:FD -- Controler: 60:6D:C7:CF:6F:C6
... some helpful commands
Both ALSA and PulseAudio come with command line appliciations to print out the state of our sound system.
- PulseAudio:
pactl list - systemctl status pulseaudio.service
- systemctl --user enable pulseaudio && systemctl --user start pulseaudio
- ALSA:
aplay -l
lspci -nv
00:1b.0 0403: 8086:8ca0
Subsystem: 103c:2b36
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at f7f10000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
---------------------------------------
00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0]
Subsystem: Hewlett-Packard Company Device [103c:2b36]
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7f10000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
---------------------------------------
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] [1002:aab0]
Subsystem: Pegatron Device [1b0a:aab0]
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at f7e60000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
---------------------------------------
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Hewlett-Packard Company Device [103c:2b36]
Flags: bus master, fast devsel, latency 0, IRQ 30
I/O ports at d000 [size=256]
Memory at f7d00000 (64-bit, non-prefetchable) [size=4K]
Memory at f0000000 (64-bit, prefetchable) [size=16K]
Capabilities:
Kernel driver in use: r8169
Kernel modules: r8169
---------------------------------------
04:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:2230]
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f7c00000 (64-bit, non-prefetchable) [size=32K]
Capabilities:
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma
lspci -vmm
Slot: 00:1b.0 Class: Audio device Vendor: Intel Corporation Device: 9 Series Chipset Family HD Audio Controller SVendor: Hewlett-Packard Company SDevice: Device 2b36 --------------------------------------- Slot: 01:00.1 Class: Audio device Vendor: Advanced Micro Devices, Inc. [AMD/ATI] Device: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] SVendor: Pegatron SDevice: Device aab0 --------------------------------------- Slot: 03:00.0 Class: Ethernet controller Vendor: Realtek Semiconductor Co., Ltd. Device: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller SVendor: Hewlett-Packard Company SDevice: Device 2b36 Rev: 0c --------------------------------------- Slot: 04:00.0 Class: Network controller Vendor: Broadcom Corporation Device: BCM43142 802.11b/g/n SVendor: Hewlett-Packard Company SDevice: Device 2230 Rev: 01
lsusb
Bus 003 Device 008: ID 0a5c:216c Broadcom Corp.usb-devices
T: Bus=03 Lev=01 Prnt=01 Port=11 Cnt=02 Dev#= 8 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=216c Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM43142A0 S: SerialNumber=606DC7CF6FC6 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=btusb I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)bluetoothctl
[bluetooth]# help Available commands: list List available controllers show [ctrl] Controller information select <ctrl> Select default controller devices List available devices paired-devices List paired devices power <on/off> Set controller power pairable <on/off> Set controller pairable mode discoverable <on/off> Set controller discoverable mode agent <on/off/capability> Enable/disable agent with given capability default-agent Set agent as the default one set-scan-filter-uuids [uuid1 uuid2 ...] Set scan filter uuids set-scan-filter-rssi [rssi] Set scan filter rssi, and clears pathloss set-scan-filter-pathloss [pathloss] Set scan filter pathloss, and clears rssi set-scan-filter-transport [transport] Set scan filter transport set-scan-filter-clear Clears discovery filter. scan <on/off> Scan for devices info [dev] Device information pair [dev] Pair with device trust [dev] Trust device untrust [dev] Untrust device block [dev] Block device unblock [dev] Unblock device remove <dev> Remove device connect <dev> Connect device disconnect [dev] Disconnect device list-attributes [dev] List attributes select-attribute <attribute> Select attribute attribute-info [attribute] Select attribute read Read attribute value write <data=[xx xx ...]> Write attribute value notify <on/off> Notify attribute value register-profile <UUID ...> Register profile to connect unregister-profile Unregister profile version Display version quit Quit program
- b43-fwcutter
- b43legacy-firmware
- bcm43xx-firmware
- pullin-bcm43xx-firmware
- bluedevil5
- bluez
- bluez-test
- kde3-kdebluetooth
- kde3-kdebluetooth-lang
- libbluetooth3
- libsbc1
- sbc
May 31st, 2017/5:15am Allllllrighty now... I have removed the above items... plus! A number of them said 'that they had to remove others'. Now I seem to remember having to include 'others' when this stuff was first installed. We'll try using the system before trying to re-load/re-install all this. See what I broke by just blindly removing stuff. What the heck, gota learn somehow and almost everyone is having the same problems I am. Reminds me of the 'old' days when I had all the troubles with my "hardware compatibility" and VMware and SuSE.
Before removal.... Dakotah-i7:/home/ctaylor # zypper se -si kernel broadcom Retrieving repository 'KDEextra' metadata ................................................................................................[done] Building repository 'KDEextra' cache .....................................................................................................[done] Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------------------+---------+-----------------+--------+------------------- i | devel_kernel | pattern | 20150918-25.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-default | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-default-devel | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-devel | package | 4.1.38-50.1 | noarch | (System Packages) i | kernel-devel | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-docs | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-firmware | package | 20160516git-3.1 | noarch | openSUSE:Leap:42.2 i | kernel-macros | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-source | package | 4.1.38-50.1 | noarch | (System Packages) i | kernel-source | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-syms | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | patterns-openSUSE-devel_kernel | package | 20150918-25.1 | x86_64 | openSUSE:Leap:42.2 After removal but before a re-boot... Dakotah-i7:/home/ctaylor # zypper se -si kernel broadcom Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------------------+---------+-----------------+--------+------------------- i | devel_kernel | pattern | 20150918-25.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-default | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-default-devel | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | kernel-devel | package | 4.1.38-50.1 | noarch | (System Packages) i | kernel-devel | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-docs | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-firmware | package | 20160516git-3.1 | noarch | openSUSE:Leap:42.2 i | kernel-macros | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-source | package | 4.1.38-50.1 | noarch | (System Packages) i | kernel-source | package | 4.4.27-2.1 | noarch | openSUSE:Leap:42.2 i | kernel-syms | package | 4.4.27-2.1 | x86_64 | openSUSE:Leap:42.2 i | patterns-openSUSE-devel_kernel | package | 20150918-25.1 | x86_64 | openSUSE:Leap:42.2 Dakotah-i7:/home/ctaylor #
Now then, I tried to use the on/off in the status bar so that I could select Re-Boot and it would NOT WORK!! I'm gona walk my dog.
June 26th, 2017 Almost a month later... I have been recovering my system. I totally destroyed the Linux System trying to get the Bluetooth to work. Then fought terribly trying to get it to work in the newly setup and installed Linux System. After installing everything in the world for Bluetooth on my system I re-booted into Windows 10 and went into the Control Panel and totally disabled Bluetooth. Upon re-booting into my Linux System it showed the Bluetooth Symbol in the task bar. However, I still could not hear anything in the headset -even though- it said it was connected!! Must be something with Pulse Audio. It was the first time I got it to work. Had to turn off the main sound to get the headset and then turn off the headset to get the main sound. Don't remember all the details and that is why it is NOT working!!
Comments...
