Differences between version 15 and predecessor to the previous major change of ServerInstallBluetoothSetupHOWTO.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 15 | Last edited on Sunday, November 7, 2010 11:02:10 am | by ElroyLiddington | Revert |
| Older page: | version 1 | Last edited on Saturday, October 30, 2010 9:56:18 pm | by ElroyLiddington | Revert |
@@ -34,11 +34,119 @@
"/etc/init.d/bluetooth restart"
<br>
+! 4.0 Check to see if our BT adapter is installed and what its capabilities are
+ "hciconfig -a" Should give something _similar_ to
+ hci0: Type: USB <br>
+ BD Address: 00:10:60:32:3A:93 ACL MTU: 384:8 SCO MTU: 64:8<br>
+ UP RUNNING PSCAN<br>
+ RX bytes:6448 acl:0 sco:0 events:270 errors:0<br>
+ TX bytes:1309 acl:0 sco:0 commands:125 errors:0<br>
+ Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80<br>
+ Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3<br>
+ Link policy: RSWITCH HOLD SNIFF PARK<br>
+ Link mode: SLAVE ACCEPT<br>
+ Name: 'xxxxxx-0' HostName removed for security reasons<br>
+ Class: 0x4a0100<br>
+ Service Classes: Networking, Capturing, Telephony<br>
+ Device Class: Computer, Uncategorized<br>
+ HCI Ver: 2.0 (0x3) HCI Rev: 0x7a6 LMP Ver: 2.0 (0x3) LMP Subver: 0x7a6<br>
+ Manufacturer: Cambridge Silicon Radio (10)<br>
+
+! 4.1 Check our BT adapters hardware MAC Address and see if the bluez BT system has done any configuring with it
+
+
+ "hciconfig version"
+
+ hci0: Type: USB<br>
+ BD Address: 00:10:60:32:3A:93 ACL MTU: 384:8 SCO MTU: 64:8<br>
+ UP RUNNING PSCAN <br>
+ RX bytes:961 acl:0 sco:0 events:27 errors:0<br>
+ TX bytes:361 acl:0 sco:0 commands:27 errors:0<br>
+
+ Check in /var/lib/bluetooth/00:10:60:32:3A:93 NOTE These numbers/colons constitute a MAC Address - note the fact that the MAC address is the same in 4.1 as it is in 4.0<br>
+
+
+<br>
+
+! 5. Configure 'main.conf' in /etc/bluetooth - these appear to be the new location for BlueZ config
+
+ 'Default adapter name' is used to label your BT adapter, so when you do a BT search on other BT devices, this is the name your Computer shows up as<br>
+ Normally the default 'Name = %h-%d' uses your Computers HostName for the BT adapters name - recommend leaving as-is.
+
+<br>
+
+ 'Default device class'<br>
+ "0x4a0100"<br>
+ NOTE: this is from what "hciconfig -a" gave us - find 'Class' and copy the similar 0x0xxxx hex? code into your main.conf - my main.conf had 0x000100 as the default value
+
+<br>
+
+! 5.1 Make your BT adapter discoverable when you do a BT search from other BT devices
+
+ "hciconfig hci0 piscan" - Check back to 'hciconfig' command - note it has a 'UP RUNNING PSCAN' section in it - re-run the (hciconfig) command, note it now has 'UP RUNNING PSCAN ISCAN ' in it - this must be what makes the BT adapter discoverable (i.e. viewable)
+
+
+
+
+<br>
+
+! 6. "tail -f /var/log/daemon.log" - Constantly outputs any info from daemons (server processes eg dhcpd, bluetoothd, sambad) to screen
+
+
+! 6.1 Stop the service called 'dbus' and 'bluetooth' - restart both making sure 'dbus' is started BEFORE 'bluetooth'<br>
+
+ Do "/etc/init.d/bluetooth stop" and "/etc/init.d/dbus stop" and /etc/init.d/dbus start" and "/etc/init.d/bluetooth start"<br>
+
+
+! 6.2 So far we have tried to do some configuring - now lets see if anything works
+
+ Try to do a search for new devices 'Pair New Device' is what I tried on my cellphone.
+
+ w00P! - I found my computer 'xxxxxx-0'<br>
+
+ Doing the 'tail -f ...daemon.log' command, and trying to connect to my computer gives me<br>
+
+ '
+ bluetoothd[8643]: pin_code_request (sba=00:10:60:32:3A:93, dba=00:18:0F:DE:98:8D)<br>
+ bluetoothd[8643]: No agent available for 0 request<br>
+
+ '<br>
+
+
+ bluetoothd[8643]: pin_code_request (sba=00:10:60:32:3A:93, dba=00:18:0F:DE:98:8D)
+Nov 7 18:54:12 bluetoothd[8643]: No agent available for 0 request
+
+
+
+<br>
+
+! 7. Unplugging, waiting a few seconds and then re-plugging my USB BT adapter
+
+ bluetoothd[8154]: Adapter /org/bluez/8153/hci0 has been disabled<br>
+ bluetoothd[8154]: Stopping security manager 0<br>
+ bluetoothd[8154]: HCI dev 0 unregistered<br>
+ bluetoothd[8154]: Unregister path: /org/bluez/8153/hci0<br>
+ bluetoothd[8154]: HCI dev 0 registered<br>
+ bluetoothd[8154]: HCI dev 0 up<br>
+ bluetoothd[8154]: Starting security manager 0<br>
+ bluetoothd[8154]: Adapter /org/bluez/8153/hci0 has been enabled<br>
+
+
+<br>
+
+! 8.
+
+<br>
+
+! 9.
+
+
+<br>
! Misc notes to self
'bluetoothd' is the bluetooth daemon - config files are located in '/etc/default/bluetooth' - this appears to be where BT mice/keyboards are configured.
@@ -55,8 +163,11 @@
<br>
'/var/lib/bluetooth/device-MAC???-address/linkkeys' appears to be the folder (and file 'linkkeys') where the devices 'Pairing' key or 'linkkey' is kept...
+<br>
+
+ Check out the scripts "./simple-agent" (dot-slash to execute) hidden in '/usr/share/doc/bluez/examples/'
<br>
@@ -72,4 +183,8 @@
<br>
http://www.linuxquestions.org/questions/debian-26/bluetooth-problems-715839/
+
+<br>
+
+http://digitalcommons.calpoly.edu/cpesp/20/ - Click on 'Download' for more info on what she was researching
