You should try https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html.
Thank you, I will give that a read, I just started my computer and went to the old kernel and it broke my bluetooth again. I will look for the right place to read/post about linux kernel issues
I’ve had some trouble with my Sony headphones recently. They sometime default to a codec that make the sound really low and crackly. In KDE you can change the codec in the “Sound” tab of system setting (or clicking on the gear in the roll-down menu of the sound tray icon)
In my specific case all the A2DP codecs are fine, all the HSP are bad. I think if I only connect one earphone, it defaults to the HSP codecs for some reason and I have to change it by hand.
Yes Mine just stopped mid use. Can’t seem to get them to function anymore. they connect and disconnect but no Audio.
– Amend 1 – I also can’t re-pair. I deleted and restarted bluetooth and set headphones to pair. I select the device and it starts to pair then says it fails. But it does add the device to the list.
– Amend 2 – They work fine with my Macbook Pro. But after I reset the headphones they no longer show up when pairing on Linux… How does this happen? I was just watching something on YouTube and they just stop. This is a brand new computer. Less than a week old.
– Amend 3 – I reset my headphones syill can’t pair them with Linux. I also can’t pair a BT Mouse with my linux machine. Both pair with my Macboook. Also I tried an earlier Grub with no difference. This is bad since I have hearing disability and need my headphones. I would annoy others in my house if i turn the volume up loud enough to be clear to me.
I am sorry to hear that you have had troubles too especially with your hearing condition. I have been struggling with this for a long time and I am glad to hear that it isn’t because I am new to this OS/non technical, and by the amount of people contributing to this post I feel like this is too common to not be an issue. Do you want to comment you results for inxi -ezxx and let others compare? Maybe the full results.
Not solved, for me or others. Marked it as un-solved.
Well I woke up today and ran updates, restarted, re-paired headphones and they are working again.
– Amend – Probably doesn’t matter for me anymore. But my INXI Results bellow.
System:
Kernel: 7.1.4-204.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: KDE Plasma v: 6.7.3 tk: Qt v: N/A wm: kwin_wayland dm: N/A
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop Mobo: Micro-Star model: MAG X870E TOMAHAWK WIFI (MS-7E59)
v: 2.0 serial: Firmware: UEFI vendor: American
Megatrends LLC. v: 2.AC3 date: 06/25/2026
CPU:
Info: 12-core model: AMD Ryzen 9 9900X bits: 64 type: MT MCP arch: Zen 5
rev: 0 cache: L1: 960 KiB L2: 12 MiB L3: 64 MiB
Speed (MHz): avg: 614 min/max: 614/5662 boost: enabled cores: 1: 614
2: 614 3: 614 4: 614 5: 614 6: 614 7: 614 8: 614 9: 614 10: 614 11: 614
12: 614 13: 614 14: 614 15: 614 16: 614 17: 614 18: 614 19: 614 20: 614
21: 614 22: 614 23: 614 24: 614 bogomips: 211199
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
XT / 5700/5700 XT] vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-1
pcie: speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1
empty: DP-1,DP-2,DP-3 bus-ID: 03:00.0 chip-ID: 1002:731f
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 pcie:
speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5, DP-6,
HDMI-A-2, Writeback-1 bus-ID: 7b:00.0 chip-ID: 1002:13c0 temp: 36.0 C
Device-3: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-9:4 chip-ID: 046d:0843
Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland
driver: gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: LG (GoldStar) HDR WQHD res: 3440x1440 hz: 60
dpi: 107 diag: 888mm (34.9")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: radeonsi
device: 2 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi wayland:
drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.5 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 5700 XT (radeonsi navi10 ACO DRM
3.64 7.1.4-204.fc44.x86_64) device-ID: 1002:731f display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
driver: mesa radv device-ID: 1002:731f device: 1 type: integrated-gpu
driver: mesa radv device-ID: 1002:13c0 device: 2 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab38
Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 7b:00.1 chip-ID: 1002:1640
Device-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-12:3
chip-ID: 0db0:cd0e
Device-4: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-9:4 chip-ID: 046d:0843
API: ALSA v: k7.1.4-204.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8126 5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: speed: 8 GT/s lanes: 1 port: e000 bus-ID: 09:00.0
chip-ID: 10ec:8126
IF: enp9s0 state: down mac:
Device-2: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
vendor: Foxconn Band Simultaneous Wireless driver: ath12k_wifi7_pci v: N/A
pcie: speed: 8 GT/s lanes: 2 bus-ID: 0a:00.0 chip-ID: 17cb:1107
IF: wlp10s0 state: up mac:
Bluetooth:
Device-1: Foxconn / Hon Hai driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 3-12:7 chip-ID: 0489:e10a
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 1.82 TiB used: 599 GiB (32.2%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT2000T705SSD3 size: 1.82 TiB
speed: 126 Gb/s lanes: 4 serial: temp: 31.9 C
Partition:
ID-1: / size: 1.82 TiB used: 598.36 GiB (32.2%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 1.9 GiB used: 629.4 MiB (32.3%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 26 MiB (4.3%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 1.82 TiB used: 598.36 GiB (32.2%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 48.0 C mobo: 24.5 C
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 35.0 C device: amdgpu temp: 49.0 C mem: 48.0 C
fan: 0
Info:
Memory: total: 32 GiB note: est. available: 30.25 GiB used: 3.8 GiB (12.6%)
Processes: 551 Power: uptime: 32m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 20
Compilers: gcc: 16.1.1 Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.41
Well I stand corrected. BT failed again. Again i was listening to YouTube then audio dropped. I looked at my headphones and the light was flashing. I reloaded youtube page and reconnected to my headphones. The audio faded back in and then dropped. So I closed everything, removed pair. and tried re-pairing and it fails as it did last time.
– Amend 1 –
It was working for a couple of hours before it dropped.
I have similar hardware and it works fine
Bluetooth:
Device-1: Foxconn / Hon Hai driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 1-12:5 chip-ID: 0489:e0e3
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Not to blame you, it could be a bug triggered but the specific chip in the headphone, or it could be triggered by some interference ?
What do you see in the output of
sudo journalctl -b -u bluetooth.service
after it disconnects?
p.s. do you use “powertop”, “tlp” or other to tune the power consumption?
Re: headphones. Well it could be being a new system i don’t have a long history with these headphones on this system to tell from experience. Although they do work with everything else i throw them at and used them for a few years without issue. Also my BT mouse also fails to pair. I normally use it through 2.4ghz dongle but for the tests I try pairing it with BT and get same results.
Re: powertop; not that I know of. I have not specifically installed anything related to power management.
Re: Log. I reset the headphones, restarted, toggled the bluetooth and tried repairing them. It failed and then i ran the command. Results bellow.
Jul 23 18:36:42 fedora systemd[1]: Starting bluetooth.service - Bluetooth service…
Jul 23 18:36:42 fedora bluetoothd[1105]: Bluetooth daemon 5.87
Jul 23 18:36:42 fedora bluetoothd[1105]: Starting SDP server
Jul 23 18:36:42 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
Jul 23 18:36:42 fedora bluetoothd[1105]: Bluetooth management interface 1.23 initialized
Jul 23 18:36:42 fedora bluetoothd[1105]: Battery Provider Manager created
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:01 fedora bluetoothd[1105]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:08 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint unregistered: sende>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:10 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Endpoint registered: sender=>
Jul 23 18:37:25 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: src/adv_monitor.c:btd_adv_mo>
Jul 23 18:37:25 customer.mlbeaus1.isp.starlink.com bluetoothd[1105]: Failed to set mode: Busy (0x>
lines 1-47/47 (END)
Could it be BIOS related? I’ve not used a regular PC hardware setup in many years. My BIOS feels, weird, I think it resets every night after it’s powered off. Perhaps this is related. I’ll see what happens after i power it off for a while and get back if there is some noticeable change from that.
The last part of the log line, including the error code, is missing. Can you run it in a larger terminal window, or simply redirect it to a file, so that all the line is there?
sudo journalctl -b -u bluetooth.service > log.txt
Afterwards, you may try to look it up on google yourself, there are a few hints about it being caused by the bluetooth chip powering off or old kernel bugs (should be solved by now, but you never know)
Could it be BIOS related? I’ve not used a regular PC hardware setup in many years. My BIOS feels, weird, I think it resets every night after it’s powered off. Perhaps this is related. I’ll see what happens after i power it off for a while and get back if there is some noticeable change from that.
That could be caused by the motherboard battery being flat/dead, it is possible to change it but may not be easy in a laptop. Do you also get the clock resetting to some distant past after poweroff? I would guess that once the system is powered on, it should not matter, but it may be a hint of something else going on.
Re the BIOS. I just rebooted and pressed the CMOS button to reset and afterwards I re-paired the headphones and they works… My CMOS battery is under one of the chunks of aluminum. Might be hard to get to without taking some parts out. Struggling to find information on that…
– Amend – Re: time/date no it’s fine.
– Amend 2 – Ohh no. It’s under a heat-sink that requires me to pull the board out and unscrew from the back… Sorry getting off topic. i’ll pursue this in my own time and come back at a later date if I have some more conclusive outcome related to the BT issue.
No rush, if in the meanwhile you can provide the last two lines of the log in full, that would help. You probably have the same issue as here.
You could also try this simpler way to restart the bluetooth chip without doing a reboot
sudo rfkill unblock bluetooth
sudo systemctl restart bluetooth
Ok well some things to add.
Re: restarting BT. It did restart it but connecting did not read the interface for the audio output to the config list. So that didn’t work the same as clearing the CMOS.
Additional observation. I turned on my controller that uses a 2.4ghz dongle immediately killed my connection. But I was able to reconnect after a normal reboot. But observing it the interface vanishes and BT can’t reconnect. But I think it might be port related. Port related, I shifted the dongle in a front case usb port and it didn’t effect the audio. Still not sure if there is an issue with my CMOS battery. But it being buried under an aluminium heat-sink screwed in from the back of the board is a… discouragement to testing the battery. Eventually I will for sanity sake.
Hi, i think is many possible You don’t have or have broken something in pipewire ore wireplumber libs. Why ? becouse this error are in setting, bus are wait to set a BT mode. This is when file of configuration are missing/broken/or blocked by alse resorce. But is very possible You have one of libs in pipewire/wireplumber conflict if connection are break. Try to add some what may be missing. (dnf list --installed | grep pipewire/wireplumber then dnf search pipewire/wireplumber) One fail libs in pipe can broke sound and connection but only in log You have answere. In my opinion is missing libs with config file but may i be wrong. I had problem with music and problem are in one of installed pipewire-jack (too many) but Busy in 0x is mean not access becouse address of memory is in use or are block (meaby becouse is protect for hardware damage(break connection when attack memory)).
I’ll look into it, I already restarted and installed some drivers and stuff like bluez but see what else I can do
Look what is installed, try to find pipewire-pulseaudio, in repo are two different and I had error when pulseaudio-jack are installed for/from different repo/else. Try to search whot are installed from rmpfussion and check is free or no. My bluez is below. Check what is different and tell me. If don’t have any of, install.
