Hi There!!
I am using Fedora 34 and my system got recently updated to
Kernel: x86_64 Linux 5.13.4-200.fc34.x86_64
I don’t know what is the problem is with bluetooth so any body got similar problem or Help me how to fix this issue?
What exactly is the problem? Your screenshot is showing that Bluetooth is turned off.
nmcli radio all; rfkill list all
$ nmcli radio all; rfkill list all
~]$ nmcli radio all; rfkill list all
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled disabled
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
sudo rfkill unblock bluetooth
Hi,
I have encountered a similar issue. After i updated yesterday; after rebooting into the same kernel-version you mentioned. Although i am not sure this is necessarily related to the kernel version.
At first activating bluetooth using the gnome menu or settings was not possible at all, after another update + reboot i could connect a bluetooth headset using the settings dialog for a few seconds. The connection breaks off almost immediately and the bluetooth settings crashed after several tries to reconnect the device.
Did you manage to solve your issues?
Regarding hardware:
Lenovo E495 with a intel Wi-Fi 6 card (combined wifi + bluetooth)
Bluetooth errors started cropping up since my system upgraded to 5.13.4
My system is on Fedora 33
Bluetooth: hci0: sending initial HCI reset command failed (-110) kernel
Bluetooth: hci0: command 0x0c03 tx timeout kernel
@imoj
Hi There!!
Welcome to Ask Fedora Project
The kernel version and hardware exactly matches with mine and I guess this problem belongs to the kernel or any other update I just did
I am too using Lenovo and I am also waiting for someone to help me…
Lets have patience
Yours,
@jetstream Can you tell us your bluetooth hardware info
If this issue is hovering over Lenovo Laptop or Computer devices
Or wifi 6 + Bluetooth devices then we might have to approach this issue in different way
Use the previous version of the kernel until the problem is fixed.
@superadmin mine is an Intel Dual Band Wireless-AC 3160
card
As a matter of fact, last night, I reverted to using the latest in 5.12.*
I had on my system, like @vgaetera has suggested.
sudo grubby --set-default /boot/vmlinuz-5.12.15-200.fc33.x86_64
I see the following output:
─ hciconfig;hciconfig -a hci0;lsmod |grep bt;dmesg | grep tooth ─╯
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
hci0: Type: Primary Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT
ebtable_nat 16384 0
ebtable_broute 16384 0
ebtable_filter 16384 0
ebtables 40960 3 ebtable_nat,ebtable_filter,ebtable_broute
btusb 65536 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
btintel 32768 1 btusb
bluetooth 675840 12 btrtl,btintel,btbcm,bnep,btusb
[ 7.258580] Bluetooth: Core ver 2.22
[ 7.258603] Bluetooth: HCI device and connection manager initialized
[ 7.258606] Bluetooth: HCI socket layer initialized
[ 7.258608] Bluetooth: L2CAP socket layer initialized
[ 7.258611] Bluetooth: SCO socket layer initialized
[ 9.569575] Bluetooth: hci0: command 0x0c03 tx timeout
[ 11.440348] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.440352] Bluetooth: BNEP filters: protocol multicast
[ 11.440356] Bluetooth: BNEP socket layer initialized
[ 17.697508] Bluetooth: hci0: sending initial HCI reset command failed (-110)
@vgaetera
seems like switching back to previous kernel didn’t fix the issue
As with @jetstream The issue was not resolved even without switching back to the preivous kernel…
Hope this issue gets resolved fast
Yours,
Try this:
sudo dnf downgrade linux-firmware
And then reboot with the previous version of the kernel.
Sorry … bit slow catching up (I’m not on the linux box that frequently)
@superadmin you’re right, I’m seeing in the logs the bluetooth errors still coming up, but I am not too fussed as long as the system is generally working. Am happy to help with any info if I can.
So, I am now running kernel 5.12.15-200.fc33.x86_64
for the foreseeable future ( displaylink-rpm currently supports upto kernel-5.12
and I need that.
@vgaetera I applied the linux-firmware downgrade
you suggested. The bluetooth error is still there. Like I said, it’s not blocking me, but including the logs here in case it helps to solve a problem.
Jul 30 22:29:04 nucv210 kernel: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Jul 30 22:29:06 nucv210 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Jul 30 22:29:14 nucv210 kernel: Bluetooth: hci0: sending initial HCI reset command failed (-110)
Jul 30 22:29:15 nucv210 pulseaudio[1554]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Jul 30 22:29:34 nucv210 pulseaudio[2451]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
I had a pairing issue with my bluetooth device. For me, downgrading bluez package, pairing bluetooth device and then upgrading it fixed the issue.
I found the answer when i asked on reddit
(https://www.reddit.com/r/Fedora/comments/o5lb5a/bluetooth_audio_not_working_properly_on_fedora_34/h2ptn4b?utm_source=share&utm_medium=web2x&context=3).
It still acts up every now and then if i keep turning bluetooth off and on repeatedly, but the pairing and audio seem to work fine now.
@vgaetera probably you have already seen these two below …
Bluetooth updates have gone in the last firmware update 20210716 in this commit and back in 20210315.
Am pretty sure BT errors have started showing up very recently.
So, if a firmware downgrade didn’t make the errors go away, I’m wondering too what else has impacted the bluetooth subsystem.
@maverick97
Can you help me with upgrading to the latest firmware after downgrading?
How do we do it?