I have a Logitech Bluetooth mouse working fine in Slack-12.1.
Does Microsoft actually make anything, like that mouse, or is
it just rebranded? I've had M$ mice before and they were Logitech
OEM mice with a M$ label.
Here's some information to share with you:
Code:
mingdao@jeremiah:~$ dmesg | grep -i bluetooth
Bluetooth: Core ver 2.11
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.9
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
input: Logitech Bluetooth Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/hci0/acl000761D17A8C/input/input9
I just rebooted into Slackware and the bluetooth mouse works fine.
Code:
mingdao@jeremiah:~$ ls -l /etc/rc.d/rc.bluetooth.conf
-rw-r--r-- 1 root root 1050 2008-10-27 21:14 /etc/rc.d/rc.bluetooth.conf
mingdao@jeremiah:~$ cat /etc/rc.d/rc.bluetooth.conf
# /etc/rc.d/rc.bluetooth.conf
#
# This file contains the configuration for the Bluetooth subsystem, BlueZ.
# The lines below allow you to configure which BlueZ daemons will be started,
# along with any daemon-specific options.
# Allowed values for each (unless otherwise noted) are "true" and "false"
# =============================================================================
# The SDP daemon allows clients to detect supported Bluetooth services
SDPD_ENABLE=true
# The HID daemon supports Bluetooth Human Interface Devices
HIDD_ENABLE=true
HIDD_OPTIONS="--server"
# This switches your Bluetooth device into HCI mode, use this if your input
# device does not support Bluetooth HID
HID2HCI_ENABLE=false
# The RFCOMM daemon is used to simulate serial connections over Bluetooth
RFCOMM_ENABLE=true
# The DUN daemon is used for Dial Up Networking over Bluetooth
DUND_ENABLE=false
DUND_OPTIONS="--listen --persist --msdun call dun"
# The PAN daemon is used to setup a Bluetooth network.
PAND_ENABLE=false
PAND_OPTIONS="--listen --role NAP"
Code:
mingdao@jeremiah:~$ ls -l /etc/bluetooth/hcid.conf
-rw-r--r-- 1 root root 1243 2008-10-27 14:18 /etc/bluetooth/hcid.conf
mingdao@jeremiah:~$ cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "1234";
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";
# Local device class
class 0x000100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
discovto 0;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
Code:
mingdao@jeremiah:~$ sudo ls -l /etc/bluetooth/passkeys/default
-rw-r--r-- 1 root root 5 2008-10-27 17:33 /etc/bluetooth/passkeys/default
mingdao@jeremiah:~$ sudo cat /etc/bluetooth/passkeys/default
1234
I never press the button, run a command again, or anything.
It works in:
Slackware-12.1
Kubuntu-8.04.1-desktop-amd64
Windows XP Pro
Windows Vista Ultimate 32-bit
Hope this information is of some use and help to you.
Edit: Make sure this file is executable:
mingdao@jeremiah:~$ ls -l /usr/sbin/hcid
-rwxr-xr-x 1 root root 253640 2008-09-18 14:01 /usr/sbin/hcid