Bluetoothctl: No default controller available
up vote
12
down vote
favorite
I'm having issues connecting my Logitech K810 Bluetooth keyboard in Debian Jessie with BlueZ version 5.23-1, kernel 3.16.0-4.
The keyboard works fine most of the time but sometimes it doesn't work at all and bluetoothctl gives me the error that the controller is unavailable.
When this occurs, hciconfig still recognizes the device and I get this output:
# hciconfig hci0 up
# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 40:2C:F4:68:02:CA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:21820 acl:1132 sco:0 events:68 errors:0
TX bytes:1182 acl:11 sco:0 commands:53 errors:0
But no devices are shown in the bluetoothctl prompt and it gives me this output:
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
Rebooting or sometimes suspending/resuming fixes the issue: bluetoothctl will again recognize both the controller and the keyboard which works again.
Bluetooth is consistently hard and soft unblocked according to rfkill.
The relevant output from lspci -v, I guess would be this:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0400000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
I didn't have this problem with the same hardware in Debian Wheezy.
What could it be the bluetooth controller to be unavailable at times?
keyboard bluetooth bluez
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
add a comment |
up vote
12
down vote
favorite
I'm having issues connecting my Logitech K810 Bluetooth keyboard in Debian Jessie with BlueZ version 5.23-1, kernel 3.16.0-4.
The keyboard works fine most of the time but sometimes it doesn't work at all and bluetoothctl gives me the error that the controller is unavailable.
When this occurs, hciconfig still recognizes the device and I get this output:
# hciconfig hci0 up
# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 40:2C:F4:68:02:CA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:21820 acl:1132 sco:0 events:68 errors:0
TX bytes:1182 acl:11 sco:0 commands:53 errors:0
But no devices are shown in the bluetoothctl prompt and it gives me this output:
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
Rebooting or sometimes suspending/resuming fixes the issue: bluetoothctl will again recognize both the controller and the keyboard which works again.
Bluetooth is consistently hard and soft unblocked according to rfkill.
The relevant output from lspci -v, I guess would be this:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0400000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
I didn't have this problem with the same hardware in Debian Wheezy.
What could it be the bluetooth controller to be unavailable at times?
keyboard bluetooth bluez
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
1
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).
– Marcus
May 22 '17 at 14:39
add a comment |
up vote
12
down vote
favorite
up vote
12
down vote
favorite
I'm having issues connecting my Logitech K810 Bluetooth keyboard in Debian Jessie with BlueZ version 5.23-1, kernel 3.16.0-4.
The keyboard works fine most of the time but sometimes it doesn't work at all and bluetoothctl gives me the error that the controller is unavailable.
When this occurs, hciconfig still recognizes the device and I get this output:
# hciconfig hci0 up
# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 40:2C:F4:68:02:CA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:21820 acl:1132 sco:0 events:68 errors:0
TX bytes:1182 acl:11 sco:0 commands:53 errors:0
But no devices are shown in the bluetoothctl prompt and it gives me this output:
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
Rebooting or sometimes suspending/resuming fixes the issue: bluetoothctl will again recognize both the controller and the keyboard which works again.
Bluetooth is consistently hard and soft unblocked according to rfkill.
The relevant output from lspci -v, I guess would be this:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0400000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
I didn't have this problem with the same hardware in Debian Wheezy.
What could it be the bluetooth controller to be unavailable at times?
keyboard bluetooth bluez
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
I'm having issues connecting my Logitech K810 Bluetooth keyboard in Debian Jessie with BlueZ version 5.23-1, kernel 3.16.0-4.
The keyboard works fine most of the time but sometimes it doesn't work at all and bluetoothctl gives me the error that the controller is unavailable.
When this occurs, hciconfig still recognizes the device and I get this output:
# hciconfig hci0 up
# hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 40:2C:F4:68:02:CA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:21820 acl:1132 sco:0 events:68 errors:0
TX bytes:1182 acl:11 sco:0 commands:53 errors:0
But no devices are shown in the bluetoothctl prompt and it gives me this output:
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
Rebooting or sometimes suspending/resuming fixes the issue: bluetoothctl will again recognize both the controller and the keyboard which works again.
Bluetooth is consistently hard and soft unblocked according to rfkill.
The relevant output from lspci -v, I guess would be this:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f0400000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
I didn't have this problem with the same hardware in Debian Wheezy.
What could it be the bluetooth controller to be unavailable at times?
keyboard bluetooth bluez
keyboard bluetooth bluez
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
edited Nov 26 '14 at 17:46
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
asked Nov 25 '14 at 21:16
MajorBriggs
6512919
6512919
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
1
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).
– Marcus
May 22 '17 at 14:39
add a comment |
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
1
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).
– Marcus
May 22 '17 at 14:39
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
1
1
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (
modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).– Marcus
May 22 '17 at 14:39
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (
modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).– Marcus
May 22 '17 at 14:39
add a comment |
4 Answers
4
active
oldest
votes
up vote
1
down vote
I believe the answer is simply to run bluetoothctl with sudo.
Thus, sudo bluetoothctl. Then every command works fine power on, agent on etc. with no errors.
Confirmed working on Raspian Stretch.
answered Nov 28 at 15:20
jamescampbell
1114
add a comment |
up vote
0
down vote
Is kernel update an option?
Have you tried the latest linux-firmware package?
Also you can try the suggestions in secion "About iwldvm support and known issues" in here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
answered Nov 29 '17 at 6:54
gat1
617
add a comment |
up vote
0
down vote
Maybe try systemctl start hciuart
answered Aug 1 at 17:48
akhilcjacob
314
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
add a comment |
up vote
-1
down vote
First enable bluetooth manually with the GUI. this is how it worked for me.
i know this post is old, but it worked for me. Just search in your main menu for "bluetooth"
(On my current mint 18 sarah it is like that)
You can then come back and try the commands with "power off"
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I believe the answer is simply to run bluetoothctl with sudo.
Thus, sudo bluetoothctl. Then every command works fine power on, agent on etc. with no errors.
Confirmed working on Raspian Stretch.
answered Nov 28 at 15:20
jamescampbell
1114
add a comment |
up vote
1
down vote
I believe the answer is simply to run bluetoothctl with sudo.
Thus, sudo bluetoothctl. Then every command works fine power on, agent on etc. with no errors.
Confirmed working on Raspian Stretch.
answered Nov 28 at 15:20
jamescampbell
1114
add a comment |
up vote
1
down vote
up vote
1
down vote
I believe the answer is simply to run bluetoothctl with sudo.
Thus, sudo bluetoothctl. Then every command works fine power on, agent on etc. with no errors.
Confirmed working on Raspian Stretch.
answered Nov 28 at 15:20
jamescampbell
1114
I believe the answer is simply to run bluetoothctl with sudo.
Thus, sudo bluetoothctl. Then every command works fine power on, agent on etc. with no errors.
Confirmed working on Raspian Stretch.
answered Nov 28 at 15:20
jamescampbell
1114
edited Nov 29 at 6:32
answered Nov 28 at 15:20
jamescampbell
1114
answered Nov 28 at 15:20
jamescampbell
1114
answered Nov 28 at 15:20
jamescampbell
1114
1114
add a comment |
add a comment |
up vote
0
down vote
Is kernel update an option?
Have you tried the latest linux-firmware package?
Also you can try the suggestions in secion "About iwldvm support and known issues" in here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
answered Nov 29 '17 at 6:54
gat1
617
add a comment |
up vote
0
down vote
Is kernel update an option?
Have you tried the latest linux-firmware package?
Also you can try the suggestions in secion "About iwldvm support and known issues" in here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
answered Nov 29 '17 at 6:54
gat1
617
add a comment |
up vote
0
down vote
up vote
0
down vote
Is kernel update an option?
Have you tried the latest linux-firmware package?
Also you can try the suggestions in secion "About iwldvm support and known issues" in here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
answered Nov 29 '17 at 6:54
gat1
617
Is kernel update an option?
Have you tried the latest linux-firmware package?
Also you can try the suggestions in secion "About iwldvm support and known issues" in here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
answered Nov 29 '17 at 6:54
gat1
617
answered Nov 29 '17 at 6:54
gat1
617
answered Nov 29 '17 at 6:54
gat1
617
answered Nov 29 '17 at 6:54
gat1
617
617
add a comment |
add a comment |
up vote
0
down vote
Maybe try systemctl start hciuart
answered Aug 1 at 17:48
akhilcjacob
314
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
add a comment |
up vote
0
down vote
Maybe try systemctl start hciuart
answered Aug 1 at 17:48
akhilcjacob
314
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
add a comment |
up vote
0
down vote
up vote
0
down vote
Maybe try systemctl start hciuart
answered Aug 1 at 17:48
akhilcjacob
314
Maybe try systemctl start hciuart
answered Aug 1 at 17:48
akhilcjacob
314
answered Aug 1 at 17:48
akhilcjacob
314
answered Aug 1 at 17:48
akhilcjacob
314
answered Aug 1 at 17:48
akhilcjacob
314
314
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
add a comment |
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
Welcome on the Unix SE! I suggest to explain, what you are doing and why.
– peterh
Aug 1 at 18:34
add a comment |
up vote
-1
down vote
First enable bluetooth manually with the GUI. this is how it worked for me.
i know this post is old, but it worked for me. Just search in your main menu for "bluetooth"
(On my current mint 18 sarah it is like that)
You can then come back and try the commands with "power off"
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
add a comment |
up vote
-1
down vote
First enable bluetooth manually with the GUI. this is how it worked for me.
i know this post is old, but it worked for me. Just search in your main menu for "bluetooth"
(On my current mint 18 sarah it is like that)
You can then come back and try the commands with "power off"
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
add a comment |
up vote
-1
down vote
up vote
-1
down vote
First enable bluetooth manually with the GUI. this is how it worked for me.
i know this post is old, but it worked for me. Just search in your main menu for "bluetooth"
(On my current mint 18 sarah it is like that)
You can then come back and try the commands with "power off"
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
First enable bluetooth manually with the GUI. this is how it worked for me.
i know this post is old, but it worked for me. Just search in your main menu for "bluetooth"
(On my current mint 18 sarah it is like that)
You can then come back and try the commands with "power off"
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
answered Feb 10 '17 at 11:36
IDontLikestackoverflow
1
1
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
add a comment |
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
What GUI? What exact steps? How would powering it off help establish a connection?
– Jeff Schaller
Feb 10 '17 at 12:08
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f169931%2fbluetoothctl-no-default-controller-available%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the same problem in OSMC running in Raspberry Pi. Did you find a solution? Share it if you have one, please.
– user2109718
Jun 19 '15 at 0:21
No, haven't found a solution ...
– MajorBriggs
Jun 27 '15 at 8:39
I have encountered the same issue with OSMC on a Raspberry Pi. The keyboard shows up when scanning with hcitool. Bluetoothctl commands result in 'No default controller available'.
– Dallas
Aug 30 '15 at 15:10
1
After coming across this question during my investigations several times now: There still seems to be no answer, however, sometimes removing (
modprobe -r btusb) and adding (modprobe btusb) the kernel module helps to get the controller back (so you can avoid doing a full reboot).– Marcus
May 22 '17 at 14:39