bluetooth does not work after resuming computer from suspend; modprobing bluetooth modules does not help
I am running latest Arch Linux and GNOME desktop.
I sometimes put my computer to sleep, but after resuming I find that my bluetooth does not work. I can't turn it on from gnome system settings.
I tried running sudo modprobe btusb bluetooth couple of times and also tried restarting bluetooth service sudo systemctl restart bluetooth.service and failed. I don't get any error on running those commands, please help.
arch-linux bluetooth suspend
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 1 more comment
I am running latest Arch Linux and GNOME desktop.
I sometimes put my computer to sleep, but after resuming I find that my bluetooth does not work. I can't turn it on from gnome system settings.
I tried running sudo modprobe btusb bluetooth couple of times and also tried restarting bluetooth service sudo systemctl restart bluetooth.service and failed. I don't get any error on running those commands, please help.
arch-linux bluetooth suspend
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actualsystemctl restartfailed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output ofbluetoothctl, for instance? Is there any error message when turning on the power withbluetoothctl? Doesdmesgsay anything? Please give more diagnostic.
– Martin Nyolt
Sep 21 '16 at 9:08
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
Checkrfkill list allas it looks like bluetooth may have been disabled
– Jeremy31
Jan 12 '17 at 22:58
|
show 1 more comment
I am running latest Arch Linux and GNOME desktop.
I sometimes put my computer to sleep, but after resuming I find that my bluetooth does not work. I can't turn it on from gnome system settings.
I tried running sudo modprobe btusb bluetooth couple of times and also tried restarting bluetooth service sudo systemctl restart bluetooth.service and failed. I don't get any error on running those commands, please help.
arch-linux bluetooth suspend
I am running latest Arch Linux and GNOME desktop.
I sometimes put my computer to sleep, but after resuming I find that my bluetooth does not work. I can't turn it on from gnome system settings.
I tried running sudo modprobe btusb bluetooth couple of times and also tried restarting bluetooth service sudo systemctl restart bluetooth.service and failed. I don't get any error on running those commands, please help.
arch-linux bluetooth suspend
arch-linux bluetooth suspend
asked Sep 20 '16 at 9:10
Edward TorvaldsEdward Torvalds
2,59373263
2,59373263
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actualsystemctl restartfailed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output ofbluetoothctl, for instance? Is there any error message when turning on the power withbluetoothctl? Doesdmesgsay anything? Please give more diagnostic.
– Martin Nyolt
Sep 21 '16 at 9:08
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
Checkrfkill list allas it looks like bluetooth may have been disabled
– Jeremy31
Jan 12 '17 at 22:58
|
show 1 more comment
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actualsystemctl restartfailed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output ofbluetoothctl, for instance? Is there any error message when turning on the power withbluetoothctl? Doesdmesgsay anything? Please give more diagnostic.
– Martin Nyolt
Sep 21 '16 at 9:08
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
Checkrfkill list allas it looks like bluetooth may have been disabled
– Jeremy31
Jan 12 '17 at 22:58
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actual
systemctl restart failed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output of bluetoothctl, for instance? Is there any error message when turning on the power with bluetoothctl? Does dmesg say anything? Please give more diagnostic.– Martin Nyolt
Sep 21 '16 at 9:08
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actual
systemctl restart failed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output of bluetoothctl, for instance? Is there any error message when turning on the power with bluetoothctl? Does dmesg say anything? Please give more diagnostic.– Martin Nyolt
Sep 21 '16 at 9:08
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
Check
rfkill list all as it looks like bluetooth may have been disabled– Jeremy31
Jan 12 '17 at 22:58
Check
rfkill list all as it looks like bluetooth may have been disabled– Jeremy31
Jan 12 '17 at 22:58
|
show 1 more comment
1 Answer
1
active
oldest
votes
I had this problem, I have the Atheros AR9485. It seems that you have to enable bluetooth coexistence manually. In this website
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
It says that the bluetooth card is AR3012.
The only way I solved it was doing (I added this to a systemd sleep script)
modprobe -r ath9k &&
modprobe -r ath3k &&
modprobe ath9k btcoex_enable=1 &&
modprobe ath3k
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f311045%2fbluetooth-does-not-work-after-resuming-computer-from-suspend-modprobing-bluetoo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had this problem, I have the Atheros AR9485. It seems that you have to enable bluetooth coexistence manually. In this website
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
It says that the bluetooth card is AR3012.
The only way I solved it was doing (I added this to a systemd sleep script)
modprobe -r ath9k &&
modprobe -r ath3k &&
modprobe ath9k btcoex_enable=1 &&
modprobe ath3k
add a comment |
I had this problem, I have the Atheros AR9485. It seems that you have to enable bluetooth coexistence manually. In this website
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
It says that the bluetooth card is AR3012.
The only way I solved it was doing (I added this to a systemd sleep script)
modprobe -r ath9k &&
modprobe -r ath3k &&
modprobe ath9k btcoex_enable=1 &&
modprobe ath3k
add a comment |
I had this problem, I have the Atheros AR9485. It seems that you have to enable bluetooth coexistence manually. In this website
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
It says that the bluetooth card is AR3012.
The only way I solved it was doing (I added this to a systemd sleep script)
modprobe -r ath9k &&
modprobe -r ath3k &&
modprobe ath9k btcoex_enable=1 &&
modprobe ath3k
I had this problem, I have the Atheros AR9485. It seems that you have to enable bluetooth coexistence manually. In this website
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
It says that the bluetooth card is AR3012.
The only way I solved it was doing (I added this to a systemd sleep script)
modprobe -r ath9k &&
modprobe -r ath3k &&
modprobe ath9k btcoex_enable=1 &&
modprobe ath3k
edited Jan 28 '18 at 20:55
yeti
2,40611225
2,40611225
answered Jan 28 '18 at 20:36
SantiagoSantiago
1
1
add a comment |
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.
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%2f311045%2fbluetooth-does-not-work-after-resuming-computer-from-suspend-modprobing-bluetoo%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
At least, systemd tells you some reason why the service could not be started, e.g. the exit code. This should also be in the journal - the relevant except would be helpful.
– Martin Nyolt
Sep 20 '16 at 12:49
@MartinNyolt systemd wouldn't show error, according to systemd there is nothing wrong with bluetooth service but still bluetooth won't work
– Edward Torvalds
Sep 21 '16 at 7:17
Sorry, then I misunderstood you saying that restarting the service failed - I thought you meant the actual
systemctl restartfailed. But the essence of my previous comment is the same: without more information from you, we cannot do much. What is the output ofbluetoothctl, for instance? Is there any error message when turning on the power withbluetoothctl? Doesdmesgsay anything? Please give more diagnostic.– Martin Nyolt
Sep 21 '16 at 9:08
@MartinNyolt here is the link to some outputs. systemctl, dmesg,bluetoothctl don't give any kind of error, I checked all of them when my bluetooth wasn't starting
– Edward Torvalds
Oct 3 '16 at 6:30
Check
rfkill list allas it looks like bluetooth may have been disabled– Jeremy31
Jan 12 '17 at 22:58