bluetooth mouse/keyboard blues
Locked
12
12
bluetooth mouse/keyboard blues
 
|
I am having trouble setting up a bluetooth mouse and keyboard on FreeBSD
7.0-BETA1. I followed the instructions from the handbook and what I found on google here... http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html . The keyboard does not work at all, but I am able to pull a configuration from bthidcontrol. The mouse buttons work, but I can't move the cursor. These issues occur in both on the console and in X. I included log messages and config files below. Any help would be greatly appreciated. Thanks Eric Millbrandt 11:58 emillbrandt@slate:/home/emillbrandt# uname -a FreeBSD slate.coldhaus.com 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 29 23:40:03 EDT 2007 [hidden email]:/usr/obj/usr/src/sys/SLATE i386 from dmesg Nov 4 10:57:38 slate kernel: ubt0: <vendor 0x0a12 product 0x0001, class 224/1, rev 2.00/19.58, addr 2> on uhub3 Nov 4 10:57:38 slate kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 Nov 4 10:57:38 slate kernel: ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 Nov 4 10:57:38 slate kernel: WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() Nov 4 10:57:38 slate kernel: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Nov 4 11:51:27 slate bthidd[1453]: Opening outbound session for 00:1b:63:fc:6c:2c (new_device=1, reconnect_initiate=1) Nov 4 11:51:57 slate bthidd[1453]: Could not connect to 00:1b:63:fc:6c:2c. Host is down (64) Nov 4 11:52:27 slate kernel: kbd3 at vkbd0 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a keyboard query device { bdaddr 00:1b:63:fc:6c:2c; control_psm 0x11; interrupt_psm 0x13; reconnect_initiate true; battery_power false; normally_connectable true; hid_descriptor { 0x05 0x01 0x09 0x06 0xa1 0x01 0x85 0x01 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 0x75 0x08 0x95 0x01 0x81 0x01 0x75 0x01 0x95 0x05 0x05 0x08 0x19 0x01 0x29 0x05 0x91 0x02 0x75 0x03 0x95 0x01 0x91 0x01 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff 0x00 0x05 0x07 0x19 0x00 0x2a 0xff 0x00 0x81 0x00 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x47 0x05 0x01 0x09 0x06 0xa1 0x02 0x05 0x06 0x09 0x20 0x15 0x00 0x26 0xff 0x00 0x75 0x08 0x95 0x01 0x81 0x02 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x11 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x81 0x01 0x75 0x01 0x95 0x01 0x05 0x0c 0x09 0xb8 0x81 0x02 0x06 0xff 0x00 0x09 0x03 0x81 0x02 0x75 0x01 0x95 0x03 0x81 0x01 0x05 0x0c 0x85 0x12 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x09 0xcd 0x81 0x02 0x09 0xb3 0x81 0x02 0x09 0xb4 0x81 0x02 0x09 0xb5 0x81 0x02 0x09 0xb6 0x81 0x02 0x81 0x01 0x81 0x01 0x81 0x01 0x85 0x13 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x06 0x01 0xff 0x09 0x0a 0x81 0x02 0x75 0x01 0x95 0x07 0x81 0x01 0xc0 }; } 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a mouse query device { bdaddr 00:12:5a:57:a6:9a; control_psm 0x11; interrupt_psm 0x13; reconnect_initiate true; battery_power true; normally_connectable false; hid_descriptor { 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0x85 0x14 0x06 0x00 0xff 0x0a 0x12 0xfe 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x03 0x81 0x02 0x0a 0x11 0xfe 0x75 0x01 0x25 0x01 0x81 0x02 0x95 0x05 0x81 0x01 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0x85 0x11 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x04 0x95 0x04 0x75 0x01 0x25 0x01 0x81 0x02 0x75 0x04 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x00 0x00 0x00 0x00 0x00 0x00 0x25 0x7f 0x81 0x06 0x95 0x01 0x81 0x01 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x19 0x06 0x00 0xff 0x1a 0x18 0xff 0x2a 0x22 0xff 0x95 0x0b 0x75 0x08 0x15 0x00 0x26 0xff 0x00 0xb1 0x02 0x0a 0x23 0xff 0x95 0x01 0x75 0x01 0x25 0x01 0xb1 0x02 0x75 0x07 0xb1 0x01 0xc0 }; } I added both of these to bthidd.conf from hcsecd.conf device { bdaddr 00:1b:63:fc:6c:2c; name "Apple Wireless Keyboard"; key nokey; pin "5625264"; } device { bdaddr 00:12:5a:57:a6:9a; name "Microsoft Bluetooth Notebook Mouse 5000"; key nokey; pin "0000"; } DING! emillbrandt@slate:/home/emillbrandt# l2ping -a keyboard 0 bytes from keyboard seq_no=0 time=1905.898 ms result=0 0 bytes from keyboard seq_no=1 time=38.023 ms result=0 0 bytes from keyboard seq_no=2 time=13.141 ms result=0 11:45 emillbrandt@slate:/home/emillbrandt# l2ping -a mouse 0 bytes from mouse seq_no=0 time=1428.790 ms result=0 0 bytes from mouse seq_no=1 time=47.168 ms result=0 0 bytes from mouse seq_no=2 time=53.263 ms result=0 rc.conf hcsecd_enable="YES" bthidd_enable="YES" _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
Eric,
> I am having trouble setting up a bluetooth mouse and keyboard on FreeBSD > 7.0-BETA1. I followed the instructions from the handbook and what I > found on google here... > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html > . The keyboard does not work at all, but I am able to pull a > configuration from bthidcontrol. The mouse buttons work, but I can't > move the cursor. These issues occur in both on the console and in X. I > included log messages and config files below. Any help would be greatly > appreciated. 1) make sure you have paired bluetooth keyboard/mouse and your pc 2) what bluetooth keyboard and mouse are you using? 3) for keyboard, please make sure you have both vkbd(4) and kbdmux(4) loaded. also make sure kbdmux(4) keyboard is the default keyboard. 4) are there any messages from bthidd(8) in /var/log/messages? 5) try to run bthidd(8) in foreground to see if it prints anything strange > 11:58 emillbrandt@slate:/home/emillbrandt# uname -a > FreeBSD slate.coldhaus.com 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 29 > 23:40:03 EDT 2007 > [hidden email]:/usr/obj/usr/src/sys/SLATE i386 ok > from dmesg > Nov 4 10:57:38 slate kernel: ubt0: <vendor 0x0a12 product 0x0001, class > 224/1, rev 2.00/19.58, addr 2> on uhub3 > Nov 4 10:57:38 slate kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > Nov 4 10:57:38 slate kernel: ubt0: Interface 1 (alt.config 5) > endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, > buffer size=294 > Nov 4 10:57:38 slate kernel: WARNING: attempt to > net_add_domain(bluetooth) after domainfinalize() > Nov 4 10:57:38 slate kernel: WARNING: attempt to > net_add_domain(netgraph) after domainfinalize() > Nov 4 11:51:27 slate bthidd[1453]: Opening outbound session for > 00:1b:63:fc:6c:2c (new_device=1, reconnect_initiate=1) > Nov 4 11:51:57 slate bthidd[1453]: Could not connect to > 00:1b:63:fc:6c:2c. Host is down (64) > Nov 4 11:52:27 slate kernel: kbd3 at vkbd0 this looks mostly ok. please make sure you have bluetooth connection between your keyboard and your pc > 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a keyboard query > device { > bdaddr 00:1b:63:fc:6c:2c; > control_psm 0x11; > interrupt_psm 0x13; > reconnect_initiate true; > battery_power false; > normally_connectable true; > hid_descriptor { > 0x05 0x01 0x09 0x06 0xa1 0x01 0x85 0x01 > 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 > 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 > 0x75 0x08 0x95 0x01 0x81 0x01 0x75 0x01 > 0x95 0x05 0x05 0x08 0x19 0x01 0x29 0x05 > 0x91 0x02 0x75 0x03 0x95 0x01 0x91 0x01 > 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff > 0x00 0x05 0x07 0x19 0x00 0x2a 0xff 0x00 > 0x81 0x00 0xc0 0x05 0x0c 0x09 0x01 0xa1 > 0x01 0x85 0x47 0x05 0x01 0x09 0x06 0xa1 > 0x02 0x05 0x06 0x09 0x20 0x15 0x00 0x26 > 0xff 0x00 0x75 0x08 0x95 0x01 0x81 0x02 > 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 > 0x85 0x11 0x15 0x00 0x25 0x01 0x75 0x01 > 0x95 0x03 0x81 0x01 0x75 0x01 0x95 0x01 > 0x05 0x0c 0x09 0xb8 0x81 0x02 0x06 0xff > 0x00 0x09 0x03 0x81 0x02 0x75 0x01 0x95 > 0x03 0x81 0x01 0x05 0x0c 0x85 0x12 0x15 > 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x09 > 0xcd 0x81 0x02 0x09 0xb3 0x81 0x02 0x09 > 0xb4 0x81 0x02 0x09 0xb5 0x81 0x02 0x09 > 0xb6 0x81 0x02 0x81 0x01 0x81 0x01 0x81 > 0x01 0x85 0x13 0x15 0x00 0x25 0x01 0x75 > 0x01 0x95 0x01 0x06 0x01 0xff 0x09 0x0a > 0x81 0x02 0x75 0x01 0x95 0x07 0x81 0x01 > 0xc0 > }; > } this looks fine to me > 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a mouse query > device { > bdaddr 00:12:5a:57:a6:9a; > control_psm 0x11; > interrupt_psm 0x13; > reconnect_initiate true; > battery_power true; > normally_connectable false; > hid_descriptor { > 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 > 0x09 0x02 0x85 0x14 0x06 0x00 0xff 0x0a > 0x12 0xfe 0x95 0x01 0x75 0x02 0x15 0x00 > 0x25 0x03 0x81 0x02 0x0a 0x11 0xfe 0x75 > 0x01 0x25 0x01 0x81 0x02 0x95 0x05 0x81 > 0x01 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 > 0x05 0x01 0x09 0x02 0x85 0x11 0x09 0x01 > 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x04 > 0x95 0x04 0x75 0x01 0x25 0x01 0x81 0x02 > 0x75 0x04 0x95 0x01 0x81 0x01 0x05 0x01 > 0x09 0x30 0x09 0x31 0x09 0x38 0x00 0x00 > 0x00 0x00 0x00 0x00 0x25 0x7f 0x81 0x06 > 0x95 0x01 0x81 0x01 0xc0 0xc0 0x05 0x0c > 0x09 0x01 0xa1 0x01 0x85 0x19 0x06 0x00 > 0xff 0x1a 0x18 0xff 0x2a 0x22 0xff 0x95 > 0x0b 0x75 0x08 0x15 0x00 0x26 0xff 0x00 > 0xb1 0x02 0x0a 0x23 0xff 0x95 0x01 0x75 > 0x01 0x25 0x01 0xb1 0x02 0x75 0x07 0xb1 > 0x01 0xc0 > }; > } > I added both of these to bthidd.conf this looks fine too. > from hcsecd.conf > device { > bdaddr 00:1b:63:fc:6c:2c; > name "Apple Wireless Keyboard"; > key nokey; > pin "5625264"; > } > > device { > bdaddr 00:12:5a:57:a6:9a; > name "Microsoft Bluetooth Notebook Mouse 5000"; > key nokey; > pin "0000"; > } looks fine > DING! emillbrandt@slate:/home/emillbrandt# l2ping -a keyboard > 0 bytes from keyboard seq_no=0 time=1905.898 ms result=0 > 0 bytes from keyboard seq_no=1 time=38.023 ms result=0 > 0 bytes from keyboard seq_no=2 time=13.141 ms result=0 looks normal (some bluetooth devices will always return 0 bytes in l2cap echo response) > 11:45 emillbrandt@slate:/home/emillbrandt# l2ping -a mouse > 0 bytes from mouse seq_no=0 time=1428.790 ms result=0 > 0 bytes from mouse seq_no=1 time=47.168 ms result=0 > 0 bytes from mouse seq_no=2 time=53.263 ms result=0 looks normal (some bluetooth devices will always return 0 bytes in l2cap echo response) > rc.conf > hcsecd_enable="YES" > bthidd_enable="YES" looks ok btw, i have apple bluetooth keyboard here, so i will try to reproduce the problem. thanks, max _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
Eric,
i just tried apple keyboard with FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 20:40:41 PDT 2007 [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 and it works just fine. granted, it almost a couple month old system, but bthidd(8) code has not changed in a while, so it still should work. i'm cvsup'ing RELENG_7 and will build it later. thanks, max On 11/4/07, Maksim Yevmenkin <[hidden email]> wrote: > Eric, > > > I am having trouble setting up a bluetooth mouse and keyboard on FreeBSD > > 7.0-BETA1. I followed the instructions from the handbook and what I > > found on google here... > > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html > > . The keyboard does not work at all, but I am able to pull a > > configuration from bthidcontrol. The mouse buttons work, but I can't > > move the cursor. These issues occur in both on the console and in X. I > > included log messages and config files below. Any help would be greatly > > appreciated. > > 1) make sure you have paired bluetooth keyboard/mouse and your pc > > 2) what bluetooth keyboard and mouse are you using? > > 3) for keyboard, please make sure you have both vkbd(4) and kbdmux(4) > loaded. also make sure kbdmux(4) keyboard is the default keyboard. > > 4) are there any messages from bthidd(8) in /var/log/messages? > > 5) try to run bthidd(8) in foreground to see if it prints anything strange > > > 11:58 emillbrandt@slate:/home/emillbrandt# uname -a > > FreeBSD slate.coldhaus.com 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 29 > > 23:40:03 EDT 2007 > > [hidden email]:/usr/obj/usr/src/sys/SLATE i386 > > ok > > > from dmesg > > Nov 4 10:57:38 slate kernel: ubt0: <vendor 0x0a12 product 0x0001, class > > 224/1, rev 2.00/19.58, addr 2> on uhub3 > > Nov 4 10:57:38 slate kernel: ubt0: Interface 0 endpoints: > > interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > > Nov 4 10:57:38 slate kernel: ubt0: Interface 1 (alt.config 5) > > endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, > > buffer size=294 > > Nov 4 10:57:38 slate kernel: WARNING: attempt to > > net_add_domain(bluetooth) after domainfinalize() > > Nov 4 10:57:38 slate kernel: WARNING: attempt to > > net_add_domain(netgraph) after domainfinalize() > > Nov 4 11:51:27 slate bthidd[1453]: Opening outbound session for > > 00:1b:63:fc:6c:2c (new_device=1, reconnect_initiate=1) > > Nov 4 11:51:57 slate bthidd[1453]: Could not connect to > > 00:1b:63:fc:6c:2c. Host is down (64) > > Nov 4 11:52:27 slate kernel: kbd3 at vkbd0 > > this looks mostly ok. please make sure you have bluetooth connection > between your keyboard and your pc > > > 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a keyboard query > > device { > > bdaddr 00:1b:63:fc:6c:2c; > > control_psm 0x11; > > interrupt_psm 0x13; > > reconnect_initiate true; > > battery_power false; > > normally_connectable true; > > hid_descriptor { > > 0x05 0x01 0x09 0x06 0xa1 0x01 0x85 0x01 > > 0x05 0x07 0x19 0xe0 0x29 0xe7 0x15 0x00 > > 0x25 0x01 0x75 0x01 0x95 0x08 0x81 0x02 > > 0x75 0x08 0x95 0x01 0x81 0x01 0x75 0x01 > > 0x95 0x05 0x05 0x08 0x19 0x01 0x29 0x05 > > 0x91 0x02 0x75 0x03 0x95 0x01 0x91 0x01 > > 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff > > 0x00 0x05 0x07 0x19 0x00 0x2a 0xff 0x00 > > 0x81 0x00 0xc0 0x05 0x0c 0x09 0x01 0xa1 > > 0x01 0x85 0x47 0x05 0x01 0x09 0x06 0xa1 > > 0x02 0x05 0x06 0x09 0x20 0x15 0x00 0x26 > > 0xff 0x00 0x75 0x08 0x95 0x01 0x81 0x02 > > 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 > > 0x85 0x11 0x15 0x00 0x25 0x01 0x75 0x01 > > 0x95 0x03 0x81 0x01 0x75 0x01 0x95 0x01 > > 0x05 0x0c 0x09 0xb8 0x81 0x02 0x06 0xff > > 0x00 0x09 0x03 0x81 0x02 0x75 0x01 0x95 > > 0x03 0x81 0x01 0x05 0x0c 0x85 0x12 0x15 > > 0x00 0x25 0x01 0x75 0x01 0x95 0x01 0x09 > > 0xcd 0x81 0x02 0x09 0xb3 0x81 0x02 0x09 > > 0xb4 0x81 0x02 0x09 0xb5 0x81 0x02 0x09 > > 0xb6 0x81 0x02 0x81 0x01 0x81 0x01 0x81 > > 0x01 0x85 0x13 0x15 0x00 0x25 0x01 0x75 > > 0x01 0x95 0x01 0x06 0x01 0xff 0x09 0x0a > > 0x81 0x02 0x75 0x01 0x95 0x07 0x81 0x01 > > 0xc0 > > }; > > } > > this looks fine to me > > > 10:59 emillbrandt@slate:/home/emillbrandt# bthidcontrol -a mouse query > > device { > > bdaddr 00:12:5a:57:a6:9a; > > control_psm 0x11; > > interrupt_psm 0x13; > > reconnect_initiate true; > > battery_power true; > > normally_connectable false; > > hid_descriptor { > > 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 > > 0x09 0x02 0x85 0x14 0x06 0x00 0xff 0x0a > > 0x12 0xfe 0x95 0x01 0x75 0x02 0x15 0x00 > > 0x25 0x03 0x81 0x02 0x0a 0x11 0xfe 0x75 > > 0x01 0x25 0x01 0x81 0x02 0x95 0x05 0x81 > > 0x01 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 > > 0x05 0x01 0x09 0x02 0x85 0x11 0x09 0x01 > > 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x04 > > 0x95 0x04 0x75 0x01 0x25 0x01 0x81 0x02 > > 0x75 0x04 0x95 0x01 0x81 0x01 0x05 0x01 > > 0x09 0x30 0x09 0x31 0x09 0x38 0x00 0x00 > > 0x00 0x00 0x00 0x00 0x25 0x7f 0x81 0x06 > > 0x95 0x01 0x81 0x01 0xc0 0xc0 0x05 0x0c > > 0x09 0x01 0xa1 0x01 0x85 0x19 0x06 0x00 > > 0xff 0x1a 0x18 0xff 0x2a 0x22 0xff 0x95 > > 0x0b 0x75 0x08 0x15 0x00 0x26 0xff 0x00 > > 0xb1 0x02 0x0a 0x23 0xff 0x95 0x01 0x75 > > 0x01 0x25 0x01 0xb1 0x02 0x75 0x07 0xb1 > > 0x01 0xc0 > > }; > > } > > I added both of these to bthidd.conf > > this looks fine too. > > > from hcsecd.conf > > device { > > bdaddr 00:1b:63:fc:6c:2c; > > name "Apple Wireless Keyboard"; > > key nokey; > > pin "5625264"; > > } > > > > device { > > bdaddr 00:12:5a:57:a6:9a; > > name "Microsoft Bluetooth Notebook Mouse 5000"; > > key nokey; > > pin "0000"; > > } > > looks fine > > > DING! emillbrandt@slate:/home/emillbrandt# l2ping -a keyboard > > 0 bytes from keyboard seq_no=0 time=1905.898 ms result=0 > > 0 bytes from keyboard seq_no=1 time=38.023 ms result=0 > > 0 bytes from keyboard seq_no=2 time=13.141 ms result=0 > > looks normal (some bluetooth devices will always return 0 bytes in > l2cap echo response) > > > 11:45 emillbrandt@slate:/home/emillbrandt# l2ping -a mouse > > 0 bytes from mouse seq_no=0 time=1428.790 ms result=0 > > 0 bytes from mouse seq_no=1 time=47.168 ms result=0 > > 0 bytes from mouse seq_no=2 time=53.263 ms result=0 > > looks normal (some bluetooth devices will always return 0 bytes in > l2cap echo response) > > > rc.conf > > hcsecd_enable="YES" > > bthidd_enable="YES" > > looks ok > > btw, i have apple bluetooth keyboard here, so i will try to reproduce > the problem. > > thanks, > max > [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
Maksim Yevmenkin wrote: > Eric, > > i just tried apple keyboard with > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > 20:40:41 PDT 2007 > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > and it works just fine. granted, it almost a couple month old system, > but bthidd(8) code has not changed in a while, so it still should > work. i'm cvsup'ing RELENG_7 and will build it later. > > thanks, > max > xp, and put that passkey directly into hcsecd.conf. Is there a step that I am missing? _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Maksim Yevmenkin-2
Maksim Yevmenkin wrote:
> Eric, > > i just tried apple keyboard with > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > 20:40:41 PDT 2007 > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > and it works just fine. granted, it almost a couple month old system, > but bthidd(8) code has not changed in a while, so it still should > work. i'm cvsup'ing RELENG_7 and will build it later. > > thanks, > max > > A1255. Apparently there was an older model of the same name. The mouse is a "Microsoft Bluetooth Notebook Mouse 5000". Neither of these need any special windows drivers. Does each new device need to be supported in bthidd? _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Eric Millbrandt
On 11/4/07, Eric Millbrandt <[hidden email]> wrote:
> > > Maksim Yevmenkin wrote: > > Eric, > > > > i just tried apple keyboard with > > > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > > 20:40:41 PDT 2007 > > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > > > and it works just fine. granted, it almost a couple month old system, > > but bthidd(8) code has not changed in a while, so it still should > > work. i'm cvsup'ing RELENG_7 and will build it later. > > > > thanks, > > max > > > How did you pair the apple keyboard? I paired it initially with windows > xp, and put that passkey directly into hcsecd.conf. Is there a step > that I am missing? first of all, what you did is not going to work. pin code only used once - when pairing. after that link key is generated and stored. unless you store link key into the bluetooth device itself, each os will store link key someplace. the point is that this link key will only be known to the os that initiated the pairing. so you need to re-pair keyboard and device (or rather os). apple keyboard is tricky because it does not give any visual of when user should enter pin code. so, what i do is 1) make sure hcsecd is running and configured with pin for your keyboard 2) if bthidd is running - stop it 3) run as root "bthidcontrol -a keyboard_bd_addr forget" 4) start bthidd - this should cause bthidd to initiate connection to your keyboard. the later in turn will make keyboard to request the key. 5) because freebsd does not know about the link key you have created under windows xp, freebsd will reject that link request and will request pin code 6) now you should type pin code on the bluetooth keyboard and press enter so, to summarize, after you start bthidd (i.e. after step 4 above) wait a couple of seconds then try to type pin code and hit enter. if you dual boot your system and use the same bluetooth device you will need to re-pair your keyboard every time you boot to another os. (if) you can get a link key from win xp registry (or elsewhere) you can put the same link key into hcsecd.conf and then you will not need to re-pair. thanks, max _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Eric Millbrandt
On 11/4/07, Eric Millbrandt <[hidden email]> wrote:
> Maksim Yevmenkin wrote: > > Eric, > > > > i just tried apple keyboard with > > > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > > 20:40:41 PDT 2007 > > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > > > and it works just fine. granted, it almost a couple month old system, > > but bthidd(8) code has not changed in a while, so it still should > > work. i'm cvsup'ing RELENG_7 and will build it later. > > > > thanks, > > max > > > > > Actually the keyboard is one of the new apple wireless keyboards, model > A1255. Apparently there was an older model of the same name. i have older "thick white" apple bluetooth keyboard. i do not think your keyboard would be that different > The mouse is a "Microsoft Bluetooth Notebook Mouse 5000". Neither of > these need any special windows drivers. Does each new device need to be > supported in bthidd? bthidd should support any bluetooth keyboard and/or mouse. it may not support, for example, extra keys or buttons, but generic set of keys/buttons should work. thanks, max _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Maksim Yevmenkin-2
Maksim Yevmenkin wrote:
> >> 1) make sure you have paired bluetooth keyboard/mouse and your pc >> >> >> Oops, I just figured out how to pair the keyboard. You need to hold the power button down for three seconds and then enter the pin. The keyboard works great. Why would the mouse buttons work but not cursor movement? Thanks for the help! Eric Millbrandt _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On 11/4/07, Eric Millbrandt <[hidden email]> wrote:
> Maksim Yevmenkin wrote: > > > >> 1) make sure you have paired bluetooth keyboard/mouse and your pc > >> > >> > >> > Oops, I just figured out how to pair the keyboard. You need to hold the > power button down for three seconds and then enter the pin. The > keyboard works great. ok > Why would the mouse buttons work but not cursor movement? what bluetooth mouse do you have exactly? you tell me that buttons work, so i assume, bluetooth communication channel works. i dumped the hid descriptor that you have provided in your previous email, and got === Collection page=Consumer usage=Consumer_Control Input id=20 size=2 count=1 page=Generic_Desktop usage=Mouse Variable, logical range 0..3 Input id=20 size=1 count=1 page=Microsoft usage=0xfe11 Variable, logical range 0..1 End collection Collection page=Generic_Desktop usage=Mouse Collection page=Generic_Desktop usage=Pointer Input id=17 size=1 count=1 page=Button usage=Button_1 Variable, logical range 0..1 Input id=17 size=1 count=1 page=Button usage=Button_2 Variable, logical range 0..1 Input id=17 size=1 count=1 page=Button usage=Button_3 Variable, logical range 0..1 Input id=17 size=1 count=1 page=Button usage=Button_4 Variable, logical range 0..1 Input id=17 size=4 count=1 page=Generic_Desktop usage=X Variable Relative, logical range 0..127 End collection End collection Collection page=Consumer usage=Consumer_Control Feature id=25 size=8 count=1 page=Microsoft usage=0xff18 Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff19 Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1a Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1b Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1c Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1d Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1e Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff1f Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff20 Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff21 Variable, logical range 0..255 Feature id=25 size=8 count=1 page=Microsoft usage=0xff22 Variable, logical range 0..255 Feature id=25 size=1 count=1 page=Microsoft usage=0xff23 Variable, logical range 0..1 End collection === one thing that is very strange is that i'm not seeing input report for the Y axis. this could be the problem with usb hid descriptor parsing, or (less likely), perhaps, this mouse uses non-standard hid report. i will need to decode it manually to see where the problem is. thanks, max _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On Sun, 4 Nov 2007 17:03:45 -0700, Maksim Yevmenkin wrote
> > > Why would the mouse buttons work but not cursor movement? > > what bluetooth mouse do you have exactly? Here is the product page for the mouse I have. http://www.microsoft.com/hardware/mouseandkeyboard/ProductDetails.aspx?pid=099&active_tab=systemRequirements Thanks Eric Millbrandt _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
In reply to this post by Maksim Yevmenkin-2
On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > On 11/4/07, Eric Millbrandt <[hidden email]> wrote: > > > > > > Maksim Yevmenkin wrote: > > > Eric, > > > > > > i just tried apple keyboard with > > > > > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > > > 20:40:41 PDT 2007 > > > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > > > > > and it works just fine. granted, it almost a couple month old system, > > > but bthidd(8) code has not changed in a while, so it still should > > > work. i'm cvsup'ing RELENG_7 and will build it later. > > > > > > thanks, > > > max > > > > > How did you pair the apple keyboard? I paired it initially with windows > > xp, and put that passkey directly into hcsecd.conf. Is there a step > > that I am missing? > > first of all, what you did is not going to work. pin code only used > once - when pairing. after that link key is generated and stored. > unless you store link key into the bluetooth device itself, each os > will store link key someplace. the point is that this link key will > only be known to the os that initiated the pairing. > > so you need to re-pair keyboard and device (or rather os). apple > keyboard is tricky because it does not give any visual of when user > should enter pin code. so, what i do is > > 1) make sure hcsecd is running and configured with pin for your keyboard > > 2) if bthidd is running - stop it > > 3) run as root "bthidcontrol -a keyboard_bd_addr forget" > > 4) start bthidd - this should cause bthidd to initiate connection to > your keyboard. the later in turn will make keyboard to request the > key. > > 5) because freebsd does not know about the link key you have created > under windows xp, freebsd will reject that link request and will > request pin code some such thing after pairing my keyboard with the Windows incarnation of my laptop, so FreeBSD will generate new link key. However, now I do not see such file in /var/db. Was that thing of the past, or are there some conditions to be met for it to exist? And if it still is around, does it need to be removed or would "bthidcontrol -a keyboard_bd_addr forget" be sufficient? -- Alexandre "Sunny" Kovalenko _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On 11/4/07, Alexandre Sunny Kovalenko <[hidden email]> wrote:
> > On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > > On 11/4/07, Eric Millbrandt <[hidden email]> wrote: > > > > > > > > > Maksim Yevmenkin wrote: > > > > Eric, > > > > > > > > i just tried apple keyboard with > > > > > > > > FreeBSD ant.private.org 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Wed Sep 12 > > > > 20:40:41 PDT 2007 > > > > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > > > > > > > > and it works just fine. granted, it almost a couple month old system, > > > > but bthidd(8) code has not changed in a while, so it still should > > > > work. i'm cvsup'ing RELENG_7 and will build it later. > > > > > > > > thanks, > > > > max > > > > > > > How did you pair the apple keyboard? I paired it initially with windows > > > xp, and put that passkey directly into hcsecd.conf. Is there a step > > > that I am missing? > > > > first of all, what you did is not going to work. pin code only used > > once - when pairing. after that link key is generated and stored. > > unless you store link key into the bluetooth device itself, each os > > will store link key someplace. the point is that this link key will > > only be known to the os that initiated the pairing. > > > > so you need to re-pair keyboard and device (or rather os). apple > > keyboard is tricky because it does not give any visual of when user > > should enter pin code. so, what i do is > > > > 1) make sure hcsecd is running and configured with pin for your keyboard > > > > 2) if bthidd is running - stop it > > > > 3) run as root "bthidcontrol -a keyboard_bd_addr forget" > > > > 4) start bthidd - this should cause bthidd to initiate connection to > > your keyboard. the later in turn will make keyboard to request the > > key. > > > > 5) because freebsd does not know about the link key you have created > > under windows xp, freebsd will reject that link request and will > > request pin code > I have vague recollection that I had to remove /var/db/hcsecd.keys or > some such thing after pairing my keyboard with the Windows incarnation > of my laptop, so FreeBSD will generate new link key. However, now I do > not see such file in /var/db. Was that thing of the past, or are there > some conditions to be met for it to exist? And if it still is around, > does it need to be removed or would "bthidcontrol -a keyboard_bd_addr > forget" be sufficient? bthidd(8) does not manage link keys, hcsecd(8) does that. bthidcontrol(8)'s 'forget' command will remove device from the 'known' list. this would force bthidd(8) to initiate connection to the device on next start. it may or may not be enough to cause re-pair. if you really want to remove link key for a device, you should remove it from /var/db/hcsecd.keys file. there is no utility to do that because this is not something that one would normally do. the whole dual-boot + re-using the same device is a big mess. if you really want to do it then you should either - program link keys into the device itself or - make sure both os'es use the same link key thanks, max > > -- > Alexandre "Sunny" Kovalenko > > _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
RE: bluetooth mouse/keyboard blues
|
In reply to this post by Eric Millbrandt
> program link keys into the device itself Do you mean using write-stored-link-keys command to store key in controller? I never tried that, will it persist? _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On 11/5/07, Iain Hibbert <[hidden email]> wrote:
> > > program link keys into the device itself > > Do you mean using write-stored-link-keys command to store key in controller? I never tried that, will it persist? yes, Write_Stored_Link_Key command. and, yes, programmed keys should persists. you can program a few keys, however the exact number might be device specific. for example, csr bluecore chips have 16 ps keys to store bd_addr + link key pairs. thanks, max _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
In reply to this post by Maksim Yevmenkin-2
On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote:
> if you dual boot your system and use the same bluetooth device you > will need to re-pair your keyboard every time you boot to another os. > (if) you can get a link key from win xp registry (or elsewhere) you > can put the same link key into hcsecd.conf and then you will not need > to re-pair. Hmm, strange, I have bluetooth mouse and it works under both Windows and FreeBSD on my noteboot without re-pairing every boot to other OS. I've not done anything special about it, just pair it once under FreeBSD, then once under Windows. What's the difference ? "Magically" it have generated same key for both OSes ? (my mouse is Logitech MX900) -- Vladimir B. Grebenschikov [hidden email] _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On Tue, 2007-11-06 at 02:03 +0300, Vladimir Grebenschikov wrote: > On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > > > if you dual boot your system and use the same bluetooth device you > > will need to re-pair your keyboard every time you boot to another os. > > (if) you can get a link key from win xp registry (or elsewhere) you > > can put the same link key into hcsecd.conf and then you will not need > > to re-pair. > > Hmm, strange, I have bluetooth mouse and it works under both Windows and > FreeBSD on my noteboot without re-pairing every boot to other OS. > > I've not done anything special about it, just pair it once under > FreeBSD, then once under Windows. > > What's the difference ? "Magically" it have generated same key for both > OSes ? > > (my mouse is Logitech MX900) > as opposed to the "combination" key) with everyone, and not generate it for every repairing. Simplest way to verify that is to store backup copy of var/db/hcsecd.keys, remove mouse key (or remove the whole file, if the mouse is the only bluetooth device you are using), reboot, repair the mouse and see if new key is any different then the old one. OT: @vova -- if you are still having problems with Evolution, you can try my patch on the Gnome Bugzilla. -- Alexandre "Sunny" Kovalenko _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
In reply to this post by Vladimir Grebenschikov-2
Dne Tue, 06 Nov 2007 02:03:15 +0300
Vladimir Grebenschikov <[hidden email]> napsal(a): > On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > > > if you dual boot your system and use the same bluetooth device you > > will need to re-pair your keyboard every time you boot to another > > os. (if) you can get a link key from win xp registry (or elsewhere) > > you can put the same link key into hcsecd.conf and then you will > > not need to re-pair. > > Hmm, strange, I have bluetooth mouse and it works under both Windows > and FreeBSD on my noteboot without re-pairing every boot to other OS. > > I've not done anything special about it, just pair it once under > FreeBSD, then once under Windows. > > What's the difference ? "Magically" it have generated same key for > both OSes ? > > (my mouse is Logitech MX900) > I got Ligitech diNovo bluetooth keyboard and mouse which works just fine on 6.3 diskless X-terminal. The Logitech USB bluetooth receiver creates the links to the keybord/mouse and on the USB side just emulates USB keybord/mouse ukbd0/ums0. The bluetooth OS subsystem is not even running (no hcsecd), but you can switch it on if you want. So there is no pairing from the hcsecd point of view. Cheers, -vlado _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
On Wed, 2007-11-07 at 07:06 +0100, Vladimir Botka wrote: > Dne Tue, 06 Nov 2007 02:03:15 +0300 > Vladimir Grebenschikov <[hidden email]> napsal(a): > > > On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > > > > > if you dual boot your system and use the same bluetooth device you > > > will need to re-pair your keyboard every time you boot to another > > > os. (if) you can get a link key from win xp registry (or elsewhere) > > > you can put the same link key into hcsecd.conf and then you will > > > not need to re-pair. > > > > Hmm, strange, I have bluetooth mouse and it works under both Windows > > and FreeBSD on my noteboot without re-pairing every boot to other OS. > > > > I've not done anything special about it, just pair it once under > > FreeBSD, then once under Windows. > > > > What's the difference ? "Magically" it have generated same key for > > both OSes ? > > > > (my mouse is Logitech MX900) > > > > I got Ligitech diNovo bluetooth keyboard and mouse which works just > fine on 6.3 diskless X-terminal. The Logitech USB bluetooth receiver > creates the links to the keybord/mouse and on the USB side just > emulates USB keybord/mouse ukbd0/ums0. The bluetooth OS subsystem is not > even running (no hcsecd), but you can switch it on if you want. So > there is no pairing from the hcsecd point of view. In my case it is "true" bluetooth connection, with appropriate entries in bthidd.conf and in hcsecd.conf: device { bdaddr 00:07:61:17:9b:27; name "mouse"; key nokey; pin "0000"; } > Cheers, > -vlado -- Vladimir B. Grebenschikov [hidden email] _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Alexandre "Sunny" Kovalenko
On Tue, 2007-11-06 at 19:19 -0500, Alexandre "Sunny" Kovalenko wrote: > On Tue, 2007-11-06 at 02:03 +0300, Vladimir Grebenschikov wrote: > > On Sun, 2007-11-04 at 14:47 -0700, Maksim Yevmenkin wrote: > > > > > if you dual boot your system and use the same bluetooth device you > > > will need to re-pair your keyboard every time you boot to another os. > > > (if) you can get a link key from win xp registry (or elsewhere) you > > > can put the same link key into hcsecd.conf and then you will not need > > > to re-pair. > > > > Hmm, strange, I have bluetooth mouse and it works under both Windows and > > FreeBSD on my noteboot without re-pairing every boot to other OS. > > > > I've not done anything special about it, just pair it once under > > FreeBSD, then once under Windows. > > > > What's the difference ? "Magically" it have generated same key for both > > OSes ? > > > > (my mouse is Logitech MX900) > > > I think spec allows cheaper devices to use single link key ("unit" key, > as opposed to the "combination" key) with everyone, and not generate it > for every repairing. > > Simplest way to verify that is to store backup copy of > var/db/hcsecd.keys, remove mouse key (or remove the whole file, if the > mouse is the only bluetooth device you are using), reboot, repair the > mouse and see if new key is any different then the old one. Hm, my hcsecd.keys has no entry for mouse, so looks like it works without key for both Windows and FreeBSD. > OT: @vova -- if you are still having problems with Evolution, you can > try my patch on the Gnome Bugzilla. I'll try your patch, thanks. -- Vladimir B. Grebenschikov [hidden email] _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
Re: bluetooth mouse/keyboard blues
|
|
In reply to this post by Maksim Yevmenkin-2
Maksim Yevmenkin wrote:
> On 11/4/07, Eric Millbrandt <[hidden email]> wrote: > >> Maksim Yevmenkin wrote: >> >>>> 1) make sure you have paired bluetooth keyboard/mouse and your pc >>>> >>>> >>>> >>>> >> Oops, I just figured out how to pair the keyboard. You need to hold the >> power button down for three seconds and then enter the pin. The >> keyboard works great. >> > > ok > > >> Why would the mouse buttons work but not cursor movement? >> > > what bluetooth mouse do you have exactly? > > you tell me that buttons work, so i assume, bluetooth communication > channel works. > > i dumped the hid descriptor that you have provided in your previous > email, and got > > > === > > Collection page=Consumer usage=Consumer_Control > Input id=20 size=2 count=1 page=Generic_Desktop usage=Mouse > Variable, logical range 0..3 > Input id=20 size=1 count=1 page=Microsoft usage=0xfe11 Variable, > logical range 0..1 > End collection > Collection page=Generic_Desktop usage=Mouse > Collection page=Generic_Desktop usage=Pointer > Input id=17 size=1 count=1 page=Button usage=Button_1 Variable, > logical range 0..1 > Input id=17 size=1 count=1 page=Button usage=Button_2 Variable, > logical range 0..1 > Input id=17 size=1 count=1 page=Button usage=Button_3 Variable, > logical range 0..1 > Input id=17 size=1 count=1 page=Button usage=Button_4 Variable, > logical range 0..1 > Input id=17 size=4 count=1 page=Generic_Desktop usage=X Variable > Relative, logical range 0..127 > End collection > End collection > Collection page=Consumer usage=Consumer_Control > Feature id=25 size=8 count=1 page=Microsoft usage=0xff18 Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff19 Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1a Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1b Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1c Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1d Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1e Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff1f Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff20 Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff21 Variable, > logical range 0..255 > Feature id=25 size=8 count=1 page=Microsoft usage=0xff22 Variable, > logical range 0..255 > Feature id=25 size=1 count=1 page=Microsoft usage=0xff23 Variable, > logical range 0..1 > End collection > > === > > one thing that is very strange is that i'm not seeing input report for > the Y axis. this could be the problem with usb hid descriptor parsing, > or (less likely), perhaps, this mouse uses non-standard hid report. i > will need to decode it manually to see where the problem is. > > thanks, > max > > > able to use sdptool, from the bluez package, I think..., to get a working hid descriptor. The mouse reports itself as a 'Microsoft Bluetooth Notebook Mouse 5000' 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0x85 0x14 0x06 0x00 0xff 0x0a 0x12 0xfe 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x03 0x81 0x02 0x0a 0x11 0xfe 0x75 0x01 0x25 0x01 0x81 0x02 0x95 0x05 0x81 0x01 0xc0 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0x85 0x11 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x04 0x95 0x04 0x75 0x01 0x25 0x01 0x81 0x02 0x75 0x04 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x95 0x03 0x75 0x08 0x15 0x81 0x25 0x7f 0x81 0x06 0x95 0x01 0x81 0x01 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x19 0x06 0x00 0xff 0x1a 0x18 0xff 0x2a 0x22 0xff 0x95 0x0b 0x75 0x08 0x15 0x00 0x26 0xff 0x00 0xb1 0x02 0x0a 0x23 0xff 0x95 0x01 0x75 0x01 0x25 0x01 0xb1 0x02 0x75 0x07 0xb1 0x01 0xc0 0x00 Now I get cursor movement and all the buttons and mouse wheel work. Thanks for the help. Eric _______________________________________________ [hidden email] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[hidden email]" |
«
Return to freebsd-bluetooth
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |