Help - Search - Members - Calendar
Full Version: How Do I Connect My Bluetooth Mouse?
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
Capn_Fish
I just got my bluetooth card working, and now I would like to connect to my bluetooth mouse. The problem is, I don't know what command to use. Can anybody tell me what to use and how to tell if it's working (if it isn't obvious)?

Thanks in advance.
Capn_Fish
Does nobody have a solution, or am I just not seeing something obvious?
karlto
I don't have a solution, but usually info on devices and drivers can be found in dmesg... (this might give you an idea of whether it is successfully connected or not)
pelrun
I think the version of bluez that comes with pdaXrom (beta1 for me) is too old to include hidd, which is necessary for the mouse/kb support. sad.gif
Capn_Fish
Oh. sad.gif Well, I can try compiling a newer version. biggrin.gif Thanks, that accounts for "sudo hidd --connect ...." working like in Cacko.
Reaper
Actually, many of the BT mice don't use HID profile, they use SPP instead. E.g., I have Porto BM-100BK mouse which clearly isn't HID, but I think it's possible to use it even with AirCable or other BT SPP device.
Capn_Fish
I tried compiling the new bluez drivers, but am haveing some problems. ./configure works fine, but then when I say make, I get an error:

#make
make all-recursive
make[1]: Entering directory /mnt/card/bluez/bluez-libs-3.4
cp:../include: omitting directory

This is followed by the usual "leavind directory", etc.

Does anybody know what this error means, or how I can fix it?

Thanks.
Da_Blitz
that dosent look like the error thats causing the problem, try doing a make clean and give it another go, sometimes you end up with x86 binaries in the source tree that need to be cleaned out

mouse over SPP, thats the most bizare thing i have heard of. however i have seen some USB odities like that that require specific drivers even thogh they shouldnt
Reaper
QUOTE(Da_Blitz @ Sep 8 2006, 01:03 AM)
mouse over SPP, thats the most bizare thing i have heard of. however i have seen some USB odities like that that require specific drivers even thogh they shouldnt
*


Cheap&dirty solution, what else did you want from these guys at Porto? Actually, I'm not 100% sure that all such mice use SPP, I'm just 100% sure they don't use HID. And I've heard that someone had managed to connect one of these mice via AirCable (on Cacko only, though, I've heard that pdaX didn't support AirCable yet).

P.S. Genius USB Bluetooth Traveller mouse is supposed to work with both built-in XP SP2 HID drivers and WM5 HID mouse profile. It works neither with XP SP2, nor with WM5, and, what's MUCH worse, there aren't even additional WM5 drivers for ANY BT mouse, either SPP or HID, with single exception of ThinkOutside Stowaway mouse, which is VERY expensive and VERY hard to get, if you're living outside US or Western Europe. And Stowaway drivers don't support any other HID mice, no-go.
Capn_Fish
I tried the 'make clean', followed by a make with the same result. Any other ideas? Thanks for your help!
Capn_Fish
OK, I cross-compiled bluez-libs. Now I'm trying for bluez-utils. It wants a newer version of dbus than the one that comes with Beta1. I looked for a newer ipk, but didn't see one. I just built the latest version, found here:

http://www.freedesktop.org/wiki/Software/d...48f432ad7dc53c8

I installed it (but forgot to remove the old one first), but when I tried ./configure again, it still didn't find it (this seems to happen with all of the libraries I try to compile). I uninstalled it, went into /usr/lib and removed all of the dbus libs, then reinstalled it with no luck. Can anybody shed some light on this? It seems to me that I am missing some step that is important for building libraries.

Thanks in advance.
Capn_Fish
Progress update: I reflashed Beta1 and removed the dbus 0.21 package and replaced it with my own. The compiler still complains about having dbus 0.21. It looks like the gcc image doesn't know I changed the package. I found a reference to it in dbus-1.pc, and changed it. I got a new error saying that that file "appears to be empty". I assume there is some other way to fix this, but I don't know what it is. Does anybody know how to tell the zgcc image I have a new dbus package? I have tried unmounting and remounting it.

Thanks in advance!
Capn_Fish
OK, I'm giving up. Can somebody compile some bluez-utils that support hidd so I can connect my mouse. I have packages for dbus 0.92 and bluez-libs 3.4 that I think are good if somebody wants them for compiling reasons. The sources can be found in these places:

BlueZ
dbus

If there are solutions I can try myself (like rebuilding the zgcc image somehow), please let me know (either with instructions or with links to instructions, as I'm kind of a linux novice).

Thanks in advance!
pelrun
Unfortunately you need newer kernel modules to enable the HID support. I've just spent a day building and packaging bluez and So Many Rotten Dependencies (10+ ipks so far!) just to get obexftpd compiled, and it's still not enough for HID. I'm not set up to compile the modules... yet.

There are bluez 2.18 ipk's (which don't need the insane dependency updates but will support HID once the kernel modules are available) at http://justnews.ru/zaurus/ - but they don't currently include the startup scripts. I might repackage them to fix that if/when I get updated modules built.
Meanie
QUOTE(pelrun @ Sep 12 2006, 02:11 PM)
Unfortunately you need newer kernel modules to enable the HID support. I've just spent a day building and packaging bluez and So Many Rotten Dependencies (10+ ipks so far!) just to get obexftpd compiled, and it's still not enough for HID. I'm not set up to compile the modules... yet.

There are bluez 2.18 ipk's (which don't need the insane dependency updates but will support HID once the kernel modules are available) at http://justnews.ru/zaurus/ - but they don't currently include the startup scripts. I might repackage them to fix that if/when I get updated modules built.
*


"steal" them from Cacko smile.gif Most kernel modules from Sharp/Cacko work on pdaXrom provided you got the modules for the matching kernel version, ie 2.4.20 for Cxx00 or 2.4.18 for Cxx0 models...
Capn_Fish
QUOTE(pelrun @ Sep 11 2006, 11:11 PM)
Unfortunately you need newer kernel modules to enable the HID support. I've just spent a day building and packaging bluez and So Many Rotten Dependencies (10+ ipks so far!) just to get obexftpd compiled, and it's still not enough for HID. I'm not set up to compile the modules... yet.

There are bluez 2.18 ipk's (which don't need the insane dependency updates but will support HID once the kernel modules are available) at http://justnews.ru/zaurus/ - but they don't currently include the startup scripts. I might repackage them to fix that if/when I get updated modules built.
*


Please fix the modules and repackage them!
desertrat
QUOTE(Capn_Fish @ Sep 12 2006, 11:52 AM)
Please fix the modules and repackage them!

Here you are:
http://www.oesf.org/forums/index.php?showt...33&#entry141233
Capn_Fish
Thanks!!! I have hidd now, but my bluetooth card isn't recognized. I replaced my bt-uart.conf file and my bluetooth.conf from here:

http://www.oesf.org/forums/index.php?showtopic=21303

but it gives me an error when I try to restart bluetooth:

#/etc/rc.d/int.d/bluetooth restart
Shutting down Bluetooth:
Starting Bluetooth: /etc/rc.d/init.d/bluetooth: line 36: /etc/rc.d/init.d/create_dev: No such file or directory

It looks like there is a file missing that I need. Can you supply it?

Thanks for your help!!!
desertrat
QUOTE(Capn_Fish @ Sep 12 2006, 07:07 PM)
Thanks!!! I have hidd now, but my bluetooth card isn't recognized. I replaced my bt-uart.conf file and my bluetooth.conf from here:

OK in /etc/pcmcia/bluetooth there is a reference to /etc/bluetooth/bt-uart.conf, and in /etc/rc.d/init.d/bluetooth there is a reference to /etc/bluetooth/uart, I'm wondering whether they should both be referring to /etc/bluetooth/bt-uart.conf. I don't have a CF-BT card so I can't test/don't care.

QUOTE
Starting Bluetooth: /etc/rc.d/init.d/bluetooth: line 36: /etc/rc.d/init.d/create_dev: No such file or directory

It looks like there is a file missing that I need. Can you supply it?

Sorry about that, you can grab that file from the bluez-utils package in the official feeds. I will repackage my package tomorrow to include it, and also fix bt-uart.conf above if indeed it is a problem.
Capn_Fish
While my card is still recognized as "serial or modem", it does work. I can use "hcitool scan" and find my mouse, but "hidd --connect..." doesn't work. It gives me an error saying "Can't open HIDP control socket: No such file or directory". Not being a bluetooth expert, I have no idea how to fix this. It looks like I need another file. All of the other stuff works great! Thank you for helping me out!
desertrat
QUOTE(Capn_Fish @ Sep 12 2006, 11:35 PM)
While my card is still recognized as "serial or modem", it does work. I can use "hcitool scan" and find my mouse, but "hidd --connect..." doesn't work. It gives me an error saying "Can't open HIDP control socket: No such file or directory". Not being a bluetooth expert, I have no idea how to fix this. It looks like I need another file. All of the other stuff works great! Thank you for helping me out!

In /etc/rc.d/init.d/bluetooth there is this (like I said above)
CODE
UART_CONF="/etc/bluetooth/uart"

start_uarts()
{
       [ -f /sbin/hciattach -a -f $UART_CONF ] || return
       grep -v '^#' $UART_CONF | while read i; do
               /sbin/hciattach $i
       done
}

Now there is no /etc/bluetooth/uart (that file is not in any of the packages), maybe it's a typo/bug and it should really be /etc/bluetooth/bt-uart.conf (which does exist). Let me know if changing it works and I'll update the package.
pelrun
Try this before starting bluetooth:

CODE
modprobe hidp


Looks like the hid kernel module is there after all (whew) biggrin.gif
Capn_Fish
Changing that didn't seem to do anything. #modprobe hipd returns "modprobe: Can't locate module hidp"

Is there anything else I can try?
desertrat
QUOTE(Capn_Fish @ Sep 13 2006, 11:49 AM)
Changing that didn't seem to do anything. #modprobe hipd returns "modprobe: Can't locate module hidp"

I see you're using a CXXX, fwiw on my 3100 the hidp module is there (as noted by pelrun):
CODE
Module                  Size  Used by    Tainted: P
hidp                    9392   0  (unused)
hci_usb                 9088   0
mousedev                4544   1
usb-storage            64356   0
...


QUOTE
Is there anything else I can try?

Upgrade to a CXXXX? biggrin.gif
Or maybe try finding out whether Cacko has the relevant module for CXXX?
pelrun
I've attached the hidp module from beta1 - this may or may not work on rc12, although I just verified it works on beta1. Couldn't get the X server reading both the HID mouse and the touchscreen simultaneously though sad.gif

Extract it to /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/net/bluetooth/hidp/ - change the 2.4.18-etc part to match your kernel, of course.
Capn_Fish
I can connect to my mouse now, but it won't move the cursor around. #hidd in the console yields "xx:xx:xx:xx:xx:xx HID Boot Device [0000:0000] connected [boot-protocol]". What does this mean and what can I do about it? #hcitool scan identifies it correctly.

Thank you so much! I've almost got my mouse working now!
Capn_Fish
desertrat-

I did change the file names in the etc/rc.d/init.d/bluetooth file. I changed the UART_CONF= line to .../bt-uart.conf, as well as the other UART_CONF parts to the full path. It looks like there's no point, as it would have been changed anyway, but it works.
pelrun
I edited the startx script to add

CODE
-mouse /dev/input/mice


to the defaultserverargs variable, and restarted X.
Capn_Fish
IT WORKS!!! I finally got my mouse to work! Thank you!!! You were right about the touchscreen, however, I was expecting it to work until I connected the mouse.

Thanks again!!!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.