Bluetooth unavailable after Timeshift Recovery

Hardware Support
1

OS: Zorin OS 18.1 x86_64 Host: A9 Max
Kernel: 7.0.0-30-generic DE: GNOME 46.0
WM: Wayland Terminal: gnome-terminal
CPU: AMD Ryzen AI 9 HX 370 w/ Radeon
GPU: AMD ATI c7:00.0 Device 150e

-> No ''Additional Drivers'' in Software & Updates offered

Dual Boot system with Win11: has Fast Start disabled
BIOS-UEFI: Secure Boot, Fast Boot and TPM disabled

Bluetooth Problem:
Bluetooth Device (WLAN included): MediaTek MT7925
MT7925 (M.2-Modul on the Platine)
├── Wi-Fi → PCIe-Connection → Driver: mt7925e
└── BT → internal USB-Connection → Driver: btusb + btmtk
BT was not working after Timeshift recovery and Reboot. Additional Reboot did not help.

rfkill list -> didn‘t show any error
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

sudo systemctl restart bluetooth
bluetoothctl list

-> Can't init device hci0: Connection timed out (110)

sudo dmesg | grep -i -E 'hci|firmware|bluetooth'
->MediaTek BT firmware timeout
:
[ 12.960394] Bluetooth: hci0: Execution of wmt command timed out
[ 12.960409] Bluetooth: hci0: Failed to send wmt patch dwnld (-110)
[ 12.960425] Bluetooth: hci0: Failed to set up firmware (-110)
[ 12.960428] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
:

Did a complete PC Power Cycle: -> afterwards BT was back working
– Have Shutdown the PC
– Disconnected the PCs Power supply for 1 minute
– Reconnected the Power supply and PC rebooted

To avoid further Autosuspend btusb:

echo "options btusb enable_autosuspend=N" | sudo tee /etc/modprobe.d/btusb.conf
sudo update-initramfs -u
sudo reboot

My questions:
– Is this "not awake out of USB-Autosuspend" a known linux kernel bug which might be fixed during next Zorin Updates?
– Are there further changes I could make to avoid the BT problem?

1 Like
2

So, You used Timeshift to go back to an earlier State. Do You remind what was changed during this earlier State and the current State from what You have go back?

1 Like
3

Thanks for your answer. I am late as I had a long working day.

Even it was not clever to do that, I tried to install a Beta app TMOG (.deb) and the installation itself hang. I went directly back to the system state with the timeshift snap which was just one hour ago before this victim app installation.

Have the timeshift LOG File about the recovery yesterday. Here parts with bluetooth and firmware mentioned:
image
image

image
image1068×600 141 KB

So far the BT problem did not occur again.
Please let me know if further info is needed.

1 Like
4

Is this adressing Bluetooth in any Way? I mean, does it use Bluetooth or is it for controlling a bluetooth Device. Stuff like that.

So, Your Bluetooth works now again, yes?

1 Like
5

No, the app TMOG (Taskmanager Tool) doesn't use BT and it wasn't even installed as the installation failed and hung. This was only the reason to go back to the system state one hour before I started the unfinished app installation. I used a timeshift snapshot. BT was only unavailable after timeshift recovery with reboot.

Yes, BT is working again since I did the complete PC Power Cycle (PC total Power Supply off for one minute). This brought the btusb out of the auto-suspend state.

But is it a Linux Kernel bug and can occur again until fix with Zorin OS updates?
Tried to implement a permanent solution with these commands:

echo "options btusb enable_autosuspend=N" | sudo tee /etc/modprobe.d/btusb.conf
sudo update-initramfs -u

sudo cat /etc/modprobe.d/btusb.conf
options btusb enable_autosuspend=N

Is this enough to avoid the BT problem to occur again? I am not sure about that.
May be this is unclear anyhow, so in this case let's just wait and see... as a workaround is available (PC total Power Supply off for one minute).

1 Like
6

I agree. When it works now, fine. Keep an Eye on it and test the next Days. When then all is still good, report back. You could then mark Your post as Solution.

1 Like
7

Yes, I will report after a few days.
:slightly_smiling_face:Thanks for your time and help to look at this issue!

2 Likes