петък, 11 декември 2009 г.

Bluetooth slackware logitech hidd devices

MX5000
1. Unplug USB dongle
2. Press and hold RED BUTTON
3. Plug usb back

lsusb - on terminal - mus see sometig like that ot without

Bus 005 Device 007: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)

edit: "/etc/bluetooth/hcid.conf"
and add:

device 00:07:61:48:34:A2 {
name "Logitech MX1000 mouse";

}
and for keyboard too.
00:07:61:48:34:A2 - this is MAC address of Mouse that can be seen with :


edit: "/etc/bluetooth/main.conf"
and add:
DisablePlugins = network - for Slackware may be other distro too
if this not help and
hcid not load delete plugin from:
/usr/lib/bluetooth/plugins/network.so
This problem appears in some version of Bluez. If have some experience with manualy compiling try some versions from this site "http://www.kernel.org/pub/linux/bluetooth/".

edit: "/etc/rc.d/rc.bluetooth.conf" and
add or change to:
HIDD_ENABLE=true
HIDD_OPTIONS="--master --server" or
"HIDD_OPTIONS="--master --connect 00:07:61:45:AF:A3 --server"" where 00:07:61:45:AF:A3 is MAC of your mouse and keyboard that you add in
"/etc/bluetooth/hcid.conf"

HID2HCI_ENABLE=true - here is the place to say this way is the same way that Logitech use to connect devices like HIDD one. Simply You control this now, and may use Your Bluetooth dobgle for other devices let say Mobile too.
Other way is when you use :
hid2hci -v046d -pc709 -m logitech - here i not discus this but you can try it.

restart Bluetooth:
/etc/rc.d/rc.bluetooth restart - for slackware
do - and must see:
ps xa | grep hidd
15443 ? Ss 0:00 /usr/bin/hidd --master --server
and do the same for "hcid" must see him too


after that:
1. hciconfig hci0 up
2. hciconfig hci0 -a
and hcitool scan
3. hidd --search - RED BUTTON on the Mouse and Keyboard must be pressed while do that if you not have 3 hand do it one by one
4. Hold The BUTTON and hidd --connect 00:07:61:45:AF:A3 one boy one for MAuse nad Keyboard
If they are connected and your X is fine use it :).
in Some cases you must restart X or define them in x.org.
for You help use:
udevadm info -a -p `udevadm info -q path -n /dev/input/eventX` | less
to see devices "eventX" must be replaced.

After that look at the
top and see if hcid eat all your CPU kill it. In this case you not use it.

Links:
http://ubuntuforums.org/showthread.php?t=227057&page=2
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/29506
http://ubuntuforums.org/showthread.php?t=594624
http://ubuntuforums.org/archive/index.php/t-325455.html
http://ubuntuforums.org/showpost.php?p=6284259&postcount=37