(base) tom@mydesktop: ~ $ sudo zypper se wire
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-----------------------------------------+--------------------------------------------------------------------------+-----------
| connman-plugin-wireguard | WireGuard plugin for connman | package
| cyreal-wire-fonts | Wire Font | package
| dracut-wireless | Wireless network support for dracut initrd | package
i+ | gstreamer-plugin-pipewire | Gstreamer Plugin for PipeWire | package
| gstreamer-plugin-pipewire-debuginfo | Debug information for package gstreamer-plugin-pipewire | package
| kpipewire-devel | Development files for kpipewire | package
| kpipewire-imports | QtQuick bindings for kpipewire | package
i | libKPipeWire5 | PipeWire integration for KDE Plasma - main library | package
i | libKPipeWire5-lang | Translations for package kpipewire | package
| libKPipeWireDmaBuf5 | PipeWire integration for KDE Plasma - DMA-BUF support | package
| libKPipeWireRecord5 | PipeWire integration for KDE Plasma - recording support | package
i | libpipewire-0_3-0 | A Multimedia Framework designed to be an audio and video server and more | package
i | libpipewire-0_3-0-32bit | A Multimedia Framework designed to be an audio and video server and more | package
| libpipewire-0_3-0-debuginfo | Debug information for package libpipewire-0_3-0 | package
i+ | libwireplumber-0_5-0 | Session / policy manager implementation for PipeWire | package
| libwireshark15 | Network packet dissection library | package
| libwireshark17 | Network packet dissection library | package
| libwiretap12 | Wireshark library for tapping | package
| libwiretap14 | Wireshark library for tapping | package
i+ | pipewire | A Multimedia Framework designed to be an audio and video server and more | package
| pipewire | A Multimedia Framework designed to be an audio and video server and more | srcpackage
i+ | pipewire-alsa | PipeWire media server ALSA support | package
| pipewire-alsa-32bit | PipeWire media server ALSA support | package
| pipewire-alsa-debuginfo | Debug information for package pipewire-alsa | package
| pipewire-debuginfo | Debug information for package pipewire | package
| pipewire-debugsource | Debug sources for package pipewire | package
| pipewire-devel | Development Files For PipeWire, A Multimedia Framework | package
| pipewire-doc | PipeWire media server documentation | package
i+ | pipewire-jack | PipeWire JACK implementation | package
i | pipewire-lang | Translations for package pipewire | package
i+ | pipewire-libjack-0_3 | PipeWire libjack replacement libraries | package
| pipewire-libjack-0_3-32bit | PipeWire libjack replacement libraries | package
| pipewire-libjack-0_3-debuginfo | Debug information for package pipewire-libjack-0_3 | package
| pipewire-libjack-0_3-devel | Development files for pipewire-libjack-0_3 | package
| pipewire-module-x11-0_3 | X11 support For PipeWire, A Multimedia Framework | package
| pipewire-module-x11-0_3-debuginfo | Debug information for package pipewire-module-x11-0_3 | package
| pipewire-module-xrdp | Enable xrdp to generate sound with pipewire | package
i+ | pipewire-modules-0_3 | Modules For PipeWire, A Multimedia Framework | package
i+ | pipewire-modules-0_3-32bit | Modules For PipeWire, A Multimedia Framework | package
| pipewire-modules-0_3-debuginfo | Debug information for package pipewire-modules-0_3 | package
i | pipewire-pulseaudio | PipeWire PulseAudio implementation | package
| pipewire-pulseaudio-debuginfo | Debug information for package pipewire-pulseaudio | package
i | pipewire-spa-plugins-0_2 | Plugins For PipeWire SPA | package
i | pipewire-spa-plugins-0_2-32bit | Plugins For PipeWire SPA | package
| pipewire-spa-plugins-0_2-debuginfo | Debug information for package pipewire-spa-plugins-0_2 | package
| pipewire-spa-plugins-0_2-jack | SPA Plugin to use PipeWire as jack client | package
| pipewire-spa-plugins-0_2-jack-debuginfo | Debug information for package pipewire-spa-plugins-0_2-jack | package
i | pipewire-spa-tools | The PipeWire SPA Tools | package
| pipewire-spa-tools-debuginfo | Debug information for package pipewire-spa-tools | package
i+ | pipewire-tools | The PipeWire Tools | package
| pipewire-tools-debuginfo | Debug information for package pipewire-tools | package
| qemu-audio-pipewire | Pipewire based audio support for QEMU | package
| tripwire | A tool to observe the filesystem | package
| wire | Compile-time Dependency Injection for Go | package
| wire | Compile-time Dependency Injection for Go | srcpackage
| wireguard-tools | WireGuard userspace tools | package
i | wireless-regdb | 802.11 regulatory domain database | package
i | wireless-tools | Tools for a wireless LAN | package
i | wireplumber | Session / policy manager implementation for PipeWire | package
i | wireplumber-audio | Enable audio support in PipeWire / WirePlumber | package
| wireplumber-devel | Session / policy manager implementation for PipeWire | package
| wireplumber-doc | Wireplumber Session / policy manager documentation | package
i | wireplumber-lang | Translations for package wireplumber | package
i | wireplumber-zsh-completion | Wireplumber zsh completion | package
| wireshark | A Network Traffic Analyser | package
| wireshark | A Network Traffic Analyser | srcpackage
| wireshark-devel | A Network Traffic Analyser | package
| wireshark-plugin-libvirt | Wireshark plugin for libvirt RPC protocol | package
| wireshark-ui-qt | A Network Traffic Analyser - Qt UI | package
| wireviz | A tool for documenting cables and wiring harnesses | package
| wireviz | A tool for documenting cables and wiring harnesses | srcpackage
| wireviz-doc | Documentation files for wireviz | package
(base) tom@mydesktop: ~ $
Bluemon connection of the bluetooth headphones terminated with message:
“br-connection unknown”
Please show the results from
zypper se -si pipewire
I want to understand if the pipewire packages are from packman or the update-sle repo. (I’m really not sure if that would impact here or not though.)
From what I can read, the firmware simply is not functioning for the OP:
Recall:
[ 20.779110] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1714
[ 20.825877] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 20.825883] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-180a.hcd'
[ 20.825886] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-180a.hcd'
I appreciate the OP posted “Note also: zypper shows BCM20702A1 firmware is installed.” but regardless, the dmesg says what it says. I suspect there is an issue there with the firmware. Else why would that dmesg appear?
I tend to agree with deano_ferrai’s approach.
But I can not tell if the OP followed any of his firmware suggestions there.
Was the dmesg ever run again to see if the “Bluetooth: hci0: BCM: firmware Patch file not found” error message continued?
.
Exactly what firmware is in place now? Did I miss that confirmation after following deano_ferrai’s suggestions?
1 Like
FWIW, I have had this happen when another nearby device (eg my mobile phone) was already paired with my headphones or earbuds.
If you run bluetoothctlin a terminal, can you then find your device using
scan on?
More info:
https://wiki.archlinux.org/title/Bluetooth#Pairing
Assuming you can pair to the device ok, hwat is then reported by the infocommand?
For BT headphones, I’d expect to see something like this in the output…
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
@oldcpu If you read the other thread, we did identify that the firmware error was a red herring and the device actually worked, bluetoothctl identified other bluetooth devices etc…
OP, has onboard bluetooth adapter, a low power bluetooth (bolt) adapter and a unifying receiver now to connect the mouse…
I did run test to see if headphones are ok and connect to android phone. They worked fine and I disabled bluetooth in the phone to avoid any conflicts.
bluetoothctl scan on for discovery of headphones results are below. The 5C:EB:68:99:C5:7F is the headphones and they are found twice. Perhaps that is a clue to something. Note bluetoothctl after starting puts cursorvat start of prompt not at end so you write over te prompt when adding command.
Agent registeredct to bluetoothd...
scan onoth]#
SetDiscoveryFilter success
Discovery started
[CHG] Controller 80:A5:89:16:E1:8E Discovering: yes
[NEW] Device 43:90:D7:D7:B4:C1 43-90-D7-D7-B4-C1
[NEW] Device 42:0C:4D:BB:7D:1B 42-0C-4D-BB-7D-1B
[CHG] Device 5C:EB:68:99:C5:7F RSSI: 0xffffffc3 (-61)
[CHG] Device 5C:EB:68:99:C5:7F TxPower: 0x0000 (0)
[NEW] Device F8:04:2E:6B:6A:43 [TV] UN50JU6500
[CHG] Device F8:04:2E:6B:6A:43 AddressType: public
[NEW] Device 67:C5:B2:28:71:24 67-C5-B2-28-71-24
[DEL] Device 43:90:D7:D7:B4:C1 43-90-D7-D7-B4-C1
[NEW] Device 43:90:D7:D7:B4:C1 43-90-D7-D7-B4-C1
[DEL] Device 67:C5:B2:28:71:24 67-C5-B2-28-71-24
[bluetooth]#
Live in assisted living so there are lots of other signals around
I tried again to start headphones. blueman gave a new message that "connection failed: br-connection-aborted-by-remote
Again blumon said connected for a period. Also headphones were not shown in pavucontrol “outputs” or “configuration”.
When they were working the headphones were shown there.
Is it critical to keep wired headphones disconnected during this investigation? Do I need to logout or reboot after disconnecting wired headphones to make any tests on bluetooth headphones?
thanks, tom kosvic
The plot thickens.
With new usb bluetooth dongle, there is still no sound in bluetooth headphones. bluetooth is disabled in bios and system rebooted. bluemon shows headphones as paired/connected but this time has 4 connection bars instead of three. pavucontrol does not show headphones in “output” or “configuration”.
Basically no change switching from mb bluetooth to usb dongle bluetooth. I believe new dongle is bus 3 device 2 below. Sound is working using wired headphones.
(base) tom@mydesktop: ~ $ lsusb
Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 03f0:ad2a HP, Inc HP ColorLaserJet MFP M278-M281
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:800a Intel Corp. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 004: ID 1058:25ed Western Digital Technologies, Inc. My Book 25ED
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 007: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 003 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 002: ID 0bda:a728 Realtek Semiconductor Corp. Bluetooth 5.4 Radio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(base) tom@mydesktop: ~ $
I’m not surprised about this. The issue seems to be more with the audio stack. I wanted you to try connecting with bluetoothctl as I already described here.
A thought. Could bluetooth be sending a pairing confirmation request that I am not seeing and responding to? How would I enable those?
That’s what the symptoms seem like.
Also, please show me the results from the command I gave in post #23.
Sorry but I do believe I sent this once before.
(base) tom@mydesktop: ~ $ sudo zypper se -si pipewire
[sudo] password for root:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------------+---------+--------------------------------------+--------+-----------------------
i+ | gstreamer-plugin-pipewire | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | gstreamer-plugin-pipewire | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i | libKPipeWire5 | package | 5.27.11-bp156.1.2 | x86_64 | oss(15.6)
i | libKPipeWire5-lang | package | 5.27.11-bp156.1.2 | noarch | oss(15.6)
i | libpipewire-0_3-0 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i | libpipewire-0_3-0 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i | libpipewire-0_3-0-32bit | package | 1.0.5+git36.60deeb2-150600.3.6.2 | x86_64 | sle-updates-leap(15.6)
i+ | pipewire | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i+ | pipewire-alsa | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire-alsa | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i+ | pipewire-jack | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire-jack | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i | pipewire-lang | package | 1.0.5+git36.60deeb2-150600.3.6.2 | noarch | sle-updates-leap(15.6)
i+ | pipewire-libjack-0_3 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire-libjack-0_3 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i+ | pipewire-modules-0_3 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire-modules-0_3 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i+ | pipewire-modules-0_3-32bit | package | 1.0.5+git36.60deeb2-150600.3.6.2 | x86_64 | sle-updates-leap(15.6)
i | pipewire-pulseaudio | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i | pipewire-pulseaudio | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i | pipewire-spa-plugins-0_2 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i | pipewire-spa-plugins-0_2 | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i | pipewire-spa-plugins-0_2-32bit | package | 1.0.5+git36.60deeb2-150600.3.6.2 | x86_64 | sle-updates-leap(15.6)
i | pipewire-spa-tools | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i | pipewire-spa-tools | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
i+ | pipewire-tools | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | Packman
i+ | pipewire-tools | package | 1.0.5+git36.60deeb2-150600.3.10.pm.1 | x86_64 | packman
(base) tom@mydesktop: ~ $
(base) tom@mydesktop: ~ $ bluetoothctl
Agent registered100to bluetoothd...
scan onGW100]#
SetDiscoveryFilter success
Discovery started
[CHG] Controller 8C:68:8B:C1:DB:B2 Discovering: yes
[NEW] Device D4:8D:26:B0:68:41 [LG] webOS TV OLED55G4SUB
connectGW100]#
Missing dev argument
info
Device 5C:EB:68:99:C5:7F (public)
Name: Grado GW100
Alias: Grado GW100
Class: 0x00240418 (2360344)
Icon: audio-headphones
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000ApFFFFdFFFF
Battery Percentage: 0x64 (100)
[Grado GW100]#
No you shared the results from sudo zypper se wire, which did not show the version and repo details. Anyway, this confirms that the pipewire packages came from packman.
They started working. After the bluetoothctl commands.
Not quite sure how to keep them going but it seems that bluetoothctl “scan on” turned them on. I am sure I did this at prior times and they didn’t work.
Any advice for maintaining operation?
The bluetoothctl output (for the connected device) reports `
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
which at least shows it is recognized as an audio device.
I’m glad that using bluetoothctl worked as suggested. It gives good visibility of the connection process and observe the reported UUIDs (to confirm how the device is seen).
Back away slowly. 
I have to admit the bluetooth 5.4 on the new dongle has doubled the range from bluetooth 4 on the motherboard. I can now go outside and still be connected.
Now I just have to keep 'em running.
thanks all, tom kosvivc