From: Esben Stien <b0ef@esben-stien.name>
To: linux-wireless@vger.kernel.org
Subject: Failed to set mode: Blocked through rfkill (0x12)
Date: Tue, 14 Jun 2016 20:36:37 +0200 [thread overview]
Message-ID: <9acc4dbc18e8738dd2766b7b1531b802@esben-stien.name> (raw)
I'm trying to get bluetooth working and it sometimes does and sometimes
not;)
I've got two chips:
BCM4360 (on motherboard, which never works)
BCM20702A0 (Targus BT USB Adapter, which works mostly)
I'm only interested in the BCM20702A0, right now.
When I do sudo systemctl status bluetooth.service, I get:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
Active: active (running) since ti. 2016-06-14 15:10:14 CEST; 4h 50min
ago
Docs: man:bluetoothd(8)
Main PID: 1036 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─1036 /usr/lib/bluetooth/bluetoothd
juni 14 19:38:58 quasar bluetoothd[1036]: Failed to set mode: Blocked
through rfkill (0x12)
juni 14 19:39:10 quasar bluetoothd[1036]: Failed to set mode: Blocked
through rfkill (0x12)
juni 14 19:39:22 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:39:59 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:40:09 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:40:32 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:40:52 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:44:20 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:45:56 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
juni 14 19:46:17 quasar bluetoothd[1036]: Failed to set mode: Failed
(0x03)
, but if I check rfkill list, it's not blocked:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
Any pointers to what may cause this? Where does these messages come
from? I'm sure it works again if
I reboot, but I need to get to the bottom of this;)
reply other threads:[~2016-06-14 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9acc4dbc18e8738dd2766b7b1531b802@esben-stien.name \
--to=b0ef@esben-stien.name \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.