This article describes how to set up a bluetooth mouse with Arch Linux. I used a Logitech v270 with a Trendnet TBW-101UB USB Bluetooth dongle, but the general process should be the same for any model.

This article describes how to set up a bluetooth mouse with Arch Linux. 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 ==

== Required software ==

−

You need the '''bluez-utils''' and '''bluez-libs''' packages from the extra repository. Looks like you also need '''dbus''' for automating things, otherwise hcid reports errors such as: "hcid[14851]: Unable to get on D-Bus". Enabling D-Bus also solved problems for local bluetooth device recognition.

+

You need the {{Pkg|bluez}} package from the extra repository.

== Configuration ==

== Configuration ==

Line 23:

Line 22:

The command

The command

−

# modprobe -v hci_usb bluetooth hidp l2cap

+

# modprobe -v btusb 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.

Line 49:

Line 48:

/etc/rc.d/bluetooth start

/etc/rc.d/bluetooth start

−

Note: The above instructions to start the mouse at startup don't work with the now outdated 3.11 bluetooth packages. New versions such as the current (3.32) packages are not affected. If you are using an older version, then to start the mouse at startup, add:

+

Note: The above instructions to start the mouse at startup do not work with the now outdated 3.11 bluetooth packages. New versions such as the current (3.32) packages are not affected. If you are using an older version, then to start the mouse at startup, add:

Note: The above instructions to start the mouse at startup do not work with the now outdated 3.11 bluetooth packages. New versions such as the current (3.32) packages are not affected. If you are using an older version, then to start the mouse at startup, add:

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 have trouble with your USB dongle, you may also want to try

# modprobe -v 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