Difference between revisions of "Bluetooth mouse"

From ArchWiki
Jump to: navigation, search
m (Connecting the mouse at startup)
(Added tips for using a Bluetooth dongle)
Line 27: Line 27:
 
  # modprobe -v hci_usb bluetooth hidp l2cap
 
  # modprobe -v hci_usb bluetooth hidp l2cap
 
loads the kernel modules you need, if they weren't loaded automatically.  
 
loads the kernel modules you need, if they weren't loaded automatically.  
 +
 +
(See below for some tips if you're stuck at this point)
  
 
== Connecting the mouse ==
 
== Connecting the mouse ==
Line 54: Line 56:
  
 
Note #2: You can connect any bluetooth mouse and/or keyboard without any further configuration and without knowing the device address. You can do it by adding the --master and/or --server option in HIDD_OPTIONS depending on your device.
 
Note #2: You can connect any bluetooth mouse and/or keyboard without any further configuration and without knowing the device address. You can do it by adding the --master and/or --server option in HIDD_OPTIONS depending on your device.
 +
 +
== Troubleshooting tips ==
 +
 +
If you plan on using a USB dongle, you may also want to try
 +
# modprobe -v bluez rfcomm
 +
 +
At this point, you should get an hci0 device with
 +
# hcitool dev
 +
 +
Sometimes the device is not active right away - try starting the interface with
 +
# hciconfig hci0 up

Revision as of 11:43, 15 January 2008

Template:I18n links start Template:I18n entry Template:I18n entry Template:I18n links endThis article describes how to set up a bluetooth mouse with Archlinux. I used a Logitech v270 with a Trendnet TBW-101UB USB Bluetooth dongle, but the general process should be the same for any model.


Required software

You need the bluez-utils and bluez-libs packages from the extra repository.

Configuration

The pertinent options in /etc/conf.d/bluetooth are

HCID_ENABLE=true
HIDD_ENABLE=true

after that, start bluetooth services with

/etc/rc.d/bluetooth start

Finding out your mouse's bdaddr

It is of the form 12:34:56:78:9A:BC. Either find it in the documentation of your mouse, on the mouse itself or with the hcitool scan command.

kernel modules

The command

# modprobe -v hci_usb bluetooth hidp l2cap

loads the kernel modules you need, if they weren't loaded automatically.

(See below for some tips if you're stuck at this point)

Connecting the mouse

hidd --search
hcitool inq

are good for device scanning.

hidd --connect <bdaddr>

to actually connect.

hidd --show

will show your currently connected devices. The mouse should show up in this list. If it doesn't, press the reset button to make it discoverable.

Note: If you have the ipw3945 module loaded (wifi on HP computer) the bluetooth wont work.

Connecting the mouse at startup

Edit /etc/conf.d/bluetooth:

# Arguments to hidd
HIDD_OPTIONS="--connect <enter here your bluetooth mouse address>"

and test the new settings:

/etc/rc.d/bluetooth stop
hidd --killall (drop mouse connection)
/etc/rc.d/bluetooth start

Note: The above instructions to start the mouse at startup don't work with the current (3.11) bluetooth packages. To start the mouse at startup, add:

hidd --connect <enter here your bluetooth mouse address (No capitals!!!)>

to your /etc/rc.local file.

Note #2: You can connect any bluetooth mouse and/or keyboard without any further configuration and without knowing the device address. You can do it by adding the --master and/or --server option in HIDD_OPTIONS depending on your device.

Troubleshooting tips

If you plan on using a USB dongle, you may also want to try

# modprobe -v bluez rfcomm

At this point, you should get an hci0 device with

# hcitool dev

Sometimes the device is not active right away - try starting the interface with

# hciconfig hci0 up