Microsoft Bluetooth mouse on suse9.2 "HID create error 25"
 

This one is not urgent, it just buggs the hell out of me that i cant figure it out.

I'm sitting here with my new Bluetooth mouse, "Microsoft Wireless IntelliMouse Explorer for Bluetooth" to be exact. I'm running suse 9.2.

Right now everything is working fine. Niema problema as they say in poland. (Dont correct me if i'm wrong-). However, to get here i have to manually kill hidd and restart it using the sript "/etc/rc.d/bluetooth" on every startup. Then i can wiggle my mouse and everything works after a few seconds.

I have found two ways of starting the bluetooth services. Either i enable it in a special setup utility or i add it to my runlevel-scripts. I cant do both because then it complains. If i disble the bluetooth services in my bluetooth setup utility (a yast module if anyone cares) and enable it in my runlevel editor everything works great. If i do the other way around it simply does not work as it is supposed to.

Using the second startup method i get the messages
"New HID device 00:50:F2:7F:38:07 (Microsoft Five Button Mouse)"
"HID create error 25 (Inappropriate ioctl for device)"
otherwise i just get the first line and everything works.

Firstly what does error 25 mean? Secondly what does it matter when i start the "hdd --server"?

Some of my own buggtracking:
If i start using the erroronous method i cannot run "hidd --search" "--connect" or "--kill" and "--show" gives nothing. If i remove the batteries from the mouse i can find it by doing "--search" right afterwards. Fine i thought, now i can just run as normal. But if i leave the mouse for long enough i get back to the same state as before. If the problem is that the bluetooth subsystem is started to early in the boot process, why does it stop working again after a reconnect?

Summary:
Firstly what does error 25 mean?
Secondly what does it matter when i start the "hdd --server"?
If the problem is that the bluetooth subsystem is started to early in the boot process, why does it stop working again after a reconnect?

Thanks for your interest
//Per Oeberg