https://discuss.getsol.us/d/9185-bluetooth-not-working from 10 days ago and only posting for the troubleshooting/elimination steps as well as a couple other t-shooting avenues--other than that unlike yours it sounds, plus no resolution.
see nothing at devtracker but I've never been able to sort by date in their search results. good luck, wish I knew more
Can't Connect or Enable Bluetooth on Plasma
- Edited
See, maybe this will help
brent typically, the ax200 series cards are detected and good with just the kernel, there aren't any special drivers needed. I did install the latest version of the ax200 linux driver manually, but no luck.
pomon Thanks, I tired most of these steps previously, but not the groupadd. Here is what I get when I get to the scan on step
[bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress
and then we have this long output
dmesg | grep -i blue 0 (0.000s) < 06:34:47
[ 4.832715] Bluetooth: Core ver 2.22
[ 4.832763] NET: Registered PF_BLUETOOTH protocol family
[ 4.832765] Bluetooth: HCI device and connection manager initialized
[ 4.832773] Bluetooth: HCI socket layer initialized
[ 4.832776] Bluetooth: L2CAP socket layer initialized
[ 4.832791] Bluetooth: SCO socket layer initialized
[ 4.875337] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 4.875404] Bluetooth: hci0: Boot Address: 0x24800
[ 4.875406] Bluetooth: hci0: Firmware Version: 15-45.22
[ 4.875409] Bluetooth: hci0: Firmware already loaded
[ 5.450045] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.450062] Bluetooth: BNEP socket layer initialized
[ 5.453803] Bluetooth: MGMT ver 1.22
[ 17.601869] Bluetooth: RFCOMM TTY layer initialized
[ 17.601895] Bluetooth: RFCOMM socket layer initialized
[ 17.601912] Bluetooth: RFCOMM ver 1.11
[ 61.055223] Bluetooth: hci0: command 0x2039 tx timeout
[ 61.055220] Bluetooth: hci0: Opcode 0x2039 failed: -110
[ 64.239201] Bluetooth: hci0: sending frame failed (-19)
[ 64.239226] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 64.239623] Bluetooth: hci0: sending frame failed (-19)
[ 64.239633] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.239964] Bluetooth: hci0: sending frame failed (-19)
[ 64.239975] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.240884] Bluetooth: hci0: sending frame failed (-19)
[ 64.240895] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.241382] Bluetooth: hci0: sending frame failed (-19)
[ 64.241395] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.241647] Bluetooth: hci0: sending frame failed (-19)
[ 64.241657] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.241899] Bluetooth: hci0: sending frame failed (-19)
[ 64.241908] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.242969] Bluetooth: hci0: sending frame failed (-19)
[ 64.242983] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.243505] Bluetooth: hci0: sending frame failed (-19)
[ 64.243516] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.243786] Bluetooth: hci0: sending frame failed (-19)
[ 64.243794] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.246004] Bluetooth: hci0: sending frame failed (-19)
[ 64.246020] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.246785] Bluetooth: hci0: sending frame failed (-19)
[ 64.246798] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 64.246871] Bluetooth: hci0: sending frame failed (-19)
[ 64.246878] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.246974] Bluetooth: hci0: sending frame failed (-19)
[ 64.246982] Bluetooth: hci0: Opcode 0x c13 failed: -19
[ 64.247001] Bluetooth: hci0: sending frame failed (-19)
[ 64.247014] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 64.248965] Bluetooth: hci0: sending frame failed (-19)
[ 64.248982] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.250019] Bluetooth: hci0: sending frame failed (-19)
[ 64.250035] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.266942] Bluetooth: hci0: sending frame failed (-19)
[ 64.266960] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 64.267071] Bluetooth: hci0: sending frame failed (-19)
[ 64.267080] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 64.322026] Bluetooth: hci0: sending frame failed (-19)
[ 64.322053] Bluetooth: hci0: Opcode 0x c13 failed: -19
[ 64.322081] Bluetooth: hci0: sending frame failed (-19)
[ 64.322092] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 66.367187] Bluetooth: hci0: command 0x0c52 tx timeout
[ 83.509985] Bluetooth: hci0: sending frame failed (-19)
[ 83.510010] Bluetooth: hci0: Opcode 0x2039 failed: -19
[ 85.567825] Bluetooth: hci0: command 0x2039 tx timeout
[ 88.720842] Bluetooth: hci0: sending frame failed (-19)
[ 88.720865] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 88.721552] Bluetooth: hci0: sending frame failed (-19)
[ 88.721569] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.721694] Bluetooth: hci0: sending frame failed (-19)
[ 88.721704] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.722090] Bluetooth: hci0: sending frame failed (-19)
[ 88.722100] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.722224] Bluetooth: hci0: sending frame failed (-19)
[ 88.722233] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 88.722304] Bluetooth: hci0: sending frame failed (-19)
[ 88.722311] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.722435] Bluetooth: hci0: sending frame failed (-19)
[ 88.722443] Bluetooth: hci0: Opcode 0x c13 failed: -19
[ 88.722457] Bluetooth: hci0: sending frame failed (-19)
[ 88.722463] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 88.729217] Bluetooth: hci0: sending frame failed (-19)
[ 88.729239] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729365] Bluetooth: hci0: sending frame failed (-19)
[ 88.729373] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729450] Bluetooth: hci0: sending frame failed (-19)
[ 88.729458] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729524] Bluetooth: hci0: sending frame failed (-19)
[ 88.729531] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729610] Bluetooth: hci0: sending frame failed (-19)
[ 88.729616] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729681] Bluetooth: hci0: sending frame failed (-19)
[ 88.729688] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729760] Bluetooth: hci0: sending frame failed (-19)
[ 88.729766] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729852] Bluetooth: hci0: sending frame failed (-19)
[ 88.729860] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.729937] Bluetooth: hci0: sending frame failed (-19)
[ 88.729943] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.730033] Bluetooth: hci0: sending frame failed (-19)
[ 88.730041] Bluetooth: hci0: Opcode 0x c13 failed: -19
[ 88.730053] Bluetooth: hci0: sending frame failed (-19)
[ 88.730059] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 88.739839] Bluetooth: hci0: sending frame failed (-19)
[ 88.739858] Bluetooth: hci0: Opcode 0x c24 failed: -19
[ 88.740629] Bluetooth: hci0: sending frame failed (-19)
[ 88.740642] Bluetooth: hci0: Opcode 0x c52 failed: -19
[ 90.751206] Bluetooth: hci0: command 0x0c52 tx timeout
[ 197.968394] Bluetooth: hci0: sending frame failed (-19)
[ 197.968474] Bluetooth: hci0: Opcode 0x2005 failed: -19
[ 197.968499] Bluetooth: hci0: sending frame failed (-19)
[ 197.968513] Bluetooth: hci0: Opcode 0x2041 failed: -19
[ 199.999767] Bluetooth: hci0: command 0x2041 tx timeout
[ 199.999781] Bluetooth: hci0: No way to reset. Ignoring and continuing
- Edited
Well, I can still propose
sudo systemctl stop bluetooth
sudo systemctl disable bluetoothand run again
sudo systemctl enable bluetooth
sudo systemctl start bluetoothand check rfkill list
- Edited
bluetoothctl and watch the response while issuing commands to bluetooth and see what it reports back
(I have nothing to connect to)
This will tell you status of service sudo systemctl status bluetooth.service
See you guys next week going out of town hope you get it working
- Edited
pomon it's not being blocked on the rfkill list, nor does disabling and restarting the service help
╰─λ sudo rfkill -o ID,TYPE-DESC,DEVICE,SOFT,HARD 0 (0.027s) < 06:23:22
ID TYPE-DESC DEVICE SOFT HARD
0 Wireless LAN ideapad_wlan unblocked unblocked
1 Bluetooth ideapad_bluetooth unblocked unblocked
2 Bluetooth hci0 unblocked unblocked
3 Wireless LAN phy0 unblocked unblocked
Axios bluetoothctl agent is on, looks like an error somewhere else, possible the bluez package?
[bluetooth]# list
Controller A4:B1:C1:36:53:11 solus-plasma [default]
[bluetooth]# show solus-plasma
Controller solus-plasma not available
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# list
Controller A4:B1:C1:36:53:11 solus-plasma [default]
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
Edit: To be sure, I ran sudo rfkill unblock all and it changed the status from unblocked to no, but no change in bluetooth behavior.
And what happens connect A4:B1:C1:36:53:11?
Brucehankins similar to your 6/2021 thread (https://discuss.getsol.us/d/6943-bluetooth-is-not-pairable/12) which ultimately determined bugs between bluetooth and bluez package...cured by update. I'll see if I can see any chatter at all about your current problem--if I do I will report back. Hard to determine [software] integrity when a bug appears, for sure.
pomon same, bluez.Error.InProgress
brent yeah, from my reading around different boards and posts, it seems to happen from time to time with bluez. I have the same ax200 card in an HP machine on 5.27.4, no connection issues on Kubuntu. Also works fine with no issues on EOS LXQt. I'm hopeful once the sync hits the problem will be fixed. I thought about switching to unstable to see if an update would help....but I think I can wait....maybe.... probably.....5.27.4 is nice.....I can wait....
- Edited
"When connecting a Bluetooth device, the separator line between connected and disconnected devices no longer briefly overlaps the connected device (Harald Sitter, Plasma 5.27.5. Link)" (https://pointieststick.com/2023/04/28/this-week-in-kde-the-bug-slaughterfest-continues/ dated a couple days ago) edit: links inside that article ^ link to current bluetooth/plasma/bluez bugs
this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359003 is interesting too from a couple days ago.
other than that not seeing a lot of current chatter about this.
Brucehankins Try bluetoothctl discoverable on from terminal and see if it starts
Then maybe bluetoothctl scan on see what happens
Axios different than these?
[bluetooth]# discoverable on
Failed to set discoverable on: org.bluez.Error.Failed
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
- Edited
Changed my mind put this into terminal and watch it as you issue commands
like turn bluetooth off/on, make discoverable
and lets see if its talking on Dbus
sudo dbus-monitor --system path=/org/bluez/hci0
This also kinda out in left field if your using wifi have you tried bluetooth without wifi on?
Well....I have a new problem now.....
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-232.current status: kernel-api
Server-1: PulseAudio v: 15.0 status: active
Bluetooth:
Message: No bluetooth data found.
Axios Okay fixed that
╰─λ inxi -EAZ 0 (0.000s) < 07:42:25
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-232.current status: kernel-api
Server-1: PulseAudio v: 15.0 status: active
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Can't even get to record anything....
╰─λ bluetoothctl 0 (0.023s) < 07:48:19
Agent registered
[bluetooth]# power on
No default controller available
I updated (on unstable) and restarted, bluetooth wasn't even there. I removed the manually installed driver and rebooted, bluetooth was there and it was enabled (at least it appeared so in system settings). I tried to pair my headphones and it sat on the scanning screen for a while. I closed it and tried again, this time it said my device wasn't pairable.
Now if I run inxi -EAZ i'm back to No data found on my bluetooth device.......
Brucehankins I have lost track on your issue now.
and where it stands
Axios no worries, it's still borked. When I restart or fresh boot, I can "see" my Intel ax200 Bluetooth and it's registered.
As soon as I try and connect to anything or run commands with bluetoothctl the device disappears. Bluetoothctl and inxi both say there is no Bluetooth device. If I reboot, it pops back up, but I still can't connect to anything.
Well, I have suggestions.
- Install kernel lts. Does BT work, run the commands related to blutetoothctl, inxi -E and other helpful.
- Start Solus Live. Does BT work, run the commands related to blutetoothctl, inxi -E and other helpful.
- Start another Linux Live distribution. (as above)