Changes between Initial Version and Version 1 of HowTo/Bluetooth/Enabling

Timestamp:

May 9, 2007, 10:40:23 AM (18 years ago)

Author:

harisk

Comment:

—

HowTo/Bluetooth/Enabling

@@ +1 @@
+This page explains how to create an image with enabled Bluetooth.
+
+== Current images with BT enabled ==
+
+ * bluetooth-0.1.0.ndz built on baseline-1.0.9.nzd with old madwifi and kernel 2.6.12
+ * bluetooth-0.1.1.ndz built on baseline-1.0.9.nzd with old madwifi and kernel 2.6.12
+
+The reason to keep this is that madwifi allows to change transmit power. Version 0.1.1 contains old madwifi with ability to fix transmission rate using iwconfig, but does not support libmac
+To Do: USB Bluetooth key chain has to be reinserted in order to be recognized.
+
+ * bluetooth-0.2.0.ndz built on baseline-2.0.ndz with hacked nodeAgent to support new madwifi
+
+== Making Bluetooth work ==
+
+The kernel must have USB and Bluetooth support enabled. If that is not the case:
+
+{{{
+/usr/src/<path to your kernel source># make menuconfig
+}}}
+
+Compile the kernel and reboot. There should be /proc/bus/usb directory created.
+
+{{{
+apt-get install bluetooth
+/etc/init.d/bluetooth start
+}}}
+
+After that you should be able to see something like:
+{{{
+node1-1:~# hciconfig
+hci0:   Type: USB
+        BD Address: 00:0A:3A:53:D4:82 ACL MTU: 192:8 SCO MTU: 64:8
+        UP RUNNING PSCAN ISCAN 
+        RX bytes:395 acl:0 sco:0 events:17 errors:0
+        TX bytes:313 acl:0 sco:0 commands:16 errors:0
+}}}
+
+In order to save the image, and be able to login to the node by means other than the serial console delete the following file if exists:
+
+{{{
+node1-1:/etc/udev/rules.d# rm z25_persistent-net.rules
+}}}
+
+Otherwise, saving an image causes the interfaces to "shift" from eth0 and eth1 to eth2 and eth3, and the node is after imaging accessible only through the serial console.
+
+== Some usefull links ==
+
+http://www.gentoo.org/doc/en/bluetooth-guide.xml
+
+http://wiki.debian.org/Bluetooth
+
+http://www.linux-usb.org/USB-guide/book1.html