This 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.

+

[[Category:Bluetooth]]

−

+

[[cs:Bluetooth Mouse]]

−

+

[[ru:Bluetooth Mouse]]

+

{{Merge|Bluetooth mouse configuration|This article does not include all necessary informations to make mouse work in linux. Also this article include lots of outdated info.}}

+

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 community repository.

+

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

== Configuration ==

== Configuration ==

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

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

−

HCID_ENABLE=true

HIDD_ENABLE=true

HIDD_ENABLE=true

after that, start bluetooth services with

after that, start bluetooth services with

+

# systemctl enable bluetooth.service

+

# systemctl start bluetooth.service

+

+

If you don't use systemd use following command instead

/etc/rc.d/bluetooth start

/etc/rc.d/bluetooth start

Line 20:

Line 25:

== kernel modules ==

== kernel modules ==

+

No additional actions are necessary if the bluetooth service is started using systemd. If it does not work try following.

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.

+

+

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

== Connecting the mouse ==

== Connecting the mouse ==

hidd --search

hidd --search

hcitool inq

hcitool inq

−

are good for device scanning.

+

are good for device scanning (I needed to use sudo for 'hidd --search' to automatically connect mouse, searching worked even without sudo).

hidd --connect <bdaddr>

hidd --connect <bdaddr>

to actually connect.

to actually connect.

hidd --show

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.

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 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

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