Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:guides:bluetooth [2010/05/28 20:43] – add toc lineaen:guides:bluetooth [2010/08/22 15:39] (current) – linea
Line 6: Line 6:
 Do following steps 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 
-  tazpkg get-install linux-bluetooth+  # tazpkg get-install linux-bluetooth
 The first package contains the Official Linux Bluetooth protocol stack www.bluez.org and the second contains the kernel modules related to bluetooth. The first package contains the Official Linux Bluetooth protocol stack www.bluez.org and the second contains the kernel modules related to bluetooth.
 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" to 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
Line 27: Line 27:
  
 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 to ask you for 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.
Line 42: Line 42:
   root@slitaz:/home/tux#   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 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: 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:
Line 62: Line 62:
   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/linux-`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/linux-`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 replace 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/linux-`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, it 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
Line 92: Line 92:
 ===== rfcomm.conf ===== ===== 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: 
 +<file>
   #   #
   # RFCOMM configuration file.   # RFCOMM configuration file.
Line 109: Line 110:
   #       comment "Example Bluetooth device";   #       comment "Example Bluetooth device";
   }   }
 +</file>
 Now with: Now with:
-  modprobe rfcomm +  # modprobe rfcomm 
-  rfcomm bind all+  # rfcomm bind all
 You can use /dev/rfcomm0 as a 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
 
en/guides/bluetooth.1275079388.txt.gz · Last modified: (external edit)