You are not logged in.
Pages: 1
I need the help of someone with more experience than me. Bluetoothctl doesn't work anymore. When I try to power it on, it says: "No default controller available".
journalctl says:
Sep 02 15:52:33 arch kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Sep 02 15:52:33 arch kernel: Bluetooth: hci0: Reading Intel version information failed (-110)
Sep 02 15:53:00 arch systemd-coredump[1995]: Process 1992 (gsettings-helpe) of user 1000 dumped core.
Stack trace of thread 1992:
#0 0x00007feb48bbba68 g_log_structured_array (libglib-2.0.so.0 + 0x58a68)
#1 0x00007feb48bbc086 g_log_default_handler (libglib-2.0.so.0 + 0x59086)
#2 0x00007feb48bbd449 g_logv (libglib-2.0.so.0 + 0x5a449)
#3 0x00007feb48bbd6f0 g_log (libglib-2.0.so.0 + 0x5a6f0)
#4 0x00007feb48dbfb59 n/a (libgio-2.0.so.0 + 0xdbb59)
#5 0x00007feb48ca75cf n/a (libgobject-2.0.so.0 + 0x1b5cf)
#6 0x00007feb48cacf64 n/a (libgobject-2.0.so.0 + 0x20f64)
#7 0x00007feb48cae744 g_object_new_valist (libgobject-2.0.so.0 + 0x22744)
#8 0x00007feb48caeaba g_object_new (libgobject-2.0.so.0 + 0x22aba)
#9 0x0000564e3edbc051 main (gsettings-helper + 0x1051)
#10 0x00007feb48f48152 __libc_start_main (libc.so.6 + 0x28152)
#11 0x0000564e3edbc18e n/a (gsettings-helper + 0x118e)From research I found people with the same problem, but I couldn't find a way to fix it.
Last edited by mrbear (2020-09-02 18:57:48)
Offline
I need the help of someone with more experience than me. Bluetoothctl doesn't work anymore. When I try to power it on, it says: "No default controller available".
journalctl says:
Sep 02 15:52:33 arch kernel: Bluetooth: hci0: command 0xfc05 tx timeout Sep 02 15:52:33 arch kernel: Bluetooth: hci0: Reading Intel version information failed (-110) Sep 02 15:53:00 arch systemd-coredump[1995]: Process 1992 (gsettings-helpe) of user 1000 dumped core. Stack trace of thread 1992: #0 0x00007feb48bbba68 g_log_structured_array (libglib-2.0.so.0 + 0x58a68) #1 0x00007feb48bbc086 g_log_default_handler (libglib-2.0.so.0 + 0x59086) #2 0x00007feb48bbd449 g_logv (libglib-2.0.so.0 + 0x5a449) #3 0x00007feb48bbd6f0 g_log (libglib-2.0.so.0 + 0x5a6f0) #4 0x00007feb48dbfb59 n/a (libgio-2.0.so.0 + 0xdbb59) #5 0x00007feb48ca75cf n/a (libgobject-2.0.so.0 + 0x1b5cf) #6 0x00007feb48cacf64 n/a (libgobject-2.0.so.0 + 0x20f64) #7 0x00007feb48cae744 g_object_new_valist (libgobject-2.0.so.0 + 0x22744) #8 0x00007feb48caeaba g_object_new (libgobject-2.0.so.0 + 0x22aba) #9 0x0000564e3edbc051 main (gsettings-helper + 0x1051) #10 0x00007feb48f48152 __libc_start_main (libc.so.6 + 0x28152) #11 0x0000564e3edbc18e n/a (gsettings-helper + 0x118e)From research I found people with the same problem, but I couldn't find a way to fix it.
I do think that is a hardware issue. Try some other flavor of linux like ubuntu, if bluetooth works in that, we can say for sure its a kernel or bluez issue.
If other linux destro is not available, U can try installing old kernel or LTS kernel, if that do fix your issue. This means that something changed with the drivers for your bluetooth hardware that breaks it. You can file a bug report or keep compiling your own kernel with that commit reverted.
From the logs I do strongly believe bluez is not to blame at all. I have seen this in an old laptop in which bluetooth works for some time after this similar errors come like hci0 command timeout etc..
Offline
Pages: 1