Hi,
I am trying to connect my JBL Charge 6 to my three-year-old laptop (ThinkPad X13).
When I try to connect it, it shows: br-connection-unknown.
I have also tried connecting it via CLI, but I get the same result.
It connects on every other distro and desktop environment, so I assume the problem is related to firmware or something similar.
I am asking for your help, please.
yarl@linux:~> lsusb | grep -i bluetooth
Bus 003 Device 004: ID 8087:0033 Intel Corp. AX211 Bluetooth
yarl@linux:~> dmesg | grep -i firmware
dmesg: Lesen des Kernelpuffers ist fehlgeschlagen: Die Operation ist nicht erlaubt
yarl@linux:~> sudo dmesg | grep -i firmware
[sudo] Passwort für yarl:
[ 0.283478] [ T1] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 1.940128] [ T76] psmouse serio1: trackpoint: Elan TrackPoint firmware: 0xa1, buttons: 3/3
[ 1.994247] [ T1] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 3.801036] [ T292] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[ 3.840580] [ T556] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.44.1
[ 3.840603] [ T556] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 22.190027] [ T1] systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
[ 22.987500] [ T112] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 23.213703] [ T58] iwlwifi 0000:00:14.3: loaded firmware version 89.af655058.0 so-a0-gf-a0-89.ucode op_mode iwlmvm
[ 23.609068] [ T196] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 23.639438] [ T196] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 23.639448] [ T196] Bluetooth: hci0: Firmware Version: 133-20.25
[ 24.218832] [ T292] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[ 24.218835] [ T292] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware file: intel/sof/sof-adl.ri
[ 24.219527] [ T292] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 24.219529] [ T292] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:1
[ 24.336058] [ T1429] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 24.336062] [ T1429] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:1
[ 25.131823] [ T196] Bluetooth: hci0: Waiting for firmware download to complete
[ 25.132030] [ T196] Bluetooth: hci0: Firmware loaded in 1457605 usecs
[ 25.156178] [ T196] Bluetooth: hci0: Firmware timestamp 2025.20 buildtype 1 build 82053
[ 25.156186] [ T196] Bluetooth: hci0: Firmware SHA1: 0x937bca4a
[ 26.836653] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 26.838790] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 26.839288] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.502955] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.508155] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.508366] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.508572] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.508587] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.819058] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.823229] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.823403] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.823566] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.823579] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.866517] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.869237] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.869382] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.869522] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
[ 32.869533] [ T1532] PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
yarl@linux:~> sudo dmesg | grep -i bluetooth
[ 22.962531] [ T1211] Bluetooth: Core ver 2.22
[ 22.962559] [ T1211] NET: Registered PF_BLUETOOTH protocol family
[ 22.962560] [ T1211] Bluetooth: HCI device and connection manager initialized
[ 22.962564] [ T1211] Bluetooth: HCI socket layer initialized
[ 22.962566] [ T1211] Bluetooth: L2CAP socket layer initialized
[ 22.962567] [ T1211] Bluetooth: SCO socket layer initialized
[ 23.262636] [ T1229] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 23.609062] [ T196] Bluetooth: hci0: Device revision is 0
[ 23.609065] [ T196] Bluetooth: hci0: Secure boot is enabled
[ 23.609066] [ T196] Bluetooth: hci0: OTP lock is enabled
[ 23.609067] [ T196] Bluetooth: hci0: API lock is enabled
[ 23.609067] [ T196] Bluetooth: hci0: Debug lock is disabled
[ 23.609068] [ T196] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 23.609070] [ T196] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 23.609805] [ T196] Bluetooth: hci0: DSM reset method type: 0x00
[ 23.639438] [ T196] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 23.639447] [ T196] Bluetooth: hci0: Boot Address: 0x100800
[ 23.639448] [ T196] Bluetooth: hci0: Firmware Version: 133-20.25
[ 24.603997] [ T1584] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 24.603999] [ T1584] Bluetooth: BNEP filters: protocol multicast
[ 24.604002] [ T1584] Bluetooth: BNEP socket layer initialized
[ 25.131823] [ T196] Bluetooth: hci0: Waiting for firmware download to complete
[ 25.132030] [ T196] Bluetooth: hci0: Firmware loaded in 1457605 usecs
[ 25.132198] [ T196] Bluetooth: hci0: Waiting for device to boot
[ 25.148042] [ T196] Bluetooth: hci0: Device booted in 15601 usecs
[ 25.150959] [ T196] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[ 25.153187] [ T196] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 25.156178] [ T196] Bluetooth: hci0: Firmware timestamp 2025.20 buildtype 1 build 82053
[ 25.156186] [ T196] Bluetooth: hci0: Firmware SHA1: 0x937bca4a
[ 25.160238] [ T196] Bluetooth: hci0: Fseq status: Success (0x00)
[ 25.160249] [ T196] Bluetooth: hci0: Fseq executed: 00.00.02.41
[ 25.160253] [ T196] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[ 25.230301] [ T1500] Bluetooth: MGMT ver 1.23
[ 32.274364] [ T2231] Bluetooth: RFCOMM TTY layer initialized
[ 32.274376] [ T2231] Bluetooth: RFCOMM socket layer initialized
[ 32.274380] [ T2231] Bluetooth: RFCOMM ver 1.11
yarl@linux:~> sudo bluetoothctl -v
bluetoothctl: 5.79
yarl@linux:~> sudo pactl info | grep "Server Name"
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
yarl@linux:~> pactl info | grep "Server Name"
Server Name: PulseAudio (on PipeWire 1.4.6)
yarl@linux:~> uname -r
6.12.0-160000.25-default
yarl@linux:~>
To start with, please check that the requisite services are active. Run as user in a terminal… systemctl --user status pipewire pipewire-pulse wireplumber
If the JBL speakers are paired, then they should be enumerated… pactl list cards short
Can you manually connect (using bluetoothctl)?
bluetoothctl
scan on
pair <MAC>
trust <MAC>
connect <MAC>
Just to clarify, this does not mean that the device failed to pair, the device is likely connected at the kernel level, but the profile might not be right.
If connected, examine how it is seen… pactl list short sinks
Thank you very much for helping me.
I have tried many workarounds from different forums, the Arch Linux Wiki, Ubuntu forums, and many other places, but without any success.
When I log in to my laptop, my system remembers my speaker and can see it, but it does not connect.
When I run these commands in the CLI, I get:
yarl@linux:~> systemctl --user status pipewire pipewire-pulse wireplumber
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
Active: active (running) since Mon 2026-02-23 17:23:42 CET; 53s ago
Invocation: fe0e5d94463149aab204ac7e700de497
TriggeredBy: ● pipewire.socket
Main PID: 2223 (pipewire)
Tasks: 3 (limit: 37990)
CPU: 45ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2223 /usr/bin/pipewire
Feb 23 17:23:42 linux.fritz.box systemd[2089]: Started PipeWire Multimedia Service.
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
Active: active (running) since Mon 2026-02-23 17:23:43 CET; 53s ago
Invocation: 236b7fbfd32c46499916788f8e2a26de
TriggeredBy: ● pipewire-pulse.socket
Main PID: 2332 (pipewire-pulse)
Tasks: 3 (limit: 37990)
CPU: 32ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─2332 /usr/bin/pipewire-pulse
Feb 23 17:23:43 linux.fritz.box systemd[2089]: Started PipeWire PulseAudio.
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Mon 2026-02-23 17:23:42 CET; 53s ago
Invocation: 003302eaed41423dbf128f4571c68295
Main PID: 2224 (wireplumber)
Tasks: 7 (limit: 37990)
CPU: 168ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2224 /usr/bin/wireplumber -p main
Feb 23 17:23:42 linux.fritz.box systemd[2089]: Started Multimedia Service Session Manager.
Feb 23 17:23:43 linux.fritz.box wireplumber[2224]: [0:00:37.096636482] [2224] WARN IPAManager ipa_manager.cpp:148 No IPA found in '/usr/lib64/libcamera/ipa'
Feb 23 17:23:43 linux.fritz.box wireplumber[2224]: [0:00:37.096657895] [2224] INFO Camera camera_manager.cpp:326 libcamera v0.5.1
yarl@linux:~> pactl list cards short
42 alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic alsa
yarl@linux:~> pactl list short sinks
55 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI3__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED
56 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI2__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED
57 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__HDMI1__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED
58 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink PipeWire s32le 2ch 48000Hz SUSPENDED
yarl@linux:~>
Then I reset my speaker (removed its connection history) and removed its configuration from KDE Bluetooth settings. I also tried to connect to it via the CLI.
So it initially pairs ok, but then fails… Failed to connect: org.bluez.Error.Failed br-connection-create-socket
Previously a different error… Failed to connect: org.bluez.Error.Failed br-connection-unknown
This error means, the Bluetooth link is established at the device level, but the OS cannot open the socket needed for streaming audio (A2DP/HF audio profile).
Try observing the user journal logging while connecting in another terminal… journalctl --user -u wireplumber -f
That might provide further details. A likely regression at play.
Another thing to try: Create another user (use Cockpit for this if not comfortable with terminal commands), login as that user, and test there.
After that, I created another user, then changed the user and tried to connect the speaker, but got the same result.
It’s so strange, because on Tumbleweed everything worked as is.
Pairing itself succeeds, and the endpoints are registered, but Bluez tries to establish the audio transport, and fails to open a socket, so the connection is aborted.
This suggests a stack-level issue rather than a pairing or configuration problem.
A bug report may be needed for this issue.
Do you have BT headphones or earbuds available to test with?
@Svyatko: wireless-regdb only affects Wi-Fi regulatory domain settings (cfg80211).
This failure occurs during BR/EDR transport socket creation in BlueZ and is unrelated to Wi-Fi regulatory rules.
Thanks everyone for the help.
I tried to install the kernel from backports, but it gives me some kind of SHIM error during boot. I haven’t been able to figure out what to do next.
I’ll just install Tumbleweed and that’s it.
I was a bit scared of a rolling distro, but it is what it is.