connect bluetooth mouse automatically

laurentwahl · 07-25-2005, 04:55 AM

Panic42 said:

Quote:

Now that you have run hidd --connect once, you should not need to do
it ever again; hidd and your mouse should automatically connect when you
waggle your mouse.

But this is my problem, I have to run hidd --connect at each startup. without this, I can waggle my mouse as much as I want but he doesn't connect automatically.

With

Code:

ps -A | grep hidd

he finds nothing.

With hidd --show he doesn't show at startup a connection, but after i have run hidd --connect, he shows:

Quote:

hidd --show
00:07:61:0D:F6:1D HID Boot Device [046d:b001] connected [boot-protocol]

panic42 · 07-25-2005, 05:27 AM

Quote:

Originally posted by laurentwahl
With

Code:

ps -A | grep hidd

he finds nothing.

...I wonder who "he" is..?

Anyway, this is the place to continue your bug search.
Your problem is clearly that the hidd server has NOT
started; you will have to find out why---perhaps by looking
in your system log.

A few possibly interesting points from my log:

Code:

kernel: usbcore: registered new driver hiddev
kernel: usbcore: registered new driver usbhid
kernel: drivers/usb/input/hid-core.c: v2.01:USB HID core driver
hidd[1813]: Bluetooth HID daemon
hidd[1813]: New HID device 00:07:61:07:19:22 (Logitech Bluetooth Mouse)

/etc/modprobe.conf contains

Code:

alias net-pf-31 bluetooth

When you have run hidd --server, running ps -A | grep hidd
should produce something like

Code:

root      1813     1  0 08:58 ?        00:00:00 /usr/bin/hidd --server

Happy bug-hunting,

-- Arne

lmcilwain · 07-25-2005, 08:12 AM

Holly Crap it worked. Thanks for the help Arne.

panic42 · 07-25-2005, 08:34 AM

Quote:

Originally posted by lmcilwain
Holly Crap it worked. Thanks for the help Arne.

Glad it helped.

Can you enlighten us with what you
have done different now that makes it work?

-- Arne

lmcilwain · 07-25-2005, 12:00 PM

The problem was exactly as you stated. The man page says that you have to have "--" infront of your hidd option. So I followed your directions to the tee.

hidd --search
hidd --connnect device<hex>
Hit the pair botton on the bottom of my mouse.

panic42 · 07-25-2005, 01:55 PM

Quote:

Originally posted by lmcilwain
hidd --search
hidd --connnect device<hex>
Hit the pair botton on the bottom of my mouse.

Just for the record: You should only need one of the above
commands; the top one searches for your mouse and connects
it, while you manually indicate the BT address to connect in
the bottom one.

And now you should never need them again! Just make sure
hidd --server is started, and waggle your mouse.

-- Arne

laurentwahl · 07-26-2005, 03:21 AM

I added now: alias net-pf-31 bluetooth to my /etc/modprobe.conf file. But this didn't help.

My log file contains only these lines:

Quote:

Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.8
usbcore: registered new driver hci_usb

panic42 · 07-26-2005, 04:09 AM

Hmmm...it seems as if the hid kernel modules haven't been
loaded. Strange. I am running FC4 kernel 2.6.12 which apparently
has them built into the kernel. Perhaps you should do a 'locate hiddev'
or similar.

-- Arne

lmcilwain · 07-26-2005, 01:29 PM

Despite my mouse working I find that my mouse is also not reconnecting and I need to reconnect after a long period of not being used or on bootup. I actually have to manually reconnect each time I want to use it after not using it for a bit of time. I created a script that helps me to do this a little faster but its still annoying. I am going to back track through this particular thread and see if I can find some other things that may help.

laurentwahl · 07-27-2005, 03:13 AM

with locate hiddev, I receive the message:

Quote:

locate hiddev
warning: locate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old
warning: Please make sure the daily cron job is enabled in /etc/updatedb.conf
/sys/bus/usb/drivers/hiddev
/usr/libexec/hald-probe-hiddev
/usr/src/kernels/2.6.11-1.1369_FC4-i686/include/linux/hiddev.h
/usr/src/kernels/2.6.11-1.1369_FC4-i686/include/config/usb/hiddev.h
/usr/include/linux/hiddev.h

This doesn't make a change.

My computer also disconnects after a long period, my problem is the same as lmcilwain's

panic42 · 07-27-2005, 04:24 AM

Quote:

Originally posted by laurentwahl
with locate hiddev, I receive the message:...

I'm sorry I was being rather vague. When I said "...or similar"
I intended that you yourself would think of relevant things to look
for. Relevant things might be hid.ko or hid-core or usbhid or...

As I said, your problem seems to be that the hidd server does
not start (or perhaps crashes immediately), because running

hidd --server

and then

ps -A | grep hidd

should result in something like

root 1801 1 0 08:01 ? 00:00:00 /usr/bin/hidd --server

Question: are you running hidd --server as root?

Another point: You should consider editing /etc/updatedb.conf to avoid the
error message from locate.

-- Arne

laurentwahl · 07-28-2005, 04:42 AM

When I run hidd --server as root, is works.
I added this now to my /etc/rc.d/rc.local file.
Thank you for your help!

panic42 · 07-28-2005, 04:56 AM

Quote:

Originally posted by laurentwahl
When I run hidd --server as root, is works.
I added this now to my /etc/rc.d/rc.local file.

Perhaps it would be better to do this in /etc/init.d/hidd,
a file which I believe you have. Then enable hidd at the runlevel
you are running -- this can typically be done using some gui
runlevel editor (e.g., Server Settings->Services in Gnome).

By the way, could you please tell me whether you see any
difference in your log file when running hidd as root and as non-root?

-- Arne

laurentwahl · 07-28-2005, 03:56 PM

I don't know how to enable hidd at the runlevel I'm running.

When I run hidd --server as root in log file is written:

Quote:

Jul 28 22:06:41 localhost kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Jul 28 22:06:41 localhost hidd[3205]: Bluetooth HID daemon
Jul 28 22:06:44 localhost hidd[3205]: New HID device 00:07:61:0D:F6:1D (Logitech Bluetooth Mouse)

With ps -A I receive exactly the same message, as as normal user:

Quote:

ps -A | grep hidd
3205 ? 00:00:00 hidd

As normal user, my log file:

Quote:

Jul 28 21:57:57 localhost kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Jul 28 21:57:57 localhost hidd[3174]: Bluetooth HID daemon
Jul 28 21:58:05 localhost hidd[3174]: New HID device 00:07:61:0D:F6:1D (Logitech Bluetooth Mouse)
Jul 28 21:58:05 localhost hidd[3174]: HID create error 13 (Permission denied)
Jul 28 21:58:07 localhost hidd[3174]: New HID device 00:07:61:0D:F6:1D (Logitech Bluetooth Mouse)
Jul 28 21:58:07 localhost hidd[3174]: HID create error 13 (Permission denied)
Jul 28 21:58:09 localhost hidd[3174]: New HID device 00:07:61:0D:F6:1D (Logitech Bluetooth Mouse)
Jul 28 21:58:09 localhost hidd[3174]: HID create error 13 (Permission denied)

and

Quote:

ps -A | grep hidd
3174 ? 00:00:00 hidd

panic42 · 07-29-2005, 01:48 AM

Quote:

Originally posted by laurentwahl
I don't know how to enable hidd at the runlevel I'm running.

If you're running Gnome, you can find it in Desktop->System Settings->Server Settings->Services. I guess KDE has something similar.

Quote:

As normal user, my log file:
Jul 28 21:58:05 localhost hidd[3174]: HID create error 13 (Permission denied)

Interesting. Do you happen to remember my post#11 (19 posts ago), where I suggested you monitored your /var/log/messages when debugging? This can be done by

tail -f /var/log/messages

Quote:

ps -A | grep hidd
3174 ? 00:00:00 hidd

This contradicts your post#16 .

It is hard to perform collaborative debugging when suggestions are silently ignored and information cannot be trusted.

-- Arne