You are not logged in.
I've been busy troubleshooting the same issue with this Bluetooth dongle that many others are. I've tried everything that I can find to get it working without success. However, I found something unexpected. The dongle starts working after I resume from suspend. As soon as I start up from suspend, the dongle light starts to flash and auto-connects. As long as I don't restart the computer, it just continues to work. I've also noticed when I reboot the computer, that the light is also flashing until I log into the computer. Once logged in, it stops working. I would like for others to test this on their computers to see if it works for them. If it does, I'm hoping that someone will know how to fix/automate this so we don't have to suspend/wake-up to get it working.
Offline
For clarity : the dongle is connected through usb and uses btusb driver ?
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)dmesg shows several acpi errors which usually means your system has low level issues.
[ 0.000000] DMI: Gigabyte Technology Co., Ltd. B365M GAMING HD/B365M GAMING HD, BIOS F1 05/30/2019[1] shows that is the very first firmware for this board and gigabyte released 3 newer versions .
I recommend you configure early microcode loading and update your firmware.
Let us know if the issue is still present after that.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hey Lone_Wolf...Thanks for the reply. I've update the bios to the newest available as per your recommendation. I've installed the Intel microcode and it is set up for early loading. I've run a new probe, but I don't see any changes to the acpi errors. Not sure if you were asking me to confirm the dongle info, so here it is; "Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)". So far, no change. Dongle still doesn't start with a reboot. Still need to suspend the computer and wake it up to enable.
New probe
https://linux-hardware.org/?probe=6c7968cf75
Last edited by Sugarcrisp (2021-06-27 13:56:17)
Offline
[ 9.938620] usb 1-3: unable to read config index 0 descriptor/all
[ 9.938631] usb 1-3: can't read configurations, error -110
[ 10.061816] usb 1-3: new full-speed USB device number 3 using xhci_hcd
[ 10.203402] usb 1-3: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
[ 10.203414] usb 1-3: New USB device strings: Mfr=0, Product=2, SerialNumber=...
[ 10.203419] usb 1-3: Product: USB1.1-ATry starting without the dongle plugged in and plug it in AFTER the system has booted.
[ 4.837153] systemd[1]: RTC configured in localtime, applying delta of 420 minutes to system time.Are you dual booting with windows ?
If not, then setting the hardware realtime clock to localtime is a bad idea.
https://wiki.archlinux.org/title/System … ware_clock for details
The probe links you posted both mention something that may block further troubleshooting :
System ArcoLinux Rolling
Are you using archlinux or arcolinux ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
No dual boot. I didn't know about the hardware clock. I read the wiki link you shared and the warning with the way I had the clock set. I've corrected it. Thanks!
I tried rebooting the system and then plugging in the bluetooth. Still no change (had to suspend and wake it up to get it working).
I started with archlinux, but I've also added the arcolinux databases and many of their settings.
Offline
I recently purchased the same bluetooth and have the same problem.
Offline