Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
en:guides:bluetooth [2010/04/03 20:27] ernia created |
en:guides:bluetooth [2010/05/28 22:43] linea add toc |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Bluetooth ====== | ||
+ | |||
+ | ===== Introduction ===== | ||
+ | |||
This guide will help you to configure bluetooth, e.g. to use your phone as a modem. | This guide will help you to configure bluetooth, e.g. to use your phone as a modem. | ||
- | Do following step as root. | + | Do following steps as root. |
First of all you must install Slitaz packages related to bluetooth: | First of all you must install Slitaz packages related to bluetooth: | ||
tazpkg get-install bluez | tazpkg get-install bluez | ||
Line 7: | Line 11: | ||
Now you can launch the bluetooth daemon: | Now you can launch the bluetooth daemon: | ||
bluetoothd | bluetoothd | ||
- | and load the module required by your local bluetooth device, this is very likely btusb | + | And load the module required by your local bluetooth device, this is very likely btusb: |
modprobe btusb | modprobe btusb | ||
- | If btusb is the module you need the command "hcitool dev" will show you the local device address: | + | If btusb is the module you need the command "hcitool dev" to show you the local device address: |
root@slitaz:/home/tux# hcitool dev | root@slitaz:/home/tux# hcitool dev | ||
Devices: | Devices: | ||
hci0 00:02:72:xx:xx:xx | hci0 00:02:72:xx:xx:xx | ||
- | If the command "hcitool dev" does not show you any hci* device you must detect which module you need and repeat previous step until you have a hci* device. | + | If the command "hcitool dev" does not show you any hci* device you must detect which module you need and repeat the previous step until you have a hci* device. |
Now that you have hci* you can run the "hcitool scan" command to show you if there is any discoverable device nearby. | Now that you have hci* you can run the "hcitool scan" command to show you if there is any discoverable device nearby. | ||
- | So if you are searching e.g. your phone remember to put it in discoverable mode. | + | So if you are searching, e.g. your phone, remember to put it in discoverable mode: |
root@slitaz:/home/tux# hcitool scan | root@slitaz:/home/tux# hcitool scan | ||
Scanning ... | Scanning ... | ||
Line 24: | Line 28: | ||
If you want to start the pairing from the remote device you need to put your local device in discoverable mode: | If you want to start the pairing from the remote device you need to put your local device in discoverable mode: | ||
hciconfig hci0 piscan | hciconfig hci0 piscan | ||
- | Now launch bluez-simple-agent, start the pairing from the remote device and wait for bluez-simple-agent ask you the pin code needed to pair. | + | |
+ | Now launch bluez-simple-agent, start the pairing from the remote device and wait for bluez-simple-agent to ask you for the pin code needed to pair. | ||
This code will be the same one you typed on the phone. When you are done you need to kill bluez-simple-agent with Ctrl-c: | This code will be the same one you typed on the phone. When you are done you need to kill bluez-simple-agent with Ctrl-c: | ||
root@slitaz:/home/tux# hciconfig hci0 piscan | root@slitaz:/home/tux# hciconfig hci0 piscan | ||
Line 35: | Line 40: | ||
mainloop.run() | mainloop.run() | ||
KeyboardInterrupt | KeyboardInterrupt | ||
- | root@slitaz:/home/tu | + | root@slitaz:/home/tux# |
- | Put your local device back in undiscoverable mode | + | Put your local device back in undiscoverable mode: |
hciconfig hci0 pscan | hciconfig hci0 pscan | ||
- | If you want to start the pairing from you local device you do it using bluez-simple-agent with the hci* of your local device and the address of the device you discovered with "hcitool scan". In this case you will choose the code in bluez-simple-agent and type the same code on the remote device: | + | If you want to start the pairing from your local device you can do it using bluez-simple-agent with the hci* of your local device and the address of the device you discovered with "hcitool scan". In this case you will choose the pin in bluez-simple-agent and type the same pin on the remote device: |
root@slitaz:/home/tux# bluez-simple-agent hci0 00:18:C5:xx:xx:xx | root@slitaz:/home/tux# bluez-simple-agent hci0 00:18:C5:xx:xx:xx | ||
RequestPinCode (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx) | RequestPinCode (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx) | ||
Line 46: | Line 51: | ||
New device (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx) | New device (/org/bluez/3078/hci0/dev_00_18_C5_xx_xx_xx) | ||
root@slitaz:/home/tux# | root@slitaz:/home/tux# | ||
- | Be fast because bluez-simple-agent have a timeout which i don't know how to set (suggestions?) | + | Be fast because bluez-simple-agent has a timeout which I don't know how to set (suggestions?) |
- | Now you have your two devices paired, i will go on with the phone as a modem example, i don't have other experience with bluetooth devices. | + | ===== Use a phone as a modem ===== |
- | To use your phone as a modem you need the rfcomm module. In the moment i am writing this guide the rfcomm module of Slitaz is compiled without tty support. You can check if this is the case with the following commands: | + | |
+ | Now you have your two devices paired, i will go on with the phone as a modem example, I don't have other experiences with bluetooth devices. | ||
+ | To use your phone as a modem you need the rfcomm module. At the moment I am writing this guide the rfcomm module of Slitaz is compiled without tty support. You can check if this is the case with the following commands: | ||
root@slitaz:/home/tux# zcat /proc/config.gz | grep RFCOMM | root@slitaz:/home/tux# zcat /proc/config.gz | grep RFCOMM | ||
CONFIG_BT_RFCOMM=m | CONFIG_BT_RFCOMM=m | ||
# CONFIG_BT_RFCOMM_TTY is not set | # CONFIG_BT_RFCOMM_TTY is not set | ||
root@slitaz:/home/tux# | root@slitaz:/home/tux# | ||
- | If CONFIG_BT_RFCOMM_TTY is not =y you must recompile the module with tty support. Install linux-source | + | If CONFIG_BT_RFCOMM_TTY is not =y you must recompile the module with tty support. Install linux-source: |
tazpkg get-install linux-source | tazpkg get-install linux-source | ||
- | cd in /usr/src/`uname -r`/ and give this command | + | cd in /usr/src/linux-`uname -r`/ and give this command: |
make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm | make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm | ||
- | This will build only the rfcomm module with tty support. You will find it in /usr/src/`uname -r`/net/bluetooth/rfcomm/rfcomm.ko. | + | This will build only the rfcomm module with tty support. You will find it in /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko. |
- | Now you can delete the old rfcomm module and change it with your module: | + | Now you can delete the old rfcomm module and replace it with your module: |
rm /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz | rm /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz | ||
- | cp /usr/src/`uname -r`/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/ | + | cp /usr/src/linux-`uname -r`/net/bluetooth/rfcomm/rfcomm.ko /lib/modules/`uname -r`/kernel/net/bluetooth/rfcomm/ |
depmod -a | depmod -a | ||
- | Now that we have a working rfcomm module we must detect the channel where the phone dialup service is listening. | + | Now that we have a working rfcomm module we must detect the channel where the phone dialup service is listening: |
sdptool browse 00:18:C5:xx:xx:xx | sdptool browse 00:18:C5:xx:xx:xx | ||
- | where 00:18:C5:xx:xx:xx is the address of your phone, will give a list with the services available on your phone. The one you are looking for is Dial-up networking or DUN. | + | Where 00:18:C5:xx:xx:xx is the address of your phone, it will give a list with the services available on your phone. The one you are looking for is Dial-up networking or DUN: |
Service Name: Dial-up networking | Service Name: Dial-up networking | ||
Service RecHandle: 0x10000 | Service RecHandle: 0x10000 | ||
Line 82: | Line 89: | ||
"Dialup Networking" (0x1103) | "Dialup Networking" (0x1103) | ||
Version: 0x0100 | Version: 0x0100 | ||
+ | | ||
+ | ===== rfcomm.conf ===== | ||
+ | |||
As you can see it is listening on channel 1, so you edit /etc/bluetooth/rfcomm.conf this way: | As you can see it is listening on channel 1, so you edit /etc/bluetooth/rfcomm.conf this way: | ||
# | # | ||
Line 99: | Line 109: | ||
# comment "Example Bluetooth device"; | # comment "Example Bluetooth device"; | ||
} | } | ||
- | now with | + | Now with: |
modprobe rfcomm | modprobe rfcomm | ||
rfcomm bind all | rfcomm bind all | ||
- | you can use rfcomm0 as you modem in a wvdial script. | + | You can use /dev/rfcomm0 as a modem in a wvdial script. |
- | you may want to check this guide http://doc.slitaz.org/en:guides:dialup | + | You may want to check this guide http://doc.slitaz.org/en:guides:dialup |
+ | |||
+ | ---- | ||
+ | \\ | ||
+ | ^ Page Review Section ^^ | ||
+ | |Quality| Good | | ||
+ | |Review| Minor Updates | | ||
+ | |Priority| Medium | | ||
+ | |Problems| add a [[http://forum.slitaz.org|forum post link]]| | ||
+ | |::: | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]| | ||
+ | |How to Improve| Add tazhw setup bluetooth ; Please create "sections" for toc| | ||
+ | |::: | | | ||
+ | \\ | ||
+ | ---- |