You are not logged in.
Pages: 1
Topic closed
Since yesterday or the day before, Bluetooth on my desktop machine has stopped working. The machine also seems to be taking more time than usual to start up, probably because it gets stuck here for a minute or so (taken from journalctl):
2月 26 12:47:34 archlinux kernel: usb 1-8: new high-speed USB device number 3 using xhci_hcd
2月 26 12:47:40 archlinux kernel: usb 1-8: device descriptor read/64, error -110
2月 26 12:47:55 archlinux kernel: usb 1-8: device descriptor read/64, error -110
2月 26 12:47:56 archlinux kernel: usb 1-8: new high-speed USB device number 4 using xhci_hcd
2月 26 12:48:01 archlinux kernel: usb 1-8: device descriptor read/64, error -110
2月 26 12:48:16 archlinux kernel: usb 1-8: device descriptor read/64, error -110
2月 26 12:48:17 archlinux kernel: usb usb1-port8: attempt power cycle
2月 26 12:48:17 archlinux kernel: usb 1-8: new high-speed USB device number 5 using xhci_hcd
2月 26 12:48:22 archlinux kernel: usb 1-8: Device not responding to setup address.
2月 26 12:48:27 archlinux kernel: usb 1-8: Device not responding to setup address.
2月 26 12:48:27 archlinux kernel: usb 1-8: device not accepting address 5, error -71
2月 26 12:48:27 archlinux kernel: usb 1-8: new high-speed USB device number 6 using xhci_hcd
2月 26 12:48:32 archlinux kernel: usb 1-8: Device not responding to setup address.
2月 26 12:48:35 archlinux systemd-udevd[318]: usb1: Worker [349] processing SEQNUM=3217 is taking a long time
2月 26 12:48:37 archlinux kernel: usb 1-8: Device not responding to setup address.
2月 26 12:48:37 archlinux kernel: usb 1-8: device not accepting address 6, error -71
2月 26 12:48:37 archlinux kernel: usb usb1-port8: unable to enumerate USB deviceIndeed, the Bluetooth functionality doesn't appear in lsusb:
$ lsusb
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 26ce:01a2 ASRock LED Controller
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 04bb:0141 I-O Data Device, Inc. I-O DATA HDPC-UT
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0b05:1910 ASUSTek Computer, Inc. TUF GAMING M3
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 0853:011d Topre Corporation Realforce 108U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubbut the Wi-Fi part of the same module, a MediaTek MT7921K, does appear in lspci, and is functioning correctly:
$ lspci
...
08:00.0 Network controller: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz
...Things that might be related are the motherboard firmware I recently updated, and possibly some package updates, though I'm not sure which, if either at all, has caused it. Is this maybe a bug somewhere, or have I misconfigured something?
I did make sure that Bluetooth functionality is "Auto" or "Enabled" in UEFI settings, and nothing changed between the two settings. I even tried "Disabled" and the same message appears in journalctl, so maybe the setting doesn't actually hide it.
The CPU is a Ryzen 9 7900X, and the motherboard is an ASRock B650M PG Riptide Wi-Fi.
Last edited by daigennki (2023-02-27 12:15:43)
Offline
That looks like a hardware problem to me. It has the look of a bad cable.
I don't think this is the issue, but verify that the version numbers reported by pacman -Q linux and uname -a match.
Last edited by ewaller (2023-02-26 15:16:28)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
That looks like a hardware problem to me. It has the look of a bad cable.
I don't think this is the issue, but verify that the version numbers reported by pacman -Q linux and uname -a match.
Uh oh, I sure hope I won't have to RMA this motherboard. The Wi-Fi module that provides Bluetooth is something like an M.2 card I believe, so any connection problem would be on a circuit board.
I'll just wait for the next firmware update, since ASRock seems to be updating it every other week or so. At the moment I only use Bluetooth for my DualSense, so I can just use USB for that until the Bluetooth gets fixed.
And yes, pacman -Q linux and uname -a match with 6.1.12.arch1-1.
Last edited by daigennki (2023-02-26 15:25:34)
Offline
Oh, nevermind all that. Looks like you were right about it being a hardware problem, so thanks for pointing me in that direction. I turned off the main power switch on the power supply, and after leaving it off for several minutes then turning it on, it's all working now. No long startup anymore, and my DualSense connects via Bluetooth just fine. Perhaps the module relied on standby power, so it never got fully reset after having some sort of problem.
I think I had a similar issue with a laptop I had in the past where fully disconnecting power fixed it, even though it was on Windows 10 and with Wi-Fi instead of Bluetooth. For the record, in that case I think it involved something like disconnecting the battery if it's removable, or if the battery isn't removable, holding down the power button for a very long time.
Anyways, marking this as solved!
Last edited by daigennki (2023-02-27 12:17:57)
Offline
Any chance that happened right after you had used Windows? Is Windows "Fast Boot" enabled? Are you sure? Microsoft has a bad reputation for silently turning it on after it has turned off by users.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Nope, I've only used this machine with Linux. No dual boot.
Last edited by daigennki (2023-02-28 00:44:55)
Offline
I turned off the main power switch on the power supply, and after leaving it off for several minutes then turning it on, it's all working now. No long startup anymore, and my DualSense connects via Bluetooth just fine. Perhaps the module relied on standby power, so it never got fully reset after having some sort of problem.
Unsure what the etiquette here is regarding necroposting. Didn't read anything in the Code of Conduct about it and thought it might be useful to someone who comes across this down the line to hear that this post helped me.
I had the exact same issue over two years after this post was made after pulling a kernel, firmware, and microcode update in one command. Like the OP, I had to shut down completely and boot back up for Bluetooth to start working again.
Last edited by SIGSTART (2025-09-18 20:48:36)
Offline
I don't know if it was wrong, but it helped me. Who knows how long I would have chased my tail before shutting down, but bluetooth worked again after a shut down and seems to hold on restarts. Note for others : I did an update that included mediatek(my laptops combined bluetooth/wifi controller), on the restart the bluetooth was down:
bluetoothctl show
No default controller available
Offline
I had the same problem. It was an Acer Swift3. Bluetoothctl returned no devices, and dmesg returned an error about being unable to enumerate the USB device.
Everything pointed to a hardware issue.
But in my case, everything worked after resetting the battery (the Acer Swift3 has this option).
I hope my experience helps someone else.
Offline
Glad to hear and yes this can often help with weird USB issues, however note that you're responding to a three year old thread https://wiki.archlinux.org/title/Genera … bumping%22 closing this.
Online
Pages: 1
Topic closed