From: James Cloos <cloos@jhcloos.com>
To: linux-bluetooth@vger.kernel.org
Subject: Keeping hci interface powered
Date: Sat, 03 Jan 2015 19:27:40 -0500 [thread overview]
Message-ID: <m3oaqfl79f.fsf@carbon.jhcloos.org> (raw)
I recently assembled a box for htpc duties, including a bluetooth
keyboard.
It mostly works, except that the hci interface continually powers down.
I suspect every time the keyboard powers down,the hci does, too.
How can I prevent that?
I want the hci always to be powered, so that the keyboard can reconnect
every time I hit a key.
As it is, whenever I want to use it, I have to ssh in from another
system, run bluetoothctl and therein run power on and connect $MAC.
You can imagine how frustrating that is.
The box has a Gigabyte F2A88XN-WIFI board, which came with a laptop-
style mini-pcie card with an intel 7260 802.11n on the pcie and an
8087:07dc bluetooth on the usb.
bluetoothctl show says:
Controller 80:86:xx:xx:xx:xx
Name: BlueZ 5.27
Alias: BlueZ 5.27
Class: 0x000104
Powered: yes
Discoverable: no
Pairable: yes
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d051B
Discovering: no
Thanks,
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next reply other threads:[~2015-01-04 0:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 0:27 James Cloos [this message]
2015-01-04 1:40 ` Keeping hci interface powered Marcel Holtmann
2015-01-05 21:28 ` James Cloos
2015-01-05 21:47 ` Marcel Holtmann
2015-01-05 22:45 ` James Cloos
2015-01-05 23:29 ` Marcel Holtmann
2015-01-06 0:33 ` James Cloos
2015-01-06 1:32 ` Marcel Holtmann
2015-01-27 2:47 ` Marcel Holtmann
2015-01-06 1:01 ` BlueZ question about HID profile Gilbert Gao
2015-01-06 1:38 ` Marcel Holtmann
2015-01-06 2:25 ` Gilbert Gao
2015-01-23 10:10 ` Gilbert Gao
2015-01-26 16:12 ` Luiz Augusto von Dentz
2015-01-27 3:44 ` Gilbert Gao
2015-01-27 8:50 ` Luiz Augusto von Dentz
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=m3oaqfl79f.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox