Very new to Linux as a whole. Decided to swap over to Fedora because I’m fed up with Microsoft (hot take, I know). Everything’s been working great so far. All but Bluetooth.
Bluetooth has not been working for me. When I go into the taskbar menu to start it, I find that it switches every second or so back and forth between disabled to no adapter found. I’ve been scouring the forums trying to find a solution but have had no luck.
So now I’m here. I’m unsure what information I should provide or how exactly I should go about doing that. However, I will at least say that I know that this is not a hardware issue, as Bluetooth still works perfectly fine in Windows (I have Windows loaded on a second NVME for the applications I have that more or less require it).
Any help would be appreciated. Thank you!
gnwiii
October 28, 2025, 12:16pm
2
Resolving Linux issues often benefits from “all linux problems are shallow given enough eyeballs”. When reporting an issue, you want to provide enough detail to allow others with similar hardware to discover your issue and reproduce the issue:
output from running inxi -Fzxx in a terminal and posting as pre-formatted, web-searchable, text.
ensure that Fedora packages and vendor firmware are full updated: a) so you aren’t chasing a solved problem, and b) so it is easy for others to replicate your configuration.
In addition to the inxi output:
Turn bluetooth off
Execute journalctl -f --no-pager in a terminal.
Toggle bluetooth on
You could also try to actually use this bluetooth service - try to connect some buds, a mouse, a keyboard, a defibrillator, anything you have to hand to pair over bluetooth
Copy and paste the journalctl output into here inside pre-formatted tags </>
1 Like
Thank you all for the help! Here’s my inxi -Fzxx output
System:
Kernel: 6.17.4-200.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 42 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop Mobo: Gigabyte model: X870E AORUS ELITE WIFI7
serial: <superuser required> UEFI: American Megatrends LLC. v: FA3a
date: 05/05/2025
CPU:
Info: 8-core model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: Zen 5
rev: 0 cache: L1: 640 KiB L2: 8 MiB L3: 96 MiB
Speed (MHz): avg: 2985 min/max: 603/5272 boost: enabled cores: 1: 2985
2: 2985 3: 2985 4: 2985 5: 2985 6: 2985 7: 2985 8: 2985 9: 2985 10: 2985
11: 2985 12: 2985 13: 2985 14: 2985 15: 2985 16: 2985 bogomips: 150108
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 48 [Radeon RX 9070/9070
XT/9070 GRE] vendor: XFX driver: amdgpu v: kernel arch: RDNA-4 pcie:
speed: 32 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, DP-3, HDMI-A-1,
Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:7550
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-2 empty: DP-4, DP-5, HDMI-A-3, Writeback-2
bus-ID: 7c:00.0 chip-ID: 1002:13c0 temp: 41.0 C
Device-3: Logitech BRIO 300
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 5-1:2 chip-ID: 046d:0942
Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
driver: gpu: amdgpu d-rect: 5120x2880 display-ID: 0
Monitor-1: DP-1 pos: bottom-r model: Gigabyte M27Q res: 2560x1440 hz: 165
dpi: 93 diag: 801mm (31.5")
Monitor-2: HDMI-A-2 pos: primary,top-left model: Dell U2722D
res: 2560x1440 hz: 60 dpi: 109 diag: 685mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: radeonsi
device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.9 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 9070 XT (radeonsi gfx1201 LLVM
20.1.8 DRM 3.64 6.17.4-200.fc42.x86_64) device-ID: 1002:7550
display-ID: :0.0
API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: discrete-gpu
driver: mesa radv device-ID: 1002:7550 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 48 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab40
Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
[Rembrandt/Strix] driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 7c:00.1 chip-ID: 1002:1640
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 7c:00.6 chip-ID: 1022:15e3
Device-4: Focusrite-Novation Scarlett Solo (3rd Gen.)
driver: snd-usb-audio type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
bus-ID: 3-9:6 chip-ID: 1235:8211
Device-5: Logitech BRIO 300
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 5-1:2 chip-ID: 046d:0942
API: ALSA v: k6.17.4-200.fc42.x86_64 status: kernel-api
Server-1: PipeWire v: 1.4.9 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 RTL8922AE 802.11be PCIe Wireless Network Adapter
driver: rtw89_8922ae v: kernel pcie: speed: 5 GT/s lanes: 1 port: d000
bus-ID: 10:00.0 chip-ID: 10ec:8922
IF: wlp16s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: c000 bus-ID: 11:00.0 chip-ID: 10ec:8125
IF: enp17s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-6:2 chip-ID: 0bda:8922
Report: btmgmt ID: hci0 rfk-id: 1041 state: up address: N/A
Drives:
Local Storage: total: 5.46 TiB used: 6.64 GiB (0.1%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T2B0C-00PXH0
size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 28.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 PRO 4TB size: 3.64 TiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 28.9 C
ID-3: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 929.93 GiB used: 6.26 GiB (0.7%) fs: btrfs dev: /dev/nvme0n1p3
ID-2: /boot size: 973.4 MiB used: 369.4 MiB (37.9%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 929.93 GiB used: 6.26 GiB (0.7%) 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: 46.0 C mobo: 25.0 C
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 30.0 C mem: 54.0 C fan: 2 device: amdgpu
temp: 42.0 C
Info:
Memory: total: 60 GiB note: est. available: 60.43 GiB used: 5.69 GiB (9.4%)
Processes: 633 Power: uptime: 10h 38m wakeups: 1 Init: systemd v: 257
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
v: 5.2.37 running-in: konsole inxi: 3.3.39
Here is the output of journalctl -f --no-pager after disabling bluetooth with sudo systemctl stop bluetooth.service
Oct 28 11:56:38 fedora kernel: Bluetooth: hci0: command 0xfc61 tx timeout
Oct 28 11:56:38 fedora kernel: Bluetooth: hci0: RTL: Failed to generate devcoredump
Oct 28 11:56:38 fedora kernel: Bluetooth: hci0: Resetting usb device.
Oct 28 11:56:38 fedora kernel: Bluetooth: hci0: RTL: RTL: Read reg16 failed (-110)
Oct 28 11:56:38 fedora systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Oct 28 11:56:38 fedora systemd[1677]: Stopped target bluetooth.target - Bluetooth.
Oct 28 11:56:39 fedora kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
Oct 28 11:56:39 fedora systemd[13991]: Reached target bluetooth.target - Bluetooth.
Oct 28 11:56:39 fedora systemd[1677]: Reached target bluetooth.target - Bluetooth.
Oct 28 11:56:39 fedora systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Oct 28 11:56:41 fedora kernel: Bluetooth: hci0: command 0xfc61 tx timeout
Oct 28 11:56:41 fedora kernel: Bluetooth: hci0: RTL: Failed to generate devcoredump
Oct 28 11:56:41 fedora kernel: Bluetooth: hci0: Resetting usb device.
Oct 28 11:56:41 fedora kernel: Bluetooth: hci0: RTL: RTL: Read reg16 failed (-110)
Oct 28 11:56:41 fedora systemd[1677]: Stopped target bluetooth.target - Bluetooth.
Oct 28 11:56:41 fedora systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Oct 28 11:56:41 fedora systemd[13991]: Stopped target bluetooth.target - Bluetooth.
Oct 28 11:56:41 fedora kernel: usb 1-6: reset full-speed USB device number 2 using xhci_hcd
Oct 28 11:56:41 fedora systemd[13991]: Reached target bluetooth.target - Bluetooth.
Oct 28 11:56:41 fedora systemd[1677]: Reached target bluetooth.target - Bluetooth.
Oct 28 11:56:41 fedora systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Okay. So, I did a little bit more testing.
Tried every method in the book including performing a BIOS update, rolling back the kernel, all the marbles.
Went to test it on Ubuntu and saw that it had the same issues. Went over to Windows and checked the drivers.
Long story short, it is simply hardware failure. I said it wasn’t because I had just used Bluetooth on my Windows install to play a game with a controller that same day and wrongfully assumed that it couldn’t possibly have broken since then.
Guess Microsoft detected I was trying to install a new operating system and fried my Bluetooth chip to try and stop me (joke).
Thank y’all for the help, and my apologies for any time wasted, sleep lost, or fingernails bitten.