Hi everyone,
I just did a fresh install of Fedora 40 KDE and everything works great, except that I can’t connect to my bluetooth headset because the system just can’t discover any active bluetooth devices even when there are many in the vicinity.
System/hardware details: inxireport - Pastebin.com
bluetoothctl output looks like this:
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 94:BB:43:01:23:07 Discovering: yes
Bluetooth seems on, but can’t detect anything. Strange.
I tried restarting the bluetooth service using systemctl but it still didn’t work.
Can anyone please help?
Welcome to
It’s ok to paste your terminal replies here in </> preformatted text :
Bluetooth:
Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-3:2 chip-ID: 13d3:3601
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Please paste here the results of :
systemctl status bluetooth
&
lsusb | grep Bluetooth
Hey, thanks!
Output of systemctl status bluetooth:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Mon 2024-05-27 02:50:15 IST; 1min 44s ago
Docs: man:bluetoothd(8)
Main PID: 934 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18311)
Memory: 2.3M (peak: 6.4M)
CPU: 97ms
CGroup: /system.slice/bluetooth.service
└─934 /usr/libexec/bluetooth/bluetoothd
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/sbc
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/sbc
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/sbc_xq
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/sbc_xq
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/faststream
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/faststream>
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/opus_05
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/opus_05
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/opus_05_dupl>
May 27 02:50:28 fedora bluetoothd[934]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/opus_05_du>
Output of lsusb | grep Bluetooth:
Bus 003 Device 002: ID 13d3:3601 IMC Networks Bluetooth Radio
Everything seems good. . . Can you try :
bluetoothctl scan on
The output for that is in the OP
Everything seems ok, have you tried re-pairing the devices? When was the last time you updated the system? dnf update ?
Pastebin is a short lived location for large amounts of data.</> button.
When it gets deleted from the pastebin link it is no longer accessible to anybody who may read your thread at a later time.
As much as possible please include data directly into the post you make here.
Yes, @hamrheadcorvette has already included the relevant part in his first reply.
Here is the full text:
System:
Kernel: 6.8.10-300.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 40 (KDE Plasma)
Machine:
Type: Laptop System: Acer product: Aspire Lite AL15-41 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Acer model: Aspire Lite AL15-41 serial: <superuser required>
part-nu: 0000000000000000 UEFI: INSYDE v: 1.07.24RAC1 date: 01/05/2024
Battery:
ID-1: BAT0 charge: 37.8 Wh (100.0%) condition: 37.8/36.2 Wh (104.4%)
volts: 12.9 min: 11.4 model: Notebook BAT serial: <filter> status: full
CPU:
Info: 6-core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB
Speed (MHz): avg: 829 high: 2206 min/max: 400/4056 cores: 1: 2206 2: 400
3: 400 4: 400 5: 400 6: 400 7: 2071 8: 400 9: 400 10: 400 11: 2071 12: 400
bogomips: 50306
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Lucienne vendor: CLEVO/KAPOK driver: amdgpu v: kernel
arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: DP-1,eDP-1
empty: DP-2 bus-ID: 05:00.0 chip-ID: 1002:164c temp: 35.0 C
Device-2: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 04f2:b729
Display: wayland server: Xwayland v: 23.2.6 compositor: kwin_wayland
driver: N/A d-rect: 3584x1152 display-ID: 0
Monitor-1: DP-1 pos: primary,left res: 2048x1152 size: N/A
Monitor-2: eDP-1 pos: right res: 1536x864 size: N/A
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.8 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
18.1.1 DRM 3.57 6.8.10-300.fc40.x86_64) device-ID: 1002:164c
display-ID: :0.0
API: Vulkan v: 1.3.280 surfaces: xcb,xlib,wayland device: 0
type: integrated-gpu driver: N/A device-ID: 1002:164c device: 1 type: cpu
driver: N/A device-ID: 10005:0000
Audio:
Device-1: AMD Renoir Radeon High Definition Audio vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:1637
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: CLEVO/KAPOK
driver: N/A pcie: speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
Device-3: AMD Family 17h/19h HD Audio vendor: CLEVO/KAPOK
driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 05:00.6 chip-ID: 1022:15e3
API: ALSA v: k6.8.10-300.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.6 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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: CLEVO/KAPOK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek vendor: AzureWave driver: rtw89_8851be v: kernel pcie:
speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:b851
IF: wlo1 state: up mac: <filter>
Device-3: Lite-On Dell Wireless Device driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-1:2 chip-ID: 04ca:00bd
Bluetooth:
Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-3:2 chip-ID: 13d3:3601
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 476.94 GiB used: 5.25 GiB (1.1%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD PC SN740
SDDQNQD-512G-1014 size: 476.94 GiB speed: 63.2 Gb/s lanes: 4
serial: <filter> temp: 32.9 C
Partition:
ID-1: / size: 475.35 GiB used: 4.92 GiB (1.0%) fs: btrfs dev: /dev/nvme0n1p3
ID-2: /boot size: 973.4 MiB used: 322 MiB (33.1%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 475.35 GiB used: 4.92 GiB (1.0%) 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: 42.0 C mobo: N/A gpu: amdgpu temp: 36.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 14.95 GiB used: 4.92 GiB (32.9%)
Processes: 374 Power: uptime: 13m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: Compiler
s: N/A Shell: Bash v: 5.2.26 running-in: kitty
I updated it right after installation.
ledeni
May 27, 2024, 10:30am
10
Your Bluetooth headset have turn on / off button ?
It’s a simple bluetooth neckband with magnetic earpieces that start when untethered.
More importantly, there are several bluetooth devices nearby, including my phone. But nothing shows up in the scan. Nor can my phone detect the laptop.
gnwiii
May 27, 2024, 12:09pm
12
Problems with wifi and bluetooth on linux are not unusual with updates, so if those are “mission-critical” is it useful to have USB dongles that you can use when a problem occurs.
Please try to post hardware details as text so others with similar hardware and issues can find this topic with a web search.
Laptops have vendor-dependent ways to disable BT (airplane mode) with a switch or function key. The status of the the BT adapter should be passed to linux but sometimes the message is lost. Usually this is fixed by a vendor firmware update and/or linux driver update. Check for vendor firmware updates. You may also want to check for similar problem reports on vendor forums. Also make sure Fedora 40 is fully updated so you aren’t chasing a solved problem and to make it easier for others with similar hardware to reproduce your problem.
You can use journalctl to search for details of your issue. Start with journalctl --no-hostname -b -g blue |cat. Here I get around 30 lines. If you get a longer output it usually has blocks of similar lines, so some editing to remove redundant lines is needed. Paste the output as pre-formatted text.
This might seem strange but I couldn’t find any setting related to the Bluetooth adaptor in my laptop’s BIOS
How do I check for vendor firmware updates on Fedora? Sorry, I am using this for the first time.
I have added all hardware details in a previous response.
Here is the journalctl --no-hostname -b -g blue |cat report:
May 28 00:49:35 kernel: usb 3-3: Product: Bluetooth Radio
May 27 19:19:41 kernel: Bluetooth: Core ver 2.22
May 27 19:19:41 kernel: NET: Registered PF_BLUETOOTH protocol family
May 27 19:19:41 kernel: Bluetooth: HCI device and connection manager initialized
May 27 19:19:41 kernel: Bluetooth: HCI socket layer initialized
May 27 19:19:41 kernel: Bluetooth: L2CAP socket layer initialized
May 27 19:19:41 kernel: Bluetooth: SCO socket layer initialized
May 27 19:19:41 systemd[1]: Starting bluetooth.service - Bluetooth service...
May 27 19:19:41 bluetoothd[945]: Bluetooth daemon 5.76
May 27 19:19:41 systemd[1]: Started bluetooth.service - Bluetooth service.
May 27 19:19:41 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 27 19:19:41 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
May 27 19:19:41 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 27 19:19:41 kernel: Bluetooth: BNEP filters: protocol multicast
May 27 19:19:41 kernel: Bluetooth: BNEP socket layer initialized
May 27 19:19:41 bluetoothd[945]: Bluetooth management interface 1.22 initialized
May 27 19:19:41 kernel: Bluetooth: MGMT ver 1.22
May 27 19:19:42 NetworkManager[1063]: <info> [1716817782.4150] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.46.0-2.fc40/libnm-device-plugin-bluetooth.so)
May 27 19:19:50 kernel: Bluetooth: RFCOMM TTY layer initialized
May 27 19:19:50 kernel: Bluetooth: RFCOMM socket layer initialized
May 27 19:19:50 kernel: Bluetooth: RFCOMM ver 1.11
May 27 19:19:59 systemd[1378]: Starting obex.service - Bluetooth OBEX service...
May 27 19:19:59 systemd[1378]: Started obex.service - Bluetooth OBEX service.
What do you see with rfkill?
1 Like
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
This might be the strangest thing I’ve ever seen with Bluetooth. According to the logs and messages, everything should be working as expected. I’ve asked all I can and you have asked the only other thing I know . . . I think there’s something else wrong here. Just can’t seem to figure it out.
1 Like
tqcharm
May 27, 2024, 4:23pm
17
This might be a stupid question, but is any of the Bluetooth devices in pairing mode?
1 Like
ersen
May 27, 2024, 4:39pm
19
Do you have realtek-firmware package installed?
Yes.
$ dnf list --installed | grep realtek
realtek-firmware.noarch 20240513-1.fc40 @updates
