As of yesterday, my bluetooth adapter is randomly disappearing during use, and the only way to get it to reappear is to fully shut down my PC, disconnect it from power for 1-30 seconds, then plug it back in and boot. The bluetooth adapter will work for hours and then suddenly all audio cuts out of my headset and Fedora insists no bluetooth adapter can be found. I’ve been using Fedora for a couple of years now and had no issue with my bluetooth adapter or this headset. When I do sudo dmesg | grep -i bluetooth it tells me hci0: corrupted ACL packet, and generally any other command line mention of bluetooth lists it in red. I’ve tried restarting bluetooth via command line, but nothing works save turning the PC off completely, cutting it from power, and starting it up. I’m at a bit of a loss over why this is happening or how to fix it.
Please be specific: what command-lines have you tried? You should strive to provide enough detail to allow others with access similar hardware to reproduce the issue. Start by posting the output from running inxi -ezxx in a terminal (you may need to install inxi) as web-discoverable pre-formatted text.
I’ve tried sudo systemctl enable bluetooth.service and sudo service bluetooth restart, though these wouldn’t help you reproduce the issue since they’re what I tried to solve the issue, and didn’t cause it. I’ve been using Linux for a couple years, but I’m a casual user and not a programmer or developer, so things like command line don’t come naturally to me, and I often don’t simply remember everything I try or precisely how to do it. The bluetooth issue simply started, seemingly with no reason other than usual updating and restarting. I’ve simply been searching for days to find ways to fix the issue, which has only persisted, so unfortunately this post was as precise as I was able to, barring further instruction or prompting. In other words, the problem simply started, and I’ve just been trying things people have insisted worked for their similar issues.
I’ve just restarted my PC again in order to get my bluetooth working again, here’s the inxi -ezxx output.
Inxi Output
inxi -ezxx
System:
Kernel: 7.1.8-200.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX Z370-I GAMING v: Rev X.0x
serial: part-nu: SKU Firmware: UEFI
vendor: American Megatrends v: 3005 date: 09/15/2021
CPU:
Info: 6-core model: Intel Core i5-8600K bits: 64 type: MCP arch: Coffee Lake
rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 9 MiB
Speed (MHz): avg: 800 min/max: 800/4300 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 bogomips: 43200
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX 56/64]
driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports:
active: DP-2,DP-3 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:687f
Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland
driver: gpu: amdgpu d-rect: 3840x1080 display-ID: 0
Monitor-1: DP-2 pos: primary,left model: Samsung C24FG70 res: 1920x1080
hz: 120 dpi: 92 diag: 613mm (24.1")
Monitor-2: DP-3 pos: right model: Sceptre F27 res: 1920x1080 hz: 100
dpi: 82 diag: 686mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 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.6 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX Vega (radeonsi vega10 ACO DRM
3.64 7.1.8-200.fc44.x86_64) device-ID: 1002:687f display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: discrete-gpu
driver: mesa radv device-ID: 1002:687f device: 1 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu, lact
wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 200 Series/Z370 Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
Device-2: Advanced Micro Devices [AMD/ATI] Vega 10 HDMI Audio [Radeon
56/64] driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:aaf8
API: ALSA v: k7.1.8-200.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: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: ASUSTeK
driver: rtw88_8822be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
bus-ID: 05:00.0 chip-ID: 10ec:b822
IF: wlp5s0 state: down mac:
Bluetooth:
Device-1: ASUSTek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 1-14:6 chip-ID: 0b05:185c
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: bt-v: 4.2
lmp-v: 8
RAID:
Hardware-1: Intel SATA Controller (RAID 0/1/5/10) In-box Compatible ID
(Desktop RST) driver: ahci v: 3.0 bus-ID: 00:17.0 chip-ID: 8086:2822
Drives:
Local Storage: total: 1.59 TiB used: 901.92 GiB (55.3%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
speed: 6.0 Gb/s serial:
ID-2: /dev/sdb vendor: Western Digital model: WD7500LPCX-60KHST0
size: 698.64 GiB type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial:
Partition:
ID-1: / size: 929.93 GiB used: 810.2 GiB (87.1%) fs: btrfs dev: /dev/sda3
ID-2: /boot size: 973.4 MiB used: 537.5 MiB (55.2%) fs: ext4
dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/sda1
ID-4: /home size: 929.93 GiB used: 810.2 GiB (87.1%) fs: btrfs
dev: /dev/sda3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.8 C mobo: N/A gpu: amdgpu temp: 38.0 C
mem: 34.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 2381
Info:
Memory: total: 16 GiB available: 15.54 GiB used: 5.17 GiB (33.3%)
Processes: 414 Power: uptime: 4m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 54
Compilers: N/A Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.41
Your UEFI firmware is from 2021. One problem with BT is power management where users have differing needs and vendors want to advertise long battery life. This can result on BT power being reduced to point where connections are less reliable. This can depend on the strength of other radio signals in your environment.
Linux has been moving to power management “standards” and away from vendor-dependent methods. You should update your firmware if a newer version is available. There may be some power management settings you can try, both in the UEFI settings and as module options.
Unfortunately, that’s the newest version available for this board. What would you suggest as far as the power management settings?
Your issue is likely specific to your system hardware and UEFI firmware, nothing specific to Fedora. The problem is to find a known workaround under the current mass of AI clickbait. Try searching for your hardware in https://linux-hardware.org if you can out-compete AI scrapers to get connected. The other option is to research power management settings in UEFI and linux and do your own experiments, starting from an always on setting to rule out radio signal problems
Part of my issue when trying to find a solution in the first place was just how much slop there is to sort through. It was funny seeing replies that said something along the lines of “Just look it up, it should be fairly simple to find”, and then it was simply impossible to find.
On the note of power profiles, I’ve been getting SELinux notifications for power-profiles- since around the same time my bluetooth issues started, which I almost feel could be related. When I went to install hw-probe, it popped up another one.
Maybe not directly related — there have been many changes (for security, simplifying support effort required of Linux devs, or to reduce energy consumption). Older platforms are lower priority for vendors, and Linux devs may not have access to the same hardware you use. I often resort to USB WiFi dongles while looking for fixes/workarounds to onboard WiFi. If your WiFi card is socketed, you should be able to upgrade to one with better support
So I bit the bullet and bought a USB dongle for the time being and… the bluetooth still disappears and only reconnects if I fully power off, disconnect from power, then restart. Which implies to me it isn’t an issue with the hardware, but I could be wrong. This dongle’s model at least seems to be from 2024, which is much more recent, but my system fully won’t show bluetooth, even in the settings, unless I power off, disconnect from power, then restart. Bluetooth doesn’t even show under Network in settings until I do so. Interestingly, I can connect/pair to my device using bluetoothctl but I’m not able to actually use it until I do the above steps to make bluetooth “work” again.
Edit: Scratch that, bluetooth has disappeared from the GUI entirely and will not reappear no matter what I do. bluetoothctl lets me pair etc. but I can’t actually select the devices for audio output or input, and the gui simply will not show bluetooth, at all. Very frustrated.
Without more details we can only guess at the cause of your issue.
This is quite old, have you looked for newer firmware? Please post the output from inxi -Ezxx as pre-formatted text using the </> button so we can see what your new device contains (sometimes vendors substitute chipsets, and there can be counterfeit versions of popular models) so it is important to check. You can try the steps in https://docs.fedoraproject.org/en-US/quick-docs/troubleshooting-bluetooth-problems/ and report what it reveals.
There continues to be no newer firmware for my UEFI. It also does not have its own power management options.
Bluetooth:
Device-1: ASUSTek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 1-14:5 chip-ID: 0b05:185c
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
lmp-v: 8
Device-2: TP-Link UB500 Adapter driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 bus-ID: 1-7:7 chip-ID: 2357:0604
Report: ID: hci1 rfk-id: 3 state: up address: <filter> bt-v: 5.1 lmp-v: 10
Your TP Link adapter needs proprietary firmware. See: https://github.com/CachyOS/distribution/issues/526 for a potential workaround.
My TP Link adapter is working fine, Fedora itself is not showing bluetooth through GUI. It isn’t there at all. It has disappeared entirely from system settings.
Simply, my hardware worked until less than 2 weeks ago, just fine. I understand my UEFI version is a paleolithic 5 years old, but it functioned just fine less than two weeks ago. I even got a different piece of hardware to replace the previous piece of hardware (not the motherboard, unfortunately), just in case (a piece of hardware which functions as a bluetooth 5.1 device barring a windows-only driver that lets it function at its full 5.4 capacity). It seems like a frustrating poweruser pratfall to hyperfixate on hardware and the age of hardware in a rapidly inflating electronic component market in an even more rapidly declining global economy, but I never had the fortune to stumble into a 6 figure job, and if I could afford to upgrade my hardware I would. However, my hardware worked fine until 12 days ago. I’d rather focus on potential ways we can undo or rectify or fix or circumvent what is almost certainly a 99.9999% claude-vibe-coded abortion commited to my machine. I’d be happy to discuss setting up a donation link for those with significantly more generous incomes to pore over my hardware and shape it to their own preferences, but I would simply like to restore the functionality I had less than two weeks ago. The problem seems to be worsening for no apparent reason, no update has been pushed that’s helped or fixed it, rather, again, it just seems to be getting worse. I would appreciate specific instruction, as specific as possible. I’ve spent countless hours of my very limited free time to this point chasing rabbit holes of people vaguely gesturing to results that “exist on the internet” and inevitably lead to deleted posts, people saying they fixed their issues and never saying how, or simply nothing at all that has just been accepted for a decade and a half as the information existing somewhere. If there just is no solution, fine. I’d rather not have to delete years of my personal data re-installing this operating system on the hopes that whatever was arbitrarily fucked will be un-fucked. Every avenue I’ve tried points me here. If anyone has had a similar issue and found a solution, if anyone just knows something I don’t, if anyone has an answer, I’d be extremely happy to hear it. If anyone wants to sneer at the age of my hardware, I offer them the opportunity to put their money where their mouth is.
Older hardware was often supported by device-dependent code provided by vendors who imposed non-free license and/or stopped maintaining it. Meanwhile, a) there has been work on standards that newer devices support without requiring hardware-specific code, and b) that mass of old unmaintained code often has security problems.
That is why it is important to have backups. Hardware can fail at inopportune moments, or be damaged in natural disaters.
Between recent updates to bluetooth (patchnotes admitted issues caused by previous updates) and reinstalling the bluedevil package (which seems to have uninstalled at some point, thank you KDE support!) the issue ssems to have been resolved. Fortunately it seems to have had nothing to do with hardware.